Skip Navigation
Home » WPML Blog – News and Updates for the WordPress Multilingual Plugin » Announcements » Translate your site with DeepL for fewer credits

Translate your site with DeepL for fewer credits

Announcements
15

About a month ago, we changed our automatic translation pricing for sites that use DeepL and Google Translate as their translation engines. After receiving your feedback, we are now lowering the number of credits required to use DeepL to translate your site

As of June 27, 2022, DeepL is 2 credits per word. Read more about the latest updates with WPML and DeepL.

Automatic translation is charged based on the number of credits you use each month. You can choose from 3 automatic translation engines: Microsoft, Google, or DeepL. These translation engines each require a different number of credits per word due to the quality of their translations and the complexity and cost of their integration with WPML.

The credit value of Microsoft Azure and Google Translate remain the same, however DeepL’s cost has been reduced. The new breakdown is as follows:

  • Microsoft Azure = 1 credit/word
  • Google Translate = 2 credits/word
  • DeepL = 3 credits/word

Read more about pricing for automatic translation.

Please note: If you already have a DeepL account, it’s not possible to use your existing account through WPML. WPML’s automatic translation feature includes the convenience of translating your site instantly within your site’s admin, plus integration with additional features such as translation memory, a customizable glossary, spellchecker, and more. If you prefer to continue using your personal DeepL account over the integration with WPML, you can use our XLIFF export feature to manage your translation jobs.

Questions?

Let us know your questions and comments below!

15 Responses to “Translate your site with DeepL for fewer credits”

  1. Thank you, but it seems like it does not work with portuguese and arabic.
    If I am wrong can you help me to setup translation portuguese , and arabic using deepl
    Regards

  2. Instead of using credits and DeepL, why not hire an actual human translator and have your website content localised the proper way? Yes, it’ll cost you some, but in return, you get the invaluable expertise of an expert who knows the language and culture of your target audience.

    • Hi Bart – Thanks for your comment. Different clients have different needs when it comes to translation quality, budgets, and timelines. That’s why we offer multiple options for translating a site, including translating it yourself, using automatic translation, and partnering with dozens of professional translation services.

  3. Thank you for introducing this. We are a small NGO that cannot afford to pay for good hired translators (who are worth the money! ). So we translate ourselves. We use Arabic, German and English. Do you have a tutorial or guide explaining how I can setup google translate and deepl for my website ? Deepl is by far the best , but for Arabic I need an alternative. Thanks for your great work and very good plugin

  4. Thank you for introducing this. We are a small NGO that cannot afford to pay for good hired translators (who are worth the money! ). So we translate ourselves. We use Arabic, German and English. Do you havens instruction how to implement ?

  5. Hi. Can I use the automatic translation to translate product categories? If so can you explain how to do this please. I use the classic editor. I have already manually translated about half of my website and I do not want to loose this work.

    Thanks

    • Hi Anthony – Thanks for your comment. Automatic translation is a feature of the Advanced Translation Editor. When using the Advanced Translation Editor, you can automatically translate all taxonomy by creating a post and assigning all taxonomy terms to it. When you translate the post, the assigned taxonomy appears in the Advanced Translation Editor, and you can translate them automatically.

      Since you’ve been using the Classic Translation Editor, these translations are not saved in the Advanced Translation Editor translation memory. You may still be able to access the translations thanks to a new feature that saves translations from other sources.

      Hope that helps!

  6. That helps a lot. Thank you.

    I have found that some of the formatting is lost in the translation of categories. For example, I use a different colour for H2 and H3 headings.

    It would also be great if the English links were converted to the appropriate French links. Is this possible?

    • Hi, Anthony!

      Glad to hear it helped. 🙂 I’m not sure what you mean about lost formatting in the translation of categories. When you translate categories, WPML translates only their value in the database and it has nothing to do with their display on the front-end.

      For converting links, please go to the WPML → Settings page and scroll to the section called Translate Link Targets. There, click the Scan now and adjust links button. After it finishes, all links should be updated to point to the correct language.

      If you need further help with any of these things, please create a ticket in our Support Forum.

  7. Can be much better if we can add our own DeepL API credential, to then use our own credits directly from DeepL. Also, other users request the same feature in another post related to DeepL. Any plans to offer this feature? Thank you in advance.-

    • Hi Santiago – Thanks for your comment. As stated in the replies to those comments, we do not have plans to allow the use of DeepL API credentials at this time.