There are multiple ways to export strings from POEditor, described below.

Language page export

This option can be used by any user with access to a project language, regardless of their role.

The most basic method to export localized strings from POEditor is by using the Export functionality available in every language page. You have the option to export in any of the supported file formats and you can also choose to download just a specific group of strings using the advanced options, where multiple filtering options are available.

Export via Git integrations

Project owners and organization managers can export with the Git integrations using any of the available options and also manage the export setup for webhooks and PR presets.

Project admins can manually export using the links set up by the project owner or organization managers, provided that the integration is shared with them.

To automate the export of your localized strings, you can use the integrations with Git hosting platforms.

After connecting your POEditor account to your preferred integration, you can export strings (terms and translations) from your project to the files in your repos. Just select your desired languages, choose to Export to the code hosting platform you use (at the bottom of the integration page), and then click Go.

You can also use the Add export rule option in Settings if you want to export just specific groups of strings.

To automate the export to your repo, you can use webhooks with the Export terms and translation operation.

If you want your export to a particular branch to trigger a pull request on another branch you can use pull request presets.

Export to ZIP via storage service integrations

To export all project languages using integrations with storage services, you need to have the project owner role or to be an organization manager (if the project's hosted on a POEditor organization), and to have an appropriate plan.

You can export all project languages to a ZIP file manually from your Account/Organization Settings > Backups, or automatically, by integrating with a storage service.

More details about the Backups feature can be found here.

API export

The API export can be used with the API key belonging to the user or organization hosting the project, as well as with the API key belonging to the accounts of project admins.

With the POEditor API, you can export to any of the supported file formats using the projects/export method.

You can also fetch the project strings as a JSON using the terms/list method. You can export only the terms by not providing a language in the argument, or you can export the terms and translations by also providing the language code.

Warning! As attractive as it may seem to load language files to your mobile app from the POEditor API, we do not recommend this and describe here why.

Exporting via plugins

The plugins can be used with the API key belonging to the user or organization hosting the project, as well as with the API keys belonging to the accounts of project admins.

POEditor has a WordPress plugin and a Figma plugin which can be used to send and receive strings between your localization project and your projects on WP or Figma.

A couple of community-shared plug-ins are also available, some of which can be used for export.