Line up the pipes in every Markdown table, keeping alignment markers and escaped pipes intact — or export the tables as CSV for a spreadsheet.
Waiting for Markdown
Finds every pipe table in the document. Tables inside a fenced code block are left alone.
Formatted tables appear here
Every pipe lined up, alignment markers kept, and an escaped pipe treated as a character rather than a boundary.
Markdown Table Formatter runs entirely on your device — nothing is uploaded.
You’re on the Free plan. Compare plans
Finds every pipe table in a Markdown document, lines up its columns, and can export the lot as CSV.
Alignment is measured in display columns rather than code points, which is the detail that separates a table that lines up from one that nearly does. A CJK character occupies two columns in a monospaced font; counting it as one leaves every row containing it short by the number of such characters, and the pipes drift. The same applies to anything else double-width.
Two things that look like column boundaries are not. An escaped pipe, \|, is a pipe character inside a cell. And a pipe inside an inline code span — a | b — belongs to the code, not to the table. Splitting on either produces a table with the wrong number of columns, which then fails to render at all in most parsers.
Alignment markers in the delimiter row are read and preserved: :--- for left, :---: for centre, ---: for right. The cell contents are padded to match, so the rendered table and the source agree about which way each column leans.
A row with a different number of cells from the header is reported rather than silently dropped or truncated. Most renderers pad or cut such a row without saying anything, which is how a column of data goes missing unnoticed. The CSV export pads them to the header's width, so every line has the same number of fields — which is what RFC 4180 requires and what a spreadsheet expects.
It should not here — widths are measured in display columns, so double-width characters count as two. If it looks wrong in your editor, the editor is using a font where those characters are not exactly double-width, which no amount of padding can fix.
Escape it as \| or wrap it in backticks. Both are recognised as content rather than as a column boundary, so the table keeps its shape.
It is padded to the header's width and reported above the output. Most renderers do the padding silently, which is how a missing column goes unnoticed.
Yes. The colons in the delimiter row are read and written back, and the cell contents are padded to match so the source looks like what renders.
Yes, to RFC 4180: a cell containing the delimiter, a quote or a line break is wrapped in quotes and its own quotes are doubled. That is what spreadsheets expect.
No. A table-shaped block inside a fence is an example of a table, not a table, so it is left alone.