ASCII Table Generator

ASCII Table Generator — Free Text Table Generator Online

Paste CSV, type your data directly, or build row by row — and instantly get a clean, perfectly aligned plain-text table. Choose from MySQL (+--+), Markdown (|--|), Unicode box-drawing (┌──┐), rounded (╭──╮), double-line (╔══╗), or reStructuredText (===) styles. Copy with one click, download as .txt, and use it anywhere text is rendered.

Perfect for code comments, GitHub README files, Stack Overflow answers, terminal scripts, plain-text emails, and Python documentation.

How to Use the ASCII Table Generator

1. Enter your data — type directly into the grid cells, or click "Paste CSV" to import comma-separated or tab-separated data from your clipboard. The first row becomes column headers automatically.
2. Choose a border style — select from MySQL, Unicode Box, Rounded, Double Line, Markdown, reStructuredText, or Minimal depending on your use case.
3. Adjust settings — pick text alignment (left, center, right), toggle the header row, enable compact mode, or adjust cell padding.
4. Copy or download — click "Copy to Clipboard" to paste the result wherever you need it, or download as a .txt file.

What Is an ASCII Table?

An ASCII table (in the formatter sense) is a plain-text table built from standard keyboard characters and Unicode box-drawing symbols. Unlike HTML or Markdown tables that require a rendering engine, ASCII tables:

• Work in any terminal, code editor, or plain-text environment
• Render correctly in any monospace font without CSS or HTML
• Survive copy-paste across Slack, email, GitHub, Jira, and Word
• Stay readable even as raw source code

This is different from the ASCII character reference table — this tool is specifically a table formatter that takes your data and draws it as aligned rows and columns.

Border Style Guide — Which to Use

MySQL / Classic (+--+): The most portable style. Uses only keyboard characters, works everywhere. Best for code comments, database output, and environments where Unicode support is uncertain.

Unicode Box Drawing (┌──┐): A clean upgrade from MySQL. Uses Unicode characters (U+2500–U+257F) for proper corners and intersections. Fully supported in all modern terminals and code editors.

Rounded (╭──╮): A softer aesthetic with rounded corners. Used in modern CLI tools and API documentation.

Double Line (╔══╗): Heavy double-line borders for visual emphasis. Good for titles, summaries, and headers that need to stand out.

Markdown (|--|): The standard format for GitHub and GitLab READMEs, wikis, and documentation sites. Not drawn as ASCII when rendered — GitHub converts it into a real HTML table.

reStructuredText (===): The format required by Python's Sphinx documentation system and ReadTheDocs. Uses === underlines instead of border characters.

Minimal: No border characters at all — just space-separated columns with a single dash separator under headers. Clean for terminal output where borders feel noisy.

Common Use Cases

• Code comments and docstrings: MySQL or minimal style tables inline in code comments add clarity to data structure documentation, API response formats, and configuration option tables — without requiring any rendering engine.
• GitHub and GitLab READMEs: Markdown-style output renders as a real table on GitHub. Perfect for dependency matrices, feature comparisons, and changelog tables.
• Terminal scripts and CLI tools: Generate properly aligned output tables for scripts, help text, and man pages. Minimal and MySQL styles work best here.
• Stack Overflow and forum answers: Both ASCII and Markdown tables survive copy-paste into Stack Overflow and most forum platforms without losing alignment.
• Python documentation: When writing .rst files or Python docstrings rendered by Sphinx, the reStructuredText output is required — this generator produces the exact === format Sphinx expects.
• Plain-text emails: ASCII minimal style preserves column alignment in email clients that strip HTML, making it ideal for developer newsletters and technical reports.

Frequently Asked Questions

How do I make an ASCII table for a GitHub README?

Use the Markdown style output. GitHub renders Markdown pipe tables (| col | col | / |---|---|) into properly formatted HTML tables. For the raw text fallback — if someone views the .md file without rendering — MySQL (+--+) style is the most universally readable alternative since it uses only basic keyboard characters.

What is the difference between ASCII table and Markdown table?

An ASCII table uses border characters (+, -, | or Unicode box-drawing symbols) to visually draw the table in raw text — it looks like a table whether rendered or not. A Markdown table uses pipe and dash syntax that only appears as a real table when processed by a Markdown renderer like GitHub or VS Code. Both outputs are generated by this tool.

Can I paste CSV directly into the generator?

Yes. Click "Paste CSV" and the tool reads comma-separated or tab-separated data from your clipboard, parses column headers from the first row, and fills the grid automatically. You can also type or edit data directly in the cells after importing.

What are Unicode box-drawing characters?

Box-drawing characters are a set of Unicode characters in the range U+2500–U+257F designed specifically for drawing text-based diagrams, frames, and tables. They include horizontal lines (─), vertical lines (│), corners (┌ ┐ └ ┘), and T-intersections (┼ ├ ┤ ┬ ┴). All modern operating systems, terminals, and code editors support them.

Does my data get sent to a server?

No. All table formatting runs entirely in your browser using JavaScript. Your data — including any sensitive cell content — is never transmitted to any server or stored anywhere outside your browser session.

What is reStructuredText (RST) table format?

reStructuredText is the markup language used by Python's Sphinx documentation system (and ReadTheDocs). RST simple tables use ===== runs to define column widths, with the same pattern above and below the header row and at the end of the table. This format is required for Python docstrings and .rst files that render through Sphinx.

The table looks misaligned when I paste it — why?

ASCII and Unicode box-drawing tables require a monospace (fixed-width) font to align correctly. If you paste into an editor using a proportional font, columns will appear misaligned. Switch to a monospace font like Fira Code, JetBrains Mono, Consolas, Monaco, or Courier New. All popular code editors use monospace fonts by default.

Resources

• Unicode Box Drawing Characters — Unicode Charts — Official Unicode chart for the full set of box-drawing characters used in Unicode table styles.
• GitHub Flavored Markdown — Tables — GitHub's official guide on Markdown table syntax, alignment, and rendering behavior.
• reStructuredText Tables — Docutils Reference — Complete reference for RST simple and grid table syntax used by Sphinx and ReadTheDocs.