Properties to JSON Converter: Java Config Both Directions

Real-world use cases

• Migrate a Spring Boot app from .properties to JSON config

  Your service still reads application.properties, but the new deployment pipeline injects config as a JSON blob. Paste the whole properties file, keep dotted-key expansion on, and you get the nested JSON tree that maps onto the same @ConfigurationProperties beans, server.port and spring.datasource.url landing in the right place. Copy it straight into the values file and skip the hand-translation that quietly loses a key.

• Inspect a dense legacy properties file as readable JSON

  A 200-line log4j or Hibernate .properties is hard to scan when related keys are alphabetised rather than grouped. Convert it with nesting on and the dotted keys collapse into a tree, so every logging.level.* or hibernate.* setting sits under one parent. You read the structure at a glance instead of grepping for prefixes.

• Generate a .properties file from JSON for a Java service

  You designed the config as JSON in a doc or an API response, but the target app only loads java.util.Properties. Paste the JSON, switch direction, and nested objects flatten to dotted keys with the right escaping on equals signs and unicode, giving you a file the Java reader accepts without edits.

• Diff two environment configs after converting both to JSON

  Comparing prod.properties and staging.properties line by line is noisy because key order differs. Convert each to JSON, paste them into a JSON formatter or diff tool, and the structural comparison shows exactly which database URL or feature flag changed, free of ordering noise.

Common pitfalls

• Expecting numbers and booleans to come back typed. .properties stores everything as text, so port=8080 converts to the string "8080", not the number 8080. The tool keeps it faithful on purpose; cast in your code where you know the type.

• Forgetting that a colon also separates keys. timeout:30 is a valid assignment with key timeout and value 30, not a key named "timeout:30". If you meant a literal colon inside the key, escape it as backslash-colon so the parser does not treat it as the separator.

• Leaving a stray trailing backslash. A line ending in \ continues onto the next line, so an accidental backslash at the end of a value silently swallows the following line into that value. If you want a literal backslash at the end, write it as \\.

Privacy