To localize Angular .xlf files with the localization management platform POEditor, you can follow the steps described in this article.
1. Set up Angular localization project
Log in to your POEditor account, create a new Angular localization project and your software's default language.
If you don't have an account, you can create one here.
2. Import strings from Angular XLIFF file
In the Angular localization project page, use the Import functionality to upload the strings from your Angular XLIFF file, also adding translations in the source language. For this, you need to check the option Get translations from <source> instead of <target> tag.
After you import the source language, we strongly recommend you set it as your project's Default Reference Language.
If you have translations in the <target> tag also and want to add them to the project, create a new language and import them there.
3. Translate Angular strings
Add the languages you want, then choose how to translate them:
- AI translation with your own OpenAI, Claude, Gemini, Azure AI or Amazon Bedrock account. You can customize the prompt to match your tone.
- Machine translation with Google Translate, DeepL or Azure AI Translator.
- Your own translators, invited as contributors to specific languages.
- Human translations, ordered from the available LSPs.
Translation memory (available from the Start plan) suggests earlier translations of identical strings, and QA checks and QE feature catch issues before export.
4. Export translations for your localized Angular app
When you want to download your target languages in the Angular XLIFF file format, you can use the Export functionality in each language page to export the localized Angular strings.
Keep in mind that to export in the Angular .xlf format it is required to have a Default Reference Language set.
If you want to automate the import/export, use the POEditor API, one of the integrations with code hosting platforms or Workflows.
Only need to edit an .xlf file, not translate it? Use the Angular XLIFF Editor.
Using .xmb and .xtb files instead? See How to translate .xmb and .xtb files.


