Adobe Is Retiring Legacy Creative Cloud Plugins
Adobe has put a deadline on the technology behind many older Creative Cloud panels and extensions. The company announced on September 24, 2026 that it is moving its flagship desktop apps from the legacy Common Extensibility Platform, or CEP, to the newer Unified Extensibility Platform, known as UXP. Adobe says CEP will be removed from new app versions after December 2029.
This is important for motion designers, editors, illustrators and studios that rely on third-party panels every day. The change does not mean every plugin suddenly stops working. It does mean creators should identify which parts of their workflow depend on CEP and plan replacements before upgrading to future app versions.
What is changing from CEP to UXP?
CEP is the older framework used to build panels and integrations for Creative Cloud applications. UXP is Adobe’s newer extensibility system, designed around a more modern architecture and security model. It already supports production plugins in Photoshop, InDesign and Premiere.
Adobe says the change is being phased in rather than imposed overnight. The company is extending UXP support to After Effects, Illustrator and Media Encoder while publishing transition milestones for developers and users.
The key dates creators should know
According to Adobe, Photoshop stops accepting new CEP Marketplace submissions in March 2027, while existing submissions can still receive updates. Photoshop CEP plugins become disabled by default in December 2027, though users can turn them back on.
Premiere stops accepting new CEP submissions in December 2027, and InDesign follows in January 2028. Adobe lists additional disabled-by-default milestones in December 2028. From December 2029 onward, CEP will no longer be included in new flagship app versions.
After Effects and Illustrator are getting UXP support
Adobe plans a public UXP plugin beta for After Effects by November 2026 and for Illustrator by spring 2027. Media Encoder already has a public beta, while Premiere supports general-availability UXP plugins and hybrid approaches.
For motion designers, this is worth tracking because many familiar panels automate complex After Effects tasks. The quality and availability of replacements will matter more than the framework name itself.
What happens to existing plugins?
Adobe’s user guidance says existing CEP plugins can continue running in app versions released before December 2029, subject to compatibility and support limitations. A plugin does not automatically become a UXP plugin just because Creative Cloud updates.
The distinction is critical: an app update can change the environment in which a panel runs. If a production team depends on a specific extension, it should not assume that the extension will work indefinitely in every future release.
Not every Adobe product is affected
The transition covers flagship Creative Cloud desktop applications. Adobe explicitly says Acrobat, Adobe Express and Lightroom are outside this CEP-to-UXP transition. Built-in features are also not the target of this change.
Adobe also says ExtendScript is not affected by this transition. Developers should still review their own integrations, because a larger workflow can combine several extension technologies.
A simple audit for creators and studios
List the extensions installed on each editing or design workstation. For each one, record the vendor, version, purpose, installation source and whether it is CEP-based. Then check the vendor’s roadmap for a UXP release or an alternative workflow.
Prioritize panels that affect delivery: render automation, template building, asset management, repetitive compositing and production handoffs. Those are the integrations that can create real delays if they fail during a client project.
How to migrate without breaking projects
Do not replace every plugin on a live deadline. Set up a test workstation or duplicate project, install the UXP version when available and compare outputs with the existing workflow. Check presets, project metadata, file paths, keyboard shortcuts and render results.
Document a rollback plan. If the new extension does not cover a critical feature, keep the current app and plugin combination stable until the replacement is reliable.
Why the change matters beyond Adobe
Creative applications increasingly depend on extensions, agents and automation. Modernizing plugin architecture can make those integrations more secure and maintainable, but it also imposes migration costs on people who built dependable workflows around older technology.
The best preparation is not panic. It is visibility into the tools a team already uses, followed by deliberate testing before the deadlines arrive.
Sources and further reading
Adobe developer announcement and detailed transition timeline
Adobe Help: Creative Cloud CEP-to-UXP transition
Explore more creative-software news on Nejma
GOT ANY QUESTIONS LEFT?
Adobe says CEP will no longer be included in flagship Creative Cloud app versions released after December 2029.
No. The transition is phased, and existing CEP plugins can continue working in supported earlier app versions. Check each vendor for future compatibility.
No. Adobe says Lightroom, Acrobat and Adobe Express are outside this flagship desktop CEP-to-UXP transition.
No. Adobe explicitly states that ExtendScript is not affected by the CEP-to-UXP transition.
