CSV to Markdown table converter

What a CSV actually stores

A CSV is already text, so it is tempting to paste it straight in. The reason to convert is that a Markdown table restates the column on every row, which removes the ambiguity a model otherwise has to resolve by counting commas.

Exported data lands as CSV constantly, and "what does this data show" is a question models answer well when the table arrives unambiguous.

What survives the conversion

All rows and columns, with the delimiter sniffed rather than assumed — comma, tab, semicolon and pipe are all handled. Quoted fields containing commas, and escaped quotes inside quoted fields, are parsed properly rather than split naively.

What does not

Nothing structural, since a CSV has almost no structure to lose. Conversion is capped at 500 rows, beyond which you are usually better off summarising than pasting — a point the token panel will make for you.

Saying so plainly is deliberate. A converter that quietly drops half a document is worse than one that tells you which half, because you can work around a limit you know about.

Questions

Does it handle commas inside quoted fields?

Yes. That is the normal case rather than an edge case, and splitting on every comma would corrupt any real export.

What about tab-separated files?

Handled — the delimiter is detected from the data rather than from the file extension.

Is there a row limit?

Five hundred rows per conversion. Past that, the context window becomes the binding constraint long before the converter does.

Converting a different format

The same engine handles eighteen formats in total, all of them in your browser.

Token rates checked 2026-08-31. See the cost on all 35 models →