Translating Avada
Last Update: September 30, 2025
Within this section, you’ll find everything you need to localize and internationalize Avada into your language. It is split into several subsections to help you easily find what you need. The Avada Website Builder and the Avada Builder and Avada Core plugins, that are bundled with Avada, are translated separately. Let’s take a look at translating Avada first.
Translatable Avada Features
Avada Translation Basics
This section will explain where you can find the files needed for translation and what these files are for. Avada comes with a steadily growing number of available languages, which can be downloaded from our public GitHub Repo. These are pre-defined translations, powered by our user base. You can see usage details here: Included Language Files
If your language is not already part of our repository, you can easily create your own translation files. Inside the Avada main folder, you will find a folder called languages. If you have downloaded the Installable WordPress Package file, you will find this file in the languages folder:
This file can be used as a starting point to create your own translations, using e.g. a third party tool like POEdit.
In order for WordPress to recognize the resulting language files, you must name them accordingly using the ISO Language Codes. For example, if you wanted to translate Avada to the Deutsch language, the filenames would be Avada-de_DE.po and Avada-de_DE.mo. View screenshot here.
Please see the next sections for detailed instructions on how to do so.
Language Code
Using the correct language code is an important factor to successfully translating Avada. If you are using Avada 3.8 or higher, we have added a System Status tab where you can easily see which language code you’re using. Please continue reading below for more information on how this is done.
How To Identify The Language Code You’re Using
The Translation Process
If your language is not already included, the only thing you have to do is to create a new .po file from the original Avada.pot located in the languages folder, translate all text strings, then save the .po file with your language code and make sure the corresponding .mo is created, which can be read by WordPress. The next subsection will explain this in detail. If you only want to change translated strings in an included .po file, the same steps apply.
Either you are setting up a completely new language file or you just want to edit translated prebuilt language files, the steps to take are easy and more or less the same.
The language files can also be used if you only want to translate a small portion of the theme, or one specific area. You do not have to translate everything, you can choose what you translate inside the Avada.po file. This is the preferred method for translation.
How To Edit The .po file With 3rd Party Software
There are different editors out there for the purpose of editing .po and .pot files, but POEdit is easy to use, it is available for all platforms and it is freeware. To download POEdit, follow this link.