Best Free Multilingual WordPress Plugin: What You Can Actually Build for €0 (2026)

Free-tier limits and prices verified August 2026.

Most “best free multilingual plugin” articles are really best-plugin articles with the word free attached. They list six tools, three of which have no free version at all, and leave you to work out which ones you can actually use.

This one is a test. Five requirements, one question: can you launch a working bilingual site without paying? Three plugins pass. Everything else fails on a specific, nameable point — and knowing which point is more useful than another feature list.

If you want the full market picture including paid tools, we have a separate comparison of seven plugins. This article is only about what €0 buys.

The test

A free tier passes if it can do all five of these without a licence:

1. Two or more languages. A plugin capped at one additional language builds bilingual sites only. That’s a legitimate product, but it isn’t multilingual.
2. Indexable translated URLs. A real /es/ URL that Google can crawl. Browser-side translation widgets don’t count — search engines never see the translated content.
3. hreflang and canonicals. Without these, your language versions compete with each other instead of reinforcing each other.
4. Interface strings, not just content. Theme buttons, menu labels, checkout text, widget headings. A site with translated posts and English “Read more” buttons is half-translated.
5. A clean exit. What happens to your database when you deactivate. This is the requirement nobody tests until it’s too late, and it separates the three passing plugins more sharply than anything else.

Requirements 1–4 are what you need on day one. Requirement 5 is what you’ll care about in month six.

The three that pass

LATW Multilingual

Free tier: unlimited languages · language-specific URLs · hreflang, canonicals, sitemap, html lang · manual translation in Gutenberg · built-in .po/.mo editor for theme and plugin strings · media translation (titles, alt text, captions, descriptions) · switcher as block, widget, shortcode, or PHP function

It passes all five requirements, and the fifth one is where it separates from the other two.

LATW uses an overlay architecture. One canonical post stays in wp_posts; translations live in the plugin’s own tables and are swapped in at render time. A 500-post site in four languages stays 500 posts. Deactivate the plugin and your content is exactly as it was — no orphaned translations, no cleanup, no restore-from-backup.

That’s a maintenance property rather than a feature, which is why it doesn’t show up on comparison grids. It’s also the single thing that makes trying a multilingual plugin cheap: if it doesn’t work out, you’re not stuck with the consequences.

Where it loses. It’s the newest plugin here and has the smallest library of tested theme, builder, and plugin integrations. On a mainstream stack that’s a non-issue. On a heavily customised Divi build with a dozen commercial plugins, WPML’s decade of compatibility work is genuinely worth paying for, and we’d rather say that than have you find out on a client’s site. There’s also no visual front-end editor — if clicking text on the page is how you want to translate, TranslatePress is more pleasant even with its one-language cap.

Paid tier adds automation rather than paywalling multilingual basics: BYOK AI translation through your own OpenAI key, bulk translation, auto-translate on publish, glossary, translation memory, and a queue that estimates cost before you spend.

Polylang

Free tier: unlimited languages · language-specific URLs · hreflang · posts, pages, CPTs, categories, tags, menus · string translation · media translation Installs: 800,000+

Polylang passes on requirements 1–4 without qualification, and it has something no other plugin here can offer: a decade of accumulated community knowledge. Whatever edge case you hit, someone has already posted about it. If your preferred way out of a problem is a search engine rather than a support ticket, that’s worth more than any architectural argument.

The workflow is manual and explicit. Create the post, click + next to the target language, write the translation. The two are linked as language versions. For teams where a mistranslation is expensive — legal, medical, technical — that explicitness is the point.

Where it costs money. Translated slugs are Pro-only, so your French page sits at /fr/contact-us/ rather than /fr/contactez-nous/ until you pay €99/year. ACF Pro and REST API support are also Pro. WooCommerce is a separate €99/year, which makes a multilingual Polylang store €198/year before a word is translated.

On requirement 5: Polylang’s duplicate-post model means translations survive uninstalling — as unlinked, orphaned posts with no language context. 500 posts in four languages leaves 1,500 entries behind. Not destructive, but a real cleanup job.

