UXP API parity for MOGRT parameter control + current ExtendScript support status

Hello,

I am currently migrating a fairly large Premiere Pro automation workflow from ExtendScript to UXP.

Most of the workflow is now handled by UXP plugins, but there is still one important operation for which I need to rely on ExtendScript: reading and modifying the exposed parameters of MOGRT instances already placed on a Premiere Pro timeline.

My workflow uses MOGRT templates extensively. After a MOGRT has been inserted into a sequence, my automation needs to access its exposed Graphic / Essential Graphics parameters and modify them programmatically.

With ExtendScript, I can currently access the MOGRT component and its exposed properties, including controls such as:

  • text fields

  • color controls

  • numerical values

  • tracking / spacing values

  • checkboxes

  • dropdowns

  • other custom controls exposed by the MOGRT

For example, I can locate an exposed text property by its custom name and then modify its value programmatically using operations such as:

property.setValue("New text", true);

The actual property names vary from one MOGRT to another because they are custom names defined inside each template.

This works reliably in my current automation.

The overall workflow is now UXP-based, but ExtendScript is still required as a bridge specifically for this MOGRT parameter manipulation.

I would therefore like to clarify both the current UXP capabilities and Adobe’s migration plans.

UXP / MOGRT API questions

  1. Is there currently a supported UXP API that allows a plugin to enumerate the exposed parameters of an existing MOGRT instance on a timeline?

  2. Can UXP currently read and modify those parameter values, including text, colors, numbers, checkboxes, dropdowns, and similar exposed controls?

  3. If this functionality is not currently available, is full MOGRT / Graphic Parameters API parity with ExtendScript on the Premiere Pro UXP roadmap?

  4. Is there an estimated Premiere Pro version or timeframe in which this functionality is expected to become available?

  5. More generally, is Adobe’s goal that operations currently available through ExtendScript APIs such as TrackItem.components, component properties, and Property.setValue() will eventually have equivalent UXP APIs?

To be clear, I am not trying to create a MOGRT, edit the original After Effects template, or modify the .mogrt file itself.

I specifically need to access and change the exposed controls of a MOGRT instance that is already placed in a Premiere Pro sequence, in the same way a user would manually change those controls in Premiere’s Properties panel.

ExtendScript support status

I would also appreciate clarification regarding the current official status of ExtendScript in Premiere Pro.

Earlier migration discussions referenced a September 2026 transition / sunset timeframe for legacy extensibility. More recently, however, I have seen Adobe state that no end-of-life date has currently been set for ExtendScript or CEP in Premiere Pro.

Could Adobe please confirm the current position?

Specifically:

  • Is ExtendScript expected to continue working after September 2026?

  • Is there currently any planned end-of-life date for ExtendScript in Premiere Pro?

  • Will existing ExtendScript functionality remain supported until equivalent UXP APIs are available?

This is particularly important for developers like me who have already migrated most of their extensions to UXP but still depend on ExtendScript for functionality that does not yet appear to have a UXP equivalent.

Any clarification regarding the recommended migration path for this specific MOGRT use case would be greatly appreciated.

Thank you.

  1. No; coming soon (the work is currently in progress).
  2. Largely, yes; this is exercised in the premiere_api sample.
  3. Yes.
  4. Adobe employees cannot comment on the feature sets of unannounced product releases. Our current plan is MAX 2026; plans can change. :wink:
  5. Yes; API feature parity is our proximal goal.

Earlier migration discussions referenced a September 2026 transition / sunset timeframe for legacy extensibility.

Our commitment remains the same as last year: We commit to supporting CEP+ExtendScript integration, for at least one calendar year from the introduction of UXP API support, in 25.4 (MAX 2025).

[Checks watch…]

Although we are nearing the end of that committed window, no removal of CEP or ExtendScript from Premiere has been planned or scheduled.

  • Is ExtendScript expected to continue working after September 2026?

Yes.

  • Is there currently any planned end-of-life date for ExtendScript in Premiere Pro?

No.

  • Will existing ExtendScript functionality remain supported until equivalent UXP APIs are available?

That is our plan, yes.

1 Like

Hi Bruce,

Thank you very much for your very detailed answer :slight_smile:

Have a great day!