A PDF page isn't a picture — until you render it
Most PDF pages are vector instructions, not pixels: text glyphs, line paths, and embedded image objects positioned by coordinates. There's no fixed 'resolution' baked into the page — a PDF page is closer to an SVG than a photograph. To turn it into a JPG, something has to rasterize it: paint that vector content onto a pixel grid at a resolution you choose.
That's what happens here using pdf.js, the same rendering engine behind Firefox's built-in PDF viewer. It walks each page's content stream and draws it onto an HTML canvas at a scale factor you set, and the canvas is then encoded to JPG. The scale factor is the single most important setting, because it directly determines both image sharpness and file size — there's no separate 'quality' slider hiding elsewhere.
What each render scale actually gives you
| Scale | Approx. equivalent | Best for |
|---|---|---|
| 1× | ~72 DPI | Quick screen preview, thumbnails |
| 2× | ~144 DPI | Typical viewing, sharing, most web use |
| 3× | ~216 DPI | Higher-detail viewing, moderate zoom |
| 4× | ~288 DPI | Print-quality output, fine text and diagrams |
Converting your PDF
Drop a PDF onto the zone — the tool reads the total page count.
Pick a render scale (1×–4×): higher means sharper output but larger files and more memory used during rendering.
Click Convert to JPG & zip — each page is rendered, encoded, and zipped locally.
Why the output is a ZIP, not individual downloads
Since most source PDFs have multiple pages, each producing its own JPG, bundling them into one ZIP avoids triggering a separate browser download prompt per page — which most browsers will throttle or block after a handful of rapid downloads anyway. Unzip the result to get each page as page-1.jpg, page-2.jpg, and so on, in reading order.
Getting sharp output without wasting memory
Rendering at 4× doesn't just make a bigger JPG — it multiplies the pixel count roughly 16x compared to 1× (4x the width, 4x the height), and every one of those pixels has to be held in browser memory during rendering before it's encoded. For a short PDF, that's rarely noticeable. For a 100+ page document, jumping straight to 4× can slow the browser down or stall on lower-memory devices.
A practical approach: use 2× as your default, and only reach for 3–4× when you specifically need to zoom in on fine text or print the result. There's rarely a reason to go above 2× for something that's only going to be viewed on a screen.
Common mistakes
Choosing 4× out of habit for a document that will only ever be viewed on-screen — it wastes file size and rendering time for no visible benefit.
Converting a scanned PDF at 1× and expecting sharp text — a scan's original resolution is fixed at capture time, and a low render scale can make already-soft scanned text look worse.
Forgetting that scale amplifies existing image quality, not creates it — rendering a low-resolution embedded image at 4× produces a bigger file, not more real detail.
Running a very large PDF at high scale on a low-memory device and expecting instant results — high scale on long documents is genuinely memory-intensive.
Where this fits vs. other formats
JPG is the right choice when you specifically need a compressed, universally compatible photo format — for uploading to platforms that require images, embedding pages in a slideshow, or sharing a quick visual preview. If you need lossless output (better for pages with sharp text or line art rather than photos), or want PNG instead of JPG, the general PDF to Images converter covers those format choices.
Real use cases
Turning a scanned contract into JPGs to attach individual pages to a support ticket or form that only accepts images.
Extracting slides from a PDF export of a presentation to drop into a different slideshow tool.
Creating quick visual thumbnails of a multi-page report for a preview gallery.
Converting scanned pages of a document at high scale to prepare them for print reproduction.
Frequently asked questions
Q: Is my PDF uploaded anywhere?
A: No — rendering uses pdf.js running entirely in your browser, with no outbound file transfer.
Q: What scale should I use?
A: 1× suits a quick screen preview (roughly 72 DPI), 2× is a solid default for typical viewing and sharing, and 3–4× is worth the larger file size for print-quality output or zooming into fine detail.
Q: Why is the output a ZIP file instead of separate downloads?
A: Most PDFs span multiple pages, and bundling every rendered JPG into one ZIP is far more convenient — and more browser-friendly — than triggering a download prompt per page.
Q: Does it work on scanned PDFs?
A: Yes. Scanned pages are already image-based, and pdf.js renders them the same way it renders text-and-vector pages.
Q: Will increasing the scale improve the quality of a low-resolution scan?
A: No — scale controls how large the output canvas is, not the underlying detail captured in the scan. Rendering a blurry scan at 4× produces a bigger blurry image, not a sharper one.
Q: My converted JPGs look slightly different in color from the PDF — why?
A: This can happen when a PDF uses a color space (like CMYK) that gets converted to RGB during rendering for screen display — a normal part of rasterizing a print-oriented PDF for JPG output.
Convert your PDF now
Turn your pages into images with the PDF to JPG tool. Need PNG or another format instead? Check PDF to Images. Want the text rather than pictures of it? Use PDF to Text, or shrink the original file first with Compress PDF.
