How to Convert PDF to JPG: Image Quality, DPI, and the 4 Methods Compared

Most "PDF to JPG" tools online give you the same blurry thumbnail no matter what you feed them, then act surprised when you complain that you can't read the text. The reason isn't that JPG is a bad format — it's that the tool quietly rasterized your 300 DPI document at 96 DPI and called it a day. Converting a PDF to a JPG is mostly an argument about resolution, and 96 DPI is the resolution that's almost never the right answer outside of a thumbnail. A page of body text that was perfectly crisp in the PDF turns into a fuzzy mess at screen DPI; the same page at 300 DPI takes ten seconds longer to render and looks nearly indistinguishable from the original.

This guide covers the four methods that actually exist for converting a PDF page to a JPG, what DPI to pick for each output target, when JPG is the wrong format and you should reach for PNG instead, and the difference between rasterizing a page and extracting the embedded images that were already inside it. By the end, you'll know exactly which path to take and why — and you can run it through ScoutMyTool's browser-based PDF to JPG converter without your file ever leaving your laptop.

Why DPI Determines Everything

DPI — dots per inch — is the resolution at which a vector PDF page is sampled into a grid of pixels. A standard US Letter page is 8.5 × 11 inches, so at 72 DPI you get a 612 × 792 pixel image; at 150 DPI you get 1275 × 1650; at 300 DPI you get 2550 × 3300. Each step up roughly quadruples the pixel count and the file size, but it also roughly halves the size at which 8-point body text starts to look like a smudge.

Three sensible defaults cover almost every real use case.

• 72–96 DPI for inline web preview thumbnails or social-media share cards. Anything text-heavy will be unreadable; this is for "show me what the page looks like at a glance."
• 150 DPI for screen viewing on a 1080p or retina monitor. Body text remains crisp, headings look sharp, and file sizes stay reasonable (a typical text page under 500 KB).
• 300 DPI for print or for archival. This matches the resolution your inkjet or laser printer would render at, and matches the print-industry minimum most professional printers require for body text.

Going above 300 DPI rarely helps — the underlying PDF was almost certainly authored against a 300 DPI assumption, and additional resolution mostly upscales noise. The exception is photos or fine line art that were embedded at higher native resolution; in that case, see the "extract" path below instead of rasterizing.

How Conversion Actually Works

Under the hood, every "PDF to JPG" pipeline does some version of the same three steps: parse the PDF page into a display list, render that display list onto a canvas at the requested DPI, then encode the resulting bitmap as JPG. The differences between tools come down to which renderer they use and how they handle the encoding step.

Browser-based converters (the kind that run entirely in your tab) typically use PDF.js, Mozilla's open-source PDF rasterizer, against an HTML5 canvas. Server-based converters use Ghostscript, MuPDF, or Poppler. Adobe Acrobat uses its own renderer, which is unsurprisingly the closest match to how the file was originally rendered. For 99% of documents, the visible difference between renderers is invisible at 150 DPI and above; for documents using exotic font subsetting or complex transparency, you may see edge artifacts in lower-quality renderers.

The encoding step is where JPG's lossy compression takes over. JPG encodes images by splitting them into 8×8 pixel blocks, applying a discrete cosine transform, and quantizing the result. This is great for photos, where the human eye can't easily see the lost frequencies — but it's bad for sharp text edges and solid color blocks, which is exactly what most PDF pages are. That's why a screenshot of a PDF page saved as JPG often looks slightly fuzzy along character edges, while the same screenshot saved as PNG looks pixel-perfect.

If your PDF contains mostly text, diagrams, or screenshots of UI, save as PNG instead. The W3C's JPEG MIME type registration is explicit that JPEG is designed for "continuous-tone color images" — photographs — not for the sharp transitions that dominate text. JPG was the wrong tool for that job from day one.

Step-by-Step Using ScoutMyTool

ScoutMyTool's PDF to JPG converter runs entirely client-side in your browser, which means the file never uploads to a server. Drop a PDF on the page, choose your output DPI (72/150/300), and the tool emits one JPG per page that you can download as a ZIP.

For multi-page PDFs you only want the cover image of, choose page range "1" before converting. For documents with hundreds of pages, switch to PNG output if file size matters less than fidelity — at 300 DPI a text page fits in a 500 KB JPG but might stretch to 1.5 MB as PNG. If you need the original embedded photos rather than rasterized pages (see next section), use the PDF image extractor instead.

When file privacy is a concern — medical records, legal exhibits, financial PDFs — the client-side conversion route is the only one that doesn't leave a copy of your document on someone else's hard drive. Server-based converters retain uploads for hours or longer regardless of what their privacy policy claims.

Worked Examples

Example 1 — Email-friendly cover thumbnail. A real estate agent has a 12-page property listing PDF. They want a single JPG of page 1 to embed in a marketing email under 100 KB. Choose page range 1, DPI 72, JPG quality 80. Output: ~85 KB JPG, 612 × 792 pixels, perfectly readable for the headline and price callout, fuzzy on the small print but the small print isn't what's selling the house.

