How it works
- 01Open the PDF.
- 02Pick PNG for sharpness or JPEG for size.
- 03Set the resolution — 150 DPI is right for screens, 300 for print.
- 04Download. One page gives you an image; several give you a zip.
PNG or JPEG, and when each is right
PNG is lossless, so text stays crisp and there are no compression artefacts around letters — the right choice for a page of text. JPEG is much smaller for photographs and scans, and its softness is invisible on a photograph and obvious on 9pt type. The panel shows the pixel dimensions before you commit.
One download, in page order
Multiple pages are packed into a zip so you get one file rather than forty prompts. Names are zero-padded — page-01, page-02 — so a file manager sorts them in the order they appear rather than 1, 10, 11, 2.
What you see is what you get
Pages are rendered from the document as it stands, including edits made in this session. Crop a page, rotate it, add a watermark, and the image reflects all of it — the same renderer draws the preview you are looking at.
Resolution costs memory
A Letter page at 300 DPI is about 2,550 by 3,300 pixels, and forty of those is a substantial amount of memory for a browser to hold at once. The panel warns when an export is heading somewhere your device may not follow, rather than letting the tab die.
Questions
- What resolution should I use?
- 150 DPI for anything that will be viewed on a screen, 300 DPI for print. Above 300 you are usually adding file size rather than detail.
- Why a zip instead of separate files?
- Because forty download prompts is not a feature. A single page is given to you directly as an image, since wrapping one file in an archive would be an obstacle.
- Can I convert images back into a PDF?
- Not yet. Building a PDF from images is a natural companion tool and is on the list.
- Is the conversion done on a server?
- No. The rendering and the image encoding both happen inside your browser.