Java Properties Editor
Edit Java .properties files with \\uXXXX decoding, comment rows and JSON interop.
No rows yet — paste .properties content above and press Parse.
Values are read as ISO-8859-1 style escapes: \uXXXX is decoded on parse and re-encoded on export. Line continuations with a trailing backslash are joined.
How to use it
- Paste your .properties content into the text panel and press Parse.
- Each setting becomes an editable row. Continuation lines and escaped characters are already resolved, so you see the real value.
- Edit keys and values in place; add rows with Add key and Add comment.
- Keep Escape non-ASCII as \uXXXX on if the file is read as ISO-8859-1 by your build, which is the classic Java behavior.
- Choose the mode to export .properties, export JSON, or build a properties file from a JSON object, then Copy or Download.
Common use cases
- Editing localization bundles - messages with accents or CJK text become readable here instead of a wall of escapes.
- Fixing a broken escape - a stray backslash shows up as an odd value in the table, where it is easy to correct.
- Moving keys between files - convert to JSON, compare or merge in your own tooling, then convert back.
- Round-tripping without losing comments - header comments and blank lines are kept in the order they appeared.
- Checking what a bundle resolves to - the decoded view answers questions about real values before you run the app.
Why it stays private
Resource bundles and property files often carry internal host names, credentials and unreleased feature names. Parsing and export are pure string work in the page, so the file is never transmitted.
FAQ
Q: Why is non-ASCII escaped by default? A: Java reads .properties as ISO-8859-1 unless the build is configured otherwise, so a literal non-ASCII byte would be misread. Turning the option off writes the characters directly, which suits builds configured for UTF-8.
Q: How are continuation lines handled? A: A line ending with an odd number of backslashes continues on the next line. The backslash is removed and the next line is appended after its leading whitespace is trimmed, matching the Java specification.
Q: Which characters are escaped in keys? A: Backslash, equals, colon, space, hash and exclamation mark, because all of them have structural meaning in a properties line. Non-ASCII characters follow the same option as values.
Q: What happens to a line that cannot be parsed? A: It is kept as a comment row instead of being dropped, so nothing disappears from your file when you round-trip it.
Your data stays on this device
Java Properties Editor runs 100% locally. Everything you paste or drop is processed by your own browser and never transmitted. Nothing is stored on our servers — close the tab and it is gone.
Nothing you type is sent to a server, logged, or used for analytics. The page works even with your network disconnected after first load.