Should this be a JPEG at all?

For photographs and smooth gradients, yes - JPEG is much smaller at the same perceived quality. For flat colour, screenshots and small text it is the wrong choice: the artifacts land exactly on the hard edges. Use the PNG tool for those.

Can I get a transparent background?

Not in JPEG - the format has no alpha channel, so transparency is flattened. The PNG tool keeps it.

What does quality actually change?

How aggressively the encoder discards detail. It changes the file, never the layout: the same markup at quality 60 and 95 has identical dimensions and identical line breaks.

Is the image watermarked?

No. The file you get here is byte-for-byte what the API returns for the same parameters.

Free tool

HTML to JPG

Paste HTML, get a JPEG — and pick the quality, because that is the whole trade JPEG asks you to make.

A JPEG rendered by Chromium at the width and quality you pick, as tall as your markup.

Capture settings

Enter the source, choose your options, then run the capture.

Result

Your capture will appear here and stay in view.

waiting

No result yet

Complete the settings and run the tool. Images, PDFs, text, and video all preview in this panel.

Send this exact request

cURL, TypeScript and Python are generated from the same configuration as the demo.

curl --fail-with-body "https://api.pagecapture.dev/v1/take" \
  -H "X-Access-Key: $PAGECAPTURE_KEY" \
  -H "Content-Type: application/json" \
  --data '{"html":"<section style=\"width:1200px;padding:96px;font:500 44px/1.32 Georgia,serif;color:#f7f4ee;background:radial-gradient(120% 140% at 10% 0%,#7a4b2a,#1d1206)\">\"We shipped the report generator in an afternoon.\"<p style=\"margin:36px 0 0;font:600 20px/1.4 system-ui,sans-serif;letter-spacing:.14em;opacity:.7\">MAYA - PLATFORM LEAD</p></section>","viewport_width":"1200","image_quality":"80","format":"jpg","full_page":true,"viewport_height":100}' \
  -o capture.jpg

Questions

Should this be a JPEG at all?: For photographs and smooth gradients, yes - JPEG is much smaller at the same perceived quality. For flat colour, screenshots and small text it is the wrong choice: the artifacts land exactly on the hard edges. Use the PNG tool for those.
Can I get a transparent background?: Not in JPEG - the format has no alpha channel, so transparency is flattened. The PNG tool keeps it.
What does quality actually change?: How aggressively the encoder discards detail. It changes the file, never the layout: the same markup at quality 60 and 95 has identical dimensions and identical line breaks.
Is the image watermarked?: No. The file you get here is byte-for-byte what the API returns for the same parameters.

Need this in your own code?

This tool is one call to the PageCapture API. The free plan gives you 100 captures a month with every feature unlocked, and no card.

Get an API key See the docs

Guides that cover this in depth

choose PNG or JPEG for a generated image
PNG or JPEG when your application generates the image
Text picks up a halo of grey speckle at the edges of glyphs, or a 1200x630 card leaves the renderer as a multi-megabyte PNG that a CDN then serves on every page view.

Doing this in your app

HTML to image

Render your own HTML into an image

Skip hosting a page. Send the markup and get the rendered result, with your own fonts and CSS.

Questions

Need this in your own code?

Guides that cover this in depth

Doing this in your app

Related tools