free · in-browser · no upload
Drop your HTML table file. We'll convert it to Markdown table right here in your browser, your file never leaves your device.
Select your file here to get started
or drop your file here.
Accepts .html, .htm
How it works
Click the dropzone above or drag a HTML table from your desktop. Files of any size, there's no upload, so there's no upload limit.
The conversion runs entirely in this tab using JavaScript and WebAssembly. Your file never touches our servers, we don't have any.
Get your Markdown table the moment the conversion finishes. Convert another, or close the tab.
Your file is never uploaded. The entire conversion runs in your browser using WebAssembly. We can't see what you convert because we have no server to see it.
Server converters cap free users at 1-2 GB and gate larger files behind a paid plan. Since nothing uploads, our limit is whatever your browser can handle.
No account required. No watermark on the output. No queue. Drop a file, get a converted file.
Why convert HTML Table → Markdown Table
HTML Table and Markdown Table are both ways to hold tabular data; this converts one to the other through a shared row-and-column model, so headers and every cell value carry across exactly. Use it to move a table into a README, GitHub issue, Obsidian note, or docs page. Runs in your browser, nothing is uploaded.
You have a table as HTML Table and need it as Markdown Table for a README, GitHub issue, Obsidian note, or docs page. Drop it here and get Markdown Table back in one step.
A column looks misaligned.
The converter uses the first row as headers. If your source has no header row, the first data row will be treated as headers; add one first.
Formats involved
An HTML table uses `<table>`, `<thead>`, `<tbody>`, `<tr>`, `<th>`, `<td>` elements to render tabular data in a browser. Predates CSS layouts and remains the right tool for actual tabular data (with appropriate ARIA for accessibility). Email clients still depend heavily on tables for layout because CSS support varies.
How to open
Open in any browser to render. View Source to see the markup. Email-template tools render HTML tables to email-client-safe layouts.
A Markdown table uses pipes (`|`) for column separators and a dash row for the header divider. Renders to HTML on GitHub, GitLab, every Markdown-aware static site generator, and dev tooling like MkDocs. Particularly useful when documentation lives next to code — paste data into a README.md and it renders as a real table.
How to open
Any text editor (Markdown is plain text). VS Code, Obsidian, Typora, and most Markdown editors live-preview tables. GitHub renders them automatically in commits, issues, PR descriptions.
You may also need
Related tools
FAQ
Yes. No signup, no watermark, no daily file count limit. Every conversion runs in your browser, your file never touches our servers because there are no servers.
Nowhere. The conversion runs entirely in your browser using JavaScript and WebAssembly. Your file is never uploaded to our servers. We don't have any servers handling files, there's nothing for us to log, store, or accidentally leak.
Whatever your browser can hold in memory. Practically, this means a few hundred MB on most computers, significantly larger than the 1-2 GB caps that server-upload converters charge for. Very large files (multi-GB) may require closing other browser tabs first.
Rendering tabular data in web pages and HTML emails. Embedding tabular data in Markdown docs and READMEs. The most common reason to convert is compatibility, Markdown table works in places where HTML table doesn't, or vice versa.
Open in any browser to render. View Source to see the markup. Email-template tools render HTML tables to email-client-safe layouts.
Once the page is loaded, the conversion itself runs entirely offline. The first time you use a tool, your browser downloads the conversion library (a one-time cache). If you reload while offline, the page won't load, but you can install the site as a Progressive Web App for full offline use.
Single file at a time for now. Batch conversion is on the roadmap, for now, drop one file, download the result, then convert the next.
