Step 1 / source
Choose the source
Drop one file here
Choose the flat json properties object you want to turn into java-style properties file.
Checking publication status...LOCAL CONFIG CONVERTER / JSON TO PROPERTIES
Write one flat JSON object as escaped Java-style key-value properties with optional Unicode escape output.
Step 1 / source
Choose the flat json properties object you want to turn into java-style properties file.
Checking publication status...This operation runs with browser APIs. Nirmion receives catalogue requests, not the selected source bytes.
The converter creates a separately named output. It never writes back into the source file.
One UTF-8 .json file up to 2 MB. The root must be a non-empty flat object of scalar values; output is limited to 20 MB.
Plain-language method
Nirmion validates one flat object, converts scalar values to text, escapes separators, comment markers, backslashes, whitespace controls, and significant leading spaces, and optionally converts non-ASCII UTF-16 code units to \uXXXX sequences.
Every value must be a string, number, boolean, or null. Null becomes an empty property value.
UTF-8 is readable in modern workflows. Escaped mode is useful for consumers expecting traditional ASCII-oriented properties.
The result ends in _nirmion_tools.properties. It uses one deterministic key=value assignment per line.
Useful when
Before converting
Know the boundary
Generic properties files do not preserve JSON types, null, nested data, arrays, comments, or duplicate keys. Test the output in the target application.
Quick answers
The conversion contract is deliberately explicit.
No. Explicit rejection avoids dotted-key collisions.
It writes non-ASCII UTF-16 units as \uXXXX sequences.
As an empty value after the equals sign.