To translate Java .properties files, import your source-language .properties file into a POEditor project, translate the strings with the available translation options, then export each language as a localized .properties file.
1. Create a translation project
Log in to your account (if you don't have one, you can create one for free here), add a new translation project in your Dashboard and add your software's source language to it.
2. Import the strings from your .properties files
In the project page, use Import to add the strings from your properties file to your localization project. Choose Also import translations to a language and select your software's source language.
This language will automatically be suggested as your project's Default Reference Language after you import the translations. You can change the DRL in project's Settings.
3. Translate your Java 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 similar strings, and QA checks and QE feature catch issues before export.
4. Export localized .properties files
At any point during localization, click Export in a language page to download that language as a .properties file, or use one of the other export options.
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 a .properties file, not translate it? See the Properties Editor.