TOML → JSON — Cargo.toml to strict JSON
Paste Cargo.toml, pyproject.toml or other TOML configs and get indented JSON for APIs and CI gates. Single-document only — local processing.
Developer notes
• Single TOML document per paste. • Use compact JSON for logs or indented JSON for reviews. • Round-trip with JSON → TOML to verify shape.
When teams pick this route
• Feed TOML configs into JSON-only validators. • Compare Cargo.toml changes as JSON trees. • Bridge Rust/Python configs into JS tooling.
About these options
CSV exports: choose a delimiter (Auto follows locale — semicolon on /fr), RFC-minimal vs always-quoted fields, line endings, and whether to emit a header row. CSV imports: delimiter + whether row 1 holds column names (Auto delimiter follows locale only for convenience). JSON output (XML, YAML, or CSV sources): indentation (including compact one-line) and optional recursive key sort. JSON → XML: toggle pretty-printing and indent width. YAML output: indent width, readable vs tighter layout, and deterministic string quoting (there is no source YAML file to “preserve”). XML comments are not represented in the intermediate JSON tree.
Worked example
Cargo package
Sample input
Sample output
Dependencies table
Sample input
Sample output
Navigate related tools
Reverse with JSON → TOML, validate JSON via JSON validator, or minify TOML at TOML minifier.
TOML → JSON FAQ
Strict JSON output
Multi-file Cargo workspaces?
Paste one file at a time — workspace merging is out of scope.
Date/time types?
Serialized as JSON strings per TOML parse rules.
Server processing?
Never — parsing is client-side only.
Looking for converters, encoders, formatters, and minifiers in one place? Developer tools hub Open the curated developer tools catalogue.