HTML para PDF

This tool accepts only local HTML files that you drop into the input area or select from your device. It is a privacy-first conversion: no website is fetched by our servers, and nothing you provide touches any remote service. The entire PDF is generated inside your browser. All processing happens in your browser — nothing leaves your device. To convert a live webpage, first save it from your browser by right-clicking and choosing Save Page As, then selecting Web Page Complete. This downloads the HTML file along with a folder containing all CSS stylesheets, JavaScript files, and images. Load the saved HTML file into this tool for accurate rendering. For dynamic single-page applications built with React, Vue, or Angular where content is injected by JavaScript after page load, the saved HTML file will be empty shell markup. In those cases the most reliable option is your browser's native Print to PDF function, which captures the fully rendered DOM including all JavaScript-generated content. For static sites, documentation pages, blog posts, and plain HTML email templates, the local-file method produces excellent results. The tool handles relative file paths correctly when the HTML and its asset folder are both selected together, ensuring fonts, images, and styles load from the local disk rather than trying to fetch from the internet.

Standard CSS 2.1 and the most widely used CSS 3 features render accurately. Fonts, colors, borders, backgrounds, padding, margins, flexbox layout, and CSS grid all translate to the PDF as designed. CSS print rules including page-break-before, page-break-after, page-break-inside, and the @page rule for margin and size declarations work correctly and give you precise control over how content flows across pages. CSS animations, transitions, and JavaScript-driven visual effects are flattened to their computed static state at the moment of conversion. External fonts loaded via @font-face work reliably when the font files are referenced with a local file path or embedded as a data URL inside the CSS. Fonts loaded from a CDN like Google Fonts may fall back to the system default if the browser cannot fetch them during the offline render. To guarantee font fidelity, download the font files locally, update the @font-face src to reference local paths, and include them alongside your HTML file. CSS filter effects like blur, drop shadow, and color matrix are supported on most engines but may render slightly differently than on-screen. As a practical tip, add a print stylesheet using @media print to hide navigation bars, sidebars, and banners that you do not want in the PDF output.

Yes. A page-size selector gives you five standard formats: US Letter at 8.5 by 11 inches, US Legal at 8.5 by 14 inches, A4 at 210 by 297 millimetres, A3 at 297 by 420 millimetres, and Tabloid at 11 by 17 inches. You can toggle between portrait and landscape orientation independently of the page size. Page margins are adjustable from zero to two inches on each side, with top, bottom, left, and right settable individually. For HTML designs not originally built for a specific page size, Letter or A4 with 0.5-inch margins on all sides produces the most predictable results across printers worldwide. Letter is the standard in the United States and Canada. A4 is the global standard everywhere else. For custom print formats such as business cards, postcards, or folded brochures, you can enter a custom width and height directly in points. One inch equals 72 points. If your HTML uses the @page CSS rule with explicit size values, those values are respected and the selector here acts as a fallback default. Preview the first page before exporting the full document to confirm that your layout fits within the chosen margins without clipping content.

Yes. Text in your HTML source is converted to real PDF text objects in the output file, not rasterised to pixel images. Any PDF reader — including Adobe Acrobat, Apple Preview, Google Chrome, Microsoft Edge, and mobile PDF viewers on iOS and Android — can select, copy, highlight, and search the text. This matters for usability and accessibility. Readers can extract data from tables, copy code snippets from documentation, or search a long report for a keyword without relying on OCR. Hyperlinks in your HTML are preserved as live, clickable link annotations in the PDF. Clicking a link in the output file opens the destination URL in the reader's browser. Images embedded in the HTML are embedded at their native resolution in the PDF, so photographs and diagrams remain sharp. An optional table of contents feature scans your HTML for h1, h2, and h3 heading elements and builds an interactive bookmark panel in the PDF sidebar that mirrors the heading hierarchy. This makes long HTML documents such as technical reports, API documentation, and e-books easy to navigate in any PDF reader that displays the bookmarks panel. Enable this option in the settings panel before converting.