Translation & Localization
Weglot
EU-Made Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Weglot SAS · www.weglot.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Weglot at a glance
- Vendor
- Weglot SAS
- Headquarters
- Not stated on the vendor’s pages as of 1 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 1 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 1 Nov 2026
- Panel verdict
- The AI panel rates Weglot 2.5/5, the mean of 6 judges. Weglot is a website translation service from WEGLOT SAS, a simplified joint-stock company in Paris under French law. how scores are made
- As of
- Vendor pages captured 1 Nov 2026; evaluated by the panel 2 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Weglot is a website translation service from WEGLOT SAS, a simplified joint-stock company in Paris under French law. Strongest are machine translation and sovereignty, with five judges at 7, and pricing transparency at 6 to 7; weakest are workflow and review at 4 to 6 and portability and exit at 4 to 5, and one judge scored 0 on every criterion. Machine translation rests on three named engines — DeepL, Google Translate and Microsoft — selected automatically per language pair, a custom model on OpenAI and Gemini, and a published Nimdzi study finding 85% of 168 sampled segments very good or acceptable. Pricing runs from €0 /month to €699 /month excl. VAT with limits published per tier; Enterprise is price on request. The judges genuinely split on developer-facing needs — the app developer scored 4 on workflow and review and integrations and formats where other judges scored 5 or 6, CSV and XLIFF being the only documented exchange formats — while separately the terms grant Weglot a right to use translations data to improve the service, and the captured pages give different figures for hosting.
Speaks for it
- Machine translation scored 7 from five of six judges, on three named engines with automatic per-pair selection and a published Nimdzi study that found 85% of 168 sampled segments very good or acceptable.
- Five public tiers from €0 /month for 2,000 total words and 1 translated language to €699 /month excl. VAT for 5,000,000 total words and 20 translated languages, with a 14-day free trial and 2 months free on annual billing.
- 70+ one-click integrations including WordPress, Shopify, Webflow, Wix, Salesforce, Adobe Experience Manager and Zendesk, plus a JavaScript snippet for any custom site.
- Sovereignty scored 7 from five of six judges: a French simplified joint-stock company in Paris, French governing law, the CNIL named as supervisory authority, a published data processing agreement and a public subprocessor list with locations.
- A stated exit path — all translations exportable by format, language pairs, qualities and types or by URL, copyright kept by the user, and a six-month window after subscription end to request a copy.
Held against it
- The terms of use grant Weglot itself a right to use translations data at no cost to improve the quality of the service, set beside commitments that OpenAI and Gemini do not store or train on client content.
- Translation memory is listed as an Extended-plan feature at €699 /month, and we found no public information on automated QA checks, review stages or per-language roles.
- CSV and XLIFF are the only documented import and export formats, and we found no public information on a CLI, Git repository sync, webhooks or over-the-air updates.
- We found no public information on translation memory export as TMX, glossary export as TBX, a migration path from another tool, or any self-hosted edition, and the judges scored portability and exit 4 to 5.
- Projects are deleted after 3 months of inactivity with 3 further months to recover them, and for the pageview and API-call limits that the terms name as plan differentiation criteria we found no public information on per-tier figures.
Best for
- You run a marketing site or online store on a mainstream platform such as Shopify or WordPress and want machine translation with in-context editing and no developer required.
- You need pricing you can compute before talking to sales, with word, language and team-member limits published per tier.
- You are a European buyer who wants a French contracting entity under French law with a published data processing agreement and a public subprocessor list.
- You want professional translators orderable inside the product on any plan when machine output needs a human pass.
Avoid if
- You need to translate Word, PowerPoint, PDF or InDesign documents with their layout — the captured pages describe website translation, and we found no public information on document handling.
- Your pipeline relies on Git repository sync, a CLI, webhooks or JSON, Android XML or iOS strings — CSV and XLIFF are the only documented exchange formats.
- Your release process needs automated QA, approval stages or per-language roles before publishing — we found no public information on these, and translation memory starts at the Extended plan.
- You send confidential or contractual text through translation — the terms grant Weglot a right to use translations data to improve the service, and we found no public information on audit logs or customer-set retention.
The scores
| Criterion | Panel median |
|---|---|
| Machine translation & AI quality | 3.5 of 5 |
| Translation memory, terminology & review workflow | 2.5 of 5 |
| Integrations, file formats & developer tools | 3 of 5 |
| Confidentiality of translated content | 3 of 5 |
| Data export, portability & self-hosting | 2.5 of 5 |
| European sovereignty | 3.5 of 5 |
| Pricing transparency | 3.5 of 5 |
Machine translation & AI quality
panel disagrees
Show reasoningHide reasoning
How this is scored
What the machine translation does and how well it is controlled: the languages and language pairs covered, the engine (own neural or LLM model, or a choice of third-party engines such as DeepL, Google, Microsoft or an LLM), glossaries and formality applied during translation, document translation that keeps the layout (Word, PowerPoint, PDF, InDesign), custom or adaptive models trained on the customer's own translations, automatic quality estimation or scoring, and published evaluations of translation quality.
0 — No machine translation of any kind, and no way to connect an engine.
3 — Machine translation is offered or one engine can be connected; languages, glossary use and quality controls are basic or not described.
5 — Machine translation for the major European and world languages with the list published, glossaries applied during translation, a formality or tone setting, document translation that keeps formatting for common office formats, and either an own engine or a choice of several named engines.
8 — Custom or adaptive models that learn from the customer's translation memory or corrections, automatic quality estimation per segment with a threshold that routes weak segments to human review, LLM-based translation with style guides and context, engine selection per language pair stated, and a published quality evaluation with its method.
10 — Translation quality that an organisation can measure and steer: evaluations against named benchmarks or blind human review published with their method, quality estimation calibrated and explained, custom models with their training data and isolation documented, and every machine-translated segment traceable to the engine, model version and glossary that produced it.
The Localization Manager
Three named engines (Google Translate, DeepL, Microsoft) with automatic selection per language pair, a glossary applied automatically, tone of voice on higher tiers, and a custom model powered by OpenAI and Gemini that learns from glossary rules, manual edits and brand preferences — that is most of what I need to steer quality. They also publish a machine translation study with Nimdzi Insights using human linguists across five providers, 168 sampled segments, 85% rated very good or acceptable, which is more evaluation method than most vendors show. What I found no public information on: per-segment quality estimation that routes weak segments to human review, or document translation that keeps layout for Word, PowerPoint or InDesign. 2 3 6 11
The App Developer
Three named first-layer engines (DeepL, Google, Microsoft) with automatic selection per language pair, plus a custom model powered by OpenAI and Gemini that learns from glossary rules, manual edits and brand preferences — that is real control. The Nimdzi study using human linguists gives a published method and concrete numbers (168 segments sampled, 85% very good or acceptable). What I do not see is per-segment quality estimation that routes weak segments to human review, so it stays just below the top band. 2 3 6 7 11
The In-House Document Translator
The captured pages describe website translation, and we found no public information on translating Word, PDF or InDesign documents with their layout. For the machine translation itself the evidence is strong: three named engines (DeepL, Google Translate, Microsoft) with automatic selection per language pair, a custom model on OpenAI and Gemini that learns from my glossary rules and manual edits, a tone of voice setting, engine versions per project, and a published Nimdzi study using human linguists as its method. 2 3 6 11 12
The Data Protection Officer
Machine translation across 110+ languages with automatic selection among named engines (Google Translate, DeepL, Microsoft), glossary rules applied during translation, a tone-of-voice setting, and a custom model built on OpenAI and Gemini that learns from manual edits and brand preferences. There is a published quality evaluation with its method, done with Nimdzi Insights using human linguists over 168 sampled segments, concluding 85% of machine-translated content was very good or acceptable. We found no public information on per-segment quality estimation that routes weak segments to review, or on document translation that keeps office file formatting. 1 3 6 11
The E-Commerce Marketer
Three named engines — DeepL, Google Translate and Microsoft — are automatically selected per language pair, and a custom model built on OpenAI and Gemini learns from my glossary rules, manual edits and brand tone, which is exactly how I would rescue a bad product name across five languages. A published Nimdzi study using human linguists found 85% of sampled machine translations very good or acceptable, with linguists never needing to edit more than 30% of segments in any pair. I found no public information on per-segment quality scoring that routes weak text to human review, nor on document translation for Word, PowerPoint or PDF files. 2 3 11
The Skeptic
The published Nimdzi study, run with human linguists over five providers with its method and sample stated, is more quality evidence than most engine vendors ever produce, and the custom OpenAI/Gemini model that learns from glossary rules and manual edits, plus automatic provider selection per language pair, sits well above a basic engine wrapper. I still found no public information on per-segment quality estimation routing weak segments to review, on document translation that keeps layout, or on tracing a segment back to the engine, version and glossary that produced it. 2 3 6 11
Translation memory, terminology & review workflow
panel disagrees
Show reasoningHide reasoning
How this is scored
How translation is managed as an ongoing process: translation memory with fuzzy matches, a termbase or glossary managed centrally, style guides, review and approval stages, automated QA checks (placeholders, tags, length, terminology, punctuation), an in-context or visual editor, screenshots and context for translators, tasks and deadlines, roles per language, and ordering or inviting human translators and agencies inside the product.
0 — No management of translations at all; text goes in and comes out with nothing stored or reviewed.
3 — Translations can be edited or a glossary kept; translation memory, review stages and QA checks are basic or not described.
5 — A translation memory reused across projects, a central glossary, at least one review or approval stage, automated QA checks for placeholders and terminology, comments and screenshots for context, and roles that limit translators to their languages.
8 — Configurable multi-step workflows with automation rules, an in-context or visual editor for apps or websites, QA checks configurable per project with blocking rules, style guides applied by the AI, translation memory and termbase shared across projects with penalties and priorities, vendor or agency management with ordering inside the product, and progress and cost reporting per language.
10 — A translation process an enterprise runs on: workflows per content type with conditional routing on quality scores, linguistic quality assessment with a named framework (MQM or similar), termbase with approval workflow and forbidden terms, full revision history per segment, and productivity and quality metrics per translator and vendor.
The Localization Manager
There is a central glossary with automatically applied rules, a visual editor on a live preview of the site, edit propagation across identical phrases, and professional translators can be ordered inside the product on all plans — but the pricing page lists translation memory as an Extended-tier feature, and I found no public information on configurable review stages, automated QA checks for placeholders or tags, or roles that limit a translator to their languages. An export filter for translation qualities and an import option to mark unchanged translations as reviewed suggest review states exist in some form, but for my release process the missing placeholder QA and the missing per-vendor progress and cost reporting are the gaps. 2 3 6 7 15
The App Developer
There is a glossary with automatically applied rules, a visual editor on a live site preview, manual edits propagated to identical phrases, and professional translators orderable inside the product — but I found no public information on automated QA checks for placeholders or tags, on review or approval stages, or on roles limiting translators to specific languages. Translation memory appears only from the Extended plan and fuzzy matching is never described, which makes this thin for app strings with format specifiers. 2 3 6
The In-House Document Translator
A central glossary with automatically applied rules and a builder template, a translation memory on the top plan, a visual editor on a live preview of the site, and ordering professional translators via TextMaster and an expert directory inside the product are all documented. We found no public information on automated QA checks for placeholders or terminology, review and approval stages, or roles that limit translators to their languages — the checks I rely on before a contract goes out the door. 2 3 6 15
The Data Protection Officer
A translation memory stores edits for consistent reuse, a central glossary with automatically applied rules, a visual editor over a live preview, and manual edits propagated to identical phrases. Professional translations can be ordered inside the product with a partner (TextMaster) and an expert directory to find collaborators. We found no public information on automated QA checks, configurable review or approval stages, or roles that limit translators to their languages, which keeps this at a solid mid level for a website translation tool rather than a managed review process. 2 3 6 7
The E-Commerce Marketer
A central glossary with automatically applied rules, manual edits that propagate to every identical phrase, and a visual editor on a live preview of my shop cover my no-translator reality, and I can order professional translations inside the product or find collaborators through the built-in directory. The product pages say edits are stored in translation memory, but the pricing page lists translation memory as an Extended-plan feature at €699 /month, so on the tiers I could afford it may not be included. Automated QA checks, approval stages and per-language roles are not described in the captured pages. 3 6 7
The Skeptic
There is a glossary with automatically applied rules, a live visual editor on a preview of the site, manual edits propagated to identical phrases, and professional translators orderable inside the product through the TextMaster partner terms — but the translation memory is gated to the Extended tier, and imports only offer marking unchanged translations as reviewed. I found no public information on automated QA checks, multi-step review or approval stages, per-language roles, or comments and screenshots for reviewers. 3 6 7 15
Integrations, file formats & developer tools
panel disagrees
Show reasoningHide reasoning
How this is scored
How content gets in and out: the file formats supported (XLIFF, PO, JSON, YAML, Android XML, iOS strings and xcstrings, Office documents, InDesign), a REST API and CLI, SDKs and over-the-air updates for apps, Git repository sync (GitHub, GitLab, Bitbucket) and CI pipelines, connectors for CMS, shop and design tools (WordPress, Contentful, Shopify, Figma), browser and office add-ins, webhooks, and a JavaScript snippet or proxy for website translation.
0 — No documented way to get content in or out except typing or pasting by hand.
3 — File upload and download or a basic API; formats, repository sync and connectors are basic or not described.
5 — A documented REST API, a list of supported file formats covering the common software and document formats, sync with at least one Git host or CI, and connectors or plugins for several named CMS, shop or design tools.
8 — A CLI and SDKs for named platforms, over-the-air updates for mobile or web apps, Git sync with branching, webhooks, connectors for the main CMS, shop, design and support tools, office or browser add-ins, a public status page, and API limits documented.
10 — Integration that scales across an organisation: an API covering every function of the product with versioning and SDKs, an app or connector framework third parties build on, continuous localization in CI with pull requests opened automatically, and every connector documented with its limits and the fields it syncs.
The Localization Manager
The connector catalogue is the strongest I have seen for websites: 70+ native integrations including WordPress, Shopify, Squarespace, Webflow, Wix, Drupal, WooCommerce, Magento, SAP Commerce Cloud, Salesforce and Adobe Experience Manager, help-centre connectors for Zendesk and Help Scout, a JavaScript snippet for any site, a React/Next.js SDK with build-time translation, and a documented API reference. For a software product, though, import and export run through CSV and XLIFF, and I found no public information on Git repository sync, CI pipelines, a CLI, webhooks, or handling of PO, JSON, YAML, Android XML or iOS strings. 1 4 5 13 15
The App Developer
The website story is huge: 70+ named connectors from WordPress to Salesforce and SAP, a JavaScript snippet for any site, a React and Next.js SDK with build-time translation, and a documented API (version 1.0, with 2.0 and an MCP server only listed as coming soon). For an app pipeline like mine I found no public information on a CLI, Git repository sync, over-the-air updates or mobile SDKs, and the only import and export formats documented are CSV and XLIFF — nothing on JSON, Android XML or iOS strings handling. 1 4 5 13 15
The In-House Document Translator
Seventy-plus native integrations are documented — WordPress, Shopify, Webflow, Wix, Salesforce, Adobe Experience Manager, SAP Commerce Cloud, Zendesk, HubSpot — plus a documented API, an npm React SDK with Next.js support, a JavaScript snippet for any website, and an API status page. The documented file exchange covers CSV and XLIFF only, and we found no public information on Git repository sync, CI pipelines, a CLI or webhooks — nor on the Office and InDesign formats my documents live in. 4 5 6 13 15
The Data Protection Officer
A documented API with a public reference, 70+ native connectors including WordPress, Shopify, Salesforce, Adobe Experience Manager and Zendesk, a JavaScript snippet that works on any website, React and Next.js packages, and CSV or XLIFF import and export. An API status item appears in the support table. We found no public information on Git repository synchronisation, CI pipelines, a command-line tool, webhooks, or documented API limits, so the developer tooling does not reach the higher level despite the exceptional connector breadth. 1 4 5 13 15
The E-Commerce Marketer
The Shopify app carries 4.4 stars from 810 reviews, claims compatibility with all themes and with apps like Klaviyo, and Weglot claims 70+ one-click connectors spanning WordPress, WooCommerce, Webflow, Wix, Zendesk and more, plus a JavaScript snippet for any custom site — as a store owner without a developer, this is the part that matters most to me. Developer depth is thinner: a documented API 1.0 with a React and Next.js package, and CSV or XLIFF import and export, but I found no public information on a CLI, Git repository sync, webhooks or over-the-air updates. 4 5 13 14 15
The Skeptic
Seventy-plus named connectors across CMS, commerce, enterprise, helpdesk and course platforms, a JavaScript snippet that works on any website, an npm package with React and Next.js wrappers, and a documented API reference (version 1.0, with 2.0 and an MCP server announced as coming soon) form a broad integration surface. The file formats I find named are CSV and XLIFF only, and I found no public information on Git repository sync, a CLI, webhooks, or over-the-air SDKs for mobile apps. 4 5 13 15
Confidentiality of translated content
panel disagrees
Show reasoningHide reasoning
How this is scored
What happens to the text a customer translates: whether source and target texts are stored and for how long, deletion after translation, whether customer content is used to train the vendor's or a third party's models, which machine translation and LLM providers a TMS sends text to and whether that can be restricted or switched off, encryption in transit and at rest, single sign-on, roles and audit logs, and certifications (ISO 27001, SOC 2) with their scope. Where the text is processed is scored under sovereignty.
0 — Customer texts are stored indefinitely and used for the vendor's own purposes, or no statement on data handling exists at all.
3 — The product is described as secure or GDPR-compliant and a privacy policy exists; retention of translated texts, model training and third-party engines are basic or not described.
5 — A documented statement that customer texts are not used to train models, retention or deletion of translated texts stated, the third-party engines or LLM providers named, encryption in transit and at rest, single sign-on on a business tier, and a data processing agreement offered.
8 — Texts deleted immediately after translation or after a retention period the customer sets, third-party AI processing switchable per project or account, zero-retention terms with the named LLM providers, audit logs, granular roles, ISO 27001 or SOC 2 certification stated with its scope, and a private or dedicated deployment option.
10 — Confidentiality that can be verified: an on-premise or customer-controlled deployment, customer-managed encryption keys, every subprocessor that sees content listed with its role, independent audit reports available, and every data flow of a translation request documented end to end.
The Localization Manager
Encryption in transit and at rest, a SOC 2 Type II report published 10 January 2025, a data processing agreement, SAML single sign-on and two-factor authentication are stated, and they warrant that their AI sub-processors (with DPAs with OpenAI and Gemini) never store content or use it to train AI models. Two things a buyer must read closely: the terms grant Weglot a right to use translations data at no cost to improve the quality of the Service, and I found no public information on customer-set retention periods, switching off third-party AI per project, audit logs or granular roles. 3 6 7 10
The App Developer
Strong bones: encryption in transit and at rest, SAML single sign-on, a published data processing agreement, SOC 2 Type II, and commitments that the AI sub-processors OpenAI and Gemini never store or train on client data. But the terms also grant Weglot a right to use translations data at no cost to improve the quality of the Service, exactly the kind of clause I would need legal to clear before sending product strings through. I found no public information on audit logs, customer-set retention periods, or switching third-party AI processing off per project. 3 6 7 10
The In-House Document Translator
A data processing agreement, SOC 2 Type II, encryption in transit and at rest, SAML single sign-on and two-factor authentication are documented, and Weglot warrants its AI sub-processors do not retain or train on client data. Against that, the terms grant Weglot a free right to use translation data to improve the quality of the service — not the clean promise I need for a draft contract — and we found no public information on customer-set retention, switching AI providers per project, or audit logs. 3 6 7 10
The Data Protection Officer
The engines and LLM providers are named, and the terms warrant that AI sub-processors do not retain use-related data beyond what is strictly necessary and do not use client data to train their models; encryption in transit and at rest, SAML single sign-on, two-factor authentication, a published DPA, SOC 2 Type II and deletion of inactive projects after three months are all documented. Two things hold it back for my use case: the terms grant Weglot itself a right to use translations data to improve the quality of the service, and we found no public information on audit logs, granular roles, or a way to switch off third-party AI processing per project or account. 3 6 7 10
The E-Commerce Marketer
Encryption in transit and at rest, two-factor and SAML single sign-on, a SOC 2 Type II report and a published data processing agreement give me the compliance paper trail, and the subprocessor agreements state that OpenAI and Gemini neither store nor train on customer content. Two things temper it: the terms grant Weglot itself a right to use translation data to improve the service, and I found no public information on customer-set retention, audit logs or a dedicated deployment option. 3 6 7 10
The Skeptic
Encryption at rest and in transit, a SOC 2 Type II report, a published data processing agreement, a subprocessor directory, two-factor and SAML single sign-on, and warranties that the AI sub-processors retain nothing and train on nothing — this is substance, not a hand-wave. But the terms of use also grant Weglot itself a right to use translations data at no cost to improve the quality of the Service, a sentence every buyer should read next to the AI training commitments, and I found no public information on switching off or restricting which third-party engines see a project, on audit logs, on customer-set retention, or on a dedicated deployment option. 3 6 7 10
Data export, portability & self-hosting
panel disagrees
Show reasoningHide reasoning
How this is scored
Whether translation assets stay the customer's and can leave with them: export of translation memory and termbase in open formats (TMX, TBX, XLIFF, CSV), export of all projects and files, import from another TMS, an API that can read every asset, the return or deletion of data on termination, open-source code and a self-hosted or on-premise edition.
0 — Translations cannot be exported; they exist only in the vendor's interface or engine.
3 — Translated files can be downloaded; export of translation memory and glossary, import and termination terms are basic or not described.
5 — Translation memory exportable as TMX and glossary as TBX or CSV, all project files downloadable, import of translation memory and glossaries from another tool, and an API that reads translations and keys.
8 — Complete export of every asset (memory, termbase, files, comments, history) in open formats, a documented migration path from named competitors, the data returned or deleted on termination under stated terms, and a self-hosted or on-premise edition with its own documentation.
10 — The customer owns the assets end to end: open-source code under a named licence that runs fully self-hosted with feature parity stated, a complete export another tool can import without loss, and the deletion of every copy on termination documented.
The Localization Manager
All translations can be exported with a choice of format, language pairs, qualities and types, CSV and XLIFF import is documented, the user keeps all copyrights on the translations, and there is a six-month window after the end of the subscription to request a copy, with customer data deleted upon leaving. However, translations are stored by Weglot and accessible through the Weglot dashboard rather than in the customer's CMS, and I found no public information on translation memory export as TMX or glossary export as TBX, or any self-hosted or on-premise edition. 2 7 10 15
The App Developer
Translations export by format, language pair, quality and type, with CSV and XLIFF import documented; copyright stays with the user and there is a six-month window after subscription end to request a copy by email. I found no public information on translation memory export as TMX, glossary export as TBX or CSV, a migration path from another tool, or any self-hosted edition. The automatic project deletion after three months of inactivity — permanent three months later — is an exit hazard I would want contractual protection against. 7 15
The In-House Document Translator
Export of all translations with a choice of format, language pairs and qualities (also by URL or by selection), CSV and XLIFF import, the user keeping copyright on translations, a six-month written-request window after the subscription ends, and deletion of customer data upon leaving are all stated. We found no public information on TMX or TBX export of memory and glossary, a documented migration path from another tool, or a self-hosted edition. 7 10 15
The Data Protection Officer
All translations can be exported with format, language pairs, qualities and types selectable, or narrowed by URLs and specific entries, with CSV and XLIFF import including an option to mark unchanged translations as reviewed. Users hold all copyrights on translations, and on leaving there is a six-month window to request a copy in writing before data is deleted, with customer data deleted upon leaving stated in the trust centre. We found no public information on export in TMX or termbase formats, a documented migration path from another system, or a self-hosted edition. 7 10 15
The E-Commerce Marketer
All translations can be exported with choices of format, language pairs, qualities and types, or by URL; CSV and XLIFF can be imported; I keep full copyright on the translations, and after cancelling I have six months to request a copy before my data is deleted. I found no public information on exporting translation memory in open TMX form, on a migration path from named competitors, or on any self-hosted edition, so my exit plan would rest on CSV, XLIFF and the API. 7 10 15
The Skeptic
Export of all translations by format, language pair, quality and type — or by URL or selection — CSV and XLIFF import, user-held copyright on all translations, deletion of customer data on leaving, and a six-month window after subscription ends to request a copy give a real exit path. I found no public information naming TMX or TBX for translation memory and terminology export, on a self-hosted edition, or on a documented migration path from another tool. 7 10 15
European sovereignty
panel opinion
panel disagrees
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where texts are translated, stored and processed, and who the subprocessors are (hosting, machine translation engines, LLM providers, CDN for over-the-air delivery, support and payment tools). Independently sourced by the sovereignty pipeline; translated texts often hold personal data and trade secrets, so the whole chain counts, including the engines a TMS calls. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (machine translation or LLM providers, CDN, support, payment) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations including the engines and LLM providers, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every text on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting, engine and every subprocessor, or a self-hosted open-source edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The Localization Manager
Weglot is a French simplified joint-stock company at 7 cité Paradis in Paris, the privacy page states data is hosted on servers located in the European Union with Amazon Web Services named as provider, the supervisory authority is the CNIL, and a subprocessor list with locations is published at their trust centre, alongside a published data processing agreement and SOC 2 Type II. Note the captured pages give different pictures for hosting — the trust centre lists Amazon Web Services covering EU or US regions — and other links in the chain (Google and Microsoft among the named engines, OpenAI and Gemini for the custom model, Datadog for US logging and monitoring) are addressed through Data Privacy Framework adherence or European Commission contractual clauses. 3 7 8 10
The App Developer
A French simplified joint-stock company in Paris, French governing law, CNIL as the supervisory authority, EU hosting on Amazon Web Services with a published DPA, a public subprocessor list with locations, and SOC 2 Type II — most of what I want from a European vendor. The chain still runs through US-based OpenAI, Gemini, Google, Microsoft and Datadog, with the Data Privacy Framework and contractual clauses as the stated safeguards, and the captured pages give different figures for hosting location (the trust centre says EU or US, the privacy policy says European Union). No self-hosted edition is documented, so the chain is theirs, not mine. 3 7 8 10
The In-House Document Translator
Weglot is a Paris simplified joint-stock company under French law with the CNIL as supervisory authority, publishes a data processing agreement, SOC 2 Type II and a subprocessor directory with locations and email notification of changes, and states data is hosted on servers in the European Union at Amazon Web Services. The captured pages give different figures for hosting location — the trust centre lists Amazon Web Services as EU or US, Datadog in the US and Cloudflare as global, with US transfers covered by the Data Privacy Framework — and give no location for the Google, Microsoft, OpenAI and Gemini engines. 7 8 10
The Data Protection Officer
The contracting entity is a French simplified joint-stock company in Paris under French law, with CNIL named as supervisory authority, a published DPA and SOC 2 Type II, and a subprocessor directory with change notification that lists locations: AWS for hosting, DeepL in the EU for machine translation, and Datadog in the US for logging, with Data Privacy Framework or contractual-clause safeguards stated for US transfers. The captured pages give different figures for hosting — the privacy policy states servers in the European Union while the trust centre lists the AWS region as EU or US — and we found no public information on where the Google, Microsoft, OpenAI and Gemini processing in the chain occurs. 7 8 10
The E-Commerce Marketer
This is a French company — WEGLOT SAS in Paris, French governing law, CNIL named as the supervisory authority — with a privacy policy stating hosting on European Union servers at Amazon Web Services, a published DPA, a SOC 2 Type II report and a public subprocessor list showing locations. The list places DeepL in the EU but Datadog in the US and Cloudflare globally, with US transfers relying on the Data Privacy Framework, and the captured pages state a hosting location for the machine translation engines only for DeepL. 7 8 10
The Skeptic
A French simplified joint-stock company in Paris under French law, CNIL named as supervisory authority, a published DPA, and a subprocessor directory with regions and email notification on change — DeepL in the EU, Datadog in the US, Cloudflare global, AWS listed as EU or US — with US transfers covered by the Data Privacy Framework or contractual clauses. The privacy policy states hosting on servers in the European Union while the trust page lists the hosting provider as EU or US, so the captured pages give different levels of specificity on where text actually sits; the Google, Microsoft, OpenAI and Gemini links in the chain are US providers carried by those stated safeguards rather than by European engines. 3 7 8 10
Pricing transparency
panel disagrees
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per tier by characters, words, keys, hosted words or seats, what happens when the volume exceeds the tier, the number of users, projects and languages included, which features (machine translation volume, AI credits, SSO, integrations, API access) cost extra, the free tier and its limits, the self-hosted edition and its support, minimum term and setup.
0 — No public prices at all; every customer is a sales call.
3 — A starting price or a free tier exists, but how cost scales with volume, seats or features is unclear.
5 — Tiers are public with their price per volume band and main inclusions, but at least one commonly needed piece (overage, extra seats, machine translation or AI volume, SSO, connectors) is unpriced or "on request".
8 — Every tier priced publicly with its scaling rule (characters, words, keys, seats), overage handling stated, add-ons and AI credits priced, the self-hosted edition's cost or licence stated, minimum term and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given volume, seat count and feature set, with every add-on, setup, support and overage fee and the cancellation and data-return terms published.
The Localization Manager
Five tiers are public with exact figures — €0, €29, €79, €299 and €699 per month excl. VAT for 2,000 to 5,000,000 total words, 1 to 20 translated languages and 5 to 50 team members — together with the number of websites per plan, VAT treatment, an annual option of 2 months free, a 14-day free trial, and overage handled by email notice and automatic migration to a higher plan with prorated payment of the difference. What keeps it short of full computability: Enterprise is "Price on request", and I found no public information on the cost of professional translations, extra seats, or the pageview and API-call limits that also differentiate plans. 1 3 6 7
The App Developer
Every self-serve tier is public — from €0 to €699 per month excluding VAT — with words, languages, team members and project counts per tier, auto-upgrade on limit with proration explained, VAT treatment stated, and two months free on annual billing. The gaps: professional translations are orderable on all plans but I found no public price for them, Enterprise is price on request, and extra languages beyond a tier's allowance are unpriced even though the terms list additional languages as a way plans differ. Translation requests are defined as monthly API calls roughly equal to pageviews, which at least makes the scaling rule legible. 6 7
The In-House Document Translator
Five tiers are public from €0 (2,000 words, one language, five team members) to €699 per month excluding VAT (5,000,000 words, 20 languages, 50 team members), with annual billing at two months free, VAT treatment stated, monthly or annual periods, and prorated automatic upgrades when a limit is exceeded. The Enterprise tier is price on request, and we found no public price for professional translations or additional languages. 6 7
The Data Protection Officer
Five tiers are published in euros excluding VAT with total words, translated languages, team members and project counts each stated, from a free tier of 2,000 words up to the Extended plan, and overage handling is explicit: email notification, automatic migration to a higher plan with only the prorated difference charged. VAT treatment, monthly versus annual billing with two months free, the 14-day trial and tacit renewal are all stated. The Enterprise plan is priced on request, human professional translation costs are not stated on the pricing pages, and we found no public information on the price of extra seats or additional languages beyond a plan. 6 7
The E-Commerce Marketer
Five tiers are public with words, languages, team members and website counts — €0 /month for 2,000 total words and 1 translated language up to €699 /month for 5,000,000 total words and 20 translated languages — and a translated word is counted once, which directly answers my fear that a growing cycling catalogue doubles the bill. Overage behaviour is stated (email notice, automatic prorated upgrade), as are VAT treatment and monthly or annual billing with 2 months free. However, pageviews are named in the terms as a plan differentiation criterion while the captured pages give no per-tier pageview limits, and neither professional translation rates nor anything beyond 'price on request' for Enterprise are published. 6 7
The Skeptic
Five tiers are public with translated words, languages, team members and project counts each, VAT exclusion and its treatment stated, annual billing at two months free, and overage handled by notified auto-upgrade with only the prorated difference charged — the word-based scaling rule is computable from the pricing page alone. What stays dark is real money: the per-tier cap on translation requests, which the terms name as a plan differentiation criterion alongside pageviews, the price of professional translations and additional languages, and the Enterprise tier is price on request. 6 7
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined ⚠ unverified | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined ⚠ unverified | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Weglot
Is Weglot European?
Yes. whats-best.ai classifies Weglot as EU-Made.
Where does Weglot store data?
Not stated on the vendor’s pages as of 1 Nov 2026.
Does Weglot have a free plan?
Not stated on the vendor’s pages as of 1 Nov 2026.
What are the best alternatives to Weglot?
As of 2 Nov 2026, the panel rates SimpleLocalize (3.5/5), LILT (3.5/5) and Phrase Localization Platform (3.5/5) highest among the other 12 Translation & Localization products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is SimpleLocalize (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Weglot alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement, Hosting location, Legal entity. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 14 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 7 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (15)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.weglot.com Checked 1 Nov 2026 Details →
- 2 Features page www.weglot.com Checked 1 Nov 2026 Details →
- 3 Features page (AI translation quality) www.weglot.com Checked 1 Nov 2026 Details →
- 4 Integrations page www.weglot.com Checked 1 Nov 2026 Details →
- 5 API documentation developers.weglot.com Checked 1 Nov 2026 Details →
- 6 Pricing page www.weglot.com Checked 1 Nov 2026 Details →
- 7 Terms of service and legal notice www.weglot.com Checked 1 Nov 2026 Details →
- 8 Privacy policy www.weglot.com Checked 1 Nov 2026 Details →
- 9 Security / trust page www.weglot.com Checked 1 Nov 2026 Details →
- 10 Security / trust page (trust centre) trust.weglot.com Checked 1 Nov 2026 Details →
- 11 Machine translation & AI quality — found from sitemap www.weglot.com Checked 1 Nov 2026 Details →
- 12 Machine translation & AI quality — found from sitemap developers.weglot.com Checked 1 Nov 2026 Details →
- 13 Integrations, file formats & developer tools — found from sitemap developers.weglot.com Checked 1 Nov 2026 Details →
- 14 Integrations, file formats & developer tools — found from sitemap www.weglot.com Checked 1 Nov 2026 Details →
- 15 Data export, portability & self-hosting — found from sitemap www.weglot.com Checked 1 Nov 2026 Details →