Skip to content
TextArray1.41.0
100% local

Properties to JSON converter

Convert Java .properties files to JSON and back, right in your browser.

Input
Output
Related tools
JSON to .env converterDeveloper tools
Env to JSONDeveloper tools
JSON formatter & validatorText formatting
INI ⇄ JSON converterDeveloper tools
i18n key diffDeveloper tools
TOML to JSON converterDeveloper tools
Properties to JSON converter
Paste a Java .properties file and get clean JSON back, or paste JSON and get a .properties file. It is the quick way to move a Spring Boot application.properties, a Log4j config or an i18n message bundle into a format your JavaScript, tests or documentation can read — and to generate one from an object you already have.
The parser follows the real .properties rules rather than a naive split on the equals sign. Both key=value and key:value pairs are read, whitespace can also separate a key from its value, and leading spaces are trimmed. Lines beginning with # or ! are treated as comments and skipped. A line ending in a backslash continues onto the next one, so a long value wrapped across several lines is joined back into a single string. Escape sequences like \n, \t, \\ and \: are unescaped, and \uXXXX becomes the character it names. Every value stays a string, so a version like 007 or a port kept as text is never silently turned into a number.
Turn on "Nest dotted keys" and a key such as db.host becomes { "db": { "host": … } }, which is what most config loaders expect; leave it off to keep the flat dotted keys verbatim. "Prettify JSON" indents the output for reading, or you can minify it. Going the other way, nested objects are flattened back into dotted keys and characters that are special in a .properties file are escaped for you. Invalid JSON is reported calmly, pointing at the bracket or comma to check, instead of failing silently.
Everything runs locally in your browser. Your configuration — database URLs, API hosts, credentials sitting in a properties file — is never uploaded, logged or sent to a server. Copy the result, download it as a file, or hand it to another TextArray tool.
FAQ
Which .properties syntax does it understand?
The standard Java format: key=value and key:value pairs, whitespace separators, # and ! comment lines, backslash line continuations, and escapes such as \n, \t, \\, \: and \uXXXX. Leading whitespace on a line is ignored.
Why are all my values strings in the JSON?
A .properties file has no types — everything is text. Guessing would corrupt data, turning a code like 007 into 7 or a version 1.0 into a number. Values are kept as strings; cast the ones you know are numeric in your own code.
What does 'Nest dotted keys' do?
It splits keys on the dot, so db.host and db.port become a nested { "db": { "host": …, "port": … } } object. Turned off, the keys stay flat exactly as written. The reverse direction always flattens nested objects back into dotted keys.
Can it convert JSON back into a .properties file?
Yes. Choose JSON → Properties. Nested objects are flattened into dotted keys and special characters are escaped, producing a file you can drop straight back into a Java or Spring project.
Is my configuration uploaded anywhere?
No. The conversion runs entirely in your browser. Nothing in your properties or JSON — hosts, keys, credentials — ever leaves your device.