WPML Alternative 2026: Free Plugins, Pricing and Multisite Compared

Hardly any decision shapes a WordPress website for as long as the choice of multilingual plugin. It determines URL structure, database layout, performance, and how painful a later switch will be. And hardly any decision is regretted as often: "WPML alternative" has been one of the most stable search queries in the WordPress world for years. Not because WPML is bad, but because many projects only realize what they've built in after they've built it in.

What WPML does well, and what it costs

In fairness: WPML is the most complete tool on the market. Posts, taxonomies, menus, widgets, theme strings, WooCommerce: it translates practically everything, and its string-translation approach has no equal for complex sites. The price for that is architecture: WPML creates its own tables, hooks into nearly every database query, and manages language URLs through its own rewrite logic. Every query that passes through extra logic costs processing time, and removing it is a project, not a click. If you want to know how plugin weight affects load times in general, we've covered the fundamentals in our post on speeding up a slow WordPress site.

There is no free version of WPML. The cheapest license, Multilingual Blog, costs €39 a year according to the WPML pricing page and includes neither String Translation nor WooCommerce support; both start with Multilingual CMS at €99 a year (as of 4 October 2026). You won't find WPML in the WordPress plugin directory either. According to wordpress.org, the listing WPML Multilingual CMS has been closed since 28 November 2017. Polylang, TranslatePress, Weglot and Wimpel are all listed, which means they passed the plugin team's review and install straight from your dashboard, no customer account needed. The only WPML product listed is its WooCommerce extension, with an install band of 100,000+ according to our census profile of WPML for WooCommerce (snapshot 28 August 2026). Its free features cover currencies. Translating the store itself requires a purchased WPML license, as the listing says.

Free WPML alternatives: what the free versions actually do

Looking for a free WPML alternative? Then you want to know whether the free version is enough for your site, and where it starts costing money. The table answers both for four routes that start without a license, based on each plugin's wordpress.org listing and the vendor's official pricing page, checked on 4 October 2026. Installs, ratings and release gaps come from our Plugin Directory Census 01/2026, snapshot 28 August 2026. wordpress.org reports installs only as a band, so 800,000+ means at least 800,000.

Side by side, the lines sit in very different places. Polylang's free version is the most generous: no language limit, menus included. Run a shop, though, and you pay anyway, because WooCommerce sits in the add-on. TranslatePress draws the line exactly where a site goes international: the second language is free, the third is not. Multisite only looks free. The network costs nothing; connecting the languages does, either as a license or as manual work on every hreflang reference.

With Wimpel, the paywall separates manual work from machine work. Language management, linking, hreflang and the switcher run fully in the free version, and the translating is up to you or any tool you like. AI translation with your own provider key and the market assistant with a cost estimate before each run are Pro.

The alternatives at a glance

Polylang: the free classic

Polylang is the most obvious WPML alternative: free at its core, in the directory since 2011, with an install band of 800,000+ according to our census of the plugin directory. The architecture resembles WPML (languages as taxonomies, connected posts, a language code in the URL), but by its own description it relies only on WordPress core features. The main caveat is removal. Translations survive as posts, but the language assignment and addresses like /en/ depend on the plugin. Remove Polylang and you still have your texts, just no working language structure.

TranslatePress: translating in the frontend

TranslatePress has the friendliest interface: you click on a text in the frontend and translate it right there, theme and plugin strings included. For editors that's wonderful. The free version covers a bilingual site; the third language is where the license starts. Technically, TranslatePress translates the rendered page and stores segments in its own tables. That works, but it couples the translation to the presentation instead of the content. On larger sites the segment database grows noticeably.

Weglot: convenient, but rented

Weglot is a SaaS service: install it, pick languages, done. Translation runs through Weglot's servers, and the translated pages are delivered from there. It's the fastest route to a multilingual site and, in the long run, the most expensive: billing is by word count and page views, your own content sits in someone else's infrastructure, and when you cancel, the multilingualism is gone. You're renting your own website back in translation. There is a free tier, but according to the Weglot pricing page it stops at 2,000 words and one language; Starter costs $17 or €15 a month (as of 4 October 2026).

MultilingualPress: one site per language

MultilingualPress connects the sites of a WordPress multisite network into language versions. Architecturally this is the cleanest classic approach: each language is a full site, nothing gets rewritten. The current version is license-only. When a network is worth it is covered further down.

Wimpel: translations as normal posts

Our own plugin Wimpel (full transparency here as always) needs no rewrite rules and no proxy, and translations never end up in a custom table. A translation is a perfectly normal post with its own permalink; Wimpel only remembers language, translation group, and homepage status and generates hreflang references, language switchers, and language filters from that. In Pro, the one-click market assistant opens up a new language with an honest cost estimate before you start (AI translation on the BYOK principle, using your own provider key). And the architectural proof: if you uninstall Wimpel, you don't lose a word or an address. The translations were never anything but content.

