Polylang allows you to create a bilingual or multilingual WordPress site. You write posts, pages and create categories and post tags as usual, and then define the language for each of them. The translation of a post, whether it is in the default language or not, is optional.

  • You can use as many languages as you want. RTL language scripts are supported. WordPress languages packs are automatically downloaded and updated.
  • You can translate posts, pages, media, categories, post tags, menus, widgets…
  • Custom post types, custom taxonomies, sticky posts and post formats, RSS feeds and all default WordPress widgets are supported.
  • The language is either set by the content or by the language code in URL, or you can use one different subdomain or domain per language
  • Categories, post tags as well as some other metas are automatically copied when adding a new post or page translation
  • A customisable language switcher is provided as a widget or in the nav menu

The author does not provide support on the wordpress.org forum. Support and extra features are available to Polylang Pro users.

If you wish to migrate from WPML, you can use the plugin WPML to Polylang

If you wish to use a professional or automatic translation service, you can install Lingotek Translation, as an addon of Polylang. Lingotek offers a complete translation management system which provides services such as translation memory or semi-automated translation processes (e.g. machine translation > human translation > legal review).


Thanks a lot to all translators who help translating Polylang.
Thanks a lot to Alex Lopez for the design of the logo.
Most of the flags included with Polylang are coming from famfamfam and are public domain.
Wherever third party code has been used, credit has been given in the code’s comments.

Do you like Polylang?

Don’t hesitate to give your feedback.


  • The Polylang languages admin panel
  • The Strings translations admin panel
  • Multilingual media library
  • The Edit Post screen with the Languages metabox


  1. Make sure you are using WordPress 4.7 or later and that your server is running PHP 5.2.4 or later (same requirement as WordPress itself)
  2. If you tried other multilingual plugins, deactivate them before activating Polylang, otherwise, you may get unexpected results!
  3. Install and activate the plugin as usual from the ‘Plugins’ menu in WordPress.
  4. Go to the languages settings page and create the languages you need
  5. Add the ‘language switcher’ widget to let your visitors switch the language.
  6. Take care that your theme must come with the corresponding .mo files (Polylang automatically downloads them when they are available for themes and plugins in this repository). If your theme is not internationalised yet, please refer to the Theme Handbook or ask the theme author to internationalise it.


Where to find help ?
Is Polylang compatible with WooCommerce?
  • You need a separate addon to make Polylang and WooCommerce work together. A Premium addon is available.
Do you need translation services?
  • If you want to use professional or automatic translation services, install and activate the Lingotek Translation plugin.


Library interface errors created by Polylang, and inability translate Tagline.

Update to “Re: Polylang does not allow me to see the full image library, and doesn not allow me to change the site tagline into the 2nd site language. ”: This is what Eleganthtemes had written: On Thu, Apr 25, 2019 at 11:39 AM, "Andrei" <andrei@elegant-themes-f149edab9071.intercom-mail.com> wrote:  This is not compatibility issue with Polylang.  If you activate default WordPress theme it should work in the same way. By doing this you can confirm if the issue is in the plugin configuration or if there is compatibility issue. If you change title and tagline in default theme you should see exactly the same result as it's not related to Divi theme or to any other theme, it's related to how the plugin should be configured and used. You will need to check settings of the plugin or contact the plugin developers so they can point you to the right option.  For example here is what I found: https://polylang.pro/doc/strings-translation/ Looking at documentation you will need to use string translation, however on your website all those values are the same: So Polylang is displaying the same values for all languages, you will need to play around with these settings to make the translation work correctly. Polylang is not our plugin, it's created by other developers and they have own support team, so I can't provide you exact instructions about how you can translate your website step by step, you will need to reach out the plugin developers for instructions. Date: 24-04-2019 Time: 21:53 Respected WordPress Community! Re: Polylang does not allow me to see the full image library, and doesn not allow me to change the site tagline into the 2nd site language. 1The error is that the whole wordpress library is not shown when I try to add images to pages on the 2nd site language (in this case the second language is Russian)! 2THE IMAGES THAT YOU SEE TODAY THERE on the page HAD BEEN ADDED BY ME A MANUALLY. The full wordpress image library is simply not “viewable” from the blurb or image or gallery modules on the Russian pages [when using the Divi builder]. 3Divi (Elegantthtemes) had suggested to me that I should use another plugin, as the problem is with Polylang. Apparently Polylang does not allow the Divi to see wordpress images that had been uploaded before the plugin had been activated. Moreover, this means that you must go from image to image, one by one in the wordpress library, and click on the little “+” sign in order to “add” the “language” file version of every image that you would like to use in the 2nd language pages. THIS IS REDICULOUSLY TIRESOME AND A GREAT WASTE OF TIME! 4This “way”, NAMELY to add images manually, should not be the only way to add and SEE IMAGES IN MY LIBRARY! 5Even if it is Polylang that causes the error, which by the way is the MOST WIDELY USED LANGUAGE PLUGIN, I hope you can find a way for me to see ALL OF MY HUNDREDS of images when I look at them via the Russian DIVI EDITOR. With respect, George.
Read all 927 reviews

