Is switching from a third-party translation app to Shopify's own native Translate & Adapt a genuine cost-optimization move, or does it just shift the cost elsewhere?
Shopify Translate & Adapt is free and auto-translates two languages at no charge, with unlimited manual translations beyond that (verified September 2026). Weglot, the paid comparison, runs $87/month for 200,000 words across five languages (per Weglot, September 2026). The switch converts a software fee into translation labor: a real saving at two languages, a cost transfer past that.
The criteria that decide it
| Shopify Translate & Adapt | Weglot (representative paid app) | |
|---|---|---|
| Price | Free | $32/mo (3 languages, 50k words) to $769/mo (20 languages, 5M words) |
| Machine translation included | 2 languages free | Included to the plan's word cap |
| Manual translations | Unlimited | Included |
| Coverage | Products, collections, pages, metafields, SEO fields including URL handles | Full-site including dynamic and third-party content |
| Language ceiling | 20 on Basic/Grow/Advanced, 30 on Plus (platform limit) | Plan-dependent |
| Store rating | 4.5★, 1,435 reviews | — |
(Shopify figures verified September 2026 against the app listing and Shopify's Markets documentation; Weglot per its pricing page, September 2026.)
Where the cost actually goes
Past two languages, Translate & Adapt stops auto-translating for free. Your options become a paid machine-translation source pasted in manually, or human translators, or an agency. Either way the spend moves from a predictable monthly subscription to a per-word or per-hour cost that spikes with every catalog expansion. And that is the part the "it's free" framing omits.
There is a second, quieter cost. Merchants consistently report the interface as slow to work in at catalog scale, and third-party content (apps, custom sections, email templates) does not always get picked up (community-reported via the app listing's reviews, 2026). A 400-SKU catalog across four markets is a different job in a native editor than in a tool built for translation workflow.
The verdict, and the profile it fits
Switch if you run two translated languages, your catalog is stable, and your content lives in native Shopify objects. That merchant genuinely saves the full subscription and takes on almost nothing. This is a common shape: a Canadian or US brand running English plus one European language.
Stay on the paid app if you run three or more languages, launch products weekly, or depend on translated app-generated content. There the subscription is buying workflow (translation memory, glossaries, reviewer roles, and change detection on updated source copy), and replacing it with a native editor means someone on your team now owns that workflow manually.
Say the quiet part: for a store at four-plus languages with frequent catalog change, switching to save $87 a month is a false economy, and we would not recommend it.
The Deploi point of view
Our own position, from building on Shopify. Separate from the facts above.
- Our take: Translation is a content-operations problem wearing a software costume. Whoever owns keeping translations current after launch determines whether this switch saves money or just relocates it onto a marketing coordinator's week.
- What we’ve seen: The failure mode after a switch is drift. Source copy changes, the translation doesn't, and nobody notices for a quarter because nothing breaks: the page just quietly reads wrong in one market. Paid tools flag that; the native editor doesn't.
- Where we disagree: "Native is free" is the wrong comparison. The comparison is total cost of keeping four locales accurate for a year, and on that basis native wins clearly at two languages and loses at five.
- What this page adds: that one of the parent's native swaps has an ongoing labor cost rather than a one-off build cost, which makes it the exception in the stack.
Reviewed by Martin Dejnicki, Director of SEO & AI Search. Facts verified 2026-09-13.