Weglot is a polished product. We just disagree with two of its core decisions: client-side delivery and vendor-hosted translation storage. Here's where we differ.
Weglot: injects JavaScript that fetches translations and rewrites the DOM on every page load. Faster than translating server-side in PHP, but slower than rendering native HTML.
Paragraphs: Cloudflare Worker substitutes translated content via HTMLRewriter before the response reaches the browser. No client-side JS dependency. Better caching. Cleaner SEO.
Weglot: translations live in Weglot's hosted store. Export is API-paginated and partial. Leaving means rebuilding your translation memory elsewhere.
Paragraphs: one-click export to JSON, XLIFF, TBX. Self-hosted option on Business+. Your translations are yours.
| Feature | Paragraphs | Weglot |
|---|---|---|
| Delivery | Edge HTMLRewriter, server-side | Client-side JS injection |
| SEO impact | Native HTML per locale, no JS dep | Crawler quirks; perf hit |
| Pricing transparency | Word bundles, GBP/EUR/USD, no overage surprise | Word metering, EUR-only, aggressive scaling |
| Data ownership | Export JSON / XLIFF / TBX any time | Translations live in Weglot's hosted store |
| Brand consistency | Glossary enforcement built in | Glossary available, less granular |
| Headless / framework adapters | Yes | JS SDK only |
| AISEO surfaces | Yes | No |
| Branches / staging | Yes | No |
| EU + US data residency | Lockable at signup | EU-only, single region |
A site translating 2 million words a month into 8 locales:
€399 / mo
Word bundle: 1M words. Above bundle: usage-priced at a per-word rate that scales aggressively.
£65 / mo
2M words / month included. Translation Memory cuts repeat content to free. Top-ups available; never auto-billed.
Weglot pricing per their website at the time of writing. We update this comparison when they change.
Export your translations as JSON; we'll ingest them. Same locale list, no re-translation cost.