Contributors & Developers

“Polylang” is open source software. The following people have contributed to this plugin.


“Polylang” has been translated into 31 locales. Thank you to the translators for their contributions.

Translate “Polylang” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Change log

2.5.3 (2019-04-16)

  • Add de_AT and pt_AO to the predefined languages list
  • Pro: Add filter pll_translate_blocks
  • Pro: fix PHP notice when the queried post type has been modified to an array
  • Pro: fix PHP warning when combined with The Event Calendar and Page builder by SiteOrigin

2.5.2 (2019-02-12)

  • Pro: Fix translated slugs not accepting forward slashes
  • Pro: Fix fatal error with ACF Pro 5.7.11
  • Fix parent categories incorrectly synchronised #327

2.5.1 (2019-01-16)

  • Security: Fix categories and media duplication not protected from CSRF
  • Pro: Allow to update the plugin with WP CLI
  • Pro: Fix search in the button block not filtered in the correct language (needs WP 5.1)
  • Add Saraiki to the predefined languages list
  • Fix a conflict causing a blank page with Divi

2.5 (2018-12-06)

  • Add compatibility with WP 5.0
  • Fix custom flags when the WP content folder is not in the WP install folder
  • Fix PHP notice if a language has no flag

2.4.1 (2018-11-27)

  • Pro: Add compatibility with REST API changes made in WP 5.0
  • Pro: Fix sticky posts in the REST API
  • Pro: Fix overwritten custom post slug when the post is updated with the REST API
  • Pro: Fix bulk translate for media
  • Fix a conflict with Custom sidebars and Content aware sidebars
  • Fix a conflict with the theme Pokemania
  • Fix PHP notices when using the function ‘icl_link_to_element’ for terms
  • Fix title slugs for posts written in German

2.4 (2018-11-12)

  • Minimum WordPress version is now 4.7
  • Pro: Add the possibility to bulk duplicate or bulk synchronise posts.
  • Pro: Add compatibility with Admin Columns
  • Pro: Add synchronised posts to the REST API
  • Pro: Fix variations messed when changing WooCommerce attributes slugs
  • Pro: Fix incorrect language for Ajax requests made on front by The Events Calendar
  • Pro: Fix term not duplicated correctly when the language is set from the content
  • Refactor the core to activate on front and for the REST api actions that were previously available only in the backend (language checks, synchronisations…).
  • Add flags to widgets displayed in only one language (Props Jory Hogeveen) #257
  • Honor the filter ‘pll_the_language_args’ for all options in menus #237
  • Add better filters for default flags and custom flags
  • Custom flags can now be stored in the polylang directory in the theme
  • Custom flags can now use SVG
  • Add compatibility with Jetpack featured content module
  • Fix Twenty Fourteen featured posts possibly not filtered per language
  • Fix home URL not working with WordPress MU Domain mapping
  • Fix Assigning a parent category breaking the hierarchy of translated category
  • Fix: Accept 0,1 and 1.0 as q factors in browser preferred language detection (Props Dominic Rubas)
  • Fix performance issue when using hundreds of widgets
  • Fix translations possibly wrong if the post language is changed without saving the post after

See changelog.txt for older changelog