Turn an HTML file into a PDF document. Rendering is done by WeasyPrint on the server, a layout engine written for print rather than for the screen, which makes it fast and predictable on self-contained markup: a generated report, an exported table, an invoice built from a template. Two limits come with that engine and are worth knowing before you upload. JavaScript is never executed, so anything a script would have drawn is absent from the result. The markup also passes through a sanitiser that removes style and script elements, so a page keeping its design in a separate stylesheet arrives plain.
Converting a real web page, or markup that depends on scripts and an external stylesheet? Use the Chromium-based HTML to PDF converter on coontool.com
Style elements and linked stylesheets are removed by the sanitiser that runs before rendering, so a page that keeps its design in a separate CSS file arrives unstyled. Only a whitelist of inline style attributes survives - colour is on it, most layout and print properties are not.
Use this one when you have an HTML file that already carries its own formatting and you want the conversion over quickly. Use the one on coontool.com when fidelity matters more than speed - it drives a real browser, so scripts run, your stylesheet is applied as written and page breaks land where you asked, and it accepts a live URL as well as pasted markup.
Not at the moment. WeasyPrint itself implements the CSS paged-media rules properly, but page-break-before and break-inside are among the properties the sanitiser discards, so the content simply flows onto as many pages as it needs.
No. There is no script engine involved at any point, so a page that assembles itself from a fetch or a front-end framework converts to a blank or near-blank document. Save the finished page out of your browser and convert that, or use the Chromium-based converter on the main coontool.com site, which lets the scripts run before it captures the page.
Files are uploaded over an encrypted connection and processed on CoonTool's own server, not in your browser. The working copy is deleted automatically once the job is done, and in any case within 24 hours. Nothing is stored permanently and no account is required.