Format and validate TOML configuration files with error highlighting and section sorting.
Paste any TOML document and get a normalized, section-sorted copy plus a spec check. The tool parses the text against the TOML grammar, and only a valid document is re-emitted, with canonical spacing and the top-level tables in alphabetical order; a parse failure is reported at the exact line and column where it occurred and highlighted in the source. The usual surprise is how strict TOML is: strings must be quoted, booleans are only true or false, numbers and dates are typed values, and duplicate keys are rejected - so a config file another tool tolerated can fail here.
A concrete input and expected output from the current implementation.
Input
[package] name="demo" version="0.1.0" [build] optimize=true
Expected output
[build] optimize = true [package] name = "demo" version = "0.1.0"
The tables are reordered alphabetically - [build] comes before [package] - and the spacing around the equals signs is normalized to one space. Key order inside each table is unchanged: sorting applies to sections, not keys.
The pasted text is parsed against the TOML grammar before any formatting happens. Keys, strings, numbers, dates, arrays, and tables must all be well-formed; a malformed construct is flagged with its line and column, and the offending span is highlighted in the source. If nothing is wrong, the document is considered valid and moves on to formatting.
On a valid parse, the document is re-emitted in canonical form: one space around each equals sign and one blank line between tables. The top-level tables are then sorted alphabetically, so [build] moves ahead of [package], while keys inside each table keep the order they were written in. The result is a stable layout that diffs cleanly against later edits.
Yes. Processing happens entirely in your browser - the pasted text is parsed locally and never uploaded or stored. Treat the page like any tool handling secrets: paste it, copy the formatted result back, and clear the input when you are finished.
No. It validates against the TOML grammar itself, so it catches syntax errors in either file, but it does not know either tool's schema: a dependency with an invalid version requirement, or a pyproject.toml missing fields PEP 621 requires, will pass. Use this for syntax, then run the consuming tool's own validation.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Format, validate, and beautify JSON with syntax highlighting and error detection.
Encode text or files to Base64 and decode Base64 strings back to their original form.
Format and indent SQL queries for better readability across all major dialects.
Convert HTML markup into clean Markdown syntax with support for tables and lists.
Write Markdown and see the rendered HTML output in real time with live preview.
Visualize unified diffs and patch files with color-coded additions and deletions.