Check compatibility at the level of the exact extension, Premiere build, operating system, and release channel. “Works with JavaScript” is not a useful compatibility statement: CEP, ExtendScript, and UXP refer to different parts of Adobe’s extension environment.
For a new Premiere plugin, Adobe directs developers toward UXP. For an existing ExtendScript workflow, confirm the vendor’s current host support before upgrading a production machine. A newer platform’s availability does not automatically convert an older extension.
What the three names mean
| Term | Role in a Premiere workflow | Common mistaken assumption |
|---|---|---|
| CEP | Extension panel environment used by many existing tools | Its panel JavaScript is the same as the host script |
| ExtendScript | Scripting runtime used to access the older host API | Any modern JavaScript snippet will run in a JSX file |
| UXP | Newer plugin platform with its own Premiere API | Renaming a CEP package makes it a UXP plugin |
In a CEP tool, the interface can communicate with ExtendScript running in Premiere. That boundary is why debugging the interface and debugging the host operation are separate tasks. Developer Tools provides an accessible place to execute and inspect ExtendScript; it is not a general-purpose runner for every Adobe plugin runtime.
Read version notes literally
Adobe’s development-tools documentation identifies Premiere 25.6 and later as supporting UXP plugins. Individual API methods may require later versions, so the platform minimum is only the first compatibility check.
The PProPanel README recommends UXP for new development and describes a transition period for CEP. Treat that as transition guidance, not an exact removal date for every installation. Verify the release notes and vendor support for the host you plan to use.
A demonstration recorded in beta also needs its own label. A feature appearing there does not establish availability in the stable release installed on an editor’s workstation.
A compatibility card for your team
Keep a small record beside each essential extension:
- Product name and installed version.
- Premiere version including the build, plus release or beta channel.
- Operating system and relevant architecture.
- Runtime and installation package provided by the vendor.
- Vendor compatibility source and the date you checked it.
- One representative operation that you verified on a disposable project.
- A preserved project copy and a recovery path if an update breaks that operation.
“The panel opens” is a useful installation check. It does not establish that an operation can read a sequence, finish an edit, or survive closing and reopening the project. Pick a test that resembles the reason you depend on the extension.
Migration is an API review
Adobe’s migration guidance explains that UXP uses modern JavaScript and different host APIs. Avoid carrying ExtendScript assumptions directly into a port. Review asynchronous calls, returned object types, permissions, and how the target API applies edits.
Also read examples for the correct Adobe application. Photoshop-specific facilities are not automatically Premiere facilities. A search result containing UXP can still lead to code for the wrong host.
Existing JSX tools can remain useful where their vendor and host versions support them. The practical decision is to keep a verified workflow working while planning new development against the documented platform. This compatibility guide is source-based; it does not certify an installed extension or claim host acceptance.