CSV to Markdown table
The separator and the header row are read from the text, asked about only when the text is unclear, and the rows write out as a pipe table a README renders.
What you get
- Writes the Kibana export's 6 rows as a 8-line pipe table — the header, the rule, one row each
- Detects the separator — comma, semicolon, tab, pipe — and whether the first row is a header, and shows the guess before writing
- Escapes a pipe inside a cell and writes a line break as <br>, so the table survives a renderer
- Reads quoted cells, embedded commas and doubled quotes the way RFC 4180 writes them
What it will not do
- Write alignment colons. The rule line is plain --- under every column.
- Render the Markdown. It writes the table text; your README renders it.
- Send your text anywhere. The page is static and the engine runs in this tab — open the network panel and watch it stay empty.
What the CSV gives
- A header and rows → a pipe table
sku,qty A,1 B,2| sku | qty | | --- | --- | | A | 1 | | B | 2 |- A pipe in a cell → escaped
a,b "x | y",1| a | b | | --- | --- | | x \| y | 1 |- A semicolon file
The separator is read from the text — comma, semicolon, tab or pipe — and shown as a chip before anything is written.
- No header row
The columns are numbered c1, c2 … and the table’s header says so; you can name them in the app.
The sample
What the first sample opens — a real file, not an illustration written for this page.
in VS Code
Read as records asks separator and first row; Convert, then Markdown writes the pipe table into a new editor.
Questions
My CSV uses semicolons. Does it work?
Yes. The separator is read from the text itself and shown as a chip; a European export with semicolons and decimal commas is the case that question exists for.
What about a cell that holds a pipe?
It is written as \|, so the table keeps its columns when rendered.
Can I go back from the table?
Yes — the Markdown table to CSV page opens a pipe table as rows with no question and writes the CSV.