Skip to content

Choose your path

Built around the job you need to finish

Convert plain-delimited physical records into literal GFM tables without silently trimming cells or dropping uneven rows.

Documentation editor

Publish a pipe-delimited checklist without activating embedded markup.

Paste actual records, inspect literal cells, choose alignment, generate and review Markdown.

Every cell is retained; links, tags and pipes stay literal text.

Operations analyst

Keep padded identifiers and detect missing cells.

Import UTF-8 records with zeros, spaces and blank lines; recover from strict width errors using explicit padding.

No silent trimming, coercion or discarded extra fields.

Mobile report author

Publish a table from a phone without losing the source.

Choose a custom separator, inspect a paged preview, copy or request a download, undo a source replacement.

Controls and contained table are usable; output includes all records.

Was this tool helpful?

Reference & details

How it works

Read physical records

CR, LF and CRLF separate records; a final terminator adds no phantom row. Separators are literal strings, not regular expressions. Quotes and backslashes have no CSV escaping meaning.

Validate the table shape

Keep spaces and empty records by default. Missing cells require explicit padding; extra cells are never dropped. Headerless padding uses the widest record and generates column names. One leading BOM is omitted from the table.

Publish literal text

Encode cell punctuation and whitespace as numeric references in GFM. Preview up to 200 original rows in pages of 50; export every row. Limits: 5,000 body rows, 200 columns, 100,000 cells, one million input and two million output characters.

Updated: August 2026

Example Scenarios

Publish a pipe-delimited checklist without activating embedded markup. Paste actual records, inspect literal cells, choose alignment, generate and review Markdown.

Keep padded identifiers and detect missing cells. Import UTF-8 records with zeros, spaces and blank lines; recover from strict width errors using explicit padding.

Publish a table from a phone without losing the source. Choose a custom separator, inspect a paged preview, copy or request a download, undo a source replacement.

Common Mistakes to Avoid

Treating a literal separator as CSV parsing

Use the separate CSV converter when quotes enclose separators or newlines.

Assuming padding can discard extra cells

Correct extra fields or the delimiter; padding only adds missing cells.

FAQ

Not as CSV syntax. This tool treats quotes literally and splits physical lines. Use CSV to Markdown Table for quoted commas, escaped quotes or multiline fields.

No automatic cleanup. Choose trimming or blank-line skipping explicitly. A blank record can trigger a width error unless you choose padding.

Strict mode rejects them. Padding fills missing cells but never discards extra cells. With headers, the header fixes the width; without headers, explicit padding uses the widest record.

It is a presentation format. The preview shows original cells, not rendered Markdown. Numeric references keep markup literal, but destination rendering can collapse whitespace; retain the original text for exact interchange.

UTF-8 imports refuse invalid bytes. Clear, example replacement and import support one-level source undo. Copy and .md download use the current complete result; changing source or options clears it. No automatic Project save is configured.

About Text to Table

Build a documentation table from plain separated lines. Make cleanup explicit, inspect the original cells and check the exported Markdown in your destination renderer.