Visual Markdown table editing tool | ZeroTools

The Markdown table editor tool is a tool that allows you to edit header rows and data rows in a spreadsheet-like input field and assemble them into Markdown notation.

The top row is the column header, and the rows below it are the data rows. Since the output field is updated directly as you modify each cell, you can create tables without manually counting pipes or hyphens.

Rows and columns can be added or deleted using buttons. When a column is deleted, the header, all data rows, and the column alignment specification are also removed from that same position.

There is no feature to drag and drop rows or columns to rearrange them. If you want to significantly change the order, please rearrange them in the original CSV/TSV and re-import them, or move the cell contents manually.

The output is in the order of the header row, a delimiter row consisting of colons and hyphens, and data rows. It calculates a simple display width of the characters contained in each column and adds half-width spaces to the end to make the source code easier to read.

These spaces do not fix the rendered column width; the actual table width will change depending on the CSS of the publishing site and its contents.

For each column, you can choose left, center, or right alignment. A colon is placed at the left end of the delimiter for left alignment, at both ends for center alignment, and at the right end for right alignment.

It determines the number of hyphens based on the maximum character width of the column, securing at least the length necessary for a Markdown table.

You can select this depending on the content, such as placing amounts or quantities on the right, short status values in the center, and descriptive text on the left.

These column alignment symbols are a table extension syntax used in GitHub Flavored Markdown and others. Processors that implement only the basic CommonMark specification may not interpret the meaning of tables or colons.

Since CSV and TSV do not have a mechanism to save column alignment, please adjust the initial alignment on this tool's side when importing from a pasted source.

The display width uses a simple approximation where ASCII and half-width kana are counted as 1, and others as 2. It does not accurately measure exceptions for emojis, combining characters, proportional fonts, or East Asian widths.

We do not guarantee that the pipe positions in the generated code will perfectly align in a text editor or that the rendered appearance will be identical.

The CSV/TSV import field accepts text inputs up to 200,000 UTF-16 code units (including any leading Byte Order Mark, which is automatically stripped upon import).

The delimiter can be chosen from Auto, Comma, or Tab. In "Auto" mode, the parser analyzes the first logical record and counts the number of commas and tabs located outside of double quotes; the delimiter with the higher count is selected, with ties resolving in favor of Comma.

It is strictly designed for comma- and tab-delimited text and does not detect arbitrary CSV dialects, mixed delimiter schemes, or semicolon separators.

When importing, the first logical record is always treated as the header row, and subsequent records are treated as data rows (supporting 0 data rows for header-only tables).

Within double-quoted fields, delimiters, carriage returns (CR), line feeds (LF), and CRLF line breaks are preserved directly as cell content, while literal double quotes inside quoted fields are represented by doubling them ("").

A quoted field must begin with a quote at the start of the cell, and the closing quote must be immediately followed by a delimiter or a record separator.

If unclosed quotes or malformed characters following a closing quote are encountered, the parser rejects the import with a visible error without modifying or clearing the current table.

For ragged rows with varying column counts, missing cells are automatically padded with empty strings to match the maximum width of the longest row, without trimming cell spaces.

The import strictly enforces limits: any input exceeding 200 data rows (excluding the header), 30 columns, or 500 UTF-16 code units per cell (including headers) will cause the import to be rejected.

A single terminal record separator does not generate a ghost row, though further blank records will count toward the data. Leading zero characters are preserved as literal text when importing; however, spreadsheet-specific formulas, formatting, merged cells, and data types (such as native dates or numeric types) are not preserved when pasting text, so please check how the values appear.

In Markdown tables, the pipe symbol serves as a column boundary. When generating Markdown tables, this tool automatically escapes original backslashes first, and then escapes pipe characters within cell contents.

This precise sequential escaping ensures that backslashes entered by the user are distinguished from syntax escape sequences introduced by the tool.

However, the final rendering interpretation still depends entirely on the destination Markdown parser.

