Why convert HTML to Markdown?
HTML is the browser's format, not always the best source format for editing. It carries tags, classes, inline styles, scripts and tracking code that make a page noisy in a notes app or Git review. If your goal is to archive the text, migrate a static site, or bring web pages into Obsidian, Bear or Logseq, Markdown is easier to search, diff and maintain.
Converting HTML to Markdown keeps the durable structure: headings, paragraphs, links, images, lists, tables and code blocks. A folder of old help-center pages becomes a set of plain text files that can be reviewed in a pull request or indexed by a local knowledge base. You are no longer tied to the original CMS theme just to keep the article content readable.
File Converter Pro performs that cleanup offline on Windows. Downloaded pages, exported CMS archives and internal web docs stay on your machine. There is no upload step, no size limit and no watermark, which is useful when the HTML contains customer examples, private URLs or draft documentation.
How to convert HTML to Markdown on Windows
- Install File Converter Pro. Install from the Microsoft Store on Windows 10 or 11 and use the free trial to test your own HTML exports.
- Add HTML pages. Drag a single .html file, a folder from a downloaded site, or an archive exported from a CMS into the queue.
- Pick Markdown. Choose CommonMark or GitHub-flavored Markdown, select how tables should be written, enable code-fence language detection, and decide whether images should be linked, copied or skipped.
- Run the conversion. Save the Markdown files locally, then open them in your note app, static-site project or code editor for review.
Batch conversion for site migrations
A migration rarely starts with one page. It starts with a folder from wget, a CMS export, or an archive of old product documentation. File Converter Pro can process the folder as a batch, so every HTML file follows the same table, link and image rules.
- Convert nested folders while keeping the original directory layout.
- Rewrite relative links so pages still point to each other after conversion.
- Copy referenced images into a Markdown-friendly assets folder.
- Skip navigation-heavy pages and keep only article-like files when cleaning archives.
Quality settings for readable Markdown
The best output depends on where the Markdown will live. Obsidian notes usually benefit from simple wiki-style content and copied images. A Docusaurus migration may need GFM tables, fenced code blocks and relative paths that match a repository. An archive might keep some raw HTML to avoid losing complex tables.
- Flavor. Pick CommonMark for portability or GFM for GitHub-compatible tables and task lists.
- Table style. Convert simple tables to Markdown, or preserve complex tables as raw HTML.
- Code-fence language detection. Use class names like language-js to label fenced blocks automatically.
- Link conversion. Keep absolute URLs, rewrite local links, or convert links to note-app-friendly relative paths.
- Image handling. Copy images, link existing assets, embed references, or skip decorative files.
Common issues and fixes
- The output includes too much navigation. Convert the article container when possible, or remove header and footer HTML from the source export before running the batch.
- Code blocks lose syntax labels. Enable language detection and check whether the source uses class names such as language-python, brush:js or code-lang-json.
- Images point to old web URLs. Choose copy image handling so referenced files are saved locally beside the Markdown.
Related conversions
FAQ
Do tables and code blocks survive HTML to Markdown conversion?
Simple HTML tables can be written as Markdown tables or kept as raw HTML when Markdown cannot represent the layout cleanly. Preformatted code blocks are converted to fenced code blocks, and language classes can be used to set the fence label.
Are inline styles preserved or stripped?
By default, visual styles are stripped because Markdown should carry structure rather than CSS. You can keep selected raw HTML where a note app or static-site engine needs details that plain Markdown cannot express.
Can I bulk-convert a downloaded HTML site?
Yes. Save the site or export the HTML folder locally, drop it into File Converter Pro, and convert the pages in one batch. Folder structure and relative links can be preserved for review.
What happens to embedded scripts and style blocks?
Script tags, tracking snippets and style blocks are normally removed so the Markdown is safe and readable. If you need to archive the original source, keep a copy of the HTML beside the converted Markdown.
Ready to clean HTML into Markdown?
Download File Converter Pro, add your HTML archive or site export, and create Markdown that is easier to edit, diff and search. The conversion runs offline on Windows, so private pages and internal links remain on your own machine.