What is TOML / JSON5 Converter?
TOML and JSON5 Converter supports development settings, examples, and relaxed-syntax compatibility review. TOML tables become JSON5 objects, while comments, quote choices, unquoted keys, hexadecimal numbers, and trailing commas normalize to values during parsing. Null, non-finite numbers, and structures without a safe TOML representation are rejected instead of producing ambiguous configuration. Common workflows include the following. Turn TOML into editable JSON5. Generate TOML from JSON5. Review relaxed syntax differences. 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
- Turn TOML into editable JSON5.
- Generate TOML from JSON5.
- Review relaxed syntax differences.
How to use it
- Identify the source format.
- Check for null and non-finite numbers.
- Convert and read normalization warnings.
- Validate dates and arrays 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"
[release]
tools = 70
ready = trueExample 2
// JSONLane
{ site: 'JSONLane', release: { tools: 70, ready: true }, }Input rules
- TOML requires a root object.
- JSON5 non-finite numbers are rejected.
- Dates require destination review.
- 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.
- TOML cannot represent null.
Output rules
- JSON5 syntax is normalized.
- TOML cannot represent null.
- Comments and layout are not retained.
- Output reflects only the current input, direction, and options; rerun after changing a mode or value instead of treating an earlier result as current.
- JSON5 comments and quote choices are lost.
Limitations and cautions
- TOML cannot represent null.
- JSON5 comments and quote choices are lost.
- Dates and source formatting are normalized.
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.