Skip Navigation

We just released WPML 4.2.5. This is a usability update, which makes it a lot easier to use our new translation editor.

For the last few months, WPML offers two translation editors.

Classic Translation Editor Advanced Translation Editor
Side-by-side translation editing Side-by-side translation editing

Spell checking

Translation memory

HTML-less editing


Machine translation (2000 words free)

The new (advanced) translation editor offers easy translation, with the features that you’d normally find only in expensive professional translation tools. This allows site owners and their translators to produce much more accurate and faster translations.

In this release of WPML, we’ve ironed out many of the usability issues that appeared in this new tool. Now, WPML’s Advanced Translation Editor is our recommended method for translating sites of any size.

How WPML’s Advanced Translation Editor Works

WPML’s translation editor separates between design and translation. When you send content for translation, you only need to translate texts and not recreate the entire design. This allows you to translate quickly. Translators only need to edit texts and never have to spend time with page builders.

Here is a quick example for content that we’ve created with the Block Editor and how we translate it with WPML:

When we create the page, we spend time not only writing the content but also styling it. There’s no need to spend this time on every translation. All you need is to translate the texts. WPML takes care of building the translated pages with the exact design and new texts.

Easy for Newbies, Powerful for Experienced Translators

WPML’s Advanced Translation Editor requires no training or experience. Open any translation job and translate.

Experienced translators, who need to translate a lot of texts will enjoy the advanced features which run silently.


When you’re translating a large website, you need to make sure that you’re translating the same term consistently in different pages. This is where a glossary comes in handy. Any time you run into an “interesting” word, which you want to remember, add it to the glossary. The editor will look out for this word, highlight it for you and show you how you’ve translated it before.

Add to glossary The same word appears on another page The glossary shows the correct translation

Translation Memory

The same text can appear several times on the same page or on other pages. There’s no need for you to translate it again and again. The translation editor will automatically find recurring texts and apply the same translation.

HTML-Less Editing

WordPress allows you to style texts. Some of the texts that translators will get include styles, links, and other HTML tags and shortcodes. If you allow translators to edit these tags, there’s a very good chance that translators will break the page.

Correct HTML Broken translated HTML
This is <strong>bold text</strong>. Esto es <fuerte>texto en negrita</fuerte>.

You don’t need to read Spanish to realize that this translation is not going to work.

WPML’s Advanced Translation Editor prevents these problems from ever happening. The translator will not need to deal with HTML tags. Instead, for every HTML tag in the text, the translator will see a marker.

Text with markers Translation with markers

Automatic Translation

Automatic (machine) translation has come a long way in the last few years. Now, it’s a good option for the first draft of most translations. WPML’s Advanced Translation Editor allows you to automatically translate individual sentences or the entire page.

Automatic translation for a sentence Automatic translation for the entire page

WPML relies on 3rd party engines for this great automatic translation. This service isn’t free, so we cannot offer it completely for free. Every new site that uses the Advanced Translation Editor receives a quota of 2000 free words to translate automatically. When you need more, we offer flexible payment plans. Your payment for the automatic translation covers more than the direct costs. It also covers the cost of developing and supporting the Advanced Translation Editor.

Try It and Leave Your Feedback

The Advanced Translation Editor is part of WPML’s Translation Management module.

When you’re building new sites with WPML, Translation Management will ask you which editor to use during the setup.

Selecting the translation editor for new sites in the Translation Management wizard

You can switch existing sites to the Advanced Translation Editor. To do this, go to the WPML -> Settings page and scroll to the How to translate posts and pages section. There, you can select the editor for new content as well as the one already translated using the Classic Translation Editor.

Selecting the translation editor for existing sites
Selecting the translation editor for existing sites

Give it a try, see how you like it, think about what you’re missing and leave your feedback. We’re all eager to get your feedback and improve our translation tool.

How can we make WPML better for you?

Share your thoughts and comments about our plugin, documentation, or videos by booking a Zoom call with Agnes, our Client Advocate. Your feedback matters and helps us improve.

Book a call with Agnes

13 Responses to “WPML 4.2.5 Greatly Improves the Advanced Translation Editor”

  1. Hello,

    nice update! Are there any risks or precautions (other than doing a backup) if we switch a website translation method from classic to advanced? (We are using Divi as theme)

    • Doing a DB backup before updates is always a good idea.

      The only big potential issue is that you can only edit existing translations with the editor that you created them. For this reason, when you switch to the new translation editor, it will only apply to new translations. When you edit existing translations, you will still get the old editor. The reason for this is that each editor does the text segmentation differently (the new editor has significant improvements in segmentation). Therefor, we cannot use the translation history from the old editor.

      When you switch to the new editor, you will not lose any translations. You will just not get the new editor for old translations.

      Does this make sense?

      • Hi Amir, is the new segmentation from the advanced translation editor also used by translation services? So, if I enable the advanced translation editor and then send the text to a translation service, do I get the translations back in the advanced editor’s format?
        (opposed to using the classic editor where you get the translations back in the classic format).


        • Yes. We’re using the same segmentation engine now for professional translation services and WPML’s Advanced Translation Editor.

  2. Hi Amir,

    thank you for the explanation, it make sense.

    Is it possible, in some way, to reset the translation status of a single page translated using the classic editor and perform again that translation starting from zero and using the new advanced editor?

    • I don’t think that we took this into account and created a way to reset the translation history. Can you create even a test page to see how the new translation editor works?

  3. Hi Amir,

    Should people be worried that the manual editor is eventually going to be phased out?

    To clarify, with manual editor I do not mean the Classic Translation Editor which offers side-by-side translations, but instead the good ol’ classic editor screen from pre-WP 5.0.


    • These editors are not going away and keep getting updates and improvements. We created the new Advanced Translation Editor as a hosted service, which allows us to implement features that we cannot build in PHP on the self-hosted WPML files.

  4. Do you have plans for PayPal support for Machine translation? The last time you had only creditcard support. In europe we dont use credit card much

    • Sorry, but we don’t have plans for PayPal integration in the immediate future. Stripe gives pretty good coverage for countries all over the world, so we’re working on other features right now.

  5. It is possible to export the TM into a local TM to use it for other documentation resp. to import a already existing TM?