Known Participant

Open for Voting

Prefer relative paths after project transfer

Forum|Forum|28 days ago
August 13, 2026
15 replies
101 views

After transferring a project and its media to another disk, I noticed that the absolute path is still used.

The original path in that case is a dying harddrive but it still is connected as I need it.

The thing is: why is the original path even used in that situation? The structure of the project didn’t change, only the drive did. Now I have to go through the process of offline all the media and relink it manually.

There should be an easier way to do that and from my perspective, I would prefer it, if relative paths were the default, not absolute ones.

Stan Jones

Community Expert

@Warren Heaton,

Thanks for the link to “Relink media in Premiere”; it explains the process PR is using, and I understand it better.

@athletic_fact6385,

I think the “Automated search logic” phase is the one that might do what you are looking for. I wonder if its limitation is that “Pass 2” only “Moves up one level to search the entire containing folder (including adjacent folders).”

That one works for me if my media files are at the same root level on the drive. I.e. project is in F:\Project folder and media is in F:\Media folder. I am, as before, renaming the original project and media folders.

What is your folder structure that is not working? (I’m assuming that they are on one drive?)

How would you modify the automated search logic so it would find your files?

Stan

A

athletic_fact6385Author

Known Participant

I don’t really understand the question.

There shouldn’t be the need to rename anything if relative paths would be used.
In my example, relative from the project file means 2 folders up, change folder, 3 folders down. That’s where my media is located before the transfer and after the transfer. Relatively the position stays the same but Premiere doesn’t choose the relative path, instead it keeps the absolute one.

I’ve already written how the search logic could be changed and what makes more sense from my perspective, so that such situations (linking to the wrong drive) wouldn’t happen:

I see two ways how that could be done:
Either Premiere checks the projects location on each start and asks if paths of media should be updated accordingly (if relative files exist)

Or there could be a command for that, which triggers that relative relinking manually without the need to offline all media manually first (a bit comparable with the command that combines redundant media in the project. Premiere doesn’t do that automatically, you have to trigger that command yourself)
If just some media is relative and some missing, there could be a prompt like “found x of y relative files. y files are at not updated”

Of course if media was located across different drives, that would be another case. In that case, there would need to be an absolute link for the media that’s not on the same dive as the project, I guess.
But as we are not talking about media that is on another drive but on the same drive as the project, relative linking should be applied first.

The two pass logic is only triggered if the stored path can’t be found as far as I can tell. But that isn’t happen here as the original path still is accessible, hence why I did a feature request for relative paths being used instead or a manual trigger to achieve that to get a quicker result than with manual relinking (which is an option but a slow one as I first need to select all the files in the project window, so I first need to unfold all the folders in my project which is taking long time and is tedious… even an “unlink all media” button would be better).

Stan Jones

Community Expert

@athletic_fact6385,

> I don’t really understand the question.
Thanks for the detailed information and continuing your reasoning. You answered my questions!

> In my example, relative from the project file means 2 folders up, change folder, 3 folders down.
I did a few more tests, and this is what I now believe. The renaming serves as the "media is missing" trigger. Yes, it could be automated, but that is the workaround for now. Once triggered, PR automatically (i.e. it does not open the locate dialogue) finds media files as long as they are on the same drive AND the project file is not more than one subdirectory below root.

Warren's linked helpx file, "Relink media in Premiere," last updated 4/15/26, indicates that the intention is to support what you want. "...Adobe Premiere automatically finds and reconnects offline media ... This process supports common workflows like moving projects between drives,...." BUT, the automatic is triggered by "When the media goes offline, ...." For moving the project file to a new location, the feature you want is for that trigger to be automatic.

I suspect that the developers provide for only one directory level up for the project to avoid some problem. And the helpx page does alert us to the limitation: "Pass 2: Moves up one level to search the entire containing folder (including adjacent folders)." The current relative path allows the media to be found by simply going to the root of the new drive. And yes, it is relative to the drive, not to the project.

If the old media is not found (i.e. renaming) AND the project is in a folder 2 or more levels below root, PR opens the "Link media" dialogue. Click Locate, select the new drive, and click Search. It takes a bit, because PR is searching the whole drive. I assume that can be improved, because the PR project has the media path relative to the drive, and could automatically pick the path. You can improve the speed currently by picking the drive and at least the first media path.

> "... how the search logic could be changed.... I see two ways how that could be done: Either Premiere checks the projects location on each start and asks if paths of media should be updated accordingly (if relative files exist)...."
I think the info exists in the project file now for that logic to be performed. If “current project file path” does not equal the last one, look for media files. But I think it would need a prompt, since the old media files (without renaming) would be available, and some users would NOT want the media files to be relocated. And a prompt "project file location has changed, do you want to relocate media files?" gets to your second method, a command that triggers that relative relinking manually.

