JSON ↔ Properties
ClientTurn JSON into key=value lines with dotted paths, or rebuild nested JSON from flat properties text.
Learn more: .properties files
Convert between nested JSON and `key=value` lines with dot-separated paths—similar to Java resource bundles and many flat config formats.
Limitations
This is a pragmatic converter, not a full Java Properties parser: comments and line continuations follow simple rules; binary or non-UTF-8 values are out of scope.
JSON ↔ Properties
?
Flat key=value lines map to nested JSON using dot segments. Lines starting with # are comments.
Common use cases
- Convert Spring- or Java-style .properties bundles into nested JSON for modern config or tests.
- Flatten JSON back to key=value lines when integrating with libraries that still read properties files.
- Compare two representations when migrating services off flat property files.
Common mistakes to avoid
Assuming comments and ordering round-trip through JSON
JSON objects do not preserve comments or key order semantics from the original file—treat output as data, not a byte-for-byte rewrite.
Mixing Unicode escapes with raw UTF-8 expectations
Properties files often use \u escapes. Confirm how your runtime decodes them versus JSON string rules.
FAQ
Is conversion performed locally?
Yes. Parsing and emission happen in your browser tab.
Should I use this or JSON ↔ .env?
Use Properties for Java ecosystem flat files. Use env tools when targeting shell-style KEY=value exports.
More tools
Related utilities you can open in another tab—mostly client-side.
JSON flatten / unflatten
ClientNested JSON ↔ dot paths for configs and i18n—round-trip in the browser.
CSV ↔ JSON
ClientPaste a table or JSON array of objects—convert both ways, choose delimiter, client-side.
TOML ↔ JSON
ClientTOML to JSON and JSON to TOML online—format, validate, convert locally.
Encoding tools
ClientBase64 and URL on this page; hub lists hex, HTML entities, JWT, JSON helpers, crypto, and tokens.