Project v35 → v33 # Downgrade Premiere Pro 2019 to 2018 Drop your Premiere Pro 2019 .prproj and get a copy that Premiere Pro 2018 opens. Everything runs locally in your browser. Downgrade panel 100% local. No upload. Drop your .prproj here Saved in Premiere Pro CC 2019? or click to browse. Multiple files are fine. Open it in Always keep your original. Downgrading bypasses the version gate and repairs known format differences, but effects and features from newer releases cannot be interpreted by older builds. After opening, import the sequences into a fresh project. ## Compatibility verdict for 2019 to 2018 2019 project version v35 2018 accepts up to v33 Major releases apart 1 Downgrade outlook low risk ## Premiere Pro 2019 vs Premiere Pro 2018: what is different? Premiere Pro 2019 (13.0, released Oct 2018) saves projects with internal schema version `35`. Premiere Pro 2018 (12.0, released Oct 2017) only understands up to `33`, which is why opening the file shows _“This project was saved in a newer version of Adobe Premiere Pro”_. The message is a gate, not a judgement about the content. | | Premiere Pro 2019 | Premiere Pro 2018 | | --- | --- | --- | | Release | Oct 2018 | Oct 2017 | | App build | 13.0 | 12.0 | | Project Version attribute | 35 | 33 | | XML serialisation | Dense (full fields) | Dense (full fields) | ## What the converter changes in your file A `.prproj` is gzip-compressed XML. The tool decompresses it, edits the root `Project` element, and compresses it again: \- + Both 2019 and 2018 use the dense serialisation, so no fields need rebuilding. Changing the version is the only edit required. ## What you may lose going from 2019 to 2018 Features below were introduced after Premiere Pro 2018. Their data may stay in the XML, but Premiere Pro 2018 has no code to interpret it, so expect them to be ignored, flattened or missing: ### Added in Premiere Pro 2019 * Selective colour grading and display colour management * Intelligent audio cleanup in Essential Sound * Add, rename and edit multiple Lumetri instances * Editable vector graphics ## Why this jump is rated low risk * Adjacent major releases share most of their project schema, which is the safest case. ## Step-by-step: open a 2019 project in 2018 1. Duplicate your `.prproj`. Never convert your only copy. 2. Drop it into the panel above and choose Premiere Pro 2018 as the target. 3. Download the converted file and open it in Premiere Pro 2018. Expect a prompt about converting an older project, which is normal. 4. Create a brand new empty project in Premiere Pro 2018 and **import** the converted project into it, rather than continuing in it. 5. Scrub every sequence. Relink media if drive letters or paths differ. Don't have Premiere Pro 2018? Open the Creative Cloud desktop app, choose _All apps → Premiere Pro → Other versions_ and install it alongside your current version. ## Frequently asked questions Can I open a Premiere Pro 2019 project in Premiere Pro 2018? Yes, in most cases. Premiere Pro 2018 refuses Premiere Pro 2019 files because the project carries version 35 while Premiere Pro 2018 only accepts up to version 33. This tool rewrites that number to 33, so Premiere Pro 2018 loads the file instead of showing "saved in a newer version". Risk for this jump is low: 1 major release apart. What will I lose downgrading from 2019 to 2018? Anything that only exists in newer releases cannot be interpreted by Premiere Pro 2018. That includes Selective colour grading and display colour management and Intelligent audio cleanup in Essential Sound. Basic cuts, tracks, clips, markers, transitions and effects that exist in both versions normally survive, but always check the timeline after opening. Why does Premiere Pro 2018 say the project was saved in a newer version? A .prproj is gzip-compressed XML and the root element stores an integer schema version (2019 = 35, 2018 = 33). Premiere reads it before anything else and stops if it is higher than its own. Is my 2019 project uploaded to a server? No. Decompression, editing and re-compression run inside your browser using JavaScript and the native Compression Streams API. Your project file never leaves your computer, and there is no backend. ## Other jumps from 2019 * [2019 → 2017](/premiere-pro-downgrader/downgrade-premiere-pro-2019-to-2017) ## Other projects that open in 2018 * [2026 → 2018](/premiere-pro-downgrader/downgrade-premiere-pro-2026-to-2018) * [2025 → 2018](/premiere-pro-downgrader/downgrade-premiere-pro-2025-to-2018) * [2024 → 2018](/premiere-pro-downgrader/downgrade-premiere-pro-2024-to-2018) * [2023 → 2018](/premiere-pro-downgrader/downgrade-premiere-pro-2023-to-2018) * [2022 → 2018](/premiere-pro-downgrader/downgrade-premiere-pro-2022-to-2018) * [2021 → 2018](/premiere-pro-downgrader/downgrade-premiere-pro-2021-to-2018) * [2020 → 2018](/premiere-pro-downgrader/downgrade-premiere-pro-2020-to-2018) Want the internals? Read [how project downgrading works](/premiere-pro-downgrader/how-premiere-project-downgrade-works) or check the [version map](/premiere-pro-downgrader/premiere-pro-project-version-map). Reverse direction: any [2019 → 2018](/premiere-pro-downgrader/downgrade-premiere-pro-2019-to-2018) copy opens in newer Premiere versions without conversion. Canonical page: https://vakago-tools.com/premiere-pro-downgrader/downgrade-premiere-pro-2019-to-2018 Keep the original project. Newer effects and features may be lost; check the converted timeline in the target Premiere Pro release.