PDF to JPG — Turn Each Page Into an Image (No Upload)
PDF was designed to be read, not unpacked. Most of the time that's fine — you open it, you scroll, you sign or print or forward. Occasionally you actually want each page as a standalone image: for an Instagram carousel, a Slack channel that strips PDF attachments, a job application that asks for "JPG of your portfolio", or a quick visual reference to drop into Notion.
The technical name for this is "rasterizing": turning the PDF's vector page into a fixed-size image. PDF pages are mostly drawn with vectors — text, shapes, lines — that look sharp at any zoom. JPGs are fixed-resolution pixels. The conversion picks a target resolution and renders each page at that size.
Convert in your browser
Buncha's PDF to Image does this client-side. Drop the PDF, pick a resolution, get a folder of JPGs (one per page) downloaded as a ZIP. Nothing uploads.
Under the hood it's pdf.js (Mozilla's PDF renderer that ships in Firefox) plus <canvas> to capture each rendered page. Both run entirely in your browser. The library downloads on first use (about 1 MB) and caches.
What resolution to pick
This is the question that matters. Too low and the text in the JPG looks fuzzy; too high and you've got a 12 MB image of one PDF page.
- Screen / social media — 150 DPI. Good for Instagram, Slack, Notion. ~1700 px wide for an A4 page. About 200–500 KB per page as JPG.
- Print quality — 300 DPI. The newspaper / letterpress standard. ~3500 px wide for A4. 500 KB to 2 MB per page. Use this if the JPGs will end up in a printed booklet.
- Reference / archival — 600 DPI. Enormous files; don't pick this unless you're scanning a book and need every detail.
If you're not sure, pick 150 DPI. It's the right answer for everything that ends up on a screen.
JPG vs. PNG
JPG is smaller and good for scanned pages with photos. PNG is bigger but cleaner for pages with mostly text and diagrams (no compression artefacts on the letter edges). Both are supported in the tool; use PNG if your PDF is a slide deck, contract, or anything text-heavy.
Common reasons people do this
- Instagram carousel from a PDF. Resize the JPGs to 1080×1080 with the Image Resizer afterwards if the carousel needs square crops. The PDF→JPG tool gives you the originals at the right aspect; the resizer crops or pads as needed.
- A workplace chat that strips PDF attachments. The PDF gets blocked for "security" but JPGs go through. Convert, post all the pages.
- A quick reference image. Drop one page from a manual into a notes app or design doc.
- Job application or portfolio upload. Some forms want JPGs of each page, not a multi-page PDF. The fastest path is convert, then upload the lot.
The reverse direction
If you have a folder of JPGs and want to combine them back into a PDF, use Image to PDF. Drag-reorder the pages before exporting.
Server-side converters — skip them
Most "PDF to JPG" sites work by uploading your PDF to their server, rendering the images server-side, and giving you a download link. That model has the usual problems:
- Your document sits on their infrastructure for some retention window.
- Many free tiers cap at 5 pages or 25 MB.
- Watermarks on the output unless you pay.
- No actual benefit over browser-side, since pdf.js renders just as fast on your laptop.
If you're handling anything sensitive — a signed contract, a tax return, medical paperwork — browser-side is the only sensible path.
The shortest path
Open PDF to Image, drop the PDF in, pick 150 DPI and JPG, download the ZIP. One click per page is the worst case; for most documents it's one click for everything.