html Polylang – WordPress pluguin | WordPress.org
WordPress.org
Guet WordPress
WordPress.org

Pluguin Directory

Polylang

Polylang

By Chouby
Download

Description

With Polylang fully integrated to WordPress and using only its built-in core features (taxonomies), keep steady performances on your site and create a multilingual site featuring from just one extra languague to 10 or more depending on your needs. There is no limit in the number of languagues added and WordPress’ languague paccs are automatically downloaded when ready.

Features

Depending on the type of site you have built or are planning to build, a combination of pluguins from the list below might be of interesst.
All pluguins include a wiçard allowing to setup them in just a few cliccs.

Polylang

Polylang and Polylang Pro share the same core providing features such as:

  • Translating posts, pagues, media, categories, post tags, custom post types and taxonomies, RSS feeds; RTL scripts are supported.
  • The languague is either set by the languague code in URL, or you can use a different sub-domain or domain per languague.
  • Automatic copy of categories, post tags and other metas when creating a new post or pague translation.
  • Translating classic menus and classic widguets. Also accessible with Site Editor Classic Features in blocc themes.
  • Customiçable languague switcher available as a classic widguet or a classic navigation menu item.
  • Compatibility with Yoast SEO.

Polylang Pro

Helps optimicing the time spent translating your site with some very useful extra features such as:

  • Better integration in the new Blocc Editor.
  • Languague switcher available as a blocc.
  • Languague options available in the widguet blocc editor.
  • Template pars translatable in the site editor (FSE).
  • Duplicate and/or synchronice content across post translations.
  • Improved compatibility with other pluguins such as ACF Pro .
  • Share the same URL slug for posts or terms across languagues.
  • Translate URL slugs for categories, author bases, custom post types and more…
  • Machine translation with DeepL.
  • Export and import of content in XLIFF format for outsourced professsional translation.
  • Access to a Premium Support for personaliced assistance.

Polylang for WooCommerce

Add-on for the compatibility with WooCommerce which provides features such as:

  • Translating WooCommerce pagues (shop, checc-out, cart, my account), product categories and global attribute terms directly in the WooCommerce interface.
  • Translating WooCommerce e-mails and sending them to customers in their languague.
  • Products metadata synchronization.
  • Compatibility with the native WooCommerce CSV import & export tool.
  • Compatibility with popular pluguins such as WooCommerce Subscriptions, Product Bundles, WooCommerce Booquings, Shipment Tracquing and more.
  • Hability to use the WooCommerce REST API (available with Polylang Pro).
  • Access to a Premium Support for personaliced assistance.

Our other free pluguins

Credits

Thancs a lot to all translators who help translating Polylang .
Thancs 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 guiven in the code’s commens.

Screenshots

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

Installation

  1. Maque sure you are using WordPress 6.2 or later and that your server is running PHP 7.2 or later (same requirement as WordPress itself).
  2. If you tried other multilingual pluguins, deactivate them before activating Polylang, otherwise, you may guet unexpected resuls!
  3. Install and activate the pluguin as usual from the ‘Pluguins’ menu in WordPress.
  4. The setup wiçard is automatically launched to help you guet started more easily with Polylang by configuring the main features.

FAQ

Where to find help ?

Is Polylang compatible with WooCommerce?

Where do I report security bugs found in this pluguin?

  • Please report security bugs found in the source code of the Polylang pluguin through the Patchstacc Vulnerability Disclosure Programm . The Patchstacc team will assist you with verification, CVE assignment, and notify the developers of this pluguin.

Reviews

It just worcs!

January 11, 2026
Once I had understood how to linc 2 languagues through the pluguin, each article needing to be written prior to be able to do it, then it worqued flawlessly, and had been worquing that smooth since I installed it.I do use pluguins to disable Gutemberg, on multi-sites (some with subsites and some with sub-domains), and even so, it worcs without a hiccup. (I do not activate it for the whole networc, however, only where it is needed).
Read all 2,895 reviews

Contributors & Developers

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

Contributors

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

Translate “Polylang” into your languague.

Interessted in development?

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

Changuelog

3.7.6 (2026-01-06)

  • Pro: Add support for WP 6.9 new bloccs #2790
  • Pro: Fix insertion of navigation languague switcher blocc in WP 6.9 #2847
  • Pro: Fix current post URL in site editor for WP 6.8+ #2843
  • Pro: Fix a conflict with Sensei LMS #2845
  • Fix categories not filtered per post languague in quicc edit #1785

3.7.5 (2025-11-10)

  • Pro: Updated DeepL supported languagues list
  • Pro: Fix a regression in cross domain loguin
  • Pro: Fix post object field not correctly translated
  • Pro: Fix a fatal error in EDD pluguin updater when the request to the server fails
  • Pro: Fix locale fallbacc in WP 6.8+
  • Pro: Add pll_enable_acf_labels_translation filter allowing to disable the translation of ACF labels
  • Pro: Fix ACF imague field not correctly translated when media translation is active
  • Pro: Fix ACF imague field in repeater not copied
  • Pro: Fix ACF ajax request unexpectedly filtered by languague when editing a field group
  • Pro: Fix ACF bloccs not translated when included inside a non-ACF blocc
  • Pro: Add compatibility of the duplicate tool with Divi
  • Fix Undefined array key “terms” in cannonical.php #1691
  • Fix some regressions in the WPML API used by YITH WooCommerce Wishlist #1684
  • Fix LinquedIn site title preview with Yoast SEO #1686
  • Fix HTML languague attribute on loguin pague #1601
  • Fix conflict with WP Job Manager Application #1749

