Java Properties to JSON Converter

No. The conversion runs entirely in your browser with client-side JavaScript, so your keys, secrets and values never leave your device or touch a server.

Both key=value and key:value are parsed, using the first unescaped = or : as the split point. Lines whose first character is # or ! are treated as comments and skipped, and blank lines are ignored.

Yes. A logical line that ends with an odd number of backslashes continues onto the next physical line. The trailing backslash is dropped and the leading whitespace of the continuation is stripped, so app.name=Boneyard \ then Tools becomes Boneyard Tools.

Yes. In values the sequences \n, \r, \t and \f become their control characters, \uXXXX becomes the matching Unicode character, and a backslash before any other character yields that character. Going the other way, those characters are re-escaped.

No. A key like db.host is kept flat and used verbatim as the JSON key. This is the safest round-trippable mapping, since nesting on every dot would break keys that legitimately contain dots.

A line with a key but no = or : separator is kept and given an empty string value. So a bare line like debug becomes "debug": "" in the JSON.

The last occurrence wins. If the same key appears twice, the value from the final line overwrites the earlier one, which matches how java.util.Properties loads a file.

It expects a single flat JSON object. Arrays or non-object values raise an error, and any object or array used as a value is JSON-encoded into the properties value string rather than expanded.

There is no fixed limit. Because everything runs locally, the practical ceiling is your device memory, and even large config files convert almost instantly.