Before
<nav>Products | Pricing</nav> <article><h1>Migration guide</h1><p>Export the pages.</p></article> <footer>Cookie settings</footer>
Readable Markdown for documents, PDFs, spreadsheets, HTML, and knowledge-base workflows.
support@mdforall.com
Markdown converter
Convert HTML to Markdown
Markdown For All converts static HTML files into cleaner Markdown for documentation migration, publishing, and content cleanup. It works best when the article or documentation text is present in the source HTML. Scripts, styles, navigation, cookie banners, and other page chrome should not become the document. Review relative links, image paths, code blocks, tables, and pages whose content is rendered only by JavaScript.
Can the useful content be found in the HTML source?
Choose the source and workflow before uploading. Markdown is strongest when it represents durable reading structure rather than exact visual layout or executable application logic.
| Source situation | Recommended decision |
|---|---|
| Static article, documentation page, or help-center export | Good fit when headings, paragraphs, lists, links, and code are present in the source. |
| Saved page with navigation and banners | Convert, then remove repeated shell content and verify the main article boundary. |
| React/Vue/SPA shell without rendered content | Not a good source. Export rendered HTML or use the original CMS/API content. |
| Authenticated or personalized page | Use an approved export and review privacy, permissions, and embedded identifiers. |
Semantic HTML that maps well and web-page behavior that does not
| Source feature | What may carry into Markdown | What to review |
|---|---|---|
| Headings and paragraphs | h1–h6 and readable text | CSS-only visual hierarchy |
| Lists and links | ul/ol and anchor text | JavaScript navigation and inaccessible click handlers |
| Code and quotes | pre/code and blockquote | Interactive widgets and syntax behavior |
| Images and tables | Paths, alt text, simple grids | Responsive layout, lazy-loaded assets, complex table spans |
Separate the article from the website shell
These visible preparation steps are also represented in the page HowTo schema. They reduce avoidable conversion errors but do not replace source comparison.
Step 1
Inspect view source
Confirm the useful text exists in the HTML rather than arriving only after JavaScript runs.
Step 2
Identify the main region
Keep article or main content; exclude navigation, footer, cookie banner, related widgets, and ads.
Step 3
Normalize semantic elements
Use proper headings, lists, links, code, quotes, and simple tables.
Step 4
Repair destinations
Resolve relative links and image paths against the final publishing location.
Evidence example: remove page chrome and keep the article
After Markdown
# Migration guide Export the pages.
What to review
Check that navigation, cookie text, and footer links were excluded; repair relative URLs and verify code blocks, image alt text, and table headers.
When another HTML workflow is required
- • Use a browser or CMS export when the source HTML contains only an application shell.
- • Use the original CMS/API data when metadata, authorship, publication dates, or structured fields are important.
- • Keep interactive examples, forms, widgets, and dynamic behavior in web-native documentation.
- • Use a private workflow for authenticated pages, customer portals, internal dashboards, or embedded secrets.
HTML field notes: DOM boundaries, URLs, and rendered content
Source HTML and rendered DOM can differ
A saved HTML file may contain the full article, or it may contain only an application shell that JavaScript fills after network requests. `view-source` reveals what the converter can read directly. If the article exists only in the rendered DOM, export the rendered page or use the CMS/API source.
Main-content selection is editorial
Semantic elements such as `<main>` and `<article>` help, but many sites use generic `<div>` containers. Navigation, related links, cookie banners, newsletter prompts, comments, and footer text can be mixed with the article. Identify the content boundary based on the publishing task, not only tag names.
Relative URLs need a base
Links such as `../guide` and images such as `/assets/diagram.png` depend on the original origin and directory. A `<base>` element can change resolution. Before publishing Markdown elsewhere, convert relative destinations to stable absolute or repository-relative paths and verify every target.
Lazy loading and interactive examples
Images may use `data-src`, `srcset`, or JavaScript loaders. Code playgrounds, tabs, accordions, and API explorers may hide content in scripts or network responses. Capture the canonical text and code examples explicitly instead of expecting an interactive widget to become portable Markdown.
Downloadable HTML regression sample
Compare article content with navigation, scripts, and footer noise
The public HTML sample contains a main article plus navigation, CSS, a footer, and JavaScript. The linked Markdown is the output observed from the current release and keeps the article heading, paragraph, and checklist while excluding the surrounding shell.
Observed result and what it proves
Semantic main content can be separated from presentation and behavior in a static document. Relative links, image URLs, lazy-loaded media, and content created only after JavaScript runs still require separate handling.
Failure case: JavaScript application shell
If view-source contains only an empty root element and script bundles, the useful content is created after JavaScript runs. Export rendered HTML, use the application’s content API, or obtain the original documentation source instead of converting the shell.
Public samples are low-risk regression fixtures. The observed output was generated by release 2026-07-17-adsense-r9 and still requires comparison with the source.
Questions users ask before relying on this output
Will scripts and CSS be kept?
No. Markdown preserves content structure, not scripts, styles, layout, or application behavior.
Can I convert a React or Vue app screen?
Only if the meaningful content is present in the provided HTML. A JavaScript shell without rendered text is not enough.
What happens to relative links?
They may remain relative and break at the new destination. Resolve them against the original or target base URL.
Are images downloaded?
The converter may preserve references or alt text, but it does not guarantee that remote assets remain available.
Can complex HTML tables convert cleanly?
Simple grids work best. Row spans, column spans, nested tables, and responsive layouts need manual redesign.
How do I remove navigation and cookie banners?
Identify the main article region before conversion or remove repeated shell content during cleanup.
Continue with the right review workflow
These links are selected for this format rather than generated as a generic related-content list.
Version and review notes
Last reviewed July 17, 2026. This page documents the public converter behavior for release 2026-07-17-adsense-r9. Changes in format support, file handling, or known limits are recorded in the public changelog.