[Comparison]

Polyglot vs Weglot

Code-Level vs Website-Level Translation

Comparing Polyglot and Weglot for multilingual apps. Understand the difference between code-level i18n with AST detection and website-level translation via proxy.

Updated September 22, 20265 min read← All comparisons
[01]Overview

Weglot and Polyglot solve multilingual content in fundamentally different ways. Weglot is a website translation layer — it sits between your site and your users (as a proxy or a JavaScript snippet) and replaces text with translations. Polyglot works at the code level — it scans your source code, finds hardcoded strings, and produces translation files that your i18n library renders at runtime.

This isn't a "which is better" question — they're different tools for different use cases. The confusion happens because developers often try Weglot first (it's easy to set up), then realize they want translations in their codebase for an app with lots of dynamic or non-website content.

[02]Quick comparison
FeaturePolyglotWeglot
How it worksCode-level (AST detection + catalog files)Website-level (proxy or JS snippet)
String detection✓Yes (tree-sitter AST)✓Yes (detects visible text on pages)
Works with SPAs/React apps✓Yes (native)✓Yes (dynamic content can need extra setup)
Works with static sites✓Yes✓Yes (excellent)
Works with mobile appsDetection for React Native and Flutter (runtime support varies)✕No
Translation approachLLM with contextAI translation + human editing
Local preview✓Yes (polyglot preview)Live on site (proxy)
SEO (hreflang, subdomains)You manage itAutomatic
CLI supportPrimary interface✕No
Free tierFree local scanning, 500 source strings (lifetime)✓Yes (2,000 words)
Starting price$0€15/mo (≈$17; Starter, 10,000 words)
Translations in your repo✓Yes (catalog files)No (hosted on Weglot)
Framework supportDetection: Next.js, Astro, SvelteKit, Vue, Angular, React Native, FlutterAny website it can serve or load its script on

Weglot's plans are priced by translated words; page views are tracked but not billed per view. Competitor pricing checked September 22, 2026.

[03]Where Weglot excels

Weglot is excellent at what it does — website translation:

01

Zero-code setup

Add a script tag or DNS change, and your entire website is translated. For marketing sites, landing pages, and content-heavy sites, this is genuinely the fastest path to multilingual.

02

Automatic SEO

Weglot handles hreflang tags, subdirectories or subdomains, and search engine indexing automatically. For WordPress sites and static marketing pages, this is a significant time saver.

03

Visual editor

Weglot's dashboard shows your actual website with translations overlaid. Translators edit strings in context, seeing exactly how they appear on the page.

04

WordPress integration

Weglot is one of the most popular WordPress translation plugins. If your site is WordPress, Weglot is the path of least resistance.

[04]Where Polyglot excels
01

Application translation

Polyglot works at the code level, so translations for SPAs, dynamic content, and client-side rendering live in your i18n library's catalogs. Detection covers Next.js, Astro, SvelteKit, Vue, Angular, React Native and Flutter; runtime support varies by setup, and Next.js App Router with next-intl is the best-tested path. With a website-level layer, content that appears after user interaction — modals, toasts, error states — can take extra configuration to catch.

02

String detection in code

Polyglot finds hardcoded strings in your source files — strings that are in your code, not yet rendered on a page — and flags them inline via a VS Code extension as you write. Weglot detects strings that appear in the rendered page.

03

LLM translation quality

Polyglot translates with fine-tuned LLMs, sending component context and glossary terms with each string. It scored 4.96/5 across 49 languages on our June 2026 pipeline, AI-judged — reproducible benchmark. Weglot offers AI translation with manual editing in its dashboard.

04

Version-controlled translations

Polyglot writes translation files to your repo — JSON, YAML, ARB, iOS .strings, or Android XML. They're in git, reviewable in PRs, and deployed through your CI pipeline. Weglot hosts translations on its servers and serves them through its service.

05

No third-party translation layer

Your app loads translations through your own i18n library. It doesn't depend on Weglot's service being online. With Weglot, if the service is unavailable, your site can show untranslated content.

06

Mobile catalogs

Polyglot's detection covers React Native and Flutter, and it can export iOS .strings and Android XML. Check runtime support for your setup. Weglot is web-only.

[05]The fundamental architectural difference

Weglot translates your rendered output (HTML). It doesn't know about your code, your components, or your build process. It works on what your site sends to the browser and replaces text.

Polyglot translates your source code's strings. It understands your component structure, identifies likely user-facing strings (via AST analysis), and produces translation files that your i18n library uses at runtime.

This means:

  • →Weglot works instantly but gives you less control and adds a runtime dependency on its service
  • →Polyglot requires i18n library setup but gives you full control and no third-party translation service at runtime
[06]The verdict

Who should choose Weglot

Weglot is the right choice if

→You have a static marketing site or WordPress site that needs quick translation
→You want zero-code setup — add a script tag and you're done
→You need automatic SEO (hreflang, subdomains) without manual configuration
→Your content is primarily server-rendered HTML (not a client-side SPA)
→You don't need translations in your git repo

Who should choose Polyglot

Polyglot is the right choice if

✓You're building a JavaScript application (React, Next.js, Astro, SvelteKit, Angular, React Native)
✓You need to translate dynamic content (SPAs, client-rendered UI, modals, toasts)
✓You want translations in your repo as version-controlled catalog files
✓You need to find hardcoded strings in your source code
✓You want no runtime dependency on a third-party translation service
✓You're building with React Native or Flutter and want detection there too (runtime support varies)

Start in your terminal

Stop hunting for untranslated strings.

Install the CLI, run a scan, and see exactly what you're missing. Free, no account required.

$curl -fsSL https://getpolyglot.ai/install.sh | bash
Polyglot vs Weglot: Code-Level vs Website-Level Translation | Polyglot