Function Scenario Guide

Shopify Translate & Adapt Language Limits (2026)

Why Translate & Adapt caps at 8 languages in some countries and 2 in others, which 14 languages it can't translate, and how to plan markets around the limit.

Marcus Chen
Multilingual SEO Specialist

Focuses on multilingual search intent and hreflang architecture.

AudienceShopify merchants localizing on a limited budget
TopicLanguage Limits
Year2026
Summary

Treat automatic translation as a scarce resource: decide which markets get the slots before you spend them.

If the app displays Translate now, your store can translate up to 8 languages automatically and use Auto-sync, even when it sits in a country that isn't on Shopify's list. Stores that only see Auto-translate get 2 languages and no Auto-sync.

Each language translated automatically uses one of the slots permanently. Removing a language from the store doesn't return it, and you can't move an automatic translation to a different language.

Fourteen languages, including Tagalog, Bengali and Hawaiian, can't be translated by the app at all — no slot, no workaround inside Shopify.

Why it matters

Why this translation scenario deserves its own workflow

This scenario is not just about translating a few strings. It usually shapes whether shoppers understand the page, trust the storefront, and continue far enough to convert.

The Translate now button decides the cap

If the app displays Translate now, your store can translate up to 8 languages automatically and use Auto-sync, even when it sits in a country that isn't on Shopify's list. Stores that only see Auto-translate get 2 languages and no Auto-sync.

Slots are spent, not borrowed

Each language translated automatically uses one of the slots permanently. Removing a language from the store doesn't return it, and you can't move an automatic translation to a different language.

Some languages are excluded outright

Fourteen languages, including Tagalog, Bengali and Hawaiian, can't be translated by the app at all — no slot, no workaround inside Shopify.

Translation scope

What should you translate first in this scenario?

The translation scope should follow the customer journey, not just the Shopify field list. Start with the surfaces that affect understanding and conversion first, then expand into supporting modules.

Critical layer: Any language translated with Translate now or Auto-translate, Languages re-translated after a content change, and Single-resource translations inside an untranslated language.

Important layer: New languages once all slots are used, Reassigning a slot to a different language, and Restoring a slot after removing a language.

Consumes a slotPriority: High
  • Any language translated with Translate now or Auto-translate
  • Languages re-translated after a content change
  • Single-resource translations inside an untranslated language
Blocked at the capPriority: High
  • New languages once all slots are used
  • Reassigning a slot to a different language
  • Restoring a slot after removing a language
Excluded regardless of slotsPriority: High
  • Bengali, Cebuano, Corsican, Frisian, Haitian Creole
  • Hawaiian, Hmong, Latin, Nyanja (Chichewa), Odia (Oriya)
  • Samoan, Scots Gaelic, Sesotho, Tagalog (Filipino)
Mistakes

What goes wrong most often here?

These mistakes matter because they do more than create awkward language. They make the experience feel unreliable, disconnect the workflow, or quietly reduce SEO and conversion.

Planning languages before checking the capHigh

Wrong example: Promising five markets in a launch plan before opening the app.

Better approach: Check the button label first: it tells you whether the ceiling is 8 or 2.

Business impact: A launch calendar built on the wrong ceiling usually slips by weeks.

Assuming removing a language frees a slotHigh

Wrong example: Removing a market's language to auto-translate a different one.

Better approach: The slot stays spent; plan the assignment as permanent.

Business impact: You can run out of automatic translation before the markets you actually needed.

Reassigning after the factMedium

Wrong example: Auto-translating French, then deciding you wanted German in that slot.

Better approach: Decide the order before the first translation, because a language can't be switched afterwards.

Business impact: One wasted slot permanently reduces your free coverage.

Ignoring the excluded languagesHigh

Wrong example: Planning a Philippines launch around free automatic translation.

Better approach: Tagalog is excluded; budget for manual or third-party translation instead.

Business impact: The market ships with untranslated content or misses its date.

Workflow options

Which setup fits this scenario best?

There is no single best setup for every team. The right choice is the one your team can maintain consistently as content changes and more markets are added.

Spend automatic slots on your highest-value markets / Manual translation for everything beyond the cap / Third-party translation app for the overflow

Spend automatic slots on your highest-value markets

Advantage
  • No cost per language
  • Weekly Auto-sync once you enable it per language
  • Covers the standard catalog fields completely
Limitation
  • Permanent assignment per language
  • 8 or 2 slots depending on whether the app shows Translate now
  • Weekly rather than on-demand, and off by default

Manual translation for everything beyond the cap

Advantage
  • No language limit
  • Works for the excluded languages
  • Full editorial control
Limitation
  • Manual effort on every field
  • Doesn't scale past a few hundred products
  • No automation for new content

Third-party translation app for the overflow

Advantage
  • No Shopify-side language cap
  • Covers excluded languages and structured content
  • Can automate sync far more often than weekly
Limitation
  • Costs money, either subscription or usage
  • Adds another system to manage
  • Needs a migration plan if you later consolidate
Checklist

What should you verify before launch?

If you are ready to publish this scenario, treat the steps below as one release checklist instead of a few disconnected settings.

  • Open Translate & Adapt and check whether the button says Translate now or Auto-translate.
  • List the markets you sell into and rank them by revenue, not by how easy they look.
  • Assign automatic languages to the top 8 or top 2 in that order, then stop.
  • Check whether any target language is on the excluded list before you promise the market internally.
  • If your store has Auto-sync, turn it on for each assigned language: it's off by default and the first run can be up to a week away.
  • Confirm what happens to a language slot before you ever remove a language.
  • Plan the overflow markets for manual translation or a third-party app from day one.
Ciwi

What Ciwi helps automate here

If you want this scenario to become an ongoing workflow instead of a one-time cleanup, these Ciwi capabilities are the parts that usually help most.

  • Translates languages beyond the Translate & Adapt cap, including the 14 Shopify excludes
  • Keeps a glossary so terminology doesn't drift across markets added later
  • Syncs new and edited products continuously instead of on a weekly cycle
  • Covers structured content such as metafields and metaobjects alongside standard fields
  • Lets you consolidate several apps' worth of translation into one workflow

See how Ciwi AI Translator handles this scenario →

Next topics

What should you read next?

Once this page is handled, the next step is usually a cluster of adjacent Shopify surfaces. These related topics help turn one translated page into a fuller multilingual workflow.

FAQ

Frequently asked questions

The questions that come up while doing the work, not before starting it.

Why does Translate & Adapt allow 8 languages in some stores and 2 in others?

The app's own signal is the test. If it shows Translate now, you get up to 8 automatic languages plus Auto-sync, even when your store is in a country that isn't on Shopify's list; the 14 listed countries are simply where that's normally available. Stores that only see Auto-translate get 2 languages, and Auto-sync isn't offered.

Does removing a language give the slot back?

No. Removing a language from your store doesn't reset the limit, so treat every automatic translation as a permanent allocation.

Can I switch an automatic translation to a different language later?

No. Once a language has been translated automatically, it can't be switched to another language. Choosing the order is a one-time decision.

Which languages can't be translated at all?

Bengali, Cebuano, Corsican, Frisian, Haitian Creole, Hawaiian, Hmong, Latin, Nyanja (Chichewa), Odia (Oriya), Samoan, Scots Gaelic, Sesotho and Tagalog (Filipino).

What happens when all slots are used?

Automatic translation becomes unavailable for any other language. You can still add languages manually, or use a third-party translation app.

Next step

Ready to operationalize this workflow?

Start with the Shopify surfaces that affect UX and conversion most, then scale the workflow into more markets and content types.