> Of course if media was located across different drives, that would be another case. In that case, there would need to be an absolute link for the media that’s not on the same dive as the project, I guess.
The current relative path is to drive letter, so a simple prompt would handle that at the same time.

For all of my projects, the project file is located in a directory one level below root, so I did not see the problem you are seeing. And it lowers the priority of the feature request you are advocating. I did upvote since I want to see robust options for relocating projects and media.

My top request in this area is for more robust project manager functions.

Stan

Stan Jones

Community Expert

@athletic_fact6385,

I understand. What would it take to further automate that process? PR currently only gets to “files missing” and looks for instruction in the relinking dialogue box process. Add a “project and media” moved button to start an upstream and downstream search process? They made some changes in this recently, but I was not paying close attention.

Stan

A

athletic_fact6385Author

Known Participant

I see two ways how that could be done:
Either Premiere checks the projects location on each start and asks if paths of media should be updated accordingly (if relative files exist)

Or there could be a command for that, which triggers that relative relinking manually without the need to offline all media manually first (a bit comparable with the command that combines redundant media in the project. Premiere doesn’t do that automatically, you have to trigger that command yourself)
If just some media is relative and some missing, there could be a prompt like “found x of y relative files. y files are at not updated”

Stan Jones

Community Expert

@athletic_fact6385,

The project path is absolute, but the media file paths are relative.

Keep the copy (particularly the media) you made on the new drive location.

Open the project on the original drive. Do a save as to the new drive location. If you want to keep the original name, delete or rename the copied project file first.

Rename the original folder so you know it is working. (It actually won’t matter unless you open the project from the recent files list.) Open Project, but navigate to the new location. The project opens without relinking the media.

Last exported locations etc are absolute paths, so first time for several things may require relocating.

I did not try moving cached files. I’d just redo those if this is a one time change.

Does that work for you?

Stan

A

athletic_fact6385Author

Known Participant

That doesn’t sound like relative paths but relative paths after jumping through hoops to be honest.
Relative should always take the current location and then look relative to that location (so for example two folders up, three folders down).

But I tried it anyway:

If I understand you correctly, I copy the media from the old (D drive) to the new location (G drive).
Then I open the project in the original location (D drive), media still is linked to D, and save it to the new location within Premiere (after saving it there, the media still is linked to the original location D).
I close Premiere, open the project on the new location (G drive, relatively it’s at the same spot to the copied media).
I don’t have to rename the original folder, because I check the metadata for the location of the media and use the open location command… still the old location (D drive).

Didn’t work on my end.

Stan Jones

Community Expert

@athletic_fact6385,

My method works for media files that are in the same directory/subdirectory paths as the project. But I erred in assuming that is what you have.

The media files have a relative path, but it includes the drive letter, I assume since it is not in the same directory as the original project. And this is, of course, a very common usage.

For my second sample, I put the media files in one directory (separate from the project directory). Renaming the original folder forces the media offline in the new project. So I was prompted at opening the project to relink, and it took only linking one file to get all the files. That could, of course, be more complicated if there are several directories or drives at issue. Some kind of relinking is almost certain to be required.

Stan

Peru Bob

Community Expert

Can you temporarily disconnect the original hard drive and then relink or is the failing drive the OS drive?

A

athletic_fact6385Author

Known Participant

I could but as it is an internal drive I’d rather not. Because that would be even more of a hassle than to unlink and relink the media.
Same story with network drives. I wouldn’t like to disconnect them just for the purpose of relinking media in a Premiere project.

I know, that would be a workaround (manual relinking also is an option that exists), but that feature requests purpose is to not longer be dependent on such workarounds. The use of relative paths would save some steps for such project transfers (same story when I collect media to send it off to another editor or the customer and want to test the collected project for issues… the media still links to the original drive)

Warren Heaton

Community Expert

Following up with @Peru Bob ‘s suggestion, it should work to temporarily eject the dying drive, open the project, allow Premiere to relink (or do so manually if needed) and then save the project. Then mount the dying drive.

If you’re worried about the drive not mounting again, you could also try changing the drive letters in Disk Management. Change the dying drive to a higher letter and change the new drive to the letter that that dying drive had.

Here’s information on how Premiere automatically finds and reconnects offline media using historical paths, search logic, and cross-platform matching.
https://helpx.adobe.com/premiere/desktop/organize-media/file-organization/relink-offline-media-automatically.html

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.