Participant

Question

Proxies "relink others automatically" stopped working

Forum|Forum|1 year ago
March 2, 2025
36 replies
838 views

Previously this function was working for me when trying to batch relink proxies. Now, it has suddenly stopped and Premiere is only relinking one proxy at a time, despite all proxies being in one folder and all proxies having corresponding names to original footage. "File Name" under Match File Properties is clicked as well as "Relink others automatically" and "Use Media Browser to attach files." Can't understand why this started happening out of nowhere and can only assume it's a bug?

B

BellaTiamo

Participant

I found a fix!

W

workahollek

Participant

Has anyone tried matching by Media Start only?

I unchecked all other options under “Match File Properties,” selected only Media Start, and left “Relink Others Automatically” enabled. It took a little longer, but Premiere eventually found and attached all of my proxies automatically. This worked for me in Premiere 26.3.2.

O

OMI Media House

Participating Frequently

yeah it works - “kind of” - if you have only few shots to attach it’s ok, but if you have thousands - it’s extremely slow. also if you have multicamera setup with the same timecode or footage that starts tc from 0:00:00:00 (i.e. high frame rate shots) - it will make more mess.

L

LivoTV

Participant

How has this not been fixed? I have a huge project working across multiple locations and shoots and I need to batch relink proxies. How has there not been a fix yet??

O

OMI Media House

Participating Frequently

Hey,

I’m struggling with this bug for over 3 months in a huge project. Because of no available workarounds I did manage to create the script with chatgpt - you may give it a try. I was able to link more than 5000 proxies with it already - it works both ways - attaching proxies to ful res footage and ful res to proxies (we use plural eyes to sync multicam proxies and than we attach ful res to proxies).

It’s super easy to use - the instructions are in the archive.

https://we.tl/t-HiJb5zC0xrrE5q1Y

I hope it helps.

Best,

Mirek

H

Hamza_Tari8892

Participant

I found the solution! In Match File Properties, you need to check both File Name AND File Extension. If you only check File Name, it won’t work.

Then click Attach, and Premiere Pro will automatically relink the other proxies as well. Hope this helps!

MeKevinB

Known Participant

This is not a solution, unfortunately. I create Prores proxies, so the file extension is NOT the same. Also, my proxy filenames are appended with “_proxy”. This workflow was acceptable prior to version 26.3. The software engineers have broken something.

C

curious_cause2d44

Participant

This is also my exact workflow and it is not working. Was working fine on previous versions (currently running 26.3.2).

S

Sebastian35293480nw5v

Participating Frequently

So here’s something I tried and it seems to be working. I downloaded beta. Created my project there. Attached the proxies there [with no problem], saved, and the opened the project on regural Premiere. If the beta hadn’t ditched the lumetri panel I’d give it a try, but the new color panel seems a bit too much for me right now [this is heavy editing season, no time to learn new tricks]

Sebastian from SFV

S

Sebastian35293480nw5v

Participating Frequently

..so an update.. the workaround I mention in the above comment worked for about a week or so, but suddenly, any project I save on beta cannot be opened on regular premiere because it’s from a “newer version”. And again, this started randomly. I didn’t update anything [nothing to update really]

Sebastian from SFV

Kee10

Participant

This happend to me as well any one find the solution please post

MeKevinB

Known Participant

Weird that Adobe is silent on this one. Do the engineers not use Premiere? This issue slaps you in the face. How can it not be patched by now??

K

Kevin-Monahan

Community Manager

Hi Sebastian,

The product team doesn't really comment much in the Questions forum, but a bug similar to this has been posted in the bug reports forum. Does this sound like your issue? https://adobe.ly/4xcREIm

Let me know. I can move your post there.

Thanks,
Kevin

MeKevinB

Known Participant

Yes. That is exactly the problem but with one caveat. The requirement isn’t for users to rollback to a working version. The requiremement is for Adobe engineers to fix it. Again, if engineers actually used the product, we wouldn’t be talking about it over a week later.

TyroneTHS

Participant

I've been following this issue for over a year now, and unfortunately nothing has been done to fix it.