The 51-second short puts that to the test: Wimpel deleted, both posts still in the post list, the English page still under its own address. What goes is what the plugin adds on top, the language switcher and the hreflang lines in the page head. The uninstall option that removes Wimpel's own linking data is off by default, and even switched on it leaves posts and pages alone.

Video: Your translations after deleting the plugin51 seconds · YouTube Short · loads only after a click

Here too, the honest limits: Wimpel doesn't translate menus, categories, or theme strings, and doesn't generate /en/ prefixes by itself. If you run a WooCommerce site with 40 language variants, WPML is the right choice. If you want to seriously tackle two or three language markets without rebuilding your WordPress, you're Wimpel's target audience, and a language market is more than a translation, after all.

WPML vs Multisite: when a network is the better choice

Comparing WPML and Multisite means comparing two ways of building a site. WPML, like Polylang, TranslatePress and Wimpel, keeps all languages in one installation and links translations post by post. Multisite turns each language into its own website inside a shared network. According to the WordPress documentation on creating a network, the sites share the core files but have their own database tables and their own upload folders.

A network plays to its strengths when your languages are really markets that drift apart:

• Country sites carry their own products, prices or legal pages that are not translated one to one.
• Each language has its own team that should only see and edit its own site.
• Markets run on their own domains, and one of them may later be switched off or handed over without touching the rest.

What you get is a clean separation. Content, roles and media library belong to one language each, while core and plugins are still updated once for the whole network.

The downside starts in the setup guide. The documentation asks for a backup and deactivated plugins before you begin, and the choice between subdomains and subfolders is hard to change afterwards. Only the network admin installs plugins; individual sites can merely activate them. Day-to-day operation adds a few more:

• Every site has its own media library. A product image that appears in five languages gets uploaded five times, or you need yet another plugin.
• The sites know nothing about each other. WordPress doesn't know which page translates which, so without an extra plugin or manual upkeep there is no hreflang and no language switcher that leads to the matching page.
• Not every plugin is built for networks. Check each one before you switch.
• The way back is long. Turning a network back into a single installation is a migration, not a setting.

Our take: if your languages are translations of the same offer, use a translation plugin. If they are separate markets with their own people and their own domains, Multisite is the more honest architecture, and you may not need WPML at all. For two or three languages on a regular business site, a network is admin work with nothing in return.

hreflang: where multilingual sites fail in Google

Whichever route you take, Google learns which page is which language version through hreflang references. According to Google Search Central's documentation on localized versions, each language version must list itself and all other versions, and if two pages don't point to each other, Google ignores the tags. Tools that derive hreflang from a maintained link between posts get this right by construction. In a multisite network without a connecting plugin, someone keeps the references in sync by hand, and that someone is you, for every new page in every language.

What we measured on a real site

For Wimpel we checked this on someone else's site, not on a demo. In our bilingual WordPress case study, the free directory version ran on 14 September 2026 on an installation with 22 pages, 67 posts and eight other active plugins. The numbers:

• 13 German/English page pairs were built in one day. Afterwards, all 26 pages carried exactly three hreflang references: German, English, x-default.
• The one page we deliberately left monolingual got no reference at all. Had Wimpel printed one there, it would have promised Google a translation that doesn't exist.
• We compared seven translation drafts with their source, character by character. The front page, with 191 blocks, two HTML islands and three inline scripts, came through untouched: 88,963 characters in the source, 88,963 in the copy.
• The next day the site owner rebuilt four pages and added a new one. All 14 page pairs still pointed at each other correctly.

Fairness requires the rest of the findings too. Page template and parent page did not carry over when copying, and there was no notice for outdated translations; it's all in the case study. For your own choice, the method matters more than our result: leave one page monolingual on purpose and check the page source to see whether your plugin still prints hreflang. It takes two minutes and works with every tool in this comparison.

Comparison table

Entry prices according to each vendor's site, as of 4 October 2026.

Our recommendation

For shops with many languages and string-translation needs, WPML remains the most complete choice, with Polylang as the free approximation, plus a paid add-on for WooCommerce. If you want to make translating as easy as possible for editors, take TranslatePress. Weglot buys speed with ongoing costs and dependency. Separate markets with their own teams belong in a multisite network. And if you want to add languages without rebuilding URLs and database, take a look at Wimpel: translations are posts of their own with normal permalinks that survive any uninstall, addresses included. For how it sits against those yearly figures, see our pricing.

Frequently asked questions