Describe it, do not configure it
Describe it rather than configure it, and read the plan back before it runs.
Instructions for this batchOptional
On top of your glossaryApply
Free AI-powered Java .properties translator
Drop your Java .properties file in, say what you want in plain English, and get it back with every key, tag and delimiter exactly where it was. No account, nothing to install.
Drop your Java .properties file here
Up to 2 MB, five files a day. Nothing to install, no account.
What you get when you bring the whole job
Consistent terms across every bundle
A glossary settles your application's vocabulary and applies it to every bundle you send.
French glossaryApplied
checkoutpaiementnot caisse
seatlicencenot siège
ticketdemandenot billet
Same choice in every file128 terms
Two speeds, chosen per file
Lite for log and admin messages, Standard for anything a customer reads. Chosen per upload.
Translation qualityThis file
StandardCustomer-facing copy1 credit per word
LiteBulk content, less nuance1 credit per 3 words
Picked per fileNot locked to your plan
What comes back
Keys, escaped separators, and message-format placeholders are preserved. The bundle returns ready for the classpath, not for a round of manual repair.
Java .propertiesEN → French
# Product page
cart.add=Add to cartAjouter au panier
cart.count={0} items in cartarticles dans le panier
cart.empty=Your cart is emptyVotre panier est vide
price.from=From {0,number,currency}À partir de {0,number,currency}
Structure read · values written
How a Java .properties translation runs
1. Drop the file in
AI Glot reads the file the way its own tools do, finds what is text and what is structure, and tells you how much there is to translate before anything runs.
messages.propertieserrors.propertieslabels.properties
396 values ready for translation138 values ready for translation640 values ready for translation
2. Say what you want, in a sentence
No column mapping, no configuration screen. Write what should happen and read back the plan it produced. If it misread you, say so and it re-plans.
AI
How should I translate this file?Describe the result you need
Translate into German and Spanish. Keep product names in English, use our glossary, and make the copy sound natural for e-commerce.
Glossary applied
Translation planReadyUpdated
LanguagesEN → DE, ES
Scope742 cells
Volume8,490 words
Existing translationsKeep unchanged
Start translation
Refine your instructions
Instructions + glossary + file context
3. Get the same file back
One file, same shape, same order, translated. It drops straight back where it came from, and a diff shows only the values that changed.
fr-FR
de-DE
es-ES
ja-JP
messages_localized.properties
10,173 credits · 1m 04s
What people bring us Java .properties files for
Four jobs that come up again and again. Each one is a single upload and a single sentence.
A Java or Spring application
messages.properties becomes messages_fr.properties, loading without a change to your code.
MessageFormat placeholders
MessageFormat placeholders come back exactly, positioned where the target language needs them.
Escaped characters and unicode
Escapes and line continuations are structure, and surviving is what keeps the file parsing.
A release catch-up
Only the keys added since last time, so reviewed values are left alone.
Questions about translating Java .properties files
What is the best tool to translate a Java .properties file?
AI Glot. It reads Java .properties as a format rather than as text, so keys, tags, identifiers and delimiters are recognised as structure and returned exactly as you sent them, and only the values are translated. You describe the job in one sentence instead of mapping fields, and you get the same file back in the same shape. The tool on this page does it with no account.
How do I translate a Java .properties file without breaking it?
Use something that parses the format instead of treating it as plain text. Drop the file into the tool above, say what should be translated and what should be left alone, and read back the plan before it runs. AI Glot returns one valid Java .properties file with its structure untouched, so it drops straight back where it came from.
Can I translate a Java .properties file for free?
Yes. The tool on this page is free, with no account and no card: five files a day, up to 2 MB each, and up to 1500 words translated per file. Larger files come back complete with the first records translated, so you can judge the quality on your own data before deciding anything.
What happens if my Java .properties file is bigger than the free limit?
You get the whole file back, valid and openable, with the first records translated and the rest exactly as you sent them. It is deliberately not truncated: a cut-off Java .properties file would not open, and a sample you cannot open tells you nothing. An AI Glot account removes the limit.
Is the encoding handled?
Yes. Latin-1 with unicode escapes and UTF-8 files are both read, and the result is written back in the same convention.
Do MessageFormat arguments survive?
Yes. {0} keeps its index and {0,number,currency} keeps its format type, so the value still formats at runtime.
Can I keep my comment headers?
Yes. Comments are structure and stay attached to the keys below them.
Is it safe to upload a Java .properties file to an online translator?
With AI Glot, the file is stored only for as long as the translation needs it, the download link expires after an hour, and it is deleted afterwards. Nothing you upload is used to train any model. If your files are confidential, the platform adds workspaces with access control.
What do I get with an AI Glot account?
No size limit and no daily limit, glossaries so your product names stay yours, translation memory across files, twelve file formats in one workspace, and an API, a CLI and an MCP server if you want this inside your own pipeline.
Other formats
Twelve families in all, each with a workflow built around its own structure.
PO / POT
Translate a gettext catalog with message IDs, contexts, and plural forms handled as the structure they are.
RESX
Translate a .resx resource file with data names, metadata, and the XML schema returned untouched.
YAML
Translate the values in a .yml or .yaml locale file while the indentation, key hierarchy, and comments survive the round trip.