Principal Product Manager

Premiere projects saved in v25.6.0 cannot be opened in other v25.x versions

Forum|Forum|2 years ago
September 5, 2023
172 replies
20346 views

We are aware that customers who saved projects in Premiere v25.6.0 may find that those files now open only in v26 (beta) and cannot be opened in v25 versions. We know this is disruptive, and we’re working on a fix.

What you need to know:

Projects saved in v25.6.0 save in the v26 version format.

Because of this, they can’t be opened in earlier versions, including v25.6.1 (even though it is the current generally available release)

We’re developing a tool that will let you convert affected projects back to a v25-compatible file.

Our Solution

We’re building a small app that will convert a v25.6.0-saved project back to the v25 format. We’ll share more information, including availability and instructions, as soon as the tool is ready in the coming days.

We know that there is nothing more important than the reliability of a project file, so we’re working with urgency to get this downgrade tool in your hands as quickly as possible.

We know there are a number of downgrading apps available online, but we strongly recommend utilizing our tool when it becomes available. Non-Adobe apps and scripts are often outdated and may cause crashes and data loss.

Further Details

A bug caused Premiere v25.6.0 to prompt customers to enable Object Masking even though it is not yet in full release. Object Masking (and our yearly major version update) changes the Premiere project file structure such that it can only be opened in v26, which is only available in public beta. Turning this on caused projects to save in the newer v26 project format, even though users were still technically on the v25 release line.

Opening an older project in v25.6.0 triggered a prompt to save a copy of the project with “_1” appended. We know that many customers upgraded the project and continued working in the new copy, potentially also deleting the original. This means the only active version became the file saved in v26 format.

Premiere 25.6.0 was only available briefly before being replaced by 25.6.1 and is no longer available to reinstall. This means impacted users who auto updated to 25.6.1 cannot open v26 formatted projects.

Show previous replies

R

rui_9488

Participant

Can you please make the Premiere Beta available for all accounts? The Premiere Beta opens the project files we can't open in the current Premiere version.

C

Collab37310681j66h

Participating Frequently

Updated the Premiere Pro from 25.5 to 25.6.1 Yesterday and having issue with opening the project that was created in 25.5. And Premiere Pro say that the project was created in a newer version of Premiere Pro. Never Opened the project in Beta or whatsoever.

"This project was saved in a newer version of Adobe Premiere Pro and cannot be opened in this version."

Please, fix this issue as soon as possible because it is affecting my workflow. Especially, when there is a Black Friday is coming up. Need to finish projects.

S

smart_Moonbeam2893

Participant

Hello, this does unfortunately not solve the problem for me, i have 25.6.1 installed and can not open the main file nor the backup files, all with the same error of the project being saved in a newer version of premiere pro. I even tryed using a online downgrader, which just corrups the file, manuelly changing the version of the project file has the same outcome for me.

V

Vinod_Naik2040

Participant

I was trying to open a project in current version but getting this. Currently i am working with 25.6.1.

Can someone please help me to open this project.

caroline_edits

Community Manager

Hi Vinod, sorry for the frustration! If you locate your Auto-Save files, do they open in 25.6.1? The Auto-Save files are located in a folder next to your original .prproj file.

Let us know,

Caroline

R Neil Haugen

Legend

Their typical staggered rollout takes up to three days. So by tomorrow, probably everyone will have this.

Everyone's mileage always varies ...

D

Dolphndude

Participant

When will this be available everywhere? By remove 25.6 and not enabling 25.6.1 everywhere, it seems a lot of us are up the creek without a paddle since we uninstalled 25.6 to fix the previous issue expecting an immediate ability to update to 25.6.1