Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The combined 256 KB cap is removed for all apps with UI extensions, across all API versions.
- Each locale file remains subject to a 30 KB limit; a large aggregate total can pass this specific check, but an oversized file cannot.
- Restore trimmed languages in the extension's locales folder, deploy a new app version, and preview the added locale in a development store.
- This change concerns UI extension strings, not storefront Translate & Adapt language slots or unrelated deployment requirements.
The combined 256 KB ceiling is gone
On October 30, 2026, Shopify removed the 256 KB combined-size limit for UI extension locale files. It applies to every app with UI extensions, on all API versions.
Existing extension versions keep working. If your files were below 256 KB, no action is required; this update does not require a rewrite or redeploy.
The 30 KB limit still applies to each file
Only the aggregate limit is gone. Each individual locale file still has a 30 KB limit, and the change does not remove other deployment constraints.
Hypothetical example: ten 27 KB files total 270 KB. Each is below 30 KB, so the old 256 KB combined ceiling would have blocked the deploy; that total alone no longer does. One 31 KB file still exceeds the per-file limit.
Restore locales with existing conventions
If you removed languages or shortened translations to fit, put the needed files, such as de.json or pt-BR.json, back in locales. File format, naming, and fallback behavior are unchanged.
These files localize UI extension strings, separately from storefront Translate & Adapt. The announcement does not expand an automatic-translation service or its language allowance.
Keep a default locale too. Shopify's checkout guide uses en.default.json as its example; it supplies the language when no other appropriate locale matches. To change the default, name the corresponding file [locale].default.json rather than marking every locale as the default.
New locales need more than translated fixed text. Review numbers, currencies, and plural forms. The checkout guide demonstrates number and currency formatting and plural keys such as zero, one, and other. Removing the aggregate cap does not create that localized content for you.
Deploy and preview
Run shopify app deploy, then preview the extension in a development store with its store or customer locale set to a language you restored. Confirm the extension strings appear.
If translated strings are missing, check the active preview locale and file naming. The checkout guide also requires adding and publishing a second language in the development store and activating it in the primary market.
Preview a language you actually restored, check the strings you previously trimmed, then switch back to the default language for comparison. Confirm file restoration, deployment, and visible translated strings separately so an unchanged preview locale is easier to spot.
Access and other checks are unchanged
The update does not announce a change to fees, geography, or extension eligibility. Checkout UI extensions on the information, shipping, and payment steps remain Shopify Plus-only, per Shopify's guide.
Sources
Frequently Asked Questions
Which language appears when no locale matches?
The checkout localization guide uses the extension's configured default locale. Its file is named [locale].default.json, such as en.default.json. This update leaves fallback behavior unchanged.
Can regional locale files still use names such as pt-BR.json?
Yes. The announcement explicitly lists pt-BR.json and de.json as files you can restore and says naming conventions are unchanged. Keep them in the extension's locales folder.
Will Shopify generate the new translations for me?
This change removes the combined file-size limit; it does not announce a new automatic-translation capability. Maintain restored or additional extension strings through your existing localization workflow.