How much does it cost to translate a Webflow store?
The parts that make up the cost of translating a Webflow store, a worked example you can redo with your own numbers, and StoreLingo's plans in AI characters.
The cost of translating a Webflow store is more than a subscription price. It is the translation itself, the time you spend setting things up and checking the result, and the room the translated content takes in your Webflow plan. This post lists those parts and shows how to estimate them for your own store.
The parts of the cost
- The translation. Paid per word to a translator, paid through a tool's plan, or your own time if you translate yourself.
- Review. Machine translation needs someone who reads the language to check it, at least for the text customers see most.
- Setup in Webflow. Whatever tool you use, someone has to decide how visitors reach each language and set that up.
- Upkeep. Every new product and every changed description needs translating again.
- Webflow plan room. If translations are stored in your site as extra products or CMS items, they count toward your Webflow plan's limits.
A worked example you can redo
The numbers below are assumptions for the example, not measurements. Replace each one with your own.
- 200 products.
- Three target languages.
- The fields you translate (by default every text field that has text: on a typical product the name and the description) add up to 600 characters per product, about 100 words.
With a translator
200 products × 100 words × 3 languages = 60,000 words
60,000 words × your translator's rate per word = first-pass cost
Ask your translator for a quote; rates vary by language pair, subject and turnaround. Every later change costs the changed words times the rate, per language.
With StoreLingo
200 products × 600 characters × 3 languages = 360,000 characters
(first pass, before any reuse from translation memory)
StoreLingo counts AI characters as the characters of source text sent to DeepL, including the formatting markup of rich text fields. Text that repeats within the same site and language pair is filled from translation memory and uses no AI characters. Editing by hand is unlimited.
In this example, 200 products and three languages fit the Growth plan's product and language limits, but 360,000 characters is more than Growth's 100,000 AI characters per month. You would either spread the first pass over several months, translate part of it by hand, or use Pro (500,000 AI characters per month) for the first month. After the first pass, the monthly need is the characters of new and changed text.
StoreLingo's plans
| Plan | USD / month | Sites | Languages | Products per site | AI characters / month |
|---|---|---|---|---|---|
| Starter | 19 | 1 | 2 | 100 | 20,000 |
| Growth | 49 | 3 | 5 | 1,000 | 100,000 |
| Pro | 99 | 10 | Unlimited | Unlimited | 500,000 |
| Agency | 249 | Unlimited | Unlimited | Unlimited | 2,000,000 |
- All products are synced. On a plan with a product limit, the first products up to that limit (oldest first) can be translated and published, and the app shows how many your plan covers. "Unlimited" is always subject to Webflow's own item limits.
- The trial lasts 14 days from install, needs no card, and runs on Starter's limits. If you choose a plan during the trial, the remaining trial days are kept.
- If the trial ends without a plan, or a subscription ends, you can still view, export and delete your data, but not translate, publish or sync. Everything already in Webflow stays.
The Webflow side of the cost
StoreLingo creates one translated copy per product and per CMS item for each language. In the example above that is 600 new products in your Webflow site. Those copies count toward your Webflow site plan's product and CMS item limits, so check your plan's limits on Webflow's pricing page before you publish.
Setup is also yours: StoreLingo does not route visitors to a language. You duplicate your listing pages per language and filter each Collection List by the Locale field that StoreLingo sets. The app shows a guide after the first publish. Text in your page templates, static pages, navigation, cart and checkout is not translated by StoreLingo.
Other routes
Webflow has its own Localization feature, which machine-translates and localizes static pages and CMS items. According to Webflow's Help Center (the "Webflow Localize overview" article, checked 30 October 2026), it does not localize Ecommerce products, categories or Ecommerce pages on sites that use Ecommerce. Other translation tools price in their own ways. Check each vendor's current pricing page; we do not quote other companies' prices here, because they change and we cannot keep them current.
If you want to see what your own catalog would use, the 14-day trial needs no card. Questions go to hello@storelingo.com; we reply within one business day (Monday to Friday, CET).
We build StoreLingo, a Webflow app that translates Webflow Ecommerce products and CMS items and publishes each language as separate items in the customer's own Webflow site. We have no relationship with Weglot, Linguana or Webflow. If we got something wrong, email hello@storelingo.com. We reply within one business day (Monday to Friday, CET).
Translate your Webflow store. Own every word of it.
StoreLingo publishes translated copies of your products and CMS items into your own Webflow site, at a flat monthly price. The copies are your content and stay in Webflow if you uninstall.