Guide
How to convert a PDF to JPG without uploading anything — using the PDF Pro browser converter.
This guide is for anyone who needs to drop a PDF into Slack as an image, embed a contract page in a slide deck, or hand a designer a flat raster of every page — and would rather not upload a confidential file to a stranger's server. Five steps, the right DPI for the job, and the gotchas that bite first-timers.
What you'll need
- A modern browser (Chrome, Edge, Firefox, or Safari from the last two years)
- The PDF you want to rasterize, on your device
- A rough idea of where the JPGs will end up — screen, print, or archive
- About two minutes — including time to spot-check a thumbnail
The five steps
Open the in-browser converter
Head to the PDF Pro PDF-to-JPG tool. The page is a single static document plus a WebAssembly renderer — no signup, no email gate, no "your file is in queue" spinner. The instant the page loads, you have a working converter.
Drop your PDF onto the page
Drag the file from Finder, Explorer, or your downloads folder onto the dashed drop zone. The renderer parses the file in-tab to count pages, read each page's media box, and check for any password protection. None of that round-trips to a server.
If the PDF is encrypted, the tool will ask for the password before rendering. The password stays in memory for the session and is discarded when you close the tab.
Pick the DPI and page range
Four DPI presets appear after parsing. The right one depends on where the JPG will live: 96 DPI for a Slack message or web preview, 150 DPI as the everyday default, 300 DPI when the image will be printed at full size, and 600 DPI only for archival or OCR work. Higher DPI means bigger files — a 300 DPI A4 page is roughly 8 MB per JPG.
Use the page-range field to skip the cover sheet, grab only the appendix, or split a deck into chapters. Syntax: 1,3,5-9.
Render and preview the thumbnails
Hit Render. Each selected page is rasterized in a Web Worker so the tab stays responsive — you'll see a progress bar tick page by page. Thumbnails appear as soon as their JPG is ready. Spot-check at least two: cover (for cropping) and any page with charts (for legibility at the chosen DPI).
Download the JPGs
Click any thumbnail to save a single JPG, or hit "Download all" to grab a zip. Filenames follow the pattern originalname-page-001.jpg so they sort cleanly. Open one in Preview or your image viewer to confirm the result before sending it on. The PDF and the JPGs both stay on your machine — there is nothing on a server to delete.
Common mistakes & gotchas
- Using 600 DPI by default. A 50-page deck at 600 DPI is over 1 GB of JPGs. Pick 150 unless you have a print-shop reason to go higher.
- Forgetting that JPG has no transparency. If your PDF page has a transparent background, the JPG will fill it with white. Use the PNG converter when you need alpha.
- Rendering all pages when you only need one. The page-range field exists for a reason. Selecting
1instead of "all" on a 400-page report saves several minutes and a lot of RAM. - Treating the JPG as searchable. Rasterizing throws away the text layer. If you need to search the result, run OCR on the JPGs after, or keep the original PDF for search.
- Skipping the preview. A wrong DPI choice or a bad page range is invisible until you open the image. Always spot-check at least one thumbnail.
Troubleshooting
The JPGs look soft. Did the converter compress too hard?
Soft output usually means the DPI was too low for the use case, not that the JPG quality slider was set wrong. Re-render at 300 DPI and the same page becomes pin-sharp. The browser converter uses JPG quality 92 by default, which is visually lossless on detail-heavy pages.
Why are my JPGs so big — 8 MB each?
You're at 300 DPI on a full A4 page, which is the right size for print but excessive for screen sharing. Drop to 150 DPI and the same page lands around 1.5 MB with no visible difference at typical zoom levels.
The converter froze on a 400-page PDF.
Browsers cap per-tab memory. Re-render in two passes: pages 1-200, then 201-400. The output is identical and the tab stays responsive. If you also need a smaller source PDF first, run it through the lossless compressor.
I need PNG instead of JPG for transparent backgrounds.
JPG cannot store an alpha channel — it always flattens transparency to white. Use the PDF-to-PNG guide instead, which preserves alpha and is lossless.
The downloaded JPGs are rotated wrong.
That happens when the PDF stores a page rotation flag the renderer didn't honor. Re-render with the "Apply page rotation" checkbox enabled — most pages have it on by default, but scanned PDFs sometimes need it forced. If the PDF was scanned sideways, the right fix is to rotate the source PDF first, then convert.
Ready to convert?
Open the in-browser converter and run your PDF through the five steps above.