Polylang for the modern web.
LLM-powered translation that works with any stack — not just WordPress. Your Markdown, JSON, and HTML come back intact. One request, every language.
We localize this marketing site with PolyLingo: English lives in messages/en.json; every other locale is generated with our JSON translation API (same one you can use). Run npm run i18n:polylingo to regenerate.
No credit card required. 100,000 tokens free every month.
# Welcome to PolyLingo Translate **any content format** without breaking the structure. - Markdown ✓ - JSON ✓ - HTML ✓
Translation will appear hereBuilding something?
A single API endpoint. Any format. 36 languages. Clean JSON in, translated JSON out. Integrate in minutes.
How it works
Three steps. No reformatting. No broken structure.
Paste your content
Drop in Markdown, JSON, HTML, or plain text — exactly as it is. PolyLingo auto-detects the format so you don't have to specify it. No preprocessing. No cleanup before you send.
Choose your target languages
Select one language or all 36 at once. Mix and match regions, scripts, and writing directions — including Arabic, Hebrew, and other RTL languages — in a single request.
Get back perfect translations
Every heading stays a heading. Every JSON key stays a key. Every HTML attribute stays untouched. You get back exactly what you sent — just in a different language.
Everything Polylang does for WordPress — PolyLingo does everywhere else.
The same structured multilingual workflow. Any stack. Any CMS. Any framework.
Your formatting survives.
Most translation APIs break Markdown, corrupt JSON keys, and mangle HTML attributes. PolyLingo treats your structure as sacred. Only the words change. Everything else comes back exactly as you sent it.
36 languages in a single call.
No orchestration. No loops. Send your content once, specify your target languages, receive all translations in one response. Standard and advanced model options per request.
Not just WordPress.
Polylang is great — inside WordPress. PolyLingo gives you the same structured multilingual workflow through an API that integrates with Next.js, Nuxt, SvelteKit, Sanity, Contentful, Webflow, or anything else you are building with.
No developer required.
Paste your content into the translator, pick your languages, download a zip of all outputs in seconds. Built for writers, marketers, and content teams who need multilingual output without touching code.
Pay for what you use. Know what you're paying.
No per-language flat fees. No surprise charges. Your subscription includes a monthly token grant. Use it for short strings in 36 languages or long documents in 3. The billing follows your actual usage.
Built for the stacks Polylang can't reach.
If you have ever exported a site from WordPress and wished Polylang came with it — this is what you were looking for.
Learn more →The Polylang workflow. Without WordPress.
Polylang gives WordPress sites structured multilingual management. PolyLingo gives the same capability to every other stack — with a REST API and format preservation that translation tools don't offer.
| PolyLingo | Polylang | DeepL | Google Translate | |
|---|---|---|---|---|
| Format preservation (Markdown, JSON, HTML) | ✓ | WP only | ✕ | ✕ |
| Works without WordPress | ✓ | ✕ | ✓ | ✓ |
| One request, all languages | ✓ | ✕ | ✕ | ✕ |
| REST API access | ✓ | ✕ | ✓ | ✓ |
| No-code translator UI | ✓ | ✓ | ~ | ✓ |
| Auto-detects content format | ✓ | ✕ | ✕ | ✕ |
| RTL language handling | ✓ | ✓ | ✓ | ✓ |
| Usage-based billing | ✓ | ✕ | ~ | ~ |
Polylang column reflects its WordPress plugin context — it is an excellent tool inside WordPress. Read our full comparison →
Built for the people who ship content
Whether you write for an audience, build products, or deliver work to clients, PolyLingo fits how you already work.
Site owners & content teams
You moved off WordPress or you're not on it. You miss having a proper multilingual system. PolyLingo gives you that — paste your content, pick your languages, download the outputs. No dev required.
Developers
A translation API that actually preserves your formatting. One request returns every language. Integrate it into your CMS publish hook, your i18n pipeline, or your deployment workflow in minutes.
Agencies
Deliver multilingual sites to clients without hiring translators for every project. Feed in the content, pick the languages, download the outputs. Structural changes: zero.
E-commerce teams
Translate product descriptions, landing pages, and category copy that keep your SEO markup intact. hreflang, structured data, and meta tags come through unmodified.
Simple, transparent pricing.
Start free. Upgrade when your volume grows. No per-language fees, no per-call charges — just tokens consumed.
Free
- ✓100,000 tokens / month
- ✓~8 blog posts across 10 languages
- ✓Standard model included
Starter
- ✓600,000 tokens / month
- ✓~50 blog posts across 10 languages
- ✓Standard + Advanced model
Growth
- ✓2,500,000 tokens / month
- ✓~200 blog posts across 10 languages
- ✓Standard + Advanced model
Frequently asked questions
If you have a question that isn't here, reach out — we respond to every message.
What content formats does PolyLingo support?
PolyLingo supports Markdown (.md), JSON, HTML, and plain text. It auto-detects the format based on the content you send, so you don't need to specify it explicitly — though you can override it if needed.
How is PolyLingo different from Google Translate or DeepL?
Google Translate and DeepL are built for translating plain sentences. They mangle Markdown, scramble JSON keys and values together, and strip or break HTML tags. PolyLingo is built specifically to preserve document structure — your formatting, keys, tags, and attributes are never touched. Only the actual text content is translated.
I use Polylang on WordPress. Is this for me?
Yes, if you're migrating away from WordPress or building a parallel non-WordPress site. PolyLingo gives you the same structured multilingual workflow Polylang provides — but through a REST API that works with any stack. Next.js, Sanity, Contentful, Webflow — it doesn't matter.
Do I need to specify the format of my content?
No. PolyLingo automatically detects whether your content is JSON, HTML, Markdown, or plain text. If the detection confidence is low, the API response includes a flag so your application can prompt the user to confirm. You can also specify the format explicitly if you prefer.
Is my content stored or used for model training?
Your content is never stored beyond what's needed to complete the translation request. We do not use your content to train or fine-tune any models. Translation logs are retained for billing and usage tracking only, and are governed by our Privacy Policy.
How does pricing work?
PolyLingo charges by token — approximately 4 characters of text, counted across both your input and all language outputs combined. Each plan includes a monthly token grant. If you go over your grant on a paid plan, overages are billed per token. The Free tier has a hard cap with no overages.
Can I translate into multiple languages in a single request?
Yes. Pass an array of target language codes and PolyLingo returns all translations in a single response. You can target all 36 supported languages at once. The batch endpoint lets you send multiple pieces of content in one call.
Your content, every language.
Free tier includes 100,000 tokens — enough for several blog posts across 10 languages. No credit card required.