Markdown to ExcelConverter

Paste a Markdown table, get an Excel file. No signup, no upload — it runs right in your browser.

Free
Fast
Private

Markdown Input

Excel Preview

Your Excel preview will appear here

Start typing Markdown on the left

Why I Built This

I kept running into the same problem at work. I had tables in my README files and docs — API endpoints, config values, test results — and someone would ask me to put them in a spreadsheet. Every time, I had two options: copy-paste each cell one at a time, or go find some online converter that wanted me to create an account first.

So I built this tool. You paste your Markdown, you get an .xlsx file. That is it. No account, no upload, no server touching your data. The whole thing runs in your browser using a library called SheetJS, which builds the Excel file right on your device. Read more about the project on our About Us page.

How the conversion works

Markdown tables use pipe characters (|) for columns and dashes (-) for the header separator. The tool looks at each line, splits it by pipes, trims the whitespace, and maps it into rows and columns. If you have a heading like ## Revenue Q3 above a table, that becomes the sheet name in Excel.

Multiple tables in one document? Each gets its own sheet. The column widths auto-adjust so your data is not crammed into tiny cells when you open the file. Want to go the other way? Use the Excel to Markdown converter.

Input → Output

| Name | Sales |
|---------|--------|
| Widget | $1,200 |
| Gadget | $3,400 |
spreadsheet.xlsx
2 columns, 2 rows, auto-width

Where People Use This

Sharing GitHub data with non-dev teams

You have a table of API endpoints or database columns in your README. Your product manager needs it in a spreadsheet so they can add comments and share it with the client. Instead of typing it all out again, you paste the Markdown here and hand them the .xlsx file. Done in 10 seconds.

Moving data out of Notion or Obsidian

Both Notion and Obsidian let you copy tables as Markdown. If you need that data in Excel — say for a report or to run some numbers — just copy the Markdown table, paste it here, and download the file. No export plugins needed.

Converting docs for clients

If you write your internal docs in Markdown (which a lot of dev teams do), but your clients want Excel, this saves you the manual work. Pricing tables, feature comparison charts, test results — just convert and send. You can also try Markdown to Word if they need a .docx instead.

Quick data cleanup

Sometimes you just need to get tabular data out of a Markdown file so you can sort it, filter it, or add formulas. Converting to Excel lets you do that without writing a script. I use this myself when I have a big comparison table and want to sort by a specific column.

Markdown Table Syntax — Quick Reference

If you are new to Markdown tables, here is what you need to know. The format is pretty simple once you see it. For the full guide, check out our blog post on creating Markdown tables or the cheatsheet.

Basic table

| Product   | Price  | In Stock |
|-----------|--------|----------|
| Keyboard  | $75    | Yes      |
| Mouse     | $40    | Yes      |
| Monitor   | $350   | No       |

Column alignment (colons in the separator row)

| Left      | Center  | Right  |
|:----------|:-------:|-------:|
| aligned   | aligned | aligned|

Things that work

  • ✓ Extra spaces between pipes (they get trimmed)
  • ✓ Dollar signs, commas, special characters in cells
  • ✓ Multiple tables in one document
  • ✓ Headings above tables (they become sheet names)

Common mistakes

  • ✗ Missing pipe at the start or end of a row
  • ✗ No separator row (the one with dashes)
  • ✗ Different number of columns in different rows
  • ✗ Using a pipe inside cell data without escaping it

Markdown Tables vs Excel — When to Use What

They solve different problems. Here is a quick breakdown so you can pick the right one for your situation:

ScenarioUse MarkdownUse Excel
Version-controlled docsYes — Git diffs show exactly what changedNo — binary files do not diff well
Sorting and filtering 500+ rowsPainful — no built-in toolsYes — that is what it is for
Sharing with non-technical peopleThey will not know the syntaxYes — everyone knows Excel
Quick reference table in a READMEYes — renders right on GitHubOverkill
Charts and formulasNot possibleYes

The sweet spot: keep your data in Markdown for docs and version control, then convert to Excel when you need to do something with it. That is exactly what this tool is for. If you work with CSV or JSON instead, we have Markdown to CSV and Markdown to JSON converters too.

Troubleshooting

"No tables found" — but I pasted a table

Check that you pasted the raw Markdown, not the rendered HTML. If you copy a table from a GitHub page by selecting it visually, you get HTML. Instead, click the "Raw" button on GitHub or copy from the file source. The tool needs the pipe characters (|) to detect tables.

Columns are shifted or merged

This usually means one row has a different number of pipes than the others. Count the | characters — every row should have the same number. If your cell data contains a literal pipe character (like a shell command), escape it with a backslash: \|

Special characters look wrong in Excel

The file is saved as UTF-8 with a BOM marker, which tells Excel to use the right character encoding. If you still see garbled text, try opening the file in Google Sheets instead — it handles UTF-8 more reliably than older versions of Excel on Windows.

Common Questions

You paste a Markdown table (the kind with pipes and dashes) into the box, and the tool turns it into a real .xlsx file. Everything runs in your browser — nothing gets uploaded anywhere. The JavaScript reads your Markdown, figures out where the rows and columns are, and builds the Excel file right on your machine.
Go for it. If your Markdown has multiple tables, each one becomes its own sheet in the Excel file. If you put a heading (like ## Sales Data) above a table, that heading becomes the sheet name.
Yes. GitHub uses a format called GFM (GitHub Flavored Markdown), and this tool handles it fine. Just copy the raw Markdown from your README — not the rendered table you see on the GitHub page. The raw source is what you need. We also have a step-by-step guide if you get stuck.
Usually it is a missing pipe character at the start or end of a row, or the separator row (the one with dashes) is not there. Every row needs to look like | something | something else |, and the second row needs to be something like |---|---|. If a cell has a pipe in it, escape it with a backslash like this: \|.
There is no hard limit. Since everything runs in your browser, it depends on your device. I have tested it with tables that had 5,000+ rows and it worked fine on a regular laptop. If your browser starts to slow down, try splitting the tables into smaller chunks.
Yes. Your data never leaves your computer. There is no server processing, no upload, nothing stored. You can even disconnect from the internet after the page loads and it will still work.
Yep. We have a separate Excel to Markdown converter for that. Upload your .xlsx file and it gives you the Markdown table syntax.
Anything that uses standard Markdown table syntax — Notion, Obsidian, Typora, Bear, VS Code, and pretty much any text editor. If your app has an "export as Markdown" option, the tables should work here.