ASCII Table Generator

What an ASCII table is for

An ASCII table is data drawn with plain text characters — pipes, dashes, and plus signs — so it lines up perfectly in any monospaced environment where rich formatting doesn't exist. Code comments, README files, terminal output, commit messages, GitHub issues, plain-text email, and chat messages all benefit from a table you can paste as-is and have it stay aligned. This generator turns raw rows and columns into a tidy, monospaced table in several border styles, including GitHub-flavored Markdown, with per-column text alignment.

Two ways to enter data

The Paste mode accepts comma-separated (CSV) or tab-separated (TSV) data, and it auto-detects which you used by counting tabs versus commas in your input — so you can paste straight from a spreadsheet (which copies as tabs) or from a CSV file without changing a setting. The Visual Editor mode gives you an editable grid where you add or remove rows and columns with buttons and type directly into cells, which is handy when you're building a small table from scratch rather than importing one.

The border styles, and how they're built

You can choose from five output styles, and the tool computes each column's width from its widest cell (plus padding) so everything aligns regardless of content length:

The Rounded and Double styles use Unicode box-drawing characters, which render beautifully in modern terminals and editors but need a UTF-8 environment; the Classic and Markdown styles use only pure ASCII and pipes, so they survive anywhere.

A worked example

Paste this CSV:

Name, Age, City
Alice, 30, New York
Bob, 25, London

With "First row is header" checked and Classic style selected, you get a boxed table where the header is separated from the body by a heavier = rule and each column is padded to fit "New York" and "Charlie". Switch the style to Markdown and the same data becomes:

| Name | Age | City |
| :---- | :-- | :------- |
| Alice | 30 | New York |

That second line is the Markdown alignment row, and it encodes your per-column choices: a leading colon means left-aligned, a trailing colon means right, and colons on both ends mean center. Set the Age column to right alignment and watch the numbers shift to the right edge of their cells — useful because right-aligned numbers are far easier to scan and compare.

Practical use cases

• README and documentation tables. Generate Markdown tables for GitHub without hand-counting pipes.
• Code comments. Drop a Classic ASCII table into a comment to document a mapping, a config matrix, or expected test outputs.
• Terminal and CLI output. Use Rounded or Double styles for help text and status displays.
• Plain-text reports and email. Share small datasets that stay aligned even where HTML isn't allowed.

Tips for clean tables

• Right-align numeric columns. Numbers compare best when their ones, tens, and hundreds digits line up vertically.
• Use Markdown for anything going on GitHub. It renders as a real HTML table there, while still staying readable as plain text in the raw file.
• Pick Classic for guaranteed compatibility. If you're unsure whether the destination supports Unicode, the pure-ASCII Classic style never shows broken boxes.
• Build small tables in the Visual Editor. For a handful of cells it's faster than formatting CSV, and you can add columns on the fly.

Common mistakes

• Forgetting to view monospaced output in a monospaced place. ASCII tables only line up in a fixed-width font. Pasted into a proportional-font document (like a Word file in the default font), the columns will drift — set the text to a monospace font first.
• Leaving the header toggle wrong. If your first row is data, not labels, uncheck "First row is header" or the tool will draw a separator in the wrong place.
• Wide cells from stray spaces. Column width follows the longest cell, so an accidental trailing space or a very long value balloons the whole column. Trim long entries if compactness matters.
• Expecting Unicode boxes everywhere. Rounded and Double styles can render as question marks or boxes in old terminals and non-UTF-8 systems. When in doubt, fall back to Classic.