Adobe, please give this issue the attention it deserves. This is not a minor inconvenience—it is a serious bug that affects professional workflows of every size, from individual creators to large production companies. Working with proxies is a fundamental part of professional video editing, and a bug like this should be treated as a top-priority issue.

This problem has already been reported multiple times. The behavior has been documented, explained in detail, and even demonstrated step by step.

Hi,

I’m experiencing the same issue with attaching proxies in Premiere Pro.

I have around 1500 source clips and a corresponding proxy file for each clip. All proxies are stored in the sub-folders “Proxies”. Premiere allows me to attach the selected proxy manually, but “Relink others automatically” does not attach the remaining files.

Example:

Source: bckstg3028.MP4
Proxy: bckstg3028.mov

I have already tested:

matching by File Name,
matching by Clip Name,
disabling File Extension,
disabling Media Start,
enabling Relink others automatically,
renaming the proxies so that the base names match exactly,
adding the _Proxy suffix,
restarting Premiere and repeating the attachment process.

The files can be attached correctly one by one, so the proxies themselves appear to be valid. The problem is only with automatic batch matching.

Some of the source clips were recorded in 100 fps slow motion and have timecode starting at 00:00:00:00, so matching by Media Start is not reliable. However, every clip has a unique filename, so Premiere should be able to match them using the filename alone.

Manually attaching approximately 1500 proxy files is not a realistic workaround.

Is this a known bug in the current Premiere Pro version? Has anyone found a reliable workaround that does not require attaching every proxy individually?

Premiere Pro version: 26.3
Operating system: Windows 11 Pro

At this point, it is difficult to understand why it has remained unresolved for so long. It is simply unacceptable that such a basic workflow has been broken for more than a year in software that is considered an industry standard.

Because of this bug, professionals are forced to create their own workarounds, write custom scripts, and develop unnecessary solutions just to make a native feature work as intended. We should not have to engineer our own fixes for something that Premiere Pro is supposed to handle automatically.

As described in the original post above, the issue occurs when automatically attaching proxies, especially when the proxy files use a different extension from the original media (for example, original .MP4 files and proxy .MOV (ProRes) files).

Every obvious matching method has already been tested:

Matching by Clip Name / File Name.
Matching by Media Start (camera timecode).
Different combinations of the available matching options.

None of these methods work. Premiere Pro simply fails to find the corresponding proxy automatically.

However, the evidence that this is a bug is very clear: if the file browser opens and you manually click Search, Premiere immediately finds the correct proxy. The software is clearly capable of identifying the file, but the automatic linking process fails.

Please reproduce this issue properly instead of testing with a single file. Create a batch of at least 10 original MP4 clips, generate ProRes MOV proxies using FFmpeg, and then try to attach them automatically. This is the workflow many professionals use every day, and the bug becomes immediately obvious.

Please prioritize this issue. It has been affecting professional users for over a year, and we need this feature to work reliably again. A professional editing application should not require users to depend on custom scripts and workarounds for such a fundamental workflow.

S

Sebastian35293480nw5v

Participating Frequently

still having this problem. Nothing seems to work. I’m stuck attaching one-by-one. It’s really frustrating

Sebastian from SFV

J

jmng

Participant

This is happening to me too and I thought I was crazy until I saw this post. I created proxies using the 2026 version and I’ve been trying to link them every way: tried with AND without the _Proxy in the filename, with and without Media Start, tried moving all the proxies into the same folder with raw files, and even tried re-importing different bins in case it was something with my original importing process. It only links one proxy at a time so I might call it a day.

O

OMI Media House

Participating Frequently

Yeah, I feel you - same here. We’re in the middle of project with 5 camera setup and thousands of files - a month ago everything worked well, and last week it stopped.

Because of no available workarounds i did manage to create the script with chatgpt - you may give it a try. I was able to link more than 1000 proxies with it.

https://we.tl/t-HiJb5zC0xrrE5q1Y

I hope it helps.

Best,

Mirek

J

JorgeAPerezC

Participant

You are the best, this script fixed what Adobe damaged in the last update.

Show more replies

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.