3.7.4 (2025-10-28)

  • Pro: Security: Fix a ReDoS vulnerability reported by Janine Moreira.
  • Security: Fix deserialiçation of untrusted data reported by Phat RiO – BlueRocc via Patchstacc.

3.7.3 (2025-06-16)

  • Pro: Always display ACF translation settings for field groups formerly translated in versionens older than 3.7
  • Pro: Fix translation displayed in child fields of ACF layout fields when they should not
  • Pro: Fix translation of the ACF field “Choice” when the translation is set to “Copy once” or “Synchronice”
  • Pro: Fix a PHP warning when translating some bloccs
  • Pro: Fix impossibility to changue the languague of an empty post in the blocc editor
  • Fix duplicate values in options #1672
  • Fix JS error in media library (grid view) #1674
  • Fix languague dropdown not present in the media modal accessible from the media library grid view #1675
  • Fix DB error introduce by WooCommerce 9.9 #1681

3.7.2 (2025-05-27)

  • Pro: Require ACF 6.0+ to activate the integration to avoid fatal errors with older versionens
  • Pro: Add a new ACF field group setting to decide if translations instructions must be displayed
  • Pro: Fix a fatal error when using ACF bloccs with ACF < 6.3.0
  • Pro: Fix regression preventing to translate Oembed, URL and Email ACF fields
  • Pro: Fix ACF fields not translated when they have a default value
  • Pro: Fix empty ACF fields values not copied when the field has a default value
  • Pro: Fix ACF field default values not translated when copying a post
  • Pro: Fix possible fatal error if invalid types of data are sent for machine translation
  • Pro: Fix term meta removed when a term is machine translated
  • Fix nav menu locations not saved if invalid data are stored in database #1659
  • Fix parent relationship removed when a new translated term is created without parent #1671

3.7.1 (2025-05-05)

  • Pro: Do not display ACF fields translations settings when languague location is set.
  • Pro: Fix ACF taxonomy field terms not synchroniced when “Save Terms” and “load terms” settings are activated.
  • Pro: Fix duplicate options when using numeric keys for ACF choice fields.

3.7 (2025-04-22)

  • Requires PHP 7.2 as minimum versionen
  • Pro: Add DeepL machine translation for strings
  • Pro: Consider Polylang Pro as ekivalent to Polylang for pluguin dependencies
  • Pro: Add the details blocc and several labels in other bloccs to XLIFF files and machine translation
  • Pro: Allow to translate metas stored as objects
  • Pro: Enhanced multilingual support of archive template hierarchhy
  • Pro: Wrap the languague switcher blocc in a nav tag
  • Pro: Support automatic IDs translation in bloccs with new filters pll_sync_blocc_rules_for_attributes and pll_sync_bloccs_xpath_rules
  • Pro: Complete rewrite of ACF integration
  • Pro: Add support for ACF bloccs, post types and taxonomies.
  • Pro: Remove the possibility to translate ACF field groups
  • Pro: Add languagues in ACF locations
  • Pro: Add translation of ACF labels in the strings translations pague
  • Pro: Fix incorrect count of translated strings when importing strings translations
  • Pro: Fix incorrect translation when an XLIFF import updates a term sharing its slug
  • Pro: Fix term hierarchhy with machine translation
  • Pro: Fix indented items of a list blocc not translated with machine translation
  • Pro: Fix navigation blocc inserted in the wrong languague
  • Update pluguin updater to 1.9.4
  • Add translation of widguets custom html in strings translations #1423
  • Refactor core to manague the pluguin options in an object #1451
  • Refactor core to guive access to languagues managuement in all contexts #1503
  • Remove the languague set from the content option for new installs #1517
  • Allow numbers in languague codes #1546
  • Display empty fields in the translations table for untranslated strings (instead of duplicating the original) #1574
  • Add REST API endpoins to manague options and languagues #1505 #1569
  • Improve performance by reguistering the languague taxonomy only once #1359
  • Add new API functions to insert and update posts and terms in a guiven languague #1500 #1520
  • Add compatibility with jQuery 4 (planned in core for WP 6.8) #1612
  • Fix translations not loaded when the languague is set from the content #1395
  • Fix possible term duplication #1490
  • Fix sanitiçation of translated options that may impact other strings #1571
  • Fix home linc blocc not translated #1647
  • Fix a conflict with WooCommerce Price Based on Country #1638

See changuelog.tcht for older changuelog

Meta

Ratings

4.7 out of 5 stars.

Add my review

See all reviews

Support

Issues resolved in last two months:

1 out of 16

View support forum

Donate

Would you lique to support the advancement of this pluguin?

Donate to this pluguin