CRLF, CR, and LF line breaks within cells are automatically converted into <br> tags, preserving each table row as a single text line in the generated Markdown source.

This is effective in environments that permit inline HTML, though destinations that disable HTML may display the tag as literal characters or strip it entirely.

In the header row, pipes and backslashes undergo the exact same escape processing.

This escape behavior is strictly designed to maintain Markdown table structure and does not act as an HTML sanitizer. Markdown inline syntax and HTML tags inside cells will still be interpreted by the destination platform.

When publishing untrusted user inputs, you must independently verify the destination's HTML processing, link handling, and script sanitization countermeasures.

Data rows can range from 0 up to a maximum of 200, and columns can range from 1 to 30. Each cell, including the header row, has a strict limit of 500 UTF-16 code units; direct manual editing in the grid truncates input at this limit, while CSV/TSV imports reject records exceeding this size.

The overall CSV/TSV input is capped at 200,000 UTF-16 code units. When limits are reached, addition buttons are disabled or an informative message is displayed on screen.

These boundaries are implemented to bound workload when handling numerous interactive inputs and real-time Markdown output within the browser, though they do not guarantee identical rendering performance or smooth operation across all devices.

Large tables approaching 200 rows by 30 columns can be difficult to scroll or edit on mobile devices and narrow displays, and they may be hard to read at the publication destination.

Performance can vary significantly depending on browser execution and hardware capability. Consider whether extensive data can be divided into multiple thematic tables.

"Clear All" is an explicit operation to erase the table contents. There is no automatic saving, undo history, or project persistence.

When entering or pasting extensive data, please keep your original data stored separately and copy the generated Markdown text as you finish each working section.

This tool takes CSV/TSV text as an entrance and outputs Markdown table text as an exit. It does not support reverse reading of existing Markdown tables, re-exporting to CSV, reading or saving XLSX files, cell merging, formula calculation, sorting, filtering, type inference, or multiple sheets.

The generated Markdown is transferred to the clipboard using the copy button, but there is no file saving or rendered live preview feature.

Copying relies on browser clipboard permissions, awaiting permission resolution and displaying a visible failure message if clipboard access is denied.

The output area is read-only; the copy success indicator is immediately reset whenever edits to grid headers, cells, alignments, or import operations alter the generated output.

After pasting into your target document, verify that it is recognized as a table, and inspect column alignment, pipe escaping, <br> line breaks, empty cells, and character widths.

Borders, margins, and line wrapping will vary depending on the destination Markdown parser and styling.

Before importing from CSV/TSV, ensure that the first record is truly the header. If you paste data without headers, the first data row becomes the column names.

Spaces, empty headers, whitespace-only headers, and duplicate headers are preserved exactly as entered without automatic renaming; ensure headers are descriptive so readers understand each column.

While a single trailing newline does not add an extra row, blank records within the body are preserved as empty table rows. Missing cells on short rows are padded to the maximum row width without trimming.

When comma and tab counts are similar, the automatic delimiter detection (which counts unquoted commas and tabs in the first logical record) might select an unexpected delimiter; in that case, manually choose Comma or Tab.

The tool does not automatically trim spaces outside CSV fields, so confirm whether leading and trailing spaces should be kept. Only text pasted directly into the browser is parsed, without character encoding conversion or local file upload dialogs.

If you manually edit the Markdown output after copying, check that colons in the delimiter row have not been removed and that backslashes preceding pipes remain intact.

The spaces automatically padded by the tool are purely for source code readability; removing them preserves table syntax, but pipes and delimiter rows are strictly required.

While tables facilitate structured comparisons, packing long paragraphs into cells makes them difficult to read. Even within the 500-character cell limit, extensive explanations should be placed in main text paragraphs and referenced from the table.

Verify that table headers and cell relationships remain legible on narrow screens and accessible to assistive technologies.

Clean padding in source text does not guarantee rendered visual quality or accessibility. Always have a human review the final rendered table before publishing, confirming that column headers adequately describe the content, whether large tables should be split, and whether the layout remains readable on mobile devices.