Base32 Encoder & Decoder
Encode and decode Base32, including the Crockford and hex variants.
Tidy a TOML file: consistent quoting, ordered tables, keys before headers.
Plain keys are always written above the first table header, because TOML would otherwise read them as part of that table. Comments are not preserved.
The TOML Formatter re-emits a file from its parsed form: plain keys written above the first table header where TOML requires them, tables as [a.b], arrays of tables as [[a]], and quoting made consistent.
TOML has one rule that catches everyone: every plain key must be written before the first table header, or it silently belongs to that table instead of the document. The formatter re-emits the file in the correct order, so that bug cannot survive a pass through it.
Beyond the ordering it normalises the rest: strings quoted consistently, bare keys left bare and awkward ones quoted, nested tables written as proper [a.b] headers, and arrays of tables as [[a]]. The file is parsed first, so a document that does not format is a document that does not parse, and you get the line number rather than a vague complaint.
A top-level key written below a [table] header belongs to that table. Re-emitting moves plain keys above the first header, where the author meant them.
Nested tables become dotted [a.b] headers and arrays of tables become [[a]] blocks, which is the only valid form for a list of records.
Bare keys stay bare, awkward ones are quoted, and string escapes are normalised.
The file is parsed before it is written, so anything that will not format reports the line it failed on.
TOML has real date and time types, so they are preserved in their original form rather than reinterpreted.
A Cargo.toml, a pyproject.toml, a Netlify config or any TOML file.
A parse failure names the line; a clean parse is reformatted straight away.
Plain keys are moved above the first table header, which is where TOML requires them.
The tidied file is ready to commit.
Because TOML assigns every key after a [table] header to that table. A top-level key written below one is not top-level at all, which is almost never what the author meant.
Single brackets declare one table. Double brackets declare an element of an array of tables, so repeating the header appends another entry.
No. The file is re-emitted from the parsed document, and comments are not part of it. Keep the original if the comments matter.
TOML has real date and time types, which JSON does not, so they are kept as strings in their original form rather than being reinterpreted.
What people who use the TOML Formatter think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the TOML Formatter. It takes half a minute and no account.
Write the first reviewEncode and decode Base32, including the Crockford and hex variants.
Build media queries with framework breakpoints and modern features.
Work out a subnet: network, broadcast, host range and usable count.
Percent-encode URLs and query strings, or decode them back to plain text.
Read a cron expression in plain English and see when it next runs.
Generate believable company names, domains and details for mockups.
Strong random passwords and passphrases, generated locally.
Convert between px, rem, em, pt, %, vw and vh with the right context.