Adobe’s UXP Transition: A Practical Plugin Checklist for Creative Teams
A production plugin rarely gets much attention when it’s working. It just opens the right panel, moves the files along, or saves a few repetitive steps. The trouble starts when that quiet helper depends on technology its host app is preparing to retire.
On September 24, 2026, Adobe outlined a phased transition from CEP, its older plugin platform, to UXP. For agencies, the headline is not that every existing plugin stops working in March. It’s that app-by-app milestones are beginning, and the right time to check dependencies is before a deadline lands in the middle of a delivery week.
What Adobe announced—and what it doesn’t mean
UXP is Adobe’s newer platform for plugins in its desktop apps. Adobe has already introduced it in several applications and is expanding support to others as part of a multi-year move away from CEP.
The transition applies to Adobe’s desktop flagship apps—not every Adobe product. Adobe says Acrobat, Adobe Express and Lightroom aren’t affected by this announcement. That distinction matters when a studio’s tool list includes more than one kind of add-on.
The March 2027 Photoshop milestone is also narrower than it may sound: starting that month, Adobe’s marketplace won’t accept new CEP plugin submissions for Photoshop. It isn’t a general shutdown date for existing plugins. Adobe says marketplace plugins already listed can continue working and receive updates during the transition.
In other words, a submission cutoff is not the same thing as a plugin suddenly vanishing from a production setup. The calendar still matters; it just needs the right label.
The dates production teams should put on the calendar
Adobe’s plan is phased by application. A useful calendar should track the milestones that affect the apps and plugins a team actually uses, rather than treating “the CEP deadline” as one universal date.
- Media Encoder: A public UXP beta is available.
- Premiere: UXP plugins are available.
- After Effects: Adobe expects a public UXP beta by November 2026.
- Photoshop: New CEP plugin submissions to Adobe’s marketplace stop in March 2027. CEP plugins are set to be disabled by default in December 2027.
- Illustrator: Adobe expects a public UXP beta by spring 2027.
- InDesign: UXP plugins have been available since 2023. Adobe expects general availability for hybrid plugins in summer 2027.
For other apps, Adobe lists later milestones: Premiere stops accepting new CEP submissions in December 2027, while InDesign follows in January 2028. After Effects, Illustrator and Media Encoder reach their new-submission milestone in December 2028. CEP is set to be disabled by default in these apps in December 2028 as well.
Disabled by default is not the same as removed. Adobe says users can turn CEP back on after that point. The broader endpoint is at the end of 2029, when CEP will no longer be included in the affected apps. Adobe also says each app will have at least two years from its public UXP beta before CEP is removed from new versions of that app.
That leaves time to plan, but not a reason to wait for the last possible update. A plugin that needs a replacement may require testing, vendor coordination and a workflow change—not just a new installer.
A practical plugin audit for agencies
A short inventory turns a platform announcement into a manageable production task. It also helps distinguish a frequently used tool from one that only survives because nobody has volunteered to remove it.
- List the dependencies. Ask each team to record the CEP plugins it uses, the app and version they run in, and the specific job each one does. Include custom panels and tools installed outside Adobe’s marketplace.
- Mark how each plugin is distributed. The March 2027 Photoshop submission milestone applies to new CEP submissions to Adobe’s marketplace. Adobe says CEP plugins distributed elsewhere aren’t affected by that particular milestone. Distribution route doesn’t remove the longer-term need to check compatibility.
- Ask vendors for a concrete plan. Find out whether a UXP version is planned, which app versions it will support, when the team can test it, and whether all current features are expected to carry over. “We’re looking at it” is a fine conversation starter; it is not a production schedule.
- Flag complex integrations. Adobe says UXP uses a different architecture and security model from CEP, so a migration may call for new approaches rather than a direct port. Workflows involving custom file handling, other services or several connected steps deserve early attention.
- Test before changing live work. Try the updated plugin or replacement in a controlled project. Check the everyday basics—installing, opening, saving, handing off files and recovering from an error—before making it part of a production template.
For each item, record an owner and a next check-in date. A simple status such as “vendor confirmed,” “testing,” or “replacement needed” is more useful than a sprawling spreadsheet that becomes another plugin nobody opens.
What teams can keep using—and what to verify
Existing marketplace plugins aren’t automatically switched off at the March 2027 Photoshop submission deadline. Adobe says listed plugins can keep working and receive updates during the transition. When CEP is disabled by default in Photoshop in December 2027, users can turn it back on. That is a bridge, not a promise that every plugin will work indefinitely in every future app version.
Plugins distributed outside the marketplace aren’t covered by the March Photoshop submission rule. That’s worth noting for in-house tools and vendor portals, while still checking their support plans directly. And ExtendScripts are not affected by this transition, according to Adobe.
For specifics, Adobe’s September 24 announcement is the reference for the published milestones. Plugin vendors are the people to ask about an individual tool’s compatibility, migration status and supported versions. The general roadmap can tell a team when to pay attention; it can’t confirm whether a particular panel will behave on a particular workstation.
Plan the handoff before it becomes urgent
The sensible approach is to treat the move as a staged compatibility project: inventory what is in use, check dates by application, talk to vendors, and test changes outside live work first. The transition is spread across several years, but the useful planning starts before a plugin becomes a surprise dependency.
Agencies already have plenty of handoffs to manage. Keeping plugin changes visible and assigned gives teams a better chance of making them on their own schedule—not during the sort of deadline that makes even a “quick update” feel optimistic.