PDF to HTML
PDF to HTML is for a readable local copy you can open in any browser. It is not a pixel-perfect clone of print CSS. Scanned pages need pictures or an OCR text layer.
Privacy and offline checks
Document processing runs locally in supported PDFForge workflows. This panel is a diagnostic view; it cannot prove that no data left the device.
Observed resource activity
0 observations in this page session · 0 need inspection
Resource timing is unavailable in this browser. Use the independent checks below.
Page timing and the active service worker report different surfaces and may observe the same request. Worker activity can be incomplete; WebSockets, request bodies and extensions are outside this view. The latest 60 sanitized observations stay in memory only. URLs, filenames, query strings, document content and byte counts are not recorded here.
Verify independently in DevTools
- Use a clean browser profile and synthetic documents. Open Network in DevTools and enable Preserve log.
- Prepare offline below. Switch Network to Offline, then reload the saved workspace and select a new file.
- Inspect, redact, run output checks and download. Inspect failed requests and request payloads, including worker requests. A same-site request can still transmit data.
- Inspect Application or Storage. Cache Storage should contain public app assets and setup records only. Document recovery and content telemetry are disabled; recipe settings are saved only after opt-in.
Offline readiness
Full workspace not prepared for offline use
English OCR not prepared for offline use
Prepare while connected to save the workspace, tools, fonts and workers. English OCR is optional. Only public app assets are saved; documents, outputs and passwords are excluded. Browser storage can be cleared or evicted. Check saved assets before disconnecting and prepare again after an app update.
Checking saved app assets…
Open saved workspaceReady for local work · One heavy job at a time in this tab
Drop your PDF file here, or browse
Supports standard PDF documents • Up to 100 MB
Private by design. Document processing runs in this browser. PDFForge has no document upload API.
How it works
How PDF to HTML works
PDF to HTML is for a readable local copy you can open in any browser. It is not a pixel-perfect clone of print CSS. Scanned pages need pictures or an OCR text layer.
Guided steps
How to use PDF to HTML
- 1Choose a PDF from your device.
- 2Select pages and optionally include page pictures.
- 3Convert locally.
- 4Download the HTML file and open it from disk.
In this tab
What stays in this browser
The file stays in this tab.
- What this tool reads
- Headings, paragraphs, and simple tables from the text layer, plus page pictures when that option is on. Empty pages can use on-device English OCR when that option is on.
- What the download contains
- An HTML file.
Questions
PDF to HTML FAQs
Does the HTML call a CDN?
No. The file is self-contained. Page pictures, if included, are embedded as data URLs and can make the file large.
Will links and forms work?
Text links that appear in the PDF text layer are not automatically turned into HTML anchors. Forms stay as visible text if they were in the text layer.
Is JavaScript added to the download?
No. The export is static HTML and CSS only.
Continue locally
Related tools
Stay in the browser with these nearby PDFForge tools.