Send the project back a version.
The client is on last year’s Premiere and your project will not
open.
Pick their version, press once, and the copy is sitting next to your file.
One payment, no renewal Your project is not touched Four versions built in Works offline
- One press - the copy lands beside your project
- Four versions built in, back to Premiere 23.4
- Teach it any other version from a project saved in it
- Every update, for as long as it exists
- Two computers on one key
- 7 days to send it back
Card or PayPal. The key and the installer arrive straight after.
What it does
Four things, and no fifth.
One press, and it is there
Pick the version from the list and press the button. A converted copy appears in the same folder as your project, named for the version it was made for. No export, no save dialog, nothing to set up first.
Your project is never written to
The file you are working in is read, never modified. The copy is a new file beside it, and an existing one is never overwritten - press it twice and you get a numbered second copy.
Four versions built in
Premiere Pro 24.3, 24.2, 24.1 and 23.4 are there the moment you install it. Need another? Point the panel at any project saved by that version and it learns that one too.
Nothing is deleted from the copy
An effect the older Premiere never had shows up there as missing, the way it would with any project - the markup is carried across rather than stripped out. Nothing is quietly removed from your work behind your back.
Why this is not a setting Adobe forgot
There is no version number to lower.
There is no single number
A project carries a schema version on every element inside it - around a thousand of them, across a hundred kinds of thing, each moved on its own timetable. An older Premiere does not read a number at the top and decide. It reads every element against the version it knows, and refuses anything it thinks came from the future.
Every project states its own
A project saved by Premiere 24.3 says, in its own markup, exactly what 24.3 writes each element at. Premiere also installs template projects Adobe last saved years ago - which is where the four built-in versions come from. Adobe’s own files, read rather than guessed at.
The conversion does two things
It rewrites those versions and restates the build, and nothing else. Nothing is deleted, no object is removed, and every internal reference is checked against the rewritten file before a single byte is saved. If that check fails, nothing is written at all.
Read this before you buy
What it cannot promise.
Only Premiere can settle it
Open the copy in the older version and check it before you rely on it. The panel says so every time it saves one, and so do we here. Nothing that reads a file can substitute for the application reading it.
Missing effects stay missing
An effect the older Premiere never had shows there as missing. That is the intended outcome rather than a fault - converting cannot add features to software released before them. The markup is carried across instead of deleted, so nothing of yours is lost in the copy.
The further back, the bigger the ask
One version back is the easy case and the common one. Four back is a bigger ask, and the honest advice is to test it on the actual project before the deadline rather than on the day of it. Seven days to send it back, no argument, if it does not do what you needed.
From paid to converted: about two minutes.
- Pay. Card or PayPal at the checkout. The receipt is instant.
- Install. The .ccx is on the confirmation page - double-click it and Creative Cloud does the rest. Restart Premiere if it was open.
- Activate. Window → UXP Plugins → Downgrader opens with a box for the key from your inbox. Once, and never again.
Licences, machines, offline use and refunds are answered on the questions page. Anything odd: hello@postprodtools.com.