Paste one or more Markdown tables, preview the parsed rows and columns, then copy TSV for Excel or Google Sheets, copy CSV, or download CSV and .xlsx files.
Convert content to see the table preview.
Markdown table to Excel, locally
Use this Markdown Table to Excel converter when your data already lives in a readable text table but someone needs a spreadsheet file. Paste a table with a header and separator row, check the structure, convert it in your browser, and download amarkdown-table.xlsx workbook. Each detected table becomes its own worksheet, and no account or upload is required.
Every row must have the same number of columns, and the second row must be a valid Markdown separator. The converter creates a worksheet from the table values so a reviewer can sort, filter, or continue editing them in Excel.
Move a README table, project register, comparison list, or small data extract into a spreadsheet without retyping each cell. The output is a practical starting workbook, not a recreation of a branded spreadsheet template.
Check column counts, header names, escaped pipe characters, and empty cells before you convert. Rich Markdown styling, merged cells, formulas, and charts are outside this route's verified boundary. Multiple Markdown tables are supported and become separate worksheets. For the reverse workflow, use Excel to Markdown Table.
A basic table has a header row, a separator row, and one or more data rows. Use pipe characters to separate cells and at least three hyphens in each separator cell. For example, a header such as | Name | Status | should be followed by | --- | --- | before the values begin.
Keep the number of cells consistent from row to row. A missing trailing pipe is acceptable, but a row with an extra unescaped pipe changes the number of cells and causes validation to fail. If a value itself contains a pipe, escape it as \| so it remains part of the cell text.
Use concise column names and avoid putting an entire paragraph into one cell. The workbook will contain the text values exactly as table data; it will not infer a date type, calculate a formula, or decide whether a number should be currency. Review those decisions in Excel after export.
The converter creates a new Excel workbook. A single detected table uses a worksheet named Table; multiple tables use Table 1, Table 2, and so on. Each header becomes the first worksheet row, while its separator row is used for validation and is not exported as data.
The generated file is a standard XLSX download named markdown-table.xlsx. It is suitable for opening in Microsoft Excel, LibreOffice Calc, Google Sheets import, and other applications that read the XLSX format. Each application may apply its own default column widths, fonts, and display behavior.
The output is intentionally simple. It does not add a branded title, freeze panes, filters, formulas, conditional formatting, or charts. It does create additional worksheets when the source contains additional Markdown tables. Add presentation and analysis features in the destination application when needed.
Engineering teams often keep small inventories, compatibility matrices, release checklists, and configuration summaries in Markdown. An XLSX handoff gives a non-technical reviewer a familiar grid for sorting rows, adding comments, or preparing a meeting view while the Markdown remains the readable source.
Product and operations teams can move a decision table, action register, project status list, or vendor comparison into Excel without manually recreating every row. Before sharing the workbook, confirm that labels, ownership fields, dates, and empty values mean what the recipient expects.
Educators, researchers, and analysts can use the route for a small sample dataset or a documentation table. It is not a data-import pipeline or validation service. Check units, decimal conventions, identifiers, and privacy classifications in Excel, especially when the source table was written for human reading rather than machine analysis.
Markdown emphasis, links, blockquotes, headings, and code styling are not converted into rich spreadsheet formatting because this route accepts a table structure rather than a full Markdown document. Cell text is placed into a worksheet so you can apply the formatting that fits your spreadsheet workflow.
There is no support for merged cells, nested tables, formulas, charts, images, comments, hidden rows, or a source workbook theme. Separate top-level Markdown tables can become separate tabs, but visual spacing cannot imply a layout. Rewrite such layouts as explicit columns or finish the design manually after download.
Column alignment markers in the separator row communicate Markdown intent but do not create a guaranteed Excel alignment style. Similarly, a number that looks numeric may arrive as text depending on its source representation. Confirm sorting and calculations with representative rows before relying on the workbook.
Open the downloaded workbook and inspect the header row, first data row, longest values, and any cells containing punctuation. Adjust column widths so important content is visible, then apply number, date, or currency formats deliberately. Do not assume that a visually tidy Markdown table has enough metadata for spreadsheet calculations.
Check that row order and spelling match the source. If the table is used for a handoff, add a source note or revision date in the spreadsheet according to your team's process. Keep the original Markdown beside the workbook so a reviewer can trace where the values came from.
For a longer table, test filters and sorting on a copy before making edits. If one row appears shifted, return to the Markdown source and inspect unescaped pipes, missing cells, or accidental line breaks. Fixing the source is safer than patching many cells after export.
The most common error is a missing or malformed separator row. Ensure the second non-empty line contains hyphens and optional colon alignment markers. A header alone is not enough; the converter needs the separator to distinguish a Markdown table from ordinary text.
If the message says rows have different column counts, count the pipes after removing an optional first and last pipe. Escape literal pipe characters inside a cell and remove stray pipes from prose. Empty cells are allowed when the separators still describe the intended columns.
Use the Example button to confirm the route, then add your table rows gradually. The file stays local, so you can test a reduced non-sensitive sample without sending the source elsewhere. Keep a copy of the original table before making validation edits.
The table is parsed in the current browser session and the XLSX bytes are generated locally. This route has no account requirement and no document upload endpoint. That is useful for internal lists, planning data, or drafts that should not be submitted to an unknown spreadsheet conversion service.
Local processing does not control browser extensions, downloads, backups, synchronization, screenshots, or operating-system search. A generated workbook may appear in a recent-file list or synced folder. Follow your organization's approved storage and retention rules when the table contains confidential information.
Keep the Markdown source in your own repository or file system. The converter does not provide recovery, revision history, access control, or a shared collaboration space. For the reverse direction, use Excel to Markdown Table and review which spreadsheet details can become plain table text.
Use the generated workbook when the recipient needs spreadsheet editing, sorting, or a familiar grid. If the information belongs in a README or documentation page, keep it as Markdown or use Markdown to HTML for a web handoff. If you need a fixed document for printing, the Markdown to PDF converter is a better fit.
When a workbook becomes the maintained source, establish clear ownership and define how updates flow back to the Markdown table. Repeated manual edits in both formats can create conflicting values. Pick one authoritative source and regenerate or reconcile the other on a predictable schedule.
Consult the privacy policy for the current boundary. A successful XLSX download confirms that a workbook was created; it does not certify formulas, business rules, data quality, accessibility, or compliance requirements that belong to your final spreadsheet workflow.
For recurring reports, document the table's column definitions and decide which values are required. A stable header makes future exports easier to compare, while a short source note tells spreadsheet users where the data came from and when it was prepared.
Keep formatting decisions in the workbook workflow rather than encoding them with spaces in Markdown. Use explicit status values, consistent date notation, and one meaning per column. This improves sorting and reduces cleanup when a table is exported more than once.
When the table feeds another system, treat the XLSX as a handoff artifact and verify it with a representative import. Confirm that the receiving application reads the header row and cell values as expected before automating any follow-up step.
