Weglot starts at €15 per month, but the right plan depends on both your translated word total and your number of target languages. A small site in six languages can need a higher plan than a larger site in two. Start with those two limits before comparing the monthly prices.
Weglot prices at a glance
| Plan | Monthly billing | Annual bill | Translated words | Target languages |
|---|---|---|---|---|
| Free | €0 | €0 | 2,000 | 1 |
| Starter | €15 | €150 | 10,000 | 1 |
| Business | €29 | €290 | 50,000 | 3 |
| Pro | €79 | €790 | 200,000 | 5 |
| Advanced | €299 | €2,990 | 1,000,000 | 10 |
| Extended | €699 | €6,990 | 5,000,000 | 20 |
| Enterprise | Custom | Custom | Custom | Custom |
Prices exclude VAT. Annual amounts are billed for the full year, not monthly instalments. Checked on 20 October 2026 against the official Weglot pricing page. Check that page before subscribing.
For example, Business costs €348 over twelve monthly payments, compared with €290 paid annually. Annual billing saves €58 over a full year. Monthly billing keeps the commitment shorter while you validate a new market.
Calculate words across languages, not pages alone
Weglot describes its allowance as unique translated words across all target languages. The allowance does not renew every month. Its monthly translation-request limit is separate and is approximately related to translated page views. See Weglot’s word-count explanation and the request definition on its pricing page.
Use this as an initial budget estimate:
18 000 × 2 = 36 000Suppose the pages you want to publish contain 18,000 source words:
| Rollout | Estimated translated words | First plan meeting both limits |
|---|---|---|
| 2 target languages | 36,000 | Business |
| 3 target languages | 54,000 | Pro |
| 6 target languages | 108,000 | Advanced |
These are calculated examples, not measured websites. The second rollout exceeds Business’s word limit. The third fits Pro’s word limit but exceeds its five-language limit. Check both ceilings.
Use Weglot’s own word counter and the actual project count to refine the estimate. Budget for the pages you will add next: product descriptions, help articles and campaign pages. A plan that fits exactly on launch day leaves little room for the next release.
Include the next release in your plan choice
Write down three things before paying:
- The pages that will actually be translated. Start with a deliberate set, such as your catalogue and buying journey. Don’t assume every archive page needs every language.
- The languages in the first rollout and the next one. Adding a sixth language can change the required plan even when the word total barely moves.
- The workflow your team needs. Export/import is available on Advanced and higher, so a spreadsheet-based review process can affect the plan choice independently of word volume.
For that last point, use the official export/import instructions. Don’t choose a lower tier and build a CSV workflow around a feature it doesn’t include.
If you only need translated pages served automatically on an existing website, compare the publishing setup as well as the translation cost. Our website translation software comparison separates tools by the job they do.
Where AI Glot fits, and what it does not replace
I built AI Glot to translate files. Weglot also publishes translated pages. Comparing their prices as if they supplied the same service would hide work you still need to do.
- Weglot publishes the language pages
- Its word and language limits still apply
- Use export/import on an eligible plan
- Your CMS or site owns each language page
- You maintain routing and language updates
- Translate source exports as files
If you keep Weglot, AI Glot can translate exported content using your glossary and instructions. Re-importing that content does not remove Weglot’s translated-word quota or subscription. Don’t budget for a lower Weglot tier simply because a different tool wrote the translations.
If your CMS already stores localized content, AI Glot can instead process that CMS’s exports. The CMS translation workflow and Webflow export guide show that route. You still need language pages, navigation, metadata and a process for keeping updates in sync.
How to process a Weglot export with AI Glot
On Advanced or a higher plan, start from Weglot’s own export, not a CSV scraped from rendered pages. Its import matches the structure of its exported content.
- 1ExportAn existing language pairAdvanced or higher
- 2TranslateWrite only word_toKeep the source columns
- 3Review and importCheck a small selection firstIn Weglot
- Export a small selection from your Weglot project’s Translations > Languages screen.
- Upload the CSV to AI Glot. Specify the target language and ask it to translate
word_fromintoword_to, leaving every other column unchanged. Review the scope in the plan. - Apply your glossary and wording instructions, then run the translation. Review names, links and high-value copy in the returned file.
- Import the CSV back into Weglot. Keep UTF-8 encoding and the exported structure; Weglot’s guide lists a 5 MB import limit. Review its import preview and test the published pages.
Those import constraints come from Weglot’s documentation. Avoid marking unchanged translations as reviewed unless somebody has actually reviewed them.
For a first trial, the free CSV translator lets you test a sample without an account. See AI Glot pricing for the full-file workflow. Add that processing cost to your Weglot subscription when comparing the complete budget.