No processing of your file contents takes place on any server. You need no data-processing agreement with gottrix to handle confidential or business documents.
Servers in GermanyGDPR by design
Origin servers at Hetzner in Germany. Since your files never leave your device, their contents are not transmitted at all.
Got a saved HTML page and need its content as a PDF? This tool removes the HTML tags and lays the readable text - headings, paragraphs and lists - into a clean PDF.
Important and honest: this is not a browser render. CSS, JavaScript, images and the exact page layout are not reproduced. It is about the text content, loosely structured by headings, paragraphs and bullet lists.
Everything happens locally in the browser, with no upload. It is not meant for formatted reports with images - that would need a full render engine (250+ MB) that is not viable on mobile.
The tool fits simple inputs best: a saved article, a plain invoice, an email in HTML format or a docs page where only the body text is needed. If a page must keep its exact pixel appearance, your browser's print dialog (“Save as PDF”) is the better choice - it uses the same engine that renders the page. This tool instead produces a lightweight, searchable text version with no external dependencies.
Specifications
Specifications
Input formats
HTML, HTM
Output format
PDF
Batch processing
No
Processing
Locally in your browser (JavaScript)
File upload
None
In 3 steps
Drop an HTML file.
Pick page size and font size.
Download the text PDF.
Limitations:No browser rendering: CSS, JavaScript, images and the exact layout are dropped. The text content (headings, paragraphs, lists) is kept. Standard Helvetica font; non-Latin characters are replaced with “?”.
FAQ
Is the file uploaded?
No, everything happens entirely locally in the browser.
Does the PDF look like the web page?
No. It is not a browser render - CSS, JavaScript and images are not reproduced, only the text content.
What is carried over?
The text, loosely structured by headings, paragraphs and bullet lists.
Why no pixel-perfect layout?
That would need a full browser engine (250+ MB), not viable on mobile - and against the lean, local approach.