Webflow Localize and the wxrks connector
Webflow Localize translates your site with general-purpose AI agents, while wxrks brings a team of specialized AI agents. On top of that, you can add human review wherever you need it and keep one translation context for everything you translate, not just your website. Here is how they compare, and what each costs.
Webflow's built-in AI translation, extended on September 29, 2026.
Your Webflow content, translated in wxrks and delivered back by the connector.
Both options are agentic: both monitor your site, translate, and let you set tone and formality per language. wxrks adds five agents that Webflow does not have, for meaning, reasoning, quality, and quoting and allocating human review, and takes tone further with Sous-Chef.
Webflow Localize only
Webflow Localize + wxrks
Both have itOnly in wxrksNot in Webflow Localize
Webflow Localize only
Webflow Localize + wxrks
Context Sensitivity follows the steps a human translator takes: read, remember, prioritize, decide.
In wxrks the model does not translate from scratch. It weighs what your team has already approved and suggests what you are most likely to confirm. What it learns stays in your account, not in the model, so changing models loses nothing. On Webflow, one model chosen by Webflow translates directly, and Webflow can switch it: it replaced Amazon's machine translation with Gemini in May 2026. When the model changes, your translations can change with it.
All prices use yearly billing, the cheaper option on both sides. Words are spread evenly across the year, because Webflow's word allowance resets every month. Webflow does not publish how many AI credits a word uses, or what Enterprise costs. The Enterprise estimate grows with your site: a base from public reports that put contracts at $40,000 to $50,000 a year to start, covering up to 10 languages at the Advanced allowance; each language beyond 10 adds Advanced's list price ($348 a year); and AI words beyond the allowance cost Advanced's list rate ($0.58 per 1,000 words). A real contract may discount this. Both paths pay Webflow Localize to publish your languages; the Webflow site plan is left out of both. On wxrks, the range runs from no extra machine translation to all of it billed at the plan's overage rate. Linguist review is priced per project, so it starts at $0 here.
| Webflow Localize only | Webflow Localize + wxrks | |
|---|---|---|
| What else it translates | Nothing beyond this Webflow site | Documents, software and code, subtitles, dubbing, audio and video, design files, and other CMSs such as Contentful, Drupal and Zendesk |
| Your context | Memory and settings stay inside this one site | One memory, glossary and style for all of it, also open to your AI assistants through the wxrks MCP |
| Agents | Two: one monitors your content, one translates | The same two, plus meaning (Context Sensitivity), tone (Sous-Chef), reasoning, quality (Smells), and quoting and allocating human review |
| Tone and voice | Formality and one of four tones, set per language | Sous-Chef: audience, tone, formality, your own rules and creativity, per account, project or language |
| Translation engine | Google Gemini, chosen by Webflow (since May 2026) | You choose. Default: Context Sensitivity, a layer that matches your context, running on OpenAI models |
| Choose the model | No | Yes, per task, on Fusion and above |
| When the model changes | Webflow switches it for everyone; quality can change with it | You decide; memory, glossary and reviewer decisions carry over |
| How the AI is used | The model translates each text directly | Works like a human translator: reads, recalls your approved translations and glossary, ranks them, then the model decides |
| What goes onto your page | The model's output, as it comes | A translation grounded in your approved work; it goes live directly or after a reviewer, as your settings decide |
| Setup | None; built into the Designer | A Webflow app connected to a wxrks account |
| Human translation, post-editing, review | No | Yes, any wxrks workflow |
| Who reviews | Your team, in the Designer, in one-time mode only | Professional linguists, in the wxrks editor |
| Keeps languages in sync with edits | Yes, in continuous mode | Yes, on a schedule you set |
| Edit translations while syncing | No, they are locked | Yes, in wxrks |
| Translation memory | This site only; can't be viewed or edited | Shared by everything you translate; editable |
| Glossary | Enterprise only | Every plan |
| What you can exclude | Whole pages or just their SEO text, components and their properties, CMS Collections or single CMS fields | Any page, folder, Collection or component you don't send; single CMS fields and component properties, also by keyword |
| Exclusion rules | Per language, and per automatic or manual translation. Individual CMS items can't be excluded | Per CMS item in recurring pulls: category, author, tags, status, dates or a yes/no field, plus translated before or never sent |
| SEO title, description, Open Graph | Yes | Yes |
| Text inside images | No | Yes, approved by a person |
| History and restore | Reset a field to the original | Every delivery kept; redeliver or restore the original |
| AI disclosure (EU AI Act) | No | Yes: optional flag on AI-translated content, plus a human vs AI report |
| Vendor and cost management | No | Yes |
| Volume before a custom plan | 500,000 AI words a month | 120 million words a year |
| Price beyond the allowance | AI credits; no published rate per word | Published price per word |
| Allowance period | Word balance resets every month; AI credits don't roll over either | Yearly word allowance |
Using both? Keep Webflow's automatic translation on one-time mode, or off, for the languages wxrks delivers. Its continuous mode replaces translations that come from an app.
Public list prices on September 30, 2026. Webflow: pricing, AI translation usage, AI credits, automatic translation launch, Gemini translation engine, Enterprise glossary. wxrks: pricing.
Enterprise estimate: Shadow Digital, Vendr, SpendHound.
Make it wxrks
