top-wave-image

The new version of Creative Cloud is out – where are your plug-ins?

Wed Nov 12 at 10:37 am

We just released our plug-ins – BarcodeMaker, PatternPack, and DataLinker – for Creative Cloud 2026 last week. As always, they came out just a few days after Adobe’s new versions of the host apps went live. And like clockwork, the moment those apps hit the update servers, our inbox fills with one question:

“Where are my Teacup plug-ins?”

The short answer: they’re coming. The slightly longer one is worth unpacking.


Why You Need to Update at All

You might wonder why Teacup plug-ins don’t just roll over automatically to new Creative Cloud versions. After all, plenty of extensions do.

The reason comes down to how Adobe’s apps can be extended. Adobe offers a variety of ways to integrate plug-ins and automation, and we use several of them: C++, ExtendScript, CEP, and UXP, among others.

Some of these technologies, like CEP or UXP, don’t need much attention when a new version of Creative Cloud rolls out. But C++ plug-ins absolutely do – and that’s where things get tricky.

Because our InDesign and Illustrator plug-ins rely heavily on C++, each new Creative Cloud version requires a rebuild and a new installer. That dependency cascades through everything else, which is why those plug-ins appear to “disappear” until we release updated builds.

By contrast, BarcodeMaker for Photoshop and Express doesn’t rely on C++, which is why those versions usually keep working even after a major update.


Why the Updates Don’t Arrive on Launch Day

Adobe does a great job of giving developers access to pre-release versions of their APIs months in advance. We use that time to get a head start on compatibility, testing, and fixing any big issues.

But there’s always a catch – or rather, a few small ones:

  • Installer dependencies: Our Windows installers require a unique identifier that Adobe doesn’t release until the official launch day. Without that, we can’t finalize or test the installer builds.
  • App-level bugs: Occasionally, the shipping version of InDesign or Illustrator includes new issues that didn’t exist in the pre-release builds. We sometimes need to wait for Adobe to patch those before we can safely ship.
  • Our own bugs: Sometimes the delay is simply us – tight deadlines, test failures, or internal roadblocks. We’d rather take an extra day or two and release something stable than rush out a build that causes problems.

In short, it’s not that we’re dragging our feet – it’s that we’re making sure your tools actually work the way they’re supposed to.


Keeping Your Workflow Moving

Every year, the Creative Cloud update cycle keeps us on our toes. And every year, we aim to get our plug-ins out as quickly as possible – stable, tested, and ready for real-world work.

The good news? The 2026 versions are live, tested, and ready to roll. You can download them now at www.teacupsoftware.com.

Here’s to another year of creative automation that just works – no matter how many times Creative Cloud changes its number.