Feature	Paragraphs	WPML	Polylang	TranslatePress	Weglot
Storage model How translations are persisted	External graph (fingerprinted)	Duplicate posts per locale	Duplicate posts per locale	String table in WP DB	Vendor-hosted, JS injection
URL flexibility Subdir / subdomain / TLD	Yes	Plugin-dictated	Plugin-dictated	Subdir only	Yes
Headless support Works without a WP frontend	Yes	No	No	No	Partial (JS)
Next.js / Astro / Nuxt First-class adapters	Yes	No	No	No	No
Translated JSON-LD Schema.org structurally translated	Yes	As strings	No	No	As strings
Per-locale llms.txt AISEO surface	Yes	No	No	No	No
Edge delivery Translation at the edge, not in PHP	Yes	No	No	No	JS injection
Translation memory Re-use prior translations across units	Yes	Manual ICL	No	No	Yes
Glossary enforcement DNT / forced / suggested	Yes	Manual	No	Manual	Yes
In-context editor Live front-end editing	Yes	No	No	Yes	Yes
Branches Stage and merge translations like code	Yes	No	No	No	No
Export your translations Own your data	Yes	Yes	Yes	Yes	Vendor lock-in
EU + US data residency Lockable at signup	Yes	Self-hosted only	Self-hosted only	Self-hosted only	No

Last updated 2026-05-12. We update this table when the incumbents change. Spot something wrong? Let us know.

Migrating from one of these?

WPML, Polylang, and TranslatePress all have one-command importers. Weglot exports to JSON; we can ingest.