Example 2 — Contract pages for client review. A solo attorney needs to email pages 4–6 of a signed engagement letter to opposing counsel as JPGs (the requesting firm refused PDF for some inscrutable IT reason). DPI 150, JPG quality 90. Output: three ~400 KB JPGs at 1275 × 1650 pixels. Body text remains crisp at 100% zoom, and the total email attachment lands well under the 25 MB Gmail cap.

Example 3 — Print-ready page extract from a textbook. A teacher pulls page 47 from a 600-page open-license textbook PDF for a classroom handout. DPI 300, JPG quality 95. Output: ~1.4 MB JPG at 2550 × 3300 pixels. Will print cleanly on a black-and-white laser printer at full Letter size with no visible degradation versus the original PDF.

Example 4 — When JPG is the wrong choice. A product designer needs to share a single page from a PDF mockup that contains 40+ small UI text labels. DPI 300 JPG produces visibly fuzzy text at full zoom — the JPG block-encoding is destroying the sharp anti-aliased edges. Switching to PNG at the same DPI produces a 2.1 MB file (versus 1.4 MB JPG) that is pixel-identical to the source. The right answer here is PNG, full stop.

Common Pitfalls

The most expensive mistake is converting at 96 DPI by default and only realizing the result is unreadable after sending it to a client. Always choose 150 or 300 unless you have a specific reason for a thumbnail-only output.

The second is choosing JPG for diagrams and text. JPG's block-based compression introduces visible "ringing" near sharp edges; on body text this looks like a faint halo around every character, and on line art it produces speckled artifacts in the white space. PNG is the right format for any page that isn't a photograph.

The third is not realizing that "page-as-image" and "extract embedded images" are different operations. If your PDF contains a high-resolution photograph and you rasterize the page at 150 DPI, you've downsampled a (possibly) 600 DPI photo to 150 DPI in the process. To pull out the original embedded image at full native resolution, you need an image-extraction pass, not a page-rasterization pass — Adobe documents the embedded-image structure in section 8.9 of the PDF 2.0 reference.

The fourth is uploading sensitive PDFs to free server-based converters. Most retain copies long enough to violate any reasonable interpretation of GDPR Article 5(1)(c) data minimization, regardless of what their marketing copy says. For HIPAA-covered documents specifically, server-side conversion without a Business Associate Agreement is a flat compliance violation.

Frequently Asked Questions

Q: Why is the JPG fuzzier than the original PDF? A: Either DPI is too low (try 150 or 300) or the PDF contains text and you should use PNG instead. JPG's lossy DCT compression damages sharp edges; for documents with body text, PNG at the same DPI is sharper at a comparable file size.

Q: What DPI should I use for printing? A: 300 DPI is the print-industry standard for body text and line art. Going to 600 DPI rarely helps unless the original PDF embedded high-resolution photos that benefit from full-resolution rasterization. Most laser and inkjet printers max out their effective resolution well below 600 DPI of the source image.

Q: Will a client-side converter handle 500-page PDFs? A: Yes, but performance depends on browser and device. Chrome/Edge on a recent laptop can rasterize about 5–10 pages per second at 150 DPI. For PDFs over 1,000 pages, batch in chunks of 100 pages or use the PDF splitter first to break the file into manageable pieces.

Q: Can I convert a password-protected PDF to JPG? A: Only if you have the password. PDF.js (and most other rasterizers) will prompt for the password before rendering — there's no legitimate way to bypass this without the credential. If the file is yours and you've forgotten the password, the PDF unlock tool handles user-password removal where it's legally permitted.

Q: What's the difference between rasterizing a page and extracting embedded images? A: Rasterizing renders the entire page (text, vectors, images, everything) into a single bitmap. Extracting pulls out the original embedded image objects from inside the PDF at their native resolution. If your PDF contains a 4000×3000 photo and you rasterize the page at 150 DPI, you've downsampled the photo to ~1275×1650; if you extract instead, you get the original 4000×3000.

Q: Is JPG better than PNG for screen sharing? A: For photographs, yes — JPG is dramatically smaller for the same perceived quality. For text, screenshots, diagrams, and line art, PNG wins on every axis except file size (and only barely loses on size). A useful rule: if the page has more than 30% text or vector content, use PNG.

Q: Why does my converted JPG look slightly different in colors? A: JPG uses 4:2:0 chroma subsampling by default, which discards 75% of the color resolution while keeping full luminance. On large flat color blocks this is invisible; on red or magenta text against a contrasting background, it can produce visible color fringing. Switching to chroma 4:4:4 (some encoders allow this) or to PNG eliminates the issue.

Wrapping Up

PDF-to-JPG conversion is mostly about three decisions: what DPI to render at (150 for screen, 300 for print, 72 only for thumbnails), whether JPG is even the right output format (it's wrong for any text-heavy page — use PNG), and whether you should rasterize the page or extract the embedded images at native resolution. Get those right and the rest is one click. Try it now with the client-side PDF to JPG converter — your PDF stays on your machine, the conversion runs in your browser, and you control every parameter that matters.