Micro Tools
Advertisement

SQL Insert to TOML converter

Convert SQL Insert to TOML free, right in your browser. Paste your SQL Insert input below and press Convert. Rows become an array of TOML tables loadable by any TOML parser. No sign-up, and nothing is ever uploaded.

SQL Insert input

Paste your SQL Insert below, then press Convert.

Runs 100% in your browser. Nothing is uploaded.

Waiting for input.

Advertisement

How the conversion works

Paste your SQL Insert on the left and press Convert. The tool first parses the SQL Insert (tokenizing each INSERT INTO statement and decoding quoted strings, NULLs and numbers) into an internal table of rows and columns, then writes it out as TOML (writing rows as an array of [[rows]] tables). If the input cannot be parsed you get a plain-English error instead of a broken file.

Where this comes in handy

People reach for this converter when migrating database dumps or seed data and TOML is needed for config files. Because everything runs locally in your browser, it is also handy for quick one-off migrations without installing database tools or writing throwaway scripts.

Related tools

JSON formatterFormat and validate JSON, privately. Regex testerTest regex live with highlighting. Base64 encoderBase64 encode and decode, plus URL encoder and JWT decoder.

SQL Insert to TOML FAQs

How are quoted strings and NULL handled?
Single-quoted strings with '' escapes, double-quoted identifiers, TRUE/FALSE and NULL are all understood, and numbers stay numeric in the output.
Does it support INSERTs from mysqldump?
Yes. Standard mysqldump INSERT INTO ... VALUES tuples parse fine. Trailing clauses like ON DUPLICATE KEY UPDATE are skipped once the values are read.
What happens to nested values?
Nested objects and arrays that TOML cannot express natively are stored as JSON strings inside their cell.
How are table rows represented in TOML?
Each row becomes an entry in an array of tables ([[rows]]), with columns as keys inside each entry.
Is there a size limit?
No hard limit, but very large pastes (tens of megabytes) can slow down the browser tab. For huge inputs, split them into smaller chunks.
Advertisement