Convert CSV to Markdown

How this tool computes its result

Runs a hand-written character-by-character CSV parser that correctly handles quoted fields, escaped double-quotes (two consecutive quote characters), and both CRLF and LF line endings, discarding rows where every field is blank after trimming. It then builds a Markdown table by finding the widest row (max column count) across the whole file, padding every shorter row with empty cells to match, escaping pipe characters as backslash-pipe and converting embedded newlines to a literal '<br>' tag, and emitting a header row, a '---' separator row per column, and the body rows.

Worked example

A CSV with header 'name,role' followed by rows '"Doe, Jane",Engineer' and 'John,"Manager, EMEA"' parses to three rows because the comma inside each quoted field is preserved as part of that field rather than treated as a delimiter. The output is a 3-row Markdown table where the first data row reads '| Doe, Jane | Engineer |' with the comma intact, not split into an extra column.

When not to use this tool

Uploads are hard-capped at 2 MB (MAX_FILE_SIZE = 2 * 1024 * 1024), and only files whose name literally ends in '.csv' are accepted — a correctly formatted CSV saved with a '.txt' extension is rejected by the filename check alone, regardless of its actual content.

Common mistakes

• - Renaming a CSV export to a different extension — handleFile checks name.toLowerCase().endsWith('.csv') and rejects anything else with 'Please upload a CSV file', even if the content parses fine.
• - Uploading rows with inconsistent column counts — shorter rows are padded with empty cells up to the widest row's width, which can misalign data if a row is missing a trailing comma rather than intentionally shorter.
• - Not noticing pipe characters in cell values — they're correctly escaped to backslash-pipe in the Markdown output, but this can look unexpected when eyeballing the raw text before rendering it.

Related tools