Loading validator...

How to Validate TOON Format - Step by Step Guide

Step 1

Input Your TOON Data

Start by inputting TOON data from your Mistral AI, Claude, xAI (Grok), or other AI workflows that you want to validate. The validator checks syntax, structure, and format compliance:

•
Paste directly: Copy your TOON data and paste it into the validator
•
Upload a file: Click "Upload" to select a .toon file from your computer
•
Try the sample: Click "Sample" to load valid TOON data as an example
Step 2

Automatic Validation

The validator automatically checks your TOON data in real-time:

•
Syntax: Reads every line the way a TOON decoder does, including keys, colons, quotes and escapes
•
Array length verification: Ensures declared array lengths match actual row counts
•
Rows and delimiters: Checks each row has one value per column, and points out rows split with a different delimiter than their header
•
Skipped lines: Catches lines a TOON reader would quietly ignore, such as a line placed after a table already has all its rows
Step 3

Review Results & Fix Errors

Get detailed validation results with actionable feedback:

•
Clear error messages: The line, the column where it can be pinned down, a plain explanation and a hint. Show in editor jumps to the line
•
Statistics and warnings: Line, array, object and value counts for valid data, plus warnings for things that are legal but probably not what you meant, like a duplicate key
•
Common issues help: Guidance on fixing typical TOON format errors

Frequently Asked Questions

What does the TOON validator check?

It reads your TOON the same way the @toon-format/toon decoder does, so the verdict matches what a real TOON reader will do. That covers [N] counts against the actual rows or items, the number of values in each table row, indentation (spaces only, in steps of two), quotes and escapes, and the colon after each key. It also catches the sneaky case where the decoder accepts the file but quietly skips lines, for example a line placed after a table already has all its rows. Errors come with the line number, the column when it can be told, and a hint, so you know the data is safe to hand to an LLM API or convert to JSON.

What are common TOON validation errors?

Most often the [N] count is off because rows were added or removed by hand. After that come rows with one value too many (usually an unquoted comma inside a value, like Smith, John), rows split with pipes or tabs under a header that declares commas, a missing colon after a key, indentation that isn't a multiple of two spaces, and a quote that is never closed.

Can the validator fix errors automatically?

No. It tells you what is wrong and how to fix it, but it never changes your data. If the only problem is messy spacing, the TOON Formatter can tidy that up for you.

Does it validate all delimiter types?

Comma, tab and pipe tables all work; the delimiter is whatever the header declares inside the brackets, like [3|] for pipes. When a row has the wrong number of values, the validator also checks whether it would fit if split on another delimiter and tells you so. It can't catch every mix-up, though: in an inline array such as tags[2]: a|b, c the pipe is just part of the first value, which is perfectly legal TOON.

Is validation performed on my server?

No. Validation runs in your browser and your TOON is never sent to our server. The page does keep your last input in this browser's local storage so it's still there after a reload; clearing the editor removes it.

Is the TOON validator free?

Yes, completely free with no limitations. Validate unlimited TOON files with no registration required. Also try our JSON to TOON and TOON to JSON converters.