Fill in a grid and get a properly formatted Markdown table. Tables are the one part of Markdown that is genuinely miserable to write by hand: the pipes have to line up to stay readable, and alignment is encoded by where you put colons in the separator row. Both are handled here, with columns padded to a common width so the source stays legible after you have edited it a few times. Alignment is per column and cycles through left, centre and right with a click. Content is escaped properly, so a cell containing a pipe does not silently end the cell. You can also paste an existing table to load it back into the grid and edit it — escaped pipes are read back correctly, so nothing is lost on the round trip.
| Separator | Alignment |
|---|---|
| --- | Left (the default) |
| :--- | Left, explicitly |
| :---: | Centre |
| ---: | Right |
| -- | Too short — some parsers reject it |
| \| | A literal pipe inside a cell |
No. The table is built in your browser.
Not to any parser — the rendered output is identical either way. It matters to you, because the Markdown source is where you edit the table, and an unpadded one is very hard to read after a couple of changes.
Through colons in the separator row: no colon is left, a trailing colon is right, and colons at both ends is centre. Click a column header here to cycle through the three.
It is escaped as \| automatically, because an unescaped pipe would end the cell. Pasting a table back in honours that escape rather than splitting on every pipe, so the content survives the round trip.
No — Markdown table cells are single-line by definition, and a newline would end the row. Line breaks in pasted content are flattened to spaces. If you need block content in a cell, a Markdown table is the wrong structure.
Because Markdown has no headerless table. The separator line under the first row is precisely what makes the block a table rather than paragraphs containing pipes.
Markdown tables are the one part of the format that is genuinely unpleasant to write by hand, because the pipes have to line up to stay readable and the separator row encodes alignment through the placement of colons. Both are handled here. Columns are padded to a common width — no parser requires it, but the source is where the table is edited and an unpadded one becomes unreadable after two edits. The separator keeps at least three dashes whatever the colons, because several parsers reject a two-dash cell, which is what you get if the colons are carved out of a fixed width rather than added to it. Alignment is per column: no colon for left, a trailing colon for right, colons at both ends for centre, and the padding inside the cells follows the same alignment so the rendered and source views agree. Cell content is escaped on the way in — a pipe would end the cell and a newline would end the row, so pipes are backslash-escaped and newlines flattened to spaces. Reading a table back in honours that escape rather than splitting on every pipe, which means a table can be pasted in, edited and regenerated without a cell containing a pipe being silently cut in two. The first row is always the header, because Markdown tables have no headerless form: the separator line beneath the first row is what makes the block a table at all. Everything runs in your browser.