How to Convert PDF to JPG

PDFs are great for sharing complete documents — but sometimes you need just one page, or one image, from inside a PDF. Converting to JPG lets you drop that content into a Slack message, embed it in a blog post, attach it to a tweet, or paste it into a PowerPoint slide without dragging the whole PDF along.

Common scenarios we see: lawyers extracting a single exhibit page for a brief; marketers pulling a chart out of a research PDF for a deck; teachers turning a worksheet page into an image for a Google Form; designers grabbing a logo or icon embedded in a PDF report.

The challenge with PDF-to-JPG is the same as any PDF extraction: PDFs are layout-format, not image-format. Each page is a vector canvas that may contain text, vector graphics, embedded raster images, or all three. Converting to JPG means rasterizing the page — rendering it pixel-by-pixel at a chosen resolution.

The conversion runs entirely in your browser using pdf.js (Mozilla's PDF rendering engine, the same one Firefox uses). No upload, no signup, no watermark. You can download each page as an individual JPG, or all pages at once as a ZIP archive.

1. 1Open the PDF to JPG tool at /?mode=pdf-to-image&format=jpeg (or pick 'PDF to JPG' from the homepage mode selector).
2. 2Drop in your PDF. The tool reads the file locally and shows you a preview of the first page.
3. 3Choose render quality: 1× (72 DPI, smallest), 2× (144 DPI, balanced — recommended), or 3× (216 DPI, highest quality).
4. 4Click 'Convert'. Each page renders to a canvas, gets captured as a JPG, and you can download them individually or as a ZIP.

Most people default to JPG because it's the most universally compatible image format — every browser, every chat app, every social platform supports it. JPGs are also much smaller than PNGs for photographic content (5–10× smaller at equivalent visual quality).

But JPG has a weakness: it doesn't support transparency, and it uses lossy compression that introduces visible artifacts around sharp edges (text, logos, line art). If your PDF page is mostly text, line drawings, or screenshots with sharp edges, PNG will look noticeably crisper at the same file size.

Practical rule: PDF pages that are photos or photo-heavy → JPG. PDF pages that are text, tables, or line art → PNG. When in doubt, JPG — the artifacts are usually invisible at 2× quality and the file size savings matter for email and chat.

1× scale (72 DPI) is the historical screen standard. Files are tiny (50–200 KB per page), but if anyone zooms in or prints, the result looks pixelated. Use this for quick chat thumbnails or web previews where size matters more than quality.

2× scale (144 DPI) is the modern default. Files are 200–800 KB per page — small enough to email 5–10 of them, large enough to look sharp on Retina displays and survive moderate zoom. This is what most users should pick.

3× scale (216 DPI) approaches print quality. Files are 500 KB–2 MB per page. Use this when the JPG will be embedded in a document that gets printed, or when you expect viewers to zoom in on details (financial tables, technical diagrams, fine print).

Above 3× is rarely useful — you hit diminishing returns and the file sizes become unwieldy. If you need true print quality (300 DPI+), export from the source application directly rather than going through PDF.

This is the part most online converters don't talk about. PDFs aren't just documents — they're often the format we use for sensitive content: contracts, medical records, financial statements, legal exhibits, school records with student PII. Every time you upload one to a server-based PDF-to-JPG converter, that content sits on someone else's hardware.

The Terms of Service on most online PDF tools say they delete your file after processing — usually within an hour or two. But you can't audit the deletion. Multiple major PDF services have been caught retaining user files for 'service improvement' (i.e., training ML models), and several have suffered data breaches where uploaded documents were exposed.

Browser-based conversion sidesteps this entirely. The PDF is read by JavaScript running in your browser tab, the rendering happens on your CPU, and the JPG is generated in your browser's memory. The file is never transmitted to a server. You can verify this in your browser's DevTools (F12 → Network tab) — you'll see zero outbound file upload requests during conversion.

For sensitive PDFs (contracts, medical records, anything with SSNs or financials), browser-based conversion is the only responsible choice. For non-sensitive PDFs (public reports, blog posts, marketing material), server-based tools are fine but offer no advantage over browser-based.