Proper CSV parsing
Quoted fields, escaped quotes, embedded commas and embedded newlines are parsed by a real CSV parser, not a split on commas.
Drop a CSV and get a GFM table you can paste into a README, a pull request description or a docs page. The first row becomes the header, and fields with commas or quotes are handled correctly.
How it works
The converter on this page is already set to CSV to Markdown. Nothing else to configure.
Drop a .csv file.
Check the header row and column count in the preview.
Copy the table into your README or download the .md file.
What you get
Quoted fields, escaped quotes, embedded commas and embedded newlines are parsed by a real CSV parser, not a split on commas.
The output is a GFM table, so it renders correctly on GitHub, GitLab, Obsidian and most Markdown editors.
Short rows are padded and long rows are trimmed so the table stays valid instead of collapsing.
CSV to Markdown
The edge cases, stated plainly.
Comma, semicolon and tab are detected automatically from the first lines of the file.
Tables with thousands of rows are technically valid but unpleasant to read. Consider splitting the data or keeping only the columns you need.
UTF-8 is assumed. Files in older encodings may show mangled accents; re-save as UTF-8 first.
Next
Each sheet becomes a Markdown heading followed by its table, so a workbook stays navigable.
Convert nowAn array of flat objects becomes a table; nested objects become headings and bullet lists; primitives become simple values.
Convert nowWord heading levels become Markdown heading levels, and nested lists keep their indentation.
Convert nowDrop the file above. No account, no queue, no watermark on the result.