AI translation for Webflow: your whole site in every language

Yes. LATW Cloud connects to your Webflow site with a site token, reads your pages, CMS items, components and products, translates them with AI and writes the translations into the languages of Webflow Localization. You pick the languages and a quality class in the LATW Cloud panel, see the cost up front and pay per word.

No. LATW Cloud works through the Webflow Data API. You generate a site token in Webflow (Site settings → Apps & integrations → API access) and paste it in the LATW Cloud panel. Nothing is installed on your site.

Read and write access to Pages, CMS and Components, and read access to Sites. Give Sites write access only if LATW Cloud should publish the whole site after each job. A token belongs to one site, and LATW Cloud stores it encrypted and shows only its last four characters.

Page texts, form placeholders, button labels, dropdown options, page titles, SEO titles and descriptions and Open Graph texts; the template pages of CMS collections; each CMS item's name, plain text and rich text fields and the alt text of its images; components; and the name, description and text fields of Webflow E-commerce products.

LATW Cloud is pay per word: from $0.0234 per 1,000 words on Economy, with no monthly fee. A site with 20,000 words costs about $0.47 per language on Economy or $9.36 on Standard, paid once. Plans from $9 a month add Batch mode at half price, your own AI keys and 20-40% cheaper Credits. A Webflow site takes one site slot and works on every plan.

Yes. Turn on Webflow Localization in the Designer and add at least one more language; how many you can add depends on your Webflow plan. LATW Cloud writes each translation into its own Webflow language and never changes the primary language. You need a site plan with CMS only if you want to translate collections.

Your choice. By default translations wait in Webflow as unpublished changes until you publish. You can let LATW Cloud publish translated CMS items at once, or publish the whole site after each job - the latter also publishes every other unpublished change made in the Designer.

Yes, if you want. Slugs are not sent to AI: they are made from the translated name or page title, but only while the slug is still the same as in the primary language, so a slug translated once is never changed and links keep working. You can also keep all slugs as they are.

A job translates the whole items you select, also those translated before, and overwrites their texts in the target languages - including your own corrections. Webflow keeps no translation status, so you choose the items yourself and select only what you want translated again.

Yes, on every paid plan from Solo at $9 a month. You pay your AI provider directly and LATW charges only for the plan; you can also mix your own keys and LATW Credits per site.

Yes, on every paid plan from Solo. LATW Cloud has an MCP server: connect Claude, ChatGPT, Claude Code, Cursor, Codex, n8n or your own agent with your LATW account - no key to copy - and ask it to translate, for example "translate all missing products into German". The agent translates with its own model and LATW Cloud checks every translation and writes it to your site, with no Credits used: Solo includes 50,000 agent words a month, Startup 250,000 and Agency 1 million. For big jobs the agent can start a regular LATW Cloud job instead - it shows you the price first.

Connecting sends LATW Cloud the site's name, its domains and its languages; after that it reads only the content chosen for translation. Text is deleted 7 days after the job, LATW Cloud is hosted in the EU and a DPA is available in your account.

They stay in Webflow. Disconnecting makes LATW Cloud stop using the token and forget it; unused Credits never expire. Webflow does not let an app delete a token, so delete it yourself in Site settings → Apps & integrations → API access.