Account

What new tool do you want?

Text & Writing

Text to Table Converter

Turn tab, comma or space separated text into a Markdown, HTML or aligned plain-text table.

How to use

  1. 1Paste rows of data, one row per line.
  2. 2Pick the separator and output format — the first row becomes the header.

Frequently asked questions

What separators are supported?

Tabs (as copied from spreadsheets), commas, semicolons, pipes and runs of two or more spaces. 'Auto' picks the most likely one.

Can I paste straight from Excel or Google Sheets?

Yes. Copied cells are tab-separated, which auto-detect handles.

Are quoted CSV values supported?

Yes. Values in double quotes may contain commas, and doubled quotes inside are unescaped.

A worked example of why quoted CSV parsing is harder than split(',')

The input a,b then "x, y",z converts correctly to a two-row, two-column table where the second row's first cell is "x, y" as a single value — not two separate cells split at the comma inside the quotes. A naive .split(",") would wrongly break "x, y" into "x" and " y"", producing a misaligned table with an extra column. The parser instead tracks whether it's currently inside a quoted value character by character, only treating the separator as a real column break when it's outside quotes, and correctly unescapes a doubled "" inside a quoted value back to a single literal quote character — exactly matching how spreadsheet programs export CSV.

Why auto-detect checks tabs before commas

The auto-detect logic checks for a tab character first, before commas, semicolons or pipes — a deliberate ordering, because copying cells directly out of Excel or Google Sheets onto your clipboard produces tab-separated values even though the cells themselves might contain actual commas (a price like "$1,234" or an address). If auto-detect checked for commas first, pasted spreadsheet data containing a comma inside a cell would be mis-split at the wrong character; checking for tabs first means a genuine spreadsheet paste is correctly recognized before the parser ever considers treating a stray comma as a column separator.

Why the plain-text output needs column-width math at all

The ASCII output format — k, v / long key, 1 rendering as aligned columns with a --+-- rule row — requires computing the widest value in each column first (Math.max across every row for that column index) before any row can be printed, since every cell in a column needs padding to match the column's single widest entry for the columns to actually line up. This is exactly the same alignment problem a terminal table-printing library solves, and it's why this has to be a two-pass process: one pass to measure every column's required width, a second pass to actually render each row padded to that width.

Short rows gain empty cells, and a column is at least three dashes wide

Blank lines are dropped, and if nothing is left the result is empty. Every row is padded out to the widest row, so a short second line becomes an empty cell rather than a broken table. Auto-detect looks at the first remaining line only. A tab wins, then a pipe, then a semicolon, then a comma, and if none of those appear it splits on two or more spaces. A pipe row loses a pipe at the very start or end, which is how a Markdown row is read. Cells are trimmed. HTML output escapes an ampersand and angle brackets, and Markdown escapes a pipe that sits inside a cell. The dash row under the header is at least three dashes wide even when the header is a single letter.

Related tools

More: Text & Writing