ConversionNested objects flatten into dotted keys (server.port). Spaces, equals signs and colons in keys are escaped per the Java spec; non-ASCII characters can be written as backslash-u escapes.

JSON sourceJSON

Load some data

.properties text.properties

Load data and the result will appear here

JSON → Java config

JSON to Properties

Nested object → key=value · Java-spec escaping · optional unicode escapes · runs locally

🔒Processed locally in your browser — never uploaded or stored

No upload, no storage

JSON is processed in memory and never sent to a server.

Share via URL fragment

Share links encode data in the # anchor — never sent to a server.

Remember last edit

Optionally keep your last input locally; clear it with one click.

Why use JSON to Properties

Spring-friendly keys

Nesting flattens into dotted keys like server.port — exactly how Spring Boot properties are written.

Escaped per the Java spec

Spaces, equals and colons in keys, newlines and leading spaces in values — all escaped the way java.util.Properties expects.

Unicode escapes on demand

Write non-ASCII as backslash-u escapes for legacy encodings, or keep the original text for modern UTF-8 setups.

Round-trips exactly

What Java reads back matches your original JSON character for character — special characters included.

Local · no upload

Config files are processed entirely in your browser; nothing is uploaded or stored.