This tool turns every page of a PDF document into a separate image file. It uses Mozilla’s PDF.js renderer to draw each page onto an HTML canvas at your chosen resolution, then encodes that canvas as JPG, PNG or WebP. JPEG output goes through a WebAssembly build of MozJPEG where the browser supports it, which typically produces a noticeably smaller file than the browser’s built-in encoder at the same visual quality, and falls back to the native encoder otherwise.
All of that happens on your own machine. There is no upload step, no queue and no temporary copy sitting on someone else’s disk — which also means the conversion speed depends on your device rather than on server load or your connection.
Your PDF is read straight from disk into browser memory. Nothing is transmitted, so contracts, medical records and ID scans can be converted without leaving your device.
A PDF page has no inherent pixel size — it is described in points, where one point is 1/72 inch. The quality setting is a render scale applied to that page geometry, so the resulting DPI follows directly from it:
| Setting | Render scale | Effective DPI | JPEG quality | A4 page output |
|---|---|---|---|---|
| High | 2.0× | ~144 DPI | 0.92 | ~1190 × 1684 px |
| Normal | 1.5× | ~108 DPI | 0.85 | ~892 × 1263 px |
High is the right default for anything you will read on screen, zoom into, or run through OCR later. Normal is worth choosing when you are converting a long document and only need legible thumbnails or email attachments. Either way, pages are capped at 8192 px on the longest side, because that is the largest canvas dimension browsers handle reliably — unusually large pages such as posters or CAD sheets are scaled down to fit that ceiling.
JPG is the safe choice for scanned documents, photographs and anything you need to share widely; every application on earth opens it. PNG is lossless, so text edges and thin table rules stay perfectly crisp, but a text-heavy page can easily be five to ten times larger than the same page as JPG. WebP sits in between and is the best option when the images are destined for a web page, since it holds PNG-like sharpness at roughly JPG file sizes — it is supported by all current browsers, though some older desktop image viewers still cannot open it.
No. The conversion runs inside your browser using PDF.js and the HTML canvas API. Your file is read from disk into memory by the page itself and never leaves your device, so there is nothing to delete afterwards and no upload wait.
High quality renders each page at 2× its native PDF size — roughly 144 DPI — and encodes JPEG at quality 0.92. Normal renders at 1.5×, roughly 108 DPI, at quality 0.85. An A4 page therefore comes out around 1190 × 1684 pixels on High and 892 × 1263 on Normal.
Every page is converted automatically. When a PDF has more than one page the images are bundled into a single ZIP archive named after the source file, with each image numbered in page order — report-1.jpg, report-2.jpg and so on. A one-page PDF downloads as a single JPG instead.
Choose JPG for scanned pages, photos and general sharing. Choose PNG when the page is mostly text, tables or line art and you want lossless edges, at the cost of a much larger file. Choose WebP when the images are for a website and you want PNG-like quality at roughly JPG file sizes.
There is no server-imposed limit, because no server is involved. The practical ceiling is your device’s available memory, since each page is rendered to a canvas before being encoded. Pages are also capped at 8192 pixels on the longest side, the maximum canvas dimension browsers reliably support.
The page needs an internet connection on first load to fetch the PDF.js and JSZip libraries. Once loaded, the conversion itself makes no network requests, so losing your connection mid-conversion will not interrupt it.
