Step 1 / source
Choose the source
Drop one file here
Choose the java-style properties file you want to turn into flat json object.
Checking publication status...LOCAL CONFIG CONVERTER / PROPERTIES TO JSON
Properties to JSON
Convert Java-style .properties assignments into a flat JSON object with continuations and standard escape decoding.
Processed in this browserOne UTF-8 .properties file up to 2 MB and 100,000 physical lines. Keys must be unique; output is limited to 20 MB.
PROPERTIES - 2 MB
No file upload
This operation runs with browser APIs. Nirmion receives catalogue requests, not the selected source bytes.
Original stays unchanged
The converter creates a separately named output. It never writes back into the source file.
Bounded work
One UTF-8 .properties file up to 2 MB and 100,000 physical lines. Keys must be unique; output is limited to 20 MB.
Plain-language method
How Properties to JSON works
The parser joins backslash continuations, ignores full-line # and ! comments, recognizes unescaped equals, colon, or whitespace separators, decodes standard tab, newline, return, form-feed, backslash, and Unicode escapes, and rejects duplicate keys.
- 01Choose a valid source
Use one logical assignment per entry. A trailing odd backslash continues onto the next physical line.
- 02Review the conversion choices
Indentation affects JSON whitespace only. Values remain strings because properties files do not carry JSON types.
- 03Inspect the separate result
The result ends in _nirmion_tools.json. Comments, separators, continuations, and original escape style are not preserved.
Useful when
Practical jobs this tool handles
- Inspect application resource settings as JSON.
- Prepare a controlled configuration migration.
- Create test fixtures from properties files.
Before converting
Check the source and destination rules
- Check continuation lines.
- Review Unicode escapes and significant spaces.
- Keep the source for comments and formatting.
Know the boundary
Know what the destination format cannot keep
The conversion preserves decoded key-value meaning, not comments, line order syntax, encoding assumptions, duplicate-key behavior, or application-specific interpolation.
Quick answers
Questions before you convert
The conversion contract is deliberately explicit.
Are Unicode escapes decoded?
Yes. Valid \uXXXX sequences become characters.
Are duplicate keys allowed?
No. Rejection prevents silent last-value-wins data loss.
Do values become numbers?
No. Every property value remains a JSON string.