Turn PDF pages into JPGs, page by page
Drop a PDF here and every page comes back as a separate JPG. That’s the whole idea. The file never gets uploaded. Rendering happens right inside your browser tab using pdf.js, so your document stays on your machine the entire time.
Why JPG? It’s lossy and small. A scanned invoice or a page full of photos shrinks down nicely, and JPGs open everywhere: email, chat, your phone’s gallery, a slide deck. You lose a little detail, but for sharing or photo-heavy pages, nobody will notice.
One thing to know up front. JPG doesn’t do transparency. If your PDF page has see-through areas, they get filled with white. For most documents that’s exactly what you want. For a logo with a cut-out background, you’d reach for PNG instead.
How the conversion works
Load the PDF, and the page count shows up immediately. Each page renders to a canvas at the DPI you picked, then gets encoded as a JPG. You’ll see thumbnails as they finish.
Click any thumbnail to save that single page. Want all of them? Hit the zip button and every page bundles into one download. A 40-page report becomes page-01.jpg through page-40.jpg, neatly inside a .zip.
Nothing leaves your device. No server, no queue, no waiting in line behind other people’s uploads. Your CPU does the work, which means speed depends on your machine and the size of the PDF.
Picking a resolution
The DPI setting controls how sharp and how big each image is. Three choices:
- Standard (~108 DPI): Good for screen viewing and quick shares. Smallest files. A text page might land around 150 KB.
- High (~180 DPI): The sweet spot for most people. Crisp on screen, readable when zoomed, still reasonable in size.
- Max (~288 DPI): For printing or when you need every line of fine text to hold up. Files get noticeably bigger, and big PDFs at this setting eat a lot of memory.
Then there’s the quality slider, separate from DPI. DPI sets pixel count; quality sets how hard the JPG compresses those pixels. Drop quality to 60 and a busy page can lose half its file size with barely visible artifacts. Push it to 95 for clean edges on text and diagrams.
Things to watch for
Big PDFs are memory-hungry. Rendering a 200-page document at Max DPI means holding hundreds of large canvases in RAM at once. On a phone or an older laptop, that tab can slow down or crash. If it struggles, drop to High or Standard, or convert in smaller batches.
Text looks softer than the original. That’s normal. JPG turns crisp vector text into pixels, so a PDF that was perfectly sharp on screen becomes a flat image. Bump DPI up if the text matters.
Scanned PDFs are already images, so converting them to JPG is basically a format swap. They tend to compress well and look fine even at Standard.
Does my PDF get uploaded anywhere? No. Everything runs in your browser with pdf.js. The file is read locally, rendered locally, and the JPGs are generated on your device. Nothing is sent to a server.
Why are some areas white instead of transparent? JPG can’t store transparency. Any transparent part of a page gets a white background. Need to keep transparency? Convert to PNG instead.
How do I get all pages at once? Click the zip button and every page downloads together in a single .zip file, named page by page. Or click one thumbnail to grab just that page.
What DPI should I use for printing? Go with Max (~288 DPI). For on-screen use or sharing, High or Standard is plenty and keeps file sizes down.
My browser froze on a huge PDF. What happened? Large or high-resolution PDFs use a lot of memory because every page renders to a full canvas. Lower the DPI, reduce quality, or split the PDF into smaller chunks before converting.
Is JPG better than PNG for this? For photos, scans, and sharing, yes. JPG files are smaller. For sharp text, line art, or anything needing transparency, PNG keeps quality better.