Comparison
A Weglot alternative for products that ship files, not pages
Weglot translates a website that already exists, in the browser, without touching your code. If what you need translated is a language file inside an app, that mechanism does not apply.
- Weglot, entry plan
- €15
- ShipGlobal
- €19
Starter. Billed per translated word and per page view of the translated site. Traffic raises the bill even when the text has not changed.
Per seat and month, incl. VAT. On top of that €10 per million tokens, and only for strings that are new or changed. Bring your own model key and the token cost disappears.
Two different machines
Weglot works by sitting in front of a live site: it detects the text, serves translated versions on language subdomains or subdirectories, and bills against translated words and page views. That is an excellent fit for a WordPress or Shopify site where nobody wants to touch the templates. It is not a fit for an iOS app, an Android app, or a React Native bundle, because there is no page for it to sit in front of. The second thing that surprises people is the page view meter. The Starter plan covers 20,000 page views a month, Business 50,000, Pro 200,000. A successful month raises the bill even though the text has not changed by a single word.
What Weglot lists
Every plan Weglot publishes, with the source and the date it was read. Prices change; this table says when it was last checked.
| Plan | Per month | Page views |
|---|---|---|
| Free | Free | 2,000 |
| Starter | €15 | 10,000 |
| Business | €29 | 50,000 |
| Pro | €79 | 200,000 |
| Advanced | €299 | 1,000,000 |
| Extended | €699 | 5,000,000 |
The fair part
When Weglot is the better choice
For a marketing site, a shop, or any content site where the goal is to serve translated pages to visitors without a build step, Weglot is the better tool and the comparison is not close. It handles the routing, the hreflang tags, the language switcher and the SEO plumbing that make translated pages actually rank, and it does it without a developer. ShipGlobal has none of that, because it operates one layer down: it translates the file, and what you do with the file is your build's problem. If your product is a website rather than an app, start with Weglot.
Getting your files out
If you have translations sitting in Weglot and want them in files, export from the Weglot dashboard and convert the export into the format your build reads. The key diff will show what is genuinely translated versus what is still passing through untouched.
One language file in. 64 languages out.
No seat you forgot to cancel, no allowance that expires, no per-language multiplier. You pay for the strings that changed and nothing else.
€19 per month incl. VAT, cancellable monthly.
Questions
- Can Weglot translate my mobile app?
- Not through its main mechanism, which serves translated versions of a live website. Mobile apps ship language files that are compiled in, and there is no page in front of which a proxy can sit. That is the case ShipGlobal is built for.
- Why do page views affect a translation bill?
- Because Weglot serves the translated pages, so its cost scales with traffic as well as with word count. Free covers 2,000 views a month, Starter 20,000, Business 50,000, Pro 200,000. It is a hosting cost as much as a translation cost, which is fair for the service and worth knowing before a launch.
- Does ShipGlobal handle hreflang and language routing?
- No. It produces translated files. Serving them, routing between languages and getting the hreflang tags right is the job of your framework. If you want that handled for you on a website, that is exactly what Weglot sells.
- We have both a site and an app. What then?
- Use both, and do not try to make one tool do both jobs. Weglot in front of the site, ShipGlobal for the app's language files. They meter different things because they do different things.