Two ways to turn HTML into a picture
Sometimes you need a webpage as an image — to attach to a bug report, to embed in a slide deck, to share an inline preview on Twitter, or to generate a social-share card for an article. This tool gives you two paths to that result: paste a URL and let our screenshot API capture the live page, or paste HTML+CSS and have the browser render it locally.
URL mode (server-powered)
Drop any public http(s):// URL and click Convert. The request is forwarded to the Screenshotone API with your viewport width, pixel scale and capture mode (viewport vs full-page). Ads, cookie banners and tracking scripts are blocked by default so the captured page looks clean. Some sites refuse the capture — busy single-page apps, authenticated dashboards, sites with strict CSP/X-Frame-Options — and the error message will tell you when that happens.
HTML mode (browser-side, fully private)
Paste any HTML and inline CSS into the textarea and the tool renders it inside a sandboxed iframe, then captures the result with html2canvas. Because everything runs locally, your code never leaves the browser — perfect for confidential internal layouts, in-progress design mockups, or anything you wouldn't want sent through a third-party service.
Self-contained markup with inline CSS works best. External fonts and images need CORS-enabled hosts to render correctly; resources from private servers that don't set the right headers will be silently skipped. Tailwind utility classes won't apply unless you also paste a <style>block with the actual rules; the browser doesn't know about your framework.
Picking the right pixel scale
Set the pixel scale to 1× for standard-resolution output (good for fast previews and lightweight files), 2×for retina-quality screenshots you'll embed on a website or in a deck, and 3× when you need the highest fidelity — typically for print or large monitors. Higher scales produce much bigger files: 3× is roughly nine times the bytes of 1×, since file size grows with the square of the pixel-density multiplier.
Format quick guide
- PNG — lossless, supports transparency. The default.
- JPG — smaller, lossy, white background. Best for photo-heavy pages.
- WEBP — smaller than JPG at the same visual quality. Universally supported on modern browsers.
- SVG — vector wrapper around the raster output. Useful when a downstream tool insists on an SVG file.