Examples

Markdown table conversion examples

Four copy-paste workflows: README, email, CLI documentation, and release notes.

Each result is generated from the same preset data used by the converter and checked against converter snapshots.

README compatibility matrix

Keep compatibility tables readable when Markdown rendering is unavailable.

Try this README example

Markdown

# Runtime support

| Runtime | Minimum | Tested |
|:---|---:|:---:|
| Node.js | 20 | Yes |
| Bun | 1.1 | Yes |
| Deno | 1.42 | Partial |

ASCII grid 

Runtime support

+---------+---------+---------+
| Runtime | Minimum | Tested  |
+---------+---------+---------+
| Node.js |      20 |   Yes   |
+---------+---------+---------+
| Bun     |     1.1 |   Yes   |
+---------+---------+---------+
| Deno    |    1.42 | Partial |
+---------+---------+---------+

Email support table

Paste a compact status table into support replies and email clients.

Try this email example

Markdown

Here is the current checklist:

| Check | Result | Notes |
|---|:---:|---|
| DNS record | Pass | A \| AAAA records verified |
| SSL certificate | Pass | Renewed automatically |
| Redirect rule | Review | Confirm final target URL |

Simple text 

Here is the current checklist:

Check            Result  Notes                    
---------------  ------  -------------------------
DNS record        Pass   A | AAAA records verified
SSL certificate   Pass   Renewed automatically    
Redirect rule    Review  Confirm final target URL

Command-line documentation

Use Unicode borders for modern terminals and developer docs.

Try this CLI example

Markdown

| Flag | Default | Description |
|---|---:|---|
| `--watch` | false | Rebuild on file changes |
| `--out` | dist | Output directory |
| `--strict` | true | Fail on invalid rows |

Unicode output 

┌──────────┬─────────┬─────────────────────────┐
│ Flag     │ Default │ Description             │
├──────────┼─────────┼─────────────────────────┤
│ --watch  │   false │ Rebuild on file changes │
├──────────┼─────────┼─────────────────────────┤
│ --out    │    dist │ Output directory        │
├──────────┼─────────┼─────────────────────────┤
│ --strict │    true │ Fail on invalid rows    │
└──────────┴─────────┴─────────────────────────┘

Release notes checklist

Share launch status with readable plain-text rows.

Try this release notes example

Markdown

# Release readiness

| Area | Owner | Status | Count |
|:---|:---:|---|---:|
| Docs | DX | ✅ Ready | 12 |
| 中文校对 | Team | Review | 3 |
| Bundle | Web | 🚀Shipped | 183 KB |

ASCII grid 

Release readiness

+----------+-------+-----------+--------+
| Area     | Owner | Status    |  Count |
+----------+-------+-----------+--------+
| Docs     |  DX   | ✅ Ready  |     12 |
+----------+-------+-----------+--------+
| 中文校对 | Team  | Review    |      3 |
+----------+-------+-----------+--------+
| Bundle   |  Web  | 🚀Shipped | 183 KB |
+----------+-------+-----------+--------+

When to choose each format

ASCII

Reliable borders for email, comments, logs, and legacy tools.

Unicode

Polished borders for modern terminals and documentation.

Simple

Compact output for narrow spaces and quick plain-text replies.