Host Script (JSX) Cannot Run in Premiere Pro 2025

Question

Hi everyone,I am experiencing an issue with CEP panel scripting in Premiere Pro 2025 and I would like to ask if anyone else has encountered this problem. I am able to open my panel, and it shows the UI, but it unable to run any JSX script in Premiere Pro 2025—including the official sample scripts. Specifically:1. Running the PProPanel sample .jsx script does nothing.2. Executing my own .jsx scripts also results in no output, no dialog, and no error message.3. Launching ExtendScript from Visual Studio Code using the ExtendScript Debugger extension shows no logs or activity inside Premiere Pro 2025.4. The exact same scripts run correctly and immediately in Premiere Pro 2024 on the same machine. Environment:Premiere Pro 2024 → JSX works normallyPremiere Pro 2025 → JSX scripts do not run at allApple M4 Pro (macOS 15.6)Questions:1. Has Adobe officially changed or deprecated CEP/ExtendScript support in Premiere Pro 2025?2. Is there any new configuration required to enable this?3. Are there recommended workarounds for running CEP that using Extendscript in Premiere Pro 2025?Any guidance would be really appreciated. Thank you in advance.

Bruce Bullis · Accepted Answer

Strange! All working fine here, and no other reports of such behavior.

What specific version (from the About box) of PPro 2025 are you running?

> 1. Has Adobe officially changed or deprecated CEP/ExtendScript support in Premiere Pro 2025?

No.

> 2. Is there any new configuration required to enable this?
No.

> 3. Are there recommended workarounds for running CEP that using Extendscript in Premiere Pro 2025?

No.

ThioJoe · Answer

It sounds like you need to enable debug mode to be able to run unsigned extensions. I found out myself that while unsigned extensions still load, they don't seem to work or do anything unless debug mode is on (at least when I also tried to get it to run jsx scripts). So I suspect that's what's happening.

Apparently Premiere Pro 2024 uses CEP 11, but 2025 uses v12, so perhaps you had already enabled debug mode for CEP 11 but not v12.

You should be able to do it by running this command in Windows command prompt:

REG ADD "HKEY_CURRENT_USER\Software\Adobe\CSXS.12" /v PlayerDebugMode /t REG_SZ /d 1 /f

Or on MacOS:

defaults write com.adobe.CSXS.12 PlayerDebugMode 1

For older versions you might need to do the same thing but for other "CSXS" versions like CSXS.11. If you want, on Windows you can go into RegEdit and see which "CSXS" folders (keys) exist and just run the command for those versions too. For people in the future, if there's a future version you see not listed above, you'd need to run it for that too.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.