Langify vs. Translate & Adapt: Is the Free Native App Enough?
Translate & Adapt wins the Langify matchup for most mid-market stores: the native app is free, covers manual plus basic auto translation, and stores every string portably in Shopify. Langify earns its subscription only when a named workflow gap survives a one-locale trial. Past roughly three locales, the better upgrade is an owned AI translation pipeline at $10,000–$30,000 (Deploi estimate, illustrative), not a rented editor.
Your profile — see how the verdict shifts
- Confidence
- High — A free native baseline with portable storage sets a high bar, and Weglot's early-2026 delisting made this category's vendor risk concrete (July 2026 research)
- Reference scenario
- $20M–$100M GMV · 1–3 extra languages · standard catalog · agency dev bench
- As of
- August 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| One extra language, stable catalog | WAIT | Translate & Adapt covers a single locale for free, and the strings stay in Shopify. A subscription here buys convenience you haven't missed yet. |
| 2–3 languages, quarterly content updates | WAIT | The native workflow strains a little at review time, but named gaps stay rare at this tempo. Log frictions for a quarter before paying anyone. |
| 3–5 languages, content-heavy catalog | CUSTOMIZE | Content velocity, not editor depth, becomes the bottleneck here; an owned AI pipeline feeding native storage beats renting a workspace, which is the parent translation verdict. |
| Daily translation ops with dedicated editors | DEPENDS | Langify's workflow depth can pay for itself in editor hours at this tempo. Run a one-locale trial and buy only the gaps that survive it. |
What Langify vs. Translate & Adapt (native, free) Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Revenue — direct | High | Localized storefronts convert international traffic that bounces off English-only pages; both lanes deliver that baseline, so the increment rides on coverage and quality, not on which editor you used. |
| Customer experience | High | Shoppers read sizes, policies, and checkout copy in their own language; one untranslated surface mid-journey costs more trust than a slightly plainer translation ever will. |
| Data & insight | Medium | Where translations live decides what you can reuse: native storage keeps strings queryable and portable for the next search surface, product feed, or AI shopping integration. |
| Operational efficiency | Medium | The matchup's live variable is hours per locale per release cycle; a paid workspace only pays when it provably shrinks that number for your team. |
| Revenue — indirect | Medium | Translated pages earn international organic visibility over time, and strings stored in Shopify keep serving that surface through theme changes and replatforms. |
Spend ceiling: Free covers the baseline, so every translation dollar needs a named gap: pay for workflow depth only when the editor hours it saves beat the fee, and move real money only at the pipeline milestone.
What buying enables (top apps)
- + A translation-first workspace with deeper manual control than the native editor's basics
- + Vendor support for localization edge cases, so translation problems come with a help desk
- + One subscription instead of any build work: no bench required at any point
What building additionally unlocks
- + Translations stored natively in Shopify: portable, queryable, and reusable by any future stack with no export step
- + A zero line item, which funds the upgrade that matters: an owned AI pipeline past three locales ($10,000–$30,000, Deploi estimate, illustrative)
- + No third-party script or switcher in the storefront's rendering path
- + First-party cadence: native translation improves with Shopify releases, at no migration cost to you
Find Your Verdict in 3 Questions
Is your store live in three or more extra languages, or heading there this year?
Yes: Go to question 2.
No: Your verdict: WAIT — enable free Translate & Adapt, ship your locales, and revisit only when a workflow gap has a name and a weekly cost.
Does a dev bench exist, agency or in-house, that could run an AI translation pipeline into native storage?
Yes: Your verdict: CUSTOMIZE — feed machine translation through an owned glossary and review flow into Shopify's storage; a rented editor stays optional.
No: Go to question 3.
Has a one-locale trial of Translate & Adapt surfaced gaps your team can name and price?
Yes: Your verdict: BUY — Langify covers named workflow gaps; diary an annual re-check, because native translation keeps improving.
No: Your verdict: WAIT — stay on the free native app; unnamed gaps don't justify a permanent subscription.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | Both lanes start fast: Langify installs and configures in days, while Translate & Adapt is already in the admin waiting to be enabled. | ||
| Recurring fees | Langify bills monthly for as long as it runs; the native app is free on every plan, with human review hours as the only recurring spend. | ||
| Maintenance & upgrades | The vendor maintains Langify against platform changes; Shopify maintains Translate & Adapt as first-party software, the lowest-maintenance seat in the stack. | ||
| Switching & exit | Leaving Langify means re-homing translations into native storage with a per-locale content freeze; native strings never need to move. | ||
| Risk | |||
| Vendor risk | The category's former default, Weglot, was delisted from the App Store in early 2026 (July 2026 research); first-party software carries no equivalent mortality. | ||
| Security & compliance surface | Translation apps touch content more than customer data, so the surface is modest; the native lane still adds no third party at all. | ||
| Platform-deprecation exposure | Apps track Shopify's roughly six-month API version cycles from outside the platform (July 2026 research); Translate & Adapt moves with the platform by definition. | ||
| Value | |||
| Fit to requirement | Honest split: Langify's translation-first workspace runs deeper than the native editor's basics, and most 1–3-locale stores never use the depth they'd be paying for. | ||
| Time to market | Neither lane keeps you waiting, and the native app skips even the install step; auto translation drafts a locale the day you enable it. | ||
| Performance & scale | Native translations render with the theme and add nothing to the request path; an app layer is one more storefront surface to keep fast. | ||
| Data ownership & AI-readiness | The decisive dimension: Translate & Adapt writes to Shopify's portable translation storage, keeping strings queryable for search, feeds, and AI surfaces; app-held strings need an export step. | ||
| Focus & opportunity cost | The native lane is the do-nothing option that works; a subscription adds one more vendor to manage for a capability the platform already covers. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Langify | Live — Long-running independent app in the native-storage lane | Monthly, flat-tiered | Teams with named manual-workflow gaps the free editor can't close |
| LangShop | Live — Broader localization suite: translation plus currency and locale switching | Tiered by plan and languages | Renting machine-translation volume without building a pipeline |
| Translate & Adapt (Shopify) | Native — The other column on this page: Shopify's free first-party translation app, the category default since Weglot's delisting (July 2026 research) | Free on all plans (included) | Every store's starting point; 1–2 locales often never need more |
The Build Path
- Adopt Translate & Adapt as the baseline: Enable the free native app, publish locales, and run scheduled human review passes. Translations land in Shopify's own storage from day one, so nothing you do here is throwaway.
- Owned AI translation pipeline (the upgrade lane): Past roughly three locales or at high content velocity, feed machine translation through your own glossary and review flow into native storage; $10,000–$30,000 (Deploi estimate, illustrative), per the parent translation decision.
- Langify exit migration: Re-home app-held translations into native storage locale by locale, behind a short content freeze. Verify export completeness before scheduling the work.
- Effort band
- Native baseline: near-zero cost; owned pipeline upgrade $10,000–$30,000 (Deploi estimate, illustrative), the $10–25K contact-form band
- Typical timeline
- Native baseline live in days; pipeline upgrade 3–6 weeks (Deploi estimate, illustrative)
- Maintenance, honestly
- Review passes are the honest recurring cost on either lane; the pipeline adds ~15–20% of build cost per year in upkeep (Deploi estimate). No subscription line exists on the native lane.
- What you own — and what you take on
- You own: every translation string, in Shopify's storage, plus the glossary and review flow if you add the pipeline. You take on: translation quality itself, because free tooling doesn't proofread.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $300–$1,200 (install + initial passes) | $500–$2,000 (locale setup + review passes) |
| Years 1–3 (recurring) | $720–$1,800 (subscription) + review hours | $900–$2,700 (review hours only) |
| 3-year total | ≈$1,000–$3,000, plus exit re-homing later | ≈$1,400–$4,700, strings already home |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † App path: a low-tens-of-dollars monthly band held flat (illustrative), plus the same review hours both lanes need.
- † Native path: Translate & Adapt free on all plans; figures show setup and review effort, not license cost; three-year horizon.
What the Sticker Price Hides
On the buy path
- — The subscription outlives the job: translation work is front-loaded, but billing continues at maintenance tempo forever (community-reported pattern)
- — Coverage surprises surface late: the gap between a translated store and every surface translated appears after purchase; verify against your theme and apps
- — Exit means re-homing strings into native storage; export completeness and re-import effort vary and need verification
- — Vendor mortality is priced in post-Weglot: this category's default app was delisted in early 2026 (July 2026 research)
On the build path
- — Auto-translation quality still needs human review passes; budget editor hours per locale rather than assuming zero cost
- — Native workflow depth is basic, and big catalogs feel the editor's limits; that friction is exactly what apps sell against
- — Past roughly three locales the honest fix is an owned pipeline at $10,000–$30,000 (Deploi estimate, illustrative), not more manual passes
What Merchants Say
The Weglot delisting reset this category's trust: merchants now ask where the translations live before they ask about features, because re-homing strings mid-contract is the pain they just watched.
The recurring complaint shape for translation apps: coverage surprises, where the store reads translated until a checkout string, app widget, or notification shows up in English.
If You Change Your Mind Later
If you bought and outgrow it
Verify at signup, not at exit, how translations export and what re-import into native storage takes; the answer decides whether leaving Langify is a weekend or a project. Schedule any migration behind a per-locale content freeze. Weglot's delisting showed that this category's exits can arrive on the vendor's timeline, not yours (July 2026 research).
If you built and want out
Nothing strands on the native lane: translations sit in Shopify's own storage and carry to any future stack, including a paid app if a named gap ever appears. Upgrading to the owned AI pipeline later writes into the same storage, so none of the early work gets thrown away.
When This Answer Changes
We're watching for:
- ▸ Shopify upgrading Translate & Adapt's auto-translation quality or workflow depth; every release shrinks what a subscription adds
- ▸ Translation-app repricing or consolidation after Weglot's delisting; an ownership change at Langify reopens this page (July 2026 research)
- ▸ Your locale count crossing three with real content velocity; that milestone moves the money to the owned AI pipeline, not to a bigger app tier
Verdict change log:
No changes since first publication (August 2026).
Common Questions
Is Translate & Adapt a real Langify alternative?
Yes: Translate & Adapt is Shopify's free native translation app and the category default since Weglot's early-2026 delisting. Merchants get manual translation, basic auto translation, and storage inside Shopify, so every string stays portable. Langify adds workflow depth on top of a subscription. Start free, run one locale end to end, and pay only for a gap you can name.
When does Langify beat Translate & Adapt?
Langify beats the native app when translation is a daily editorial job and the free workflow measurably slows it; deeper manual control and editor conveniences are the pitch. Verify each claimed gap against your own catalog and theme before subscribing. Teams translating 1–2 languages a few times a quarter almost never hit that boundary.
What does Langify cost compared to Translate & Adapt?
Translate & Adapt costs nothing on any Shopify plan. Langify runs as a monthly subscription in a low-tens-of-dollars band (illustrative), which compounds to four figures over three years. The fee is rarely the real question: exit effort and where translations live decide the cost, and native storage keeps both at zero.
Your Next Steps
If you're going with WAIT(matches your selected profile)
- Enable Translate & Adapt and publish one full locale end to end, checkout and notification surfaces included
- Log every workflow friction with a name and a minutes-per-week cost; that list is the only valid future buy case
- Set a review cadence for auto-translated strings; quality passes are the real recurring cost on the free lane
- Diary a re-decision at three locales or a content-velocity jump; the owned-pipeline math starts there
If you're going with BUY
- Run a Langify trial against the exact gaps on your friction list, on one locale
- Verify string coverage against your theme, installed apps, and notifications before subscribing
- Get the export path and re-import effort into native storage confirmed in writing
- Cap the spend: price the subscription against the $10,000–$30,000 owned pipeline it defers (Deploi estimate, illustrative)
- Diary an annual re-check as Shopify keeps upgrading the free baseline
Official Docs & Sources
- Add language translations using the Translate & Adapt app — Shopify Help Center
- Markets — Shopify Help Center
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Should You Build or Buy Translation on Shopify?
Translation on Shopify is a CUSTOMIZE call: free native Translate & Adapt as the floor, an owned AI pipeline on the translation APIs past three locales.
Should You Build or Buy Multi-Currency & Market Pricing on Shopify?
Multi-currency is native on Shopify. The real decision is the market-pricing layer on top.
Should You Build or Buy Duties & Import Taxes on Shopify?
Duties and import taxes are a true DEPENDS: pay the merchant-of-record fee while lean, own the flow as international scales, never build the landed-cost engine.
Should You Build or Buy Cross-Border Compliance for Shopify?
Cross-border compliance is bought expertise: GPSR-class rules need specialist review per market, while your store publishes the documentation it produces.
Lifetimely vs. Warehouse LTV Models: Buy the Dashboard or Own It?
Lifetimely wins on speed and price; warehouse LTV models win once bundles, 3PL fees, and wholesale mix push app COGS off finance's books.
Ready to decide your translation stack?
We'll audit your locales against the free native baseline, and price the owned AI pipeline only if your content velocity earns it. If Langify's workflow depth genuinely fits your team, we'll say so and help you verify coverage before you sign.
Contact us todayVerdict scored for the reference scenario above. This page decides the named Langify matchup; the category-wide translation decision is its own page. Estimates are not quotes; Langify pricing is banded re-verified quarterly. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.