PDF to PNG — a page capture you can attach to a ticket or a slide
Sometimes you do not need the document, you need one page of it as a picture: a screenshot for a support ticket, a page pasted into a slide, a thumbnail filed next to an invoice. This route takes a PDF you drop into the studio, executes the page you selected onto a canvas in the same tab, and hands back a PNG. The two decisions you make are which page and how large the pixel grid should be; everything else follows from the page's own measurements.
The page is flattened to pixels: selectable text, links and form fields become part of the picture and are no longer separate.
Processed on your device. Files aren’t sent anywhere.
Walking the capture from page to file
There is no upload step and no server queue. The file is read in the tab, the page you named is drawn onto a canvas, and only then does the browser encode that canvas as PNG bytes you can download.
- Drop a single PDF, up to 20 MiB. A document above 40 pages is rejected outright rather than quietly cut down.
- Choose the page with the page-number slider (pages 1 through 40), or switch to Every page.
- Pick a render scale: 1x, 2x or 3x. The default is 2x.
- The page is drawn onto a canvas at that scale, so text, rules, logos and embedded pictures all land on one pixel grid.
- The canvas is encoded as PNG and offered as a file named after the original document. Every-page mode gives you one PNG per page.
Questions about page captures
Which page gets captured?
Is there a quality slider?
What happens to a 60-page PDF?
Are my files sent anywhere?
Choosing the page and the pixel size
| Control | Setting | Result you get |
|---|---|---|
| Page slider | Page 1 | One PNG of the first page only |
| Page slider | Page 2 | One PNG of that page only |
| Render scale | 1x | 240x120 pixels, the page's own measurements |
| Render scale | 2x (default) | 480x240 pixels, small type stays legible |
| Render scale | 3x | 720x360 pixels for images that will be zoomed |
| Page choice | Every page | One separate PNG file per page |
The pixel ceiling, explained honestly
A single frame is capped at 4,000,000 pixels. If your scale choice would push past that, the capture is lowered to fit instead of failing, so a large poster page still gives you a usable picture rather than exhausting the tab's memory.
Because the cap applies per frame, choosing every page keeps each page inside the limit instead of stacking one enormous canvas. The output is never stretched or cropped to a preset size: it is the page's measurements multiplied by your scale, then reduced if the cap says so.
What the snapshot is and what it drops
- PNG encoding is lossless, so the pixels in the file are exactly the pixels the renderer produced. Lossy encoding is what the PDF to JPG and PDF to WebP routes do instead.
- Selectable text is gone. Words become painted shapes, so a screen reader or a search box sees an image, not words.
- Fonts and embedded image objects are not carried over. The export is a flattened picture; there is no font inventory and no separate image file inside it.
- Links and form fields stop working, because a raster frame has no interactive layer.
- Transparency is not guaranteed. Check the downloaded picture against the background where you intend to use it.
A PNG of a PDF page is a photograph of that page: readable, but no longer searchable.
Why capture routes and text routes are separate