Pikkola TOML, tool No. 52

TOML, read by the spec and written back clean.

Paste a pyproject.toml, a Cargo.toml or a wrangler.toml and read it as JSON or YAML. Change one value and the same document comes back as TOML. The reader follows TOML 1.0, a mistake is marked at its line and column, and nothing is uploaded.

3
formats
6
directions
0
uploads

The studio

One document, three shapes

The source and the target are separate choices, so any of the three formats can become either of the others. The result follows every keystroke.

Input
Examples
Output

            

There is no output yet. Paste something on the left, or load one of the examples.

Checks

    Nothing leaves the tab

    No request, no account, no storage. The Content-Security-Policy sets connect-src to none, so the page could not upload a file even if it tried.

    Why the result can be trusted

    A converter is only as good as its reader. This one is a parser for the whole grammar, and a writer that keeps the order you wrote.

    01

    A parser, not a pattern

    Tables, arrays of tables, dotted keys, inline tables, four string styles, four date and time forms and every radix for numbers are read by their rules. A quoted dot stays inside the key it belongs to.

    02

    An error points at a character

    Line and column come from the parser position, so a missing equals sign or a table declared twice is marked where it starts, not where the file ends. Press a finding and the editor scrolls to it.

    03

    Your file stays here

    Three readers and three writers, in files on this domain. No request, no account, no storage. Load the page once and it keeps working with the network off.

    What the checker looks for

    Syntax first, then the structures that are legal in one format and a mistake in another. Every finding names a line and a column, and the line in the editor is marked when you press it.

    It checks the format, not the schema. A clean result means the file is well formed, not that pip or Cargo will accept it.

    • TOML
      A table declared twiceA [table] header may appear once, while [[array]] may repeat. A key that already holds a value cannot turn into a table later.
    • TOML
      A value that is not TOML0123, 1_000_, 2026-02-31 and a bare word are named with their line and column instead of being read as a string and copied onward.
    • TOML
      An inline table over two lines{ key = value } has to close on the line it opens, and a trailing comma inside it is refused. That is the rule of the format, not a preference of this page.
    • JSON
      A comma JSON forbidsTrailing commas, comments, single quotes and bare keys are rejected at the character that broke the rule, so the message points at the comma, not at the end of the file.
    • YAML
      A tab in the indentationYAML allows a tab inside a value but not in the indent. The column of the first tab is reported, and so is a block that does not line up with its parent.
    • Any
      A document with no TOML shapeTOML starts with a table. A root array or a single value cannot be written as TOML, so the output is withheld and the reason is given instead of an invented key.

    Questions

    Is my file sent anywhere?

    No. There is no endpoint to send it to. The three readers and three writers are JavaScript files on this domain, and the page's Content-Security-Policy sets connect-src to none. Load it once and it keeps working with the network off.

    Which TOML version is this?

    TOML 1.0.0. Bare and quoted keys, dotted keys, tables, arrays of tables, inline tables, basic, multiline basic, literal and multiline literal strings, integers in decimal, hex, octal and binary, floats including inf and nan, and offset, local, date and time values.

    What happens to my comments?

    Turn on Keep comments and a TOML to TOML pass carries them back, attached to the key or the table they sat above, with the inline comment at the end of its line. JSON and YAML have no comment of their own, so the count of dropped comments is reported instead.

    What happens to dates and times?

    A TOML date keeps the text it was written as, so an offset date-time comes back with the same offset and the same fractional seconds. In JSON and YAML it becomes an ISO 8601 string, because a native date there would not survive a round trip through three formats.

    Can anything become TOML?

    Only a document whose root is an object. A JSON array or a bare value has no TOML form, so the output is withheld with the reason. Null has no TOML value at all, so a null key is left out and listed in the checks.

    Does it check my pyproject or my wrangler config?

    It checks the syntax and the structure of the format, not the keys pip, Cargo or Wrangler expect. A clean result means the file is well formed TOML, not that the service will accept it.