Multilanguage by BestWebSoft

Free tier: 80+ languages · manual translation of posts, pages, categories, tags, menus, widgets · customisable switcher (flags, dropdown, list) · automatic hreflang · Open Graph translation · Classic and Gutenberg · RTL support Pro: €39/year per domain, or €380 lifetime

It passes the first three requirements and does so at the lowest price point in the category if you ever upgrade — €39/year undercuts everything else here by a wide margin.

It belongs on a genuinely-free list, and most roundups either omit it or misrepresent what it does. For a five-page local business site that needs a Polish and English version and will never grow past that, it’s a reasonable choice.

Two things to know before installing. Interface string coverage is partial, and slug translation, custom fields, custom post types, Elementor, Yoast, and WooCommerce integration all sit behind Pro — a narrower free tier than the headline suggests.

More importantly, there’s a recurring report on the WordPress.org page from a user who deactivated the plugin and found pages missing, requiring a restore from backup. We haven’t reproduced it and can’t confirm the cause. But it’s exactly the requirement-5 failure mode that most people never think to test — and it’s a reminder to take a full backup and try any multilingual plugin on staging first, whichever one you pick.

The three that fail, and where

These aren’t bad plugins. Two of them are better than us at something. They just don’t clear the bar this article is testing for.

TranslatePress — fails on language count

One additional language in the free tier. That’s the hard stop, and it’s underplayed in most roundups because everything else about the free version is generous: visual front-end editor, WooCommerce support, gettext strings, image translation, 2,000 AI words.

The visual editor is the best translation experience in this comparison and nothing here is close. You browse your site, click any text — heading, button, form label — and translate it with the page visible beside you. For a non-technical site owner doing their own translation, that’s worth more than everything on our feature grid.

If two languages is genuinely your ceiling, stop reading and install TranslatePress. If there’s any chance of a third, you’re looking at €99/year — at which point you’re comparing a paid tier against free ones, and the SEO Pack (translated slugs, translated meta titles and descriptions) is also in that €99.

One thing most comparisons get wrong, including an earlier version of ours: TranslatePress doesn’t duplicate your posts. It translates string by string into its own tables and keeps a single canonical post, so wp_posts stays flat. The catch is on the way out — those strings don’t convert into another plugin’s format, and the tables stay behind when you deactivate.

GTranslate — fails on SEO, completely

It’s a JavaScript widget. When a visitor picks a language, Google Translate rewrites the rendered HTML in their browser. No /es/ URL. No page for Google to crawl. No hreflang. Nothing in your sitemap. Nothing stored anywhere. Search engines see your site in one language, permanently. GTranslate documents this themselves; it gets lost anyway, because “103 languages, free” with 900,000 installs reads like a multilingual site to most people.

When it’s the right tool anyway: when visitors who already found you simply need to read the page in their language. An intranet, a documentation site, a support portal, a local business whose customers arrive via map search. Zero setup, 103 languages, genuinely useful. It’s an accessibility widget, not an SEO tool.

Indexable URLs start at $199.90/year — more than WPML, Polylang Pro, or TranslatePress Personal.

Weglot — fails on both language count and word count

2,000 words, one language, and it’s a cumulative total, not a monthly refill. Roughly a homepage plus an about page. Exceed it and Weglot stops serving translations until you upgrade. The counter only goes up, so a blog that publishes weekly is on an escalator toward €149/year and beyond.

What Weglot genuinely is: the fastest setup in the category by a wide margin. Install, connect, pick languages, done — no configuration decisions, no API key, no thinking about architecture. For an agency shipping a client’s bilingual site by Friday, that’s often the correct commercial call. It just isn’t a free plugin, and the free plan is a trial with no expiry date rather than a tier.

Two that aren’t in the running

