Free · No signup · Runs in your browser

Convert CSV to an AsciiDoc table.

Drop a CSV, get a well-formed AsciiDoc table — header row marked, pipes escaped, numeric columns right-aligned. Paste it straight into any .adoc document.

To convert CSV to AsciiDoc, drop or paste a CSV file — csvtodashboard parses it into rows and columns in your browser, then emits an AsciiDoc table. You get a pipe-delimited table inside |=== fences, ready for Asciidoctor and Antora. Nothing is uploaded; the whole conversion runs on your device.

01 · How it works

Three steps, then done.

AsciiDoc tables are clean to read but fiddly to write by hand — the |=== delimiters, the [options="header"] attribute, one cell per | line. This converter does it instantly. Numeric columns get right-aligned through the cols spec, and any pipe inside your data is escaped so it never breaks the table.

i. drop

Drop your file

Drag from Finder, click to choose, or paste data directly into the input pane.

ii. detect

We read the shape

Column types are inferred from the data, so numeric columns get right-aligned in the cols spec instead of treated as text.

iii. use it

Copy, download, or dashboard

Copy the AsciiDoc, download it as an .adoc file, or hit 'Build dashboard' to see what's actually in your data.

02 · Why ours

Tables that render the first time.

Most converters that target AsciiDoc forget the escaping and the header attribute, so your table either won't render or silently drops cells. Ours produces source Asciidoctor parses cleanly.

  • 01

    Proper escaping

    Pipes inside cells are escaped as \| so they never start a new cell. Newlines collapse to spaces, since each cell sits on its own | line.

  • 02

    Header + alignment

    The block carries [options="header"] so the first row renders as headings, and numeric columns get a right-align cols spec automatically.

  • 03

    Local-first

    Your file is parsed and converted in your browser. Nothing is uploaded; you can verify in DevTools → Network.

  • 04

    One click to dashboard

    If the table raised a question about your data, hit 'Build full dashboard' and the same CSV opens in our visualization tool.

"I pasted it straight into our Antora docs and it just rendered. No fixing pipes by hand."
— anyone who writes docs in AsciiDoc
Good to know

csv to asciidoc notes.

Format-specific details worth knowing before you convert CSV to AsciiDoc.

  • Fenced table block

    Output is an AsciiDoc table between |=== fences with one |cell entry per value, ready for Asciidoctor or Antora docs.

  • The pipe is the delimiter

    A literal pipe in your data is escaped (\|) so it doesn't start a new cell and shift the row.

  • Header row marked

    The first row is tagged as the header via the table options line, so Asciidoctor styles and repeats it correctly.

03 · FAQ

to asciidoc questions.

What AsciiDoc table syntax does it use?
Standard Asciidoctor tables: a [options="header"] attribute line, the |=== delimiters that open and close the block, and one cell per | line. This is the canonical form Asciidoctor, Antora, and GitHub's AsciiDoc renderer all understand.
The cell separator in AsciiDoc is the pipe (|), so any pipe inside your data is escaped as \| to keep it inside its cell. Newlines within a cell are collapsed to spaces because each cell occupies its own | line.
Yes — numeric columns are detected by type and get a right-align marker (>) in the cols attribute, so figures line up on the right. Text and category columns stay left-aligned (<).
Yes — set a title and we emit a leading .Title line directly above the block, which Asciidoctor renders as the table caption. Leave it blank to omit it.
No. Everything runs locally in your browser. Open DevTools → Network and you'll see zero requests when you drop a file.