How to Convert a PDF to JPG (Every Page, in Your Browser)

A client sends a 40-page PDF catalog, and you need just page 6 as an image to drop into a presentation slide. PDFs don't paste cleanly into most design tools or social platforms — they need to be images first. That gap between "document format" and "image format" is exactly what a PDF to JPG converter closes, and it's one of the most-searched PDF conversions for that reason.

What the conversion actually renders

Each page is rendered through pdfjs-dist— the same rendering engine behind Chrome's and Firefox's built-in PDF viewers — onto an HTML canvas at 2x scale, then exported as a JPG at 92% quality. That scale factor is deliberately higher than a typical 72-dpi screen render: it's tuned for print-usable output, not just something crisp enough for a thumbnail. What comes out is a faithful visual snapshot of the page — text, images, vector graphics, all flattened into one raster image, pixel for pixel what you'd see if you opened the PDF and took a perfect screenshot.

One thing this tool deliberately doesn't do: there's no PNG or WebP option, and no DPI or page-range picker. It converts every page in the file to JPG, full stop. If you need a different output format or only specific pages, that's a second step (more on that below).

How to convert a PDF to JPG

1. Open the PDF to JPG tool and add your PDF.
2. Click "Convert & download." Every page renders on your device, one at a time.
3. A single-page PDF downloads directly as a .jpg. A multi-page PDF downloads as a .zip with one numbered JPG per page — unzip it to get individual files.

There's no waiting on a queue and no size limit tied to page count — a 60-page PDF converts at roughly the same per-page speed as a 2-page one, since your own device is doing the rendering.

Why this stays entirely on your device

Rendering a PDF page to a canvas is something browsers are already good at — it's the same machinery a browser's built-in PDF preview uses. Because none of that needs a server-side rendering engine, the whole conversion — render, encode, zip — happens locally using pdfjs-distand the browser's own Canvas API. Your file is never uploaded, which matters if the PDF you're converting has anything sensitive on it.

If you only need a few pages, or need a different format

Only need one or two pages out of a large PDF? Run Extract Pagesfirst to pull out just the pages you want, then convert that smaller file — it's faster than converting everything and deleting images you didn't need.

Need PNG or WebP instead of JPG? Convert to JPG first, then run the result through JPG to PNG. There's a real cost to this two-step path though — JPG's compression is lossy, so you're not getting back the crispness a native PNG render would have, particularly on pages with small text.

File already password-protected? A locked PDF can't be parsed by pdfjs-dist at all. Run it through Unlock PDF with the password first, then convert the unlocked result.

Images came out larger than expected?That's the 2x render scale doing its job — it's tuned for quality, not minimum file size. If you need smaller files for email or web use, run the output through Image Compressor afterward.

Going the other direction

If you're starting from images and want a PDF instead — scanned pages, screenshots, photos of a document — JPG to PDF does the reverse conversion, combining one or more images into a single PDF, one image per page.