HTML converter

HTML is the document format of the web, defined as a parsed tree of elements, attributes, text, links, embedded resources, and browser behavior. A saved .html file may be a clean article, an exported report, a full application shell, an email body, or a table copied from a dashboard. Conversion begins by deciding whether the HTML is a document or a data table. Our routes use Pandoc for document conversions such as HTML to DOCX, ODT, RTF, LaTeX, reStructuredText, EPUB, Markdown, TXT, and PDF, while tabular routes handle HTML tables to CSV, TSV, JSON, XLSX, ODS, SQL, Parquet, XML, YAML, Markdown, and TXT.

Version labels are less useful than parser behavior. Modern HTML follows the WHATWG living standard, while old pages may carry HTML4 or XHTML doctype strings. Browsers repair invalid markup, close missing tags, and build a DOM even when source HTML is messy. Character encoding may come from a meta tag, HTTP header, or default guess. CSS controls layout but is separate from document structure. JavaScript can create content after load, but a static converter only sees submitted markup unless the page has already been rendered and saved. External images, fonts, stylesheets, iframes, and scripts may be unavailable during conversion.

Readers and writers include browsers, CMS systems, email clients, static-site generators, documentation tools, reporting libraries, notebooks, office suites, and web scrapers. Each produces different HTML. A documentation page may use semantic headings and code blocks that convert well to Markdown. A marketing page may depend on CSS grid, background images, and client-side components that do not map to DOCX. An exported table may be perfect for CSV, while a layout table should remain part of a document conversion. Inspect the source for real heading tags, table elements, link hrefs, and local asset references before choosing a target.

HTML conversion breaks when presentation is mistaken for content. CSS positioning, responsive layouts, hover states, scripts, forms, and interactive widgets do not become editable Word features. HTML to PDF typesets a static page view and may not match a specific browser screenshot. HTML to Markdown keeps headings, lists, links, code, and simple tables, but custom components become plain blocks or disappear. HTML to CSV only extracts table data. Before conversion, inline or preserve important assets, remove navigation that should not enter the document, choose whether links remain absolute, and test one page with tables, images, and code blocks.

Official HTML specification