What is YAML / TOML Converter?
YAML and TOML Converter moves data between team-oriented configuration and project tooling. Restricted YAML handling and a mature TOML parser process objects, arrays, strings, numbers, booleans, and dates while explicitly rejecting null, unsafe tags, and imprecise integers instead of producing configuration that only looks valid. Common workflows include the following. Migrate team YAML configuration to project TOML. Inspect arrays, nested tables, and dates. Turn TOML into editable YAML. 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
- Migrate team YAML configuration to project TOML.
- Inspect arrays, nested tables, and dates.
- Turn TOML into editable YAML.
How to use it
- Choose a direction and paste a complete configuration.
- Confirm that YAML uses a root object.
- Load an example to inspect nested tables and arrays.
- Convert and read the type warnings.
- Validate dates and special scalars in the destination application.
- Load one of the realistic examples first to verify the selected options and processing direction before replacing it with your own data.
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
project: JSONLane
release:
tools: 50
ready: true
channels: [develop, main]Example 2
project = "JSONLane"
[release]
tools = 50
ready = true
channels = ["develop", "main"]Input rules
- YAML to TOML requires a root object.
- Unsafe YAML features and integers are rejected.
- TOML must follow supported standard syntax.
- 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.
- YAML to TOML requires a root object and cannot represent null.
Output rules
- Nested objects become TOML tables.
- TOML dates become strings in YAML.
- Comments and source 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.
- Comments, anchors, aliases, and original layout are not retained.
Limitations and cautions
- YAML to TOML requires a root object and cannot represent null.
- Comments, anchors, aliases, and original layout are not retained.
- Dates and special scalars require destination-specific review.
How your data is handled
All parsing, format 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.