Shopify UI Extension: bundle limits and 2026 API deadline

Shopify UI extensions are getting stricter

Shopify hasn't made UI extensions slower, it has made them stricter. With the introduction of API version 2025-10, every UI extension is subject to a maximum limit of 64 KB of compressed JavaScript. Full page extensions for customer accounts get a bit more room, up to 128 KB, but the principle remains the same: this isn't a guideline, it's a real deployment gate.

Exceeding this threshold means the extension simply cannot be published. This isn't an optional best practice, it's a technical constraint that blocks production release.

The real problem isn't the limit itself

The core issue isn't the maximum allowed size, but the ability to identify in time what's bloating the bundle. Many teams only discover the problem at deploy time, when it's too late to address it calmly.

Shopify has clarified the most common causes of oversized bundles, and no exceptions will be granted for these:

• large libraries included without real necessity
• duplicate dependencies within the same bundle
• translations bundled directly into the code instead of using the native localization APIs

These are considered avoidable inefficiencies, not objective technical limitations. As a result, an app with these issues won't be able to obtain an exception to the bundle limit.

How to request an exception

If, after careful optimization, the extension still exceeds the threshold, there's an official process to request an exception. It involves:

1. Running shopify app build to generate the minified bundle
2. Retrieving the esbuild metafile generated during the build
3. Submitting both files through Shopify's official form

Each request is reviewed case by case by the Shopify team, which checks whether the extra size is genuinely justified by real functional requirements rather than code inefficiencies.

The deadline you shouldn't underestimate

Beyond the size limit, there's an equally important deadline. Starting October 1, 2026, every existing UI extension must use API version 2026-01 or later to remain deployable. Earlier API versions will no longer be supported for deploying new builds.

This means that anyone managing a portfolio with multiple apps and active extensions needs to plan the migration well in advance, rather than scrambling right before the September 2026 deadline. A late audit across dozens of extensions can easily turn into a major operational bottleneck.

Immediate action checklist

For those developing or maintaining UI extensions on Shopify, particularly checkout extensions and customer account extensions on Shopify Plus, it's advisable to act now by following these steps:

• Audit the API versions across all active UI extensions in your portfolio
• Measure the actual compressed bundle size using the shopify app build command
• Identify and remove heavy or duplicate dependencies within the code
• Migrate translation handling to Shopify's native localization APIs
• If needed, start the exception request process well ahead of the official deadline

Why it pays to act now

Postponing the bundle audit and API version migration exposes you to a real risk: reaching September 2026 with non-deployable extensions and little time to fix things. For agencies and teams managing multiple clients or apps, early planning is the only way to avoid disruptions in releases.

Those working daily on Shopify Plus projects, with teams dedicated to building checkout and customer account extensions, may want to explore specialized resources like those described on the page dedicated to Shopify development services for developers and agencies to handle the audit, optimization, and API version migration in a structured way before the 2026 deadline.