HTML to PDF

No. Scripts are disabled for safety when rendering your HTML — only the visual layout, styles, and images are captured.

Your HTML is rendered at a fixed page width, then automatically sliced into multiple pages based on its total height. The slicer prefers to break between elements rather than through the middle of a paragraph or image, though very long unbroken blocks of content may still be split across a page boundary.

Only if they're embedded directly in the HTML (inline <style>, inline <img> data URIs) or referenced by a full absolute URL. Relative paths like styles.css or images/photo.png point to files on your computer that this tool has no access to, so they won't load — you'll see unstyled or broken-image output in that case.

No. The output PDF is image-based — each page is a picture of your rendered HTML, so text can't be selected, searched, or copied from the resulting file.

Yes, completely free. No sign-up, no limits, no hidden charges.

Your content never leaves your device for processing. Note that images, fonts, or stylesheets your HTML references by URL will still be fetched over the network as your browser normally would, even though embedded scripts don't run. Use the "Block external resources" option if you'd rather avoid that for HTML from a source you don't fully trust.

Yes, though rendering complex pages may be faster on a desktop or laptop.