TOML Converter (JSON/YAML)
Convert JSON and YAML mappings to TOML, or TOML to JSON and YAML, with explicit directions and data-loss checks.
About this toml converter (json/yaml)
TOML Converter (JSON/YAML) — browser-based utility.
How this tool works
Converts JSON-compatible mappings between TOML 1.1 and JSON or YAML 1.2 core. Strings, booleans, supported numbers, arrays and nested tables retain their data values. Dotted keys create nested tables; quoted dots remain part of a key. Duplicate definitions and table conflicts are rejected. TOML output uses quoted keys and inline tables.
- Load the sample JSON object with app.name and port.
- Choose JSON → TOML and Run locally.
- Check the nested app value, copy the complete TOML output and convert it back with TOML → JSON.
Worked example
Scenario: Load the sample JSON object with app.name and port.
Sample input:
Processing: Converts JSON-compatible mappings between TOML 1.1 and JSON or YAML 1.2 core. Strings, booleans, supported numbers, arrays and nested tables retain their data values. Dotted keys create nested tables; quoted dots remain part of a key. Duplicate definitions and table conflicts are rejected. TOML output uses quoted keys and inline tables.
Illustrative output:
Limits and verification
The document root must be an object or mapping. Input is limited to 1,000,000 UTF-16 code units, output to 8,388,608 and nesting to 100 collection levels. YAML expansion also uses the YAML converter’s 8,388,608-unit JSON output limit. Empty input, invalid Unicode, null values and typed TOML dates or times are rejected. Numbers must be finite, without decimal precision loss or underflow; integers must stay within ±9,007,199,254,740,991. Comments, layout and key order are not preserved.
Examples demonstrate an expected workflow; they do not prove every input or every branch of an external specification. Check important results with an independent source before using them for money, security, compliance, safety, or irreversible file changes.
Browser processing boundary
Tool input is processed by code running in the browser and is not intentionally sent to a CZOA processing API. The page can still request ordinary site assets, analytics, or advertising when those services are enabled. Browser extensions and managed-device software remain outside this tool's control.
Relevant references
These references govern or help explain the format, protocol, or calculation used here. Listing a reference does not claim certification or complete implementation of every optional feature.
Content owner: CZOA Tools · Last reviewed: 2026-09-15 · Review methodology
How to use it
- Load the sample JSON object with app.name and port.
- Choose JSON → TOML and Run locally.
- Check the nested app value, copy the complete TOML output and convert it back with TOML → JSON.
Frequently asked questions
How do I explicitly convert JSON to TOML?+
Select JSON to TOML, paste JSON, and run locally. `{ "app":{"name":"CZOA"}, "port":8787 }` produces quoted `app` and `port` keys with an inline table and numeric port.
Why are TOML keys quoted in the generated output?+
The encoder quotes keys in this conversion path, including simple keys. Quoting is output syntax here and does not change the JSON property name or integer value.
Can TOML conversion preserve every YAML or JSON representation detail?+
No. It converts supported data structures, not comments or each lexical spelling. Use an explicit direction and independently check types such as dates, arrays, and nested tables.
What text boundary applies to TOML conversion?+
Input must be valid Unicode and within the converter limit. The page transforms text in the browser; ordinary site resources are separate, and no file upload is offered.