Adobe’s Plugin Shift Has a Clock. Agencies Should Start Planning
A plugin can be a small part of an app and a large part of a production day. It might batch out client graphics, organize a project, or automate a step that nobody wants to repeat by hand. So Adobe’s new timeline for moving creative-app plugins from CEP to UXP is worth putting on the production calendar, even if the migration still feels a few projects away.
Adobe plans public UXP plugin betas for After Effects by November 2026 and Illustrator by spring 2027. For those apps, CEP will be disabled by default in December 2028, then no longer included starting in December 2029. The gap gives agencies time to assess the change, ask developers what’s coming, and test new versions before an old workflow meets a new deadline.
The dates to put on the production calendar
Adobe announced the phased transition on September 29, 2026. Its migration timeline and developer guidance set out different milestones for the affected Creative Cloud desktop apps.
- By November 2026: Adobe plans a public UXP plugin beta for After Effects.
- By spring 2027: Adobe plans a public UXP plugin beta for Illustrator.
- December 2028: CEP will be disabled by default in After Effects, Illustrator, and Media Encoder. Users can turn it back on at that point.
- Starting December 2029: CEP will no longer be included in these apps.
Adobe says each flagship app will have at least two years between its UXP public beta and CEP’s removal from new versions of that app. That’s a useful window, but it isn’t a reason to leave every decision until the final year. A beta gives developers and users a place to test; it doesn’t guarantee that every CEP plugin will have a UXP version ready on the same day.
The dates above concern the affected flagship apps, not every Creative Cloud product. Adobe says Acrobat, Adobe Express, and Lightroom aren’t part of this transition. ExtendScripts are also unaffected. Those distinctions matter when an agency has a long list of extensions and scripts: a change to one plugin system doesn’t automatically mean every automation needs replacing.
Start with an inventory, not a rewrite
The first step is a list, not a code migration. Agencies can record each plugin in use, the app and project where it appears, the people who rely on it, and the task it performs. A plugin that saves seconds on an occasional mockup belongs on the list. So does the one that keeps a complicated daily handoff from turning into a manual checklist.
For each item, note whether it’s CEP-based, who maintains it, and what happens if it stops working. Include client-facing work as well as internal templates and production files. Older projects deserve attention too: a team may need to reopen and revise an archive long after its original delivery, which is an inconvenient time to discover that a familiar panel has gone missing.
Then ask the plugin developer for a clear migration plan. Is a UXP version planned? When might it be available for testing? Will it support the same tasks and settings? Does it require a new installation or a different way to work? A brief answer can help; “we’re looking into it” is a status update, but it’s not yet a schedule.
That inventory also helps teams prioritize. A production-critical plugin with no published plan deserves attention sooner than a rarely used add-on with a straightforward alternative. Agencies can group dependencies by app, workflow, and deadline, then assign someone to track the open questions. It’s basic project management, which is often where technology plans go to become useful.
Test the workflow the plugin supports
Adobe says UXP and CEP have different architectures, so a migration may not be a direct, one-to-one port. A developer might need to adopt a UXP-supported pattern or change how a feature works. Adobe also points to webview and hybrid plugins as ways to bridge some of the current differences. Those options can help, but they don’t prove that a particular agency workflow is covered.
That’s why testing a successful install isn’t enough. A plugin can open in the app and still miss a key step, produce a different output, or require users to change a sequence they’ve used for years. Each pilot should test the job itself, using a representative project rather than a tidy demo file designed to make everything look cheerful.
For an After Effects plugin, that might mean running a real project through the full sequence of setup, iteration, rendering, and review. For Illustrator, it could mean trying the plugin on a client asset with the layers, naming rules, and export needs the team encounters in regular work. Teams should record what the plugin does, what takes longer, what breaks, and what workarounds are needed.
Keep those tests small enough to manage and realistic enough to matter. A project lead can name one or two frequent users, agree on the tasks to check, and write down the approved version and any limitations. That gives the next person something better than a whispered warning near the coffee machine.
Plan for the transition in stages
Agencies can use the milestones to set internal checkpoints. First, complete the plugin inventory and ask developers about their plans. Next, identify the most important dependencies and arrange pilots as UXP betas become available. Before December 2028, review which CEP-based plugins are still in production and make a plan for the ones without a tested replacement. Aim to finish the key workflow checks before CEP is no longer included in December 2029.
Teams should also tell project staff which plugin versions are approved, where to find them, and whom to contact if a familiar step changes. That information can live alongside the project’s production notes. If a replacement has a new setup process or a temporary limitation, say so plainly. People can adapt to a changed tool more easily when the change isn’t discovered halfway through a client delivery.
Adobe’s timeline doesn’t require agencies to rewrite everything today. It does give them a reason to find out which parts of production still depend on CEP, and to start testing before a deadline makes the choices for them. A little planning now can keep the eventual switch from arriving as a surprise in the middle of a very ordinary Tuesday.