Function Scenario Guide

How to Translate a Shopify Store for Free in 2026

Translate a Shopify store at no app cost with Translate & Adapt: the 8-or-2 language cap, Auto-sync that stays off until you enable it per language, and the four gaps that still need another tool.

Sofia Ricci
Beauty & Fashion Localization

Specializes in beauty and fashion brand voice across languages.

AudienceShopify merchants localizing on a limited budget
TopicFree Translation
Year2026
Summary

Get a second and third language live without paying an app subscription — and know exactly where the free path stops.

Translate & Adapt installs itself the moment you add a language, and Shopify's AI translation fills in content that hasn't been translated yet. There is no per-word invoice and no second app to buy.

What's capped is how many languages can be translated automatically, not how much text you push through — so the real planning question is which markets get the automatic slots.

Standard product, collection, page, blog and theme content is covered. Images, tags, collection filters and most third-party app text sit outside the app entirely.

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.

Automatic translation now ships with Shopify

Translate & Adapt installs itself the moment you add a language, and Shopify's AI translation fills in content that hasn't been translated yet. There is no per-word invoice and no second app to buy.

The free ceiling is a language count, not a price

What's capped is how many languages can be translated automatically, not how much text you push through — so the real planning question is which markets get the automatic slots.

Free covers the catalog, not the edges

Standard product, collection, page, blog and theme content is covered. Images, tags, collection filters and most third-party app text sit outside the app entirely.

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: Product titles and descriptions, Collection titles and descriptions, Pages and blog posts, Theme and storefront text, and Menus and navigation.

Important layer: Legal policies, which can't be auto-translated, URL handles: typed by hand for each language, because automatic translation skips them, Fields you choose to write yourself, and Any language that has used up the automatic slots.

Translated automaticallyPriority: High
  • Product titles and descriptions
  • Collection titles and descriptions
  • Pages and blog posts
  • Theme and storefront text
  • Menus and navigation
Manual onlyPriority: Medium
  • Legal policies, which can't be auto-translated
  • URL handles: typed by hand for each language, because automatic translation skips them
  • Fields you choose to write yourself
  • Any language that has used up the automatic slots
Outside the appPriority: High
  • Product images
  • Tags
  • Collection filters
  • Forms built with the Shopify Forms app
  • Manual payment method instructions
  • Third-party app content that isn't a Shopify translatable resource
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.

Spending language slots on the wrong marketsHigh

Wrong example: Auto-translating your four biggest markets first, then finding the cap blocks the launch that actually matters.

Better approach: Rank markets by revenue potential and current traffic, then assign automatic slots in that order.

Business impact: Removing a language doesn't free the slot, so a bad assignment can cost a market launch.

Assuming Auto-sync is already onHigh

Wrong example: Turning on a language and expecting new products to translate themselves.

Better approach: Auto-sync is off by default and runs once a week; enable it per language and expect the first run up to a week later.

Business impact: New products sit in the source language for days and read as unfinished.

Publishing before the legal pages are writtenHigh

Wrong example: Launching a market with machine-translated terms and refund policies.

Better approach: Legal policies can't be auto-translated; finish them before the market goes live.

Business impact: Compliance exposure and avoidable refund disputes in the new market.

Treating a full progress bar as finishedMedium

Wrong example: Assuming everything is translated because the app shows all languages complete.

Better approach: Images, tags, filters and third-party app text sit outside the app and need a separate audit.

Business impact: A storefront that reads as half-translated exactly where buyers make decisions.

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.

Translate & Adapt with automatic translation / Manual translation inside Translate & Adapt / CSV export and re-import

Translate & Adapt with automatic translation

Advantage
  • No app cost and no per-word billing
  • Installs automatically with the language
  • Auto-sync keeps translations current once you enable it per language
Limitation
  • Capped at 8 languages where the app shows Translate now, 2 elsewhere
  • Weekly cadence rather than real time
  • Doesn't reach images, tags, filters or non-standard app content

Manual translation inside Translate & Adapt

Advantage
  • No language cap — add as many languages as Markets supports
  • Full control over wording in every field
  • The only free route for legal policies, which can't be machine translated
Limitation
  • Every field is typed by hand
  • Effort scales with catalog size
  • No glossary enforcement across thousands of products

CSV export and re-import

Advantage
  • Reaches translatable resources the app search doesn't surface, such as metafields
  • Good for one bulk pass before launch
  • Free
Limitation
  • No diffing or change tracking
  • Errors are hard to spot in a large sheet
  • Re-running after catalog changes is manual work
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.

  • Add the language in your Shopify settings — Translate & Adapt installs automatically when a language is added.
  • Check whether the app shows Translate now for your store: that decides whether you get 8 automatic languages plus Auto-sync, or 2 without it.
  • Rank your markets by revenue potential and assign the automatic slots in that order, because a slot can't be reassigned later.
  • Run Translate now for the first language and review the machine output on your 20 best-selling products before publishing.
  • If your store has Auto-sync, turn it on per language so weekly updates keep pace with catalog changes instead of drifting.
  • Write or commission the legal policies before publishing the market — they can't be machine translated.
  • Enter a translated URL handle for each language by hand, because automatic translation skips handles, then open a localized product URL in the browser to confirm it resolves. The products segment of the path can't be translated.
  • Export a CSV for metafields and any other resource the app search doesn't list.
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.

  • Localizes product metafields and metaobjects the Translate & Adapt app can't surface in its own search
  • Translates product images and alt text, not only the text fields around them
  • Covers third-party app content such as reviews, loyalty widgets and chat
  • Keeps terminology consistent across large catalogs with glossary and custom prompts
  • Runs continuous sync for catalogs too large to re-translate by hand every week

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.

Is Translate & Adapt really free?

Yes. It ships with Shopify and has no app subscription or per-word charge. What's capped is the number of languages you can translate automatically, not the amount of text you translate.

How many languages can I translate for free?

If the app shows Translate now, up to 8 beyond your default language, and Auto-sync comes with it. That's normally the case in Austria, Belgium, Canada, Denmark, France, Germany, Ireland, Italy, the Netherlands, Spain, Sweden, Switzerland, the UK and the US, but the button is the real test: stores in other countries can qualify too. Stores that only see Auto-translate get 2 languages and no Auto-sync.

Does it translate new products automatically?

Only when Auto-sync is switched on for that language, and it runs once a week. Otherwise you press Translate now, and it fills in whatever is missing at that moment.

Can I translate into Tagalog for free?

No. Tagalog (Filipino) is one of 14 languages the app can't translate. Those languages need manual translation or a third-party translation app.

What breaks first as the store grows?

Images, tags, collection filters, metafields and third-party app content — none of which the app reaches, so they stay in the source language while the rest of the store looks finished.

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.