What is JSON / Properties Converter?
JSON and Properties Converter supports Java-style resource and configuration key lists. Nested objects flatten into dotted paths, common backslash and control-character escapes are handled, and import rebuilds object structure while preserving values as strings rather than applying unreliable type inference. Common workflows include the following. Export nested JSON configuration as a property-key list. Turn Java Properties text into searchable JSON. Inspect conflicting paths, duplicates, and special-character escaping. The page also documents input boundaries, output behavior, and practical cautions so you can review the result before putting it into an application, configuration, test, or production workflow.
When to use it
- Export nested JSON configuration as a property-key list.
- Turn Java Properties text into searchable JSON.
- Inspect conflicting paths, duplicates, and special-character escaping.
How to use it
- Paste a JSON object or property text.
- Decide whether dots should represent nested paths.
- Convert and resolve conflicting keys.
- Review array text and string typing before copying.
- Load one of the realistic examples first to verify the selected options and processing direction before replacing it with your own data.
- Review the output, status message, and documented limits; copy, download, or continue only after the result matches your expectation.
Runnable examples
The “Example 1” and “Example 2” buttons load the matching inputs. They cover different structures, directions, or boundaries and can be run directly in the workspace.
Example 1
{"app":{"name":"JSONLane","locale":"en"},"build":{"branch":"develop","tools":40},"ports":[80,443]}Example 2
app.name=JSONLane
app.locale=en
build.branch=develop
build.tools=40
message=Line one\nLine twoInput rules
- The JSON root value must be an object.
- Property entries require an explicit equals or colon separator.
- Conflicting dot paths, duplicates, and dangerous keys are rejected.
- Text input is counted before processing and is limited to 1,000,000 characters on this page; file modes apply the separate file limit shown in the workspace.
- Dots in keys are interpreted as nested paths.
Output rules
- Nested objects flatten into dotted paths.
- Arrays are written as JSON text values.
- Imported values remain strings rather than inferred numbers or booleans.
- Output reflects only the current input, direction, and options; rerun after changing a mode or value instead of treating an earlier result as current.
- Arrays export as JSON text and types are not inferred on import.
Limitations and cautions
- Dots in keys are interpreted as nested paths.
- Arrays export as JSON text and types are not inferred on import.
- Continuation lines and every legacy Java encoding detail are not supported.
How your data is handled
All parsing, conversion, binary encoding, and intermediate data remain in the current browser tab. JSONLane does not upload the input or retain it after refresh or close.