What is TOML / Properties Converter?
TOML and Properties Converter connects project configuration with Java resource keys and dotted-path files. Nested values flatten to stable paths, arrays use JSON text, and reverse conversion rejects duplicate, conflicting, and dangerous names. Because Properties has no reliable type system, imported values remain strings and literal dots, dates, and arrays need review against the destination framework. Common workflows include the following. Generate Java Properties. Restore dotted paths as TOML. Review arrays and path conflicts. 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
- Generate Java Properties.
- Restore dotted paths as TOML.
- Review arrays and path conflicts.
How to use it
- Paste a TOML object or Properties text.
- Review dotted paths and arrays.
- Convert and resolve conflicts.
- Validate string types in the destination.
- 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
site = "JSONLane"
locales = ["zh-cn", "en"]
[release]
tools = 70Example 2
site=JSONLane
locales=[zh-cn, en]
release.tools=70Input rules
- The root must flatten into object paths.
- Properties paths cannot conflict.
- Dangerous and duplicate 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 represent nested paths.
Output rules
- Objects use dotted paths.
- Arrays use JSON text.
- Imported values do not infer types.
- 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 are stored as JSON text.
Limitations and cautions
- Dots represent nested paths.
- Arrays are stored as JSON text.
- Imported values remain strings.
How your data is handled
All parsing, conversion, Base64 work, and intermediate data remain in the current browser tab. JSONLane does not upload the input or retain it after refresh or close.