Guide: downgrade a Premiere Pro project
You received a .prproj created in a newer version of Premiere Pro than yours? This guide walks you through lowering its internal version so you can open it — 100% locally, your file never leaves your machine.
“This project was saved in a newer version of Adobe Premiere Pro”
This message appears when a .prproj file was saved in a newer version of Premiere Pro than the one installed on your machine. Premiere then refuses to open the project. The Downgrade .prproj tool on this page rewrites the project's header to the target version (default “30”), 100% locally, so the file becomes openable in your Premiere release again.
Premiere Pro: internal version numbers (.prproj)
Each Adobe Premiere Pro release maps to an internal number written in the Version="N" attribute of the .prproj file's <Project> tag. To open a project in an older release, pick the matching target value below in the downgrade tool. Values below 30 are intentionally blocked because they can make modern projects appear corrupted.
| Year / Release | Premiere Pro version | Internal .prproj version |
|---|---|---|
| 2026 | 26.x | 45 |
| 2025 | 25.x | 44 |
| 2024 | 24.x | 43 |
| 2023 | 23.x | 42 |
| 2022 | 22.x | 39 |
| 2021 | 15.x | 37 |
| 2020 | 14.x | 35 |
| 2019 | 13.x | 33 |
| 2018 | 12.x | 32 |
| 2017 | 11.x | 31 |
| CC 2015.3 | 10.3 | 30 |
Indicative values observed on real-world projects. Adobe's minor builds may introduce slight variations; if in doubt, inspect the .prproj file with the tool to read its exact internal version. Version 30 maps to Premiere Pro CC 2015.3 and is the practical minimum kept by the tool.
Open a 2025 project in Premiere Pro 2024
This is the most requested downgrade: a project saved with Premiere Pro 2025 (25.x, internal version 44) is refused by Premiere Pro 2024, which expects internal version 43. Lowering the header is all it takes to make it openable.
1. Back up the original project
Make a copy of the .prproj before anything else. The tool never modifies the original, but the backup is your safety net.
2. Drop the file into the Downgrade tool
The detected version should read 44 (Premiere Pro 2025 · 25.x). If the tool shows a different value, use that value as your starting point in the next step.
3. Pick 43 as the target version
43 is Premiere Pro 2024's internal version. Click “Download”: the downgraded file is saved with the “_downgraded” suffix.
4. Open the file in Premiere Pro 2024
Premiere offers to “convert” the project: accept, then save under a new name right away. Afterwards, review your sequences (effects, titles, captions).
An effect, setting or feature introduced in Premiere Pro 2025 may be lost or reset in 2024 — Adobe does not guarantee functional backward compatibility. If Premiere 2024 still crashes after the downgrade, run the file through Prproj Doctor: most known crash causes (duplicate IDs, orphan references) are detected and fixed there.
Same principle for newer projects: a 2026 project (internal version 45) can be lowered straight to 43 to open it in Premiere Pro 2024.
Steps
1. Back up your original project
Before anything else, make a copy of the .prproj file. The tool never modifies the original (a new file is generated), but a backup is still the safest insurance against mistakes.
2. Identify the target version
Figure out which Premiere Pro release you want to open the project in (e.g. Premiere 2023, 2022, CC 2019…). If unsure, leave the default value “30”: it is the most reliable practical threshold observed on modern projects.
3. Drop the file into the tool
Drag your .prproj onto the drop zone (or click to browse). The tool immediately shows the current version it detected in the file.
4. Pick the target version and download
Enter the desired target version then click “Download”. The downgraded file is generated in your browser and saved automatically (suffixed “_downgraded”).
5. Open the file in Premiere Pro
Premiere Pro will offer to “convert” the project on opening: that is expected. Save it under a new name right away so you keep both the original and the converted version.
Picking the right target version
Why “30” by default?
A .prproj's internal version is an integer that goes up with each major format change. On modern projects, very old values (1–29) can make Premiere report the file as corrupted: the header claims an old schema while the XML body remains modern. Version 30 is therefore used as the reliable practical minimum.
Which value should I enter?
Any integer between 30 and your file's current version is allowed. If you know your Premiere release accepts internal version N, pick N. Otherwise stick with 30 — that is the safest bet for recent projects.
Manual procedure (if the tool fails)
A .prproj is simply an XML file compressed with gzip. If the tool fails (corrupted file, exotic browser, very large project), you can perform the operation by hand with a compression utility and a text editor. Always make a backup copy of the original file first.
1. Duplicate and rename to .gz
Copy the original file and rename the copy, replacing the .prproj extension with .prproj.gz (e.g. MyProject.prproj → MyProject.prproj.gz). On macOS, confirm the extension change in the dialog.
2. Decompress the gzip
Open the .gz file with 7-Zip (Windows), Keka or The Unarchiver (macOS), or from the command line: gunzip MyProject.prproj.gz. You get a plain XML file (rename it to .xml if it helps your editor open it).
3. Edit the version in the XML
Open the XML in a text editor (VS Code, Sublime Text, Notepad++, BBEdit — avoid Word). Near the top of the file, find the tag <Project ObjectRef="…" ClassID="…" Version="N"> and replace the N in the Version attribute with your target version (for example Version="30" as the reliable threshold). Do not change anything else. Save as UTF-8 without BOM.
4. Recompress with gzip
Recompress the XML with gzip: from the command line, gzip MyProject.xml produces MyProject.xml.gz. With 7-Zip, explicitly pick the gzip format (not zip or 7z, otherwise Premiere will not be able to read the file back).
5. Rename to .prproj and open
Rename the resulting .gz file to .prproj (e.g. MyProject_manual.prproj) and open it in Premiere Pro. The app will offer to convert the project: accept and save under a new name.
If Premiere refuses to open the file after this manipulation, the recompression is usually not standard gzip, a character in the XML was accidentally modified, or the target version is too old. Start over from the backup and retry with a target ≥ 30.
Frequently asked questions
Is my .prproj sent to a server?
No. The whole conversion (gzip decompress, XML edit, gzip recompress) runs in your browser: no file is uploaded. Only an anonymous usage counter is incremented.
Will I lose effects or settings?
Possibly. Adobe does not guarantee functional backward compatibility: an effect or setting introduced in a recent release may not exist in the target version. Downgrading is still the best way to open a project that is too new for your Premiere.
Premiere Pro offers to “convert” the project, is that normal?
Yes, it is expected: Premiere sees a format older than its current version and offers to re-save it. Accept and save under a new name to preserve both files.
Does the generated file overwrite the original?
No. The tool produces a new file named after the original with the “_downgraded” suffix. The original stays untouched on your disk.
What is the difference between the “internal version” and the Adobe Premiere Pro version?
The internal version is a plain integer (1, 2, 3…) Adobe writes in the .prproj XML header; it evolves independently from the commercial names (Premiere 2023, 2024…). That is the integer Premiere Pro checks to decide whether it can read the file.
Can I upgrade a version with this tool?
Technically yes: if you enter a target version higher than the current one, the tool will write it. But Premiere Pro will most likely refuse to open a file whose version is higher than what it knows how to handle. The intended use is downgrading.
How do I know which Premiere Pro release a .prproj was saved in?
Drop the file into the tool: the detected internal version is shown right next to the project name before any conversion runs. Cross-reference the version table above to find the matching commercial name (for example 43 → Premiere Pro 2024, 42 → 2023, 39 → 2022).
Can I downgrade Premiere Pro 2024 to 2022 (or 2023 to 2021)?
Yes — that is the most common use case. Downgrading a .prproj from 2024 (internal version 43) to 2022 (39), or from 2023 (42) to 2021 (37), reliably opens in the target release. Effects or settings introduced after the target version may still be lost — Adobe does not guarantee functional backward compatibility — so plan a quick sequence review after conversion.
How do I open a Premiere Pro 2025 project in Premiere Pro 2024?
A 2025 project carries internal version 44; Premiere Pro 2024 expects 43. Drop the file into the Downgrade tool, pick 43 as the target version, open the downgraded file in 2024 and accept the conversion. Features introduced in 2025 may be lost — review your sequences afterwards. If crashes persist, Prproj Doctor detects the known causes (duplicate IDs, orphan references).
Your files never leave your browser. No trackers, no ads.