WPML has no free version. Plans start at $39/year for a single site, $99 for Multilingual CMS, $199 for Agency, with automatic translation billed separately in credits (1 word costs 1–4 credits; 2,000 credits free per month). It’s the most capable multilingual framework for WordPress and the compatibility library is the reason it costs money — but it doesn’t belong on a free shortlist.

If you already run WPML and it’s the credit bill rather than the plugin that hurts, you don’t have to leave: LATW AI Translator for WPML plugs into WPML’s own translation editor and routes jobs through your OpenAI key. Same setup, same URLs, different billing.

MultilingualPress is premium-only now — $149/year minimum. The old v2 on WordPress.org is retired. If you found it via a listicle promising a free multisite multilingual solution, that listicle is out of date.

What breaks after six months

Everything above is about day one. The failures that actually cost you are slower.

Post-table sprawl. Duplicate-post plugins (Polylang, WPML) create a real post per language. At 20 pages, invisible. At 500 posts × 4 languages, your admin list tables, exports, search, and any plugin that queries wp_posts are all working against 2,000 rows instead of 500.

Content drift. With separate posts per language, updating the English version doesn’t flag the French one. Six months in, your translations quietly describe an older version of your product. Overlay architectures tie translations to a single canonical post, so drift is visible rather than silent.

Slug debt. If you launch on untranslated slugs and add them later, every translated URL changes. That means redirects for every page, and a ranking dip while Google reprocesses. Cheaper to decide before launch than after.

The exit. Covered above, but worth restating as a planning question rather than a feature: if this doesn’t work out in three months, what does undoing it cost? Overlay: nothing. Duplicate-post: orphaned posts to clean up. SaaS: export, rebuild, and the translated site goes dark when you stop paying. Free GTranslate: nothing, because nothing was ever stored.

Choosing

You want a genuinely free multilingual site with working SEO. LATW Multilingual. Unlimited languages, full SEO signals, string and media translation, clean uninstall — all at €0. Unless community size matters more to you than architecture, in which case Polylang’s 800,000 installs and decade of documentation is the safer bet.

Two languages, and you’ll be doing the translating yourself. TranslatePress. The visual editor is worth accepting the one-language cap for. Unless a third language is plausible, or you need translated slugs — both push you to €99/year, and at that point LATW’s free tier does the same job.

A small site that will stay small. Multilanguage by BestWebSoft covers the basics, and €39/year is the cheapest upgrade path in the category. Unless you want string coverage or a builder integration, which are Pro-only — and test deactivation on staging before you commit.

A WooCommerce store. LATW Multilingual. Products, attributes, variations, category archives, cart and checkout strings, and transactional emails are covered on the free tier — Polylang charges a separate €99/year for the same, WPML gates it behind the $99 CMS tier. The overlay architecture matters more on a store than anywhere else: a 500-product catalogue in four languages stays 500 products instead of becoming 2,000.

A heavily customised build with a large plugin stack. WPML, and it isn’t close. If the site runs a page builder plus a dozen commercial plugins with their own post types and field groups, compatibility is the problem, and WPML has spent over a decade solving it. LATW has the smallest tested-integration set here — on a mainstream stack that’s fine, on a deadline with twelve unusual plugins it’s a risk you shouldn’t take.

You want it live this week and cost isn’t the constraint. Weglot. It’s the least work by a wide margin. Just don’t call it free.

The bottom line

Of the plugins that show up in most “best free multilingual WordPress plugin” roundups, two have no free version, two cap the free tier at a single additional language, and one produces translations search engines never see.

That leaves three that pass a basic test, and two that pass it comfortably: LATW Multilingual and Polylang. Both give you unlimited languages, indexable URLs, hreflang, and string translation for nothing. Choose LATW if you want translated slugs included, media translation, and an uninstall that leaves no trace. Choose Polylang if the size of the community and the volume of existing documentation matters more than architecture.

Whichever you install: take a full backup, test on staging, and check Search Console for your translated URLs before you scale. Requirement 2 is the one people assume and the one that most often isn’t there.

Try LATW Multilingual free →

FAQ