Shopify has had a native multi-language framework since 2020, and most store themes include a currency selector too. So the question for a store expanding beyond one language is no longer “is this possible” but “which app owns the translation workflow, and how is it going to charge me.” The answer splits into three pricing shapes: per-word subscriptions where the app bundles the translation engine (Weglot, Transcy), flat tiered plans priced by product count or language count (Langify, Translate My Store, LangShop), and the newer “bring your own engine key” model where the app is the UI and you pay DeepL, Google, or ChatGPT directly (T-Lab).

Each of those shapes suits a different store size and translation volume. For a shop launching into one extra market with a tight catalog, a free or near-free plan from any of these covers the first phase. For a store with a thousand SKUs and three live languages, the pricing model is the single biggest cost variable in the stack, and the picks below reflect that spread.

Key Takeaways
1
Translation apps on Shopify charge in three distinct ways: per translated word, flat tiered plans, or BYO engine key. Pick the one that scales with your word volume.
2
AI translation (DeepL, Google, GPT) is a draft, not a finished product. A professional review pass still earns its keep in a market you care about.
3
Shopify’s native multi-language layer covers product fields and theme strings. A translation app still owns the hard parts: image text, third-party app content, SEO signals (hreflang), and the switcher UX.

How Shopify Translation Apps Price Themselves

The three pricing shapes mentioned above look alike on a feature list but behave very differently as a store grows.

Per-word subscriptions are the classic model: the app charges you by the volume of translated text, usually bundled with a hosted translation engine. Weglot and Transcy are the clearest examples. The math is easy at low volume, but a store with large collections and long product descriptions tends to hit the word-count ceiling of its plan quickly and gets pushed up a tier.

Flat tiered plans price by what you have (product count, language count, feature set) rather than what the engine translates. Langify, Translate My Store, and LangShop all run this way. These suit a store whose catalog does not change much month to month: the bill is the bill, regardless of translation volume.

BYO engine key is the newest shape, and T-Lab is the clearest example. You pay the app a modest tier fee for the UI, glossary, and workflow, then you plug in a DeepL, Google Translate, or ChatGPT API key and pay that engine directly for every word it translates. For a mid-size catalog in several languages, the total bill usually lands well below a bundled per-word competitor, with the trade-off that you own one more vendor relationship.

The decision tree is simpler than it looks: short catalogs stay cheap on anything, mid-to-large catalogs usually win with BYO, and stores that want zero touch of an API account stick with a bundled plan and accept the per-word cost.

AI Translation vs Human Translation

Every modern translation app ships some version of machine translation (DeepL, Google, or OpenAI under the hood). What varies is how good the app’s defaults are and whether it leaves a path to a human review.

AI translation is a draft. For transactional surfaces (cart messages, generic shipping copy, FAQ pages), modern engines produce output a native speaker can accept without edits most of the time. For brand copy, hero sections, and anything that carries tone, the output is a very good first pass and nothing more. Shipping it unreviewed to a market you care about is a business decision, not a translation one.

Human translation sits inside most of these apps too. LangShop and Pluglin both ship a professional-translation workflow out of the box (Pluglin is the Shopify arm of Blarlo, a human-translation marketplace), and Weglot and Transcy both support ordering reviewed translations from inside the app. The right balance for most stores is machine translation on the bulk of the catalog, human review on the pages that drive the sale.

Glossaries are the quiet upgrade. Most of these apps let you lock in that your brand name is never translated, that technical terms always render the same way, that measurement units convert cleanly. A glossary is a small time investment that lifts machine output noticeably.

What To Check Before You Install One

Four things to verify on the demo or the trial, in order of how often they bite later.

hreflang and URL structure. The app should output clean hreflang tags so Google knows which page serves which language. It should also give each language its own URL (either /fr/, fr.yourstore.com, or .fr), not fire the translation in JavaScript on top of the English URL. Any app that only overlays a widget on your English pages ships no SEO value.

Language switcher placement. A switcher the shopper cannot find is as good as no translation at all. Preview the demo on mobile first; make sure the switcher is reachable one tap in, not buried in a hamburger menu.

Image and app content. Native Shopify translation covers product fields and theme strings. It does not touch text baked into images, text inside third-party apps (reviews, upsell widgets, product filters), or button labels injected by the theme. If any of those matter to your store, the app has to translate them too.

Load impact on the page. A translation layer that injects a script per language and refetches text on every page view will measurably slow the store on real-world connections. The lightest apps precompile translations into the HTML Shopify serves; the heaviest overlay JavaScript at runtime. Chrome’s Core Web Vitals tool catches this in a minute.

Our Picks: 8 Shopify Translation Apps for 2026