Understand what Adobe's extensibility transition means for the plugins you use in your Creative Cloud desktop apps.
Creative Cloud plugins moving from CEP to UXP
Adobe is moving Creative Cloud extensibility from CEP (Common Extensibility Platform) to UXP (Unified Extensibility Platform), the modern platform for the plugins and extensions that add features to Creative Cloud desktop apps. The move will happen in stages over several years. If you use plugins built on CEP, find out whether you're affected and what to expect. If you're a developer, you'll find migration guidance on the Adobe Developer site.
The transition applies only to Creative Cloud desktop flagship apps. Acrobat, Adobe Express, Lightroom, and the built-in features of your Creative Cloud apps aren't affected.
Adobe is moving the platform behind third-party plugins in Creative Cloud desktop apps from CEP to UXP. UXP is the modern, long-term platform, and it already powers plugins in Photoshop, InDesign, and Premiere. CEP is being phased out over several years.
This transition will impact you only if you use plugins built on CEP. If you don't use CEP plugins, nothing changes for you. If you do, you can keep using them in Creative Cloud app versions released before December 2029. You'll want a UXP version of those plugins before you move to a version released after that date.
It's best to plan your move to UXP early rather than wait. Your CEP plugins keep working in the app versions you use today, and in any Creative Cloud app version released before December 2029. Adobe removes CEP from app versions released after December 2029, so a CEP plugin won't run once you update to one of those newer versions. To keep a CEP plugin past then, you'd have to stay on an older app version, which means missing newer releases and features. Adobe also can't guarantee CEP plugins will keep working in older versions over time. Moving to UXP versions of your plugins ahead of these dates keeps your workflows current and supported.
Adobe supports the latest and previous major versions of each app. Staying on CEP limits how current you can keep your apps. Refer to the Creative Cloud support policy for details.
In most cases, no. The plugin's developer provides the UXP version. Watch for updates from the developers of the plugins you rely on, and check with your plugin vendor, or your internal team if the plugin was built in-house, about their migration plans.
CEP plugins (previously called extensions) live in these folders:
System extension folder
- Windows (x64): C:\Program Files (x86)\Common Files\Adobe\CEP\extensions, and C:\Program Files\Common Files\Adobe\CEP\extensions (since CEP 6.1)
- macOS: /Library/Application Support/Adobe/CEP/extensions
Per-user extension folder
- Windows: C:\Users\<USERNAME>\AppData\Roaming\Adobe\CEP/extensions
- macOS: ~/Library/Application Support/Adobe/CEP/extensions
Contact the plugin's developer first, since CEP plugins are built by third-party developers rather than Adobe. If the problem is with an Adobe app, check the known issues page or contact Adobe Support.
If your plugin is distributed on our marketplace, Adobe Exchange, you can find the contact details for your developer when you go to the plugin’s listing and check under Help & Support.
If you find the links to the developer’s website or Get Support links are broken, reach out to ccintrev@adobe.com.
You can describe your issue in the Adobe UXP Developer Forums to find a developer or reach out to your point of contact at Adobe when you are an Enterprise customer. You can also connect with the Developer Community Team. Enterprises can write an email to wwds@adobe.com. Note that there are additional Enterprise support options.
Only CEP plugins for Photoshop need Rosetta. If your version of macOS no longer supports Rosetta, Photoshop still runs natively, but your CEP plugins won't work. To keep using them, stay on a macOS version that supports Rosetta.
Adobe doesn't store or own your data through CEP, and this change requires no data migration on Adobe's side. Some third-party plugins store data within the plugin itself, which Adobe doesn't manage. If you have data privacy questions about a specific plugin, contact that plugin's developer.
No. However, some complicated C++ plug-ins currently use CEP in conjunction with C++. If in doubt, contact the developer of the tool(s) you use.
