SQL to Markdown Table Converter

Paste your SQL query output, get a Markdown table. Works with MySQL, PostgreSQL, SQLite -- any pipe or tab-separated result.

100% Free
Privacy-First
Instant Conversion

SQL Output Input

Markdown Output

Markdown output will appear here

Paste SQL output on the left to see conversion

From Terminal Output to Documentation

Query Results That Look Good in READMEs

You ran a SELECT query and now you want to include the results in your docs. Manually converting those pipe-separated rows into Markdown is annoying work. Paste your terminal output here and get a properly formatted Markdown table in one step. I use this constantly for database documentation and architecture decision records. For API data instead of SQL output, try the JSON to Markdown converter.

Safe for Production Data

Your query results might have customer names, order amounts, or internal metrics. All the processing happens in your browser. Nothing gets sent to a server. You can safely paste production query output without worrying about data leaks.

Works with Any SQL Client

MySQL CLI, psql, sqlite3, MySQL Workbench, pgAdmin, DBeaver, DataGrip -- if it outputs text with pipes or tabs between columns, this tool can parse it. Divider rows get stripped automatically. You can also convert to other formats with CSV to Markdown or export to spreadsheets with JSON to Excel.

Situations Where This Helps

Documenting Table Schemas

Run DESCRIBE on your table or query information_schema, copy the output, and paste it here. Now you've got a Markdown table showing column names, types, and constraints that you can put straight into your project's docs or wiki.

Writing Runbooks

On-call runbooks need example outputs from health check queries. Run the query, convert the output to Markdown, and include it in your runbook. When someone at 3am is following the playbook, they'll know exactly what "healthy" output looks like.

Pull Request Descriptions

Reviewing a migration script? Include a "before" and "after" Markdown table in your PR description showing what the query returns. Reviewers can see the expected output without running the query themselves. Saves a round of back-and-forth.

Writing Database Tutorials

If you write about SQL -- blog posts, tutorials, Stack Overflow answers -- you need to show query results. Run the query, paste the output here, and get a Markdown table that renders nicely on any platform. Looks way better than a code block with fixed-width text.

Frequently Asked Questions

It takes the text output you get from running a SELECT query in your terminal (MySQL, PostgreSQL, SQLite, or any SQL client) and turns it into a Markdown table. You know those pipe-separated or tab-separated results you see in the CLI? Paste that here and you get a clean Markdown table you can drop into a README or wiki page.
Two main formats: pipe-separated output (the +----+----+ style from MySQL and PostgreSQL CLIs, where columns are separated by | characters) and tab-separated output (what SQLite and some other clients produce). The tool auto-detects which one you've pasted based on whether the first line has tabs or pipes.
Run your query in your SQL client, select the output text from the terminal, copy it, and paste it here. The tool strips out the divider rows (those +---+---+ lines), extracts the header and data rows, and builds a Markdown table. Click Copy to grab it for your docs, or Download to save it as a .md file.
Nope, leave them in. The converter automatically filters out rows made of plus signs, dashes, and pipes. You can paste the raw output exactly as it appears in your terminal. If some rows are missing or extra, that's fine too -- the tool handles messy input.
Yes. When you copy results from the grid view in MySQL Workbench, pgAdmin, DBeaver, or DataGrip, the text usually comes out tab-separated or pipe-separated. Paste that directly and it'll work. The key is to copy the text representation of the results, not just the visual grid selection.
One query result at a time works best. Each result set needs its own header row, so combining multiple results in one paste can confuse the parser. Just paste one, copy the Markdown output, then paste the next one.
However your SQL client displays NULLs is how they'll appear in the Markdown table. If your client shows the text NULL, you'll see NULL in the table cell. If it shows an empty string for NULLs, you'll get an empty cell. The tool doesn't interpret or change the values.
100%. Everything runs in your browser. Your SQL output -- which might include customer data, financial records, or internal metrics -- never leaves your device. No server, no logging, no tracking.
Yep, completely free. Also check out JSON to Markdown, CSV to Markdown, TSV to Markdown, and Markdown to Excel for other formats.