Skip to main content
Participant
February 10, 2026
Question

Are there known UXP differences between Premiere Pro Stable vs Beta on macOS? (Plugin works only on Beta)

  • February 10, 2026
  • 0 replies
  • 12 views

I’m working on a UXP plugin for Adobe Premiere Pro and I’m trying to understand a behavior difference I’m seeing between Stable and Beta builds on macOS.
 

Scenario

  • The plugin works as expected on:

    • Premiere Pro Beta (macOS)

    • Premiere Pro Stable & Beta (Windows)

  • On Premiere Pro Stable (macOS):

    • The plugin loads correctly

    • Authentication / initialization succeeds

    • But when performing certain runtime operations (e.g. actions on a sequence), the flow fails

The same plugin build works without issues on Premiere Pro Beta on macOS, which makes me wonder if there are runtime, permission, or sandboxing differences between the two.
 

Questions

At a high level, I’d like to understand:

  1. Are there known discrepancies or limitations between:

    • Premiere Pro Stable vs Beta UXP runtimes on macOS?

  2. Are there any macOS-specific restrictions (permissions, networking, sandboxing, security) that behave differently in Stable vs Beta?

  3. Are there recommended ways to verify UXP support or runtime capabilities on Premiere Pro macOS (non-beta)?

  4. If this might be caused by a corrupted or outdated environment:

    • What are the recommended steps for a clean Premiere Pro + UXP reset on macOS?

    • Are there any folders, caches, or UXP-related locations that should be cleared?

I’m mainly trying to determine whether this is:

  • An environment/setup issue

  • A Stable vs Beta runtime difference

  • Or a known macOS limitation

Any guidance or pointers to documentation would be greatly appreciated
Thanks!