JSON ↔ Properties

Client

Turn 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.

Nearby workflows on Toolcore

  • JSON formatter — when the document must parse before any transform or export.
  • Flatten JSON — for dot-path objects from nested trees.

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.
  • Inspect i18n or message bundles as nested JSON before handing them to tooling that only accepts properties syntax.

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.

  • Duplicate keys in the source file

    Many loaders treat the last duplicate key as winning; others error. After conversion, verify which value your deployment actually reads.

FAQ

Is conversion performed locally?

Yes. Parsing and emission happen in your browser tab.

Should I use this or JSON → env / env → JSON?

Use Properties for Java-style flat bundles. Use the env tools when targeting shell exports and their escaping rules.

How does this differ from INI ↔ JSON?

INI often models sections with `[headers]` and looser typing. Properties is usually flat `key=value` with dot paths; pick the tool that matches your source file format.

More tools

Related utilities you can open in another tab—mostly client-side.