How do you use this tool?
- Drag a CSV or TSV file in or use the file picker — alternatively paste the content directly
- Check delimiter and header row in the preview — override manually if the heuristic is off
- Click 'Download Markdown' or copy to clipboard with the button
Why convert CSV to Markdown?
CSV (Comma-Separated Values) is the simplest data exchange format — text with delimiters, in use since the 1970s, readable by every tool. Markdown pipe tables are the simplest table format for wikis and AI prompts — plain text that renders in any Markdown renderer.
Yet the direct hand-off doesn’t work: you can’t paste a CSV file into Obsidian, a Hugo post, or a Claude prompt — it would arrive as raw text. This tool takes your CSV (or TSV, or PSV) and writes clean GitHub Flavored Markdown.
How does the conversion work?
An established open-source spreadsheet library reads CSV/TSV files directly in the browser. A heuristic runs before parsing to detect the delimiter: it counts the frequency of comma, semicolon, tab and pipe in the first lines — the candidate with the most consistent column count wins. That covers European locale (semicolon), US locale (comma), TSV exports and PSV in a single path.
After parsing, the header row is detected (first row vs. rest), and the
tool writes a GFM pipe table with a header divider row (| --- |). Long
cells get wrapped if needed, empty cells stay empty (no ‘N/A’ padding).
What is the tool actually used for?
- Data list in wiki documentation. A CSV of subscription plans, vendor list or inventory becomes a Markdown table in internal docs.
- AI prompt with tabular data. Claude or GPT receives the CSV data as a pipe table directly in the prompt — more precise than raw CSV text.
- Hugo / Astro content tables. Statistics tables from database exports land as Markdown blocks in blog posts.
- Obsidian Dataview sources. Markdown tables with clearly defined headers can later be processed in Dataview queries.
- GitHub issue tables. CSV exports from tracking tools become pipe tables that stay readable inside issue bodies.
What stays — what doesn’t?
Preserved: all cell values (text and numbers), header row (when
detected or manually set), column order, special characters (via
RFC 4180 quoting), line breaks within fields (as HTML <br> inside
Markdown pipe tables).
Added: header divider row (| --- |) — Markdown requires it for
the table to render as a table.
Deliberately dropped: original delimiter information (implicit in the Markdown pipe syntax), Excel formats (CSV doesn’t have those — only strings and numbers), encoding BOM markers (the Markdown is always UTF-8). The conversion is clearly defined: tabular plain text becomes tabular plain text, in a different syntax.
Privacy — everything stays in your browser tab (Datenschutz)
CSV files often contain very sensitive datasets: newsletter subscriber lists, customer database exports, payroll data, internal KPIs, lead lists. Uploading that data to an online converter — even one that promises ‘24-hour deletion’ — violates internal compliance in almost any GDPR-relevant context.
None of that happens here. The CSV is read and converted in the browser
tab via web standards (File API). Open the Network panel of your
developer tools and check: not a single record leaves your machine.
The paste mode also runs fully client-side.
Which related converters exist?
This tool is part of the Markdown converter family:
- XLSX to Markdown — Excel including XLS and ODS, multi-sheet support.
- HTML to Markdown — file or paste mode.
- PDF to Markdown — including scanned PDFs via OCR.
- DOCX to Markdown — Word documents with heading structure and lists preserved.
Last updated: