Guide
Publishing a PDF as a real web page
Many “PDF to HTML” converters copy the page exactly, placing every line of text in an absolutely positioned box. The result looks like the PDF on a desktop screen and falls apart everywhere else: it doesn’t reflow on phones, screen readers struggle with it, and it is painful to edit. This tool does the opposite. It recovers the document’s structure and writes simple, semantic HTML that adapts to any screen.
What the HTML looks like
The output is a complete, valid page:
- a
<title>taken from the file name and a viewport tag for phones, - headings as
<h1>to<h4>, recognised from font size and weight, - paragraphs as
<p>, with lines and hyphenated words joined back together, - bulleted and numbered lists as
<ul>and<ol>.
There are no scripts, no tracking code and no external files. All text is escaped, so characters like < and & from the PDF can’t break the page.
With or without styling
Include a simple readable stylesheet adds a few lines of CSS: a comfortable reading width, your visitor’s system font, generous line height and a dark color scheme for devices set to dark mode. Use it for a standalone page you upload as it is.
Turn it off when the content goes into an existing website. Pasting the bare headings and paragraphs into WordPress, Ghost, Webflow or a static site lets your own theme style them.
Page anchors
Documents are often cited by page: “see page 12 of the annual report”. Add page anchors places an invisible marker where each original page started, so report.html#page-12 jumps to that point. It costs nothing visually.
Why a web page beats a PDF on your website
- Phones: text reflows to the screen instead of requiring pinch and zoom.
- Search: the page can have its own title, description and internal links, and it loads faster.
- Accessibility: real headings and lists give screen-reader users a map of the document.
- Updates: fixing a typo means editing text, not re-exporting a PDF.
Keep the PDF as a download link for people who want to print.
What to check after converting
Headings are inferred, so glance at the heading levels in the preview. Tables arrive as lines of text; rebuild important ones as HTML tables or extract them with PDF to CSV. Images are not included; save them with Extract PDF Images and add them to the page. Scanned PDFs need OCR PDF first.
A worked example: a policy page
- Open the 8-page privacy policy PDF.
- Turn off the stylesheet and keep running-header removal on.
- Copy the body from the source view into the CMS.
- Add a link to the original PDF at the bottom of the page.
For Markdown instead of HTML, see PDF to Markdown. To go from HTML to PDF, use HTML to PDF.
Turning the HTML into a full web page
The generated file is a starting point. Before publishing, give the page a meta description, add links to related pages on your site, and replace any heading levels that came out wrong (a document title that became an <h2>, for example). If the original had a table of contents page, remove it: the headings already provide the structure, and your site’s navigation does the rest. Finally, link to the original PDF for readers who want to print it, and check the page on a phone.
Checked against the current version of the PDF to HTML on .