Drop a PDF here
or click to browse
Rendering pages…
Your file never leaves your browser
Conversion failed
- No uploads
- No account
- No watermarks
How to use PDF to JPG
-
1
Upload your PDF. Open the PDF to JPG tool and drop your PDF into the upload area, or click to browse. The page count is detected automatically in your browser.
-
2
Choose which pages to convert. Type "all" to export every page, or enter a specific range like 1-3, 5 to export only the pages you need.
-
3
Set quality and resolution. Adjust the JPEG quality slider (30–100%) and choose a DPI: 72 for screen use, 150 for standard output, or 300 for print-quality images.
-
4
Click Convert to JPG. PDF.js renders each page in your browser at the chosen DPI. A progress message tracks each page — no upload, no server queue.
-
5
Download your images. Click the download icon on any preview thumbnail to save that page as a JPG. To get all pages, click Download all — files are saved one by one.
-
6
Convert another PDF. Click "Convert another PDF" to reset the tool and start a new conversion.
By Mohit Khatri · Last updated
Learn more about PDF to JPG
Direct Answer: The PDF to JPG converter turns PDF pages into standalone image files — JPG, PNG, or WebP — entirely in your browser. It is a task page that opens ToolWeb's Browser PDF Editor with the Convert dialog ready: load a PDF, pick a format and a resolution preset, choose all pages or just the current one, and download the result. No upload, no account, no watermark, no page limit.
Because a PDF page is a layout — text, vectors, and images composed together — converting it to an image means rendering it, exactly as it appears on screen. That makes this tool the fast path whenever you need a page as a picture: a slide for a deck, a figure for a blog post, a thumbnail for a listing, or a proof to drop into a chat where nobody wants to open an attachment.
Direct Answer: Images go where PDFs can't. Presentation software, website builders, social platforms, chat apps, and CMS media libraries all take images natively, while a PDF often needs a download-and-open detour. Converting a page to JPG or PNG makes it instantly embeddable and previewable everywhere.
Images are also frozen. A JPG of a signed page or a priced quote can't have its text reflowed or its fields edited by whatever app opens it next — what you exported is what everyone sees. And because each page becomes its own file, you can pull one figure out of a 200-page report without sending the whole document along with it. If you only need the words rather than the picture, extract the text from your PDF instead.
Direct Answer: Conversion uses the PDF.js canvas renderer — the same engine that draws pages in the editor — running at the scale you choose. Standard renders at 1× (72 dpi), High at 2× (144 dpi), and Print at 3× (216 dpi). The rendered canvas is then encoded to your chosen format on-device: lossy formats (JPG and WebP) are encoded at 0.92 quality, a sweet spot that keeps artifacts invisible at normal viewing sizes, while PNG is pixel-for-pixel lossless.
When you export all pages, each image is generated and packaged into a single ZIP archive built in the browser — no server assembles it, so it downloads the moment the last page finishes rendering. Any page rotation you applied in the editor is respected in the export, so a landscape scan you straightened comes out straight.
Direct Answer: The right format depends on what is on the page:
- PNG is lossless. Choose it for pages dominated by text, line diagrams, tables, or screenshots — edges stay razor sharp with zero compression artifacts.
- JPG is the smallest for photo-heavy pages: scanned photos, magazine layouts, full-bleed imagery. At the 0.92 encoding quality, photos look clean while files stay compact and universally compatible.
- WebP balances both — smaller than JPG at similar quality and it handles mixed text-and-photo pages well, though a few older apps still don't accept it.
Simple rule: text and diagrams get PNG, photographs get JPG, and modern web destinations get WebP. If the exported images end up too heavy for a web page, run them through the image compressor afterward.
Direct Answer: Resolution should match the destination, not maximum-everything:
- Standard (72 dpi / 1×): On-screen use at normal size — email previews, chat, thumbnails, quick reference images. Smallest files, fastest export.
- High (144 dpi / 2×): Retina displays, presentation slides, and blog images that may be zoomed. Text stays crisp on high-density screens.
- Print (216 dpi / 3×): Physical printing, large-format display, or downstream cropping where you need pixel headroom.
Exporting at Print "to be safe" triples the pixel dimensions and multiplies file size for no visible benefit on screen — and oversized images slow the very pages you embed them in. Pick the preset the destination actually needs.
Direct Answer: These workflows come up constantly:
- Presentation slides: Export report pages at High and drop them straight into PowerPoint, Keynote, or Google Slides instead of screenshotting each one.
- Thumbnails and covers: Render page one of a whitepaper or ebook as its cover image for a landing page, store listing, or library view.
- Social posts: Turn an infographic page or announcement into a JPG that feeds render inline — platforms preview images, not PDFs.
- Print and design proofs: Send a Print-preset page image to a client for approval when they don't have a PDF viewer handy.
- Documentation: Extract figures and charts from a spec as PNGs for a wiki, README, or knowledge base.
Working the other direction — assembling photos into a document — is the job of the JPG to PDF converter.
Direct Answer: You control exactly how much gets exported. Current page only gives you a single image download — perfect when one figure is all you need. All pages renders every page and packages the images into one ZIP so a 60-page deck arrives as a single tidy archive rather than 60 separate downloads.
For bigger jobs, batch mode converts many PDFs to images in one run — ideal for turning a folder of one-page flyers into a folder of JPGs, or generating cover thumbnails for an entire document library. And the editor scales with you: virtualized rendering keeps 500+ page documents scrolling smoothly, session recovery autosaves to IndexedDB for files up to 80 MB, and full-text search helps you find the exact page worth exporting.
Direct Answer: Every render, encode, and ZIP is produced on your own device. The PDF is never uploaded, so there is no server-side copy, no processing queue, and no retention window — nothing exists to breach or leak. For contracts, medical documents, unreleased designs, and anything confidential, that is a structurally stronger guarantee than any "we delete your files" promise.
There is no account and no email capture, and the only local trace is the session-recovery data in your own browser's IndexedDB. The proof of the architecture: once the editor has loaded, you can disconnect from the internet entirely and the conversion still works.
Direct Answer: Get cleaner exports with a few habits:
- Match dpi to destination: 72 for web and chat, 144 for retina screens and slides, 216 for print. Don't default to the biggest.
- PNG for text, JPG for photos. Exporting a text-dense page as JPG invites fuzzy edges around characters; exporting a photo page as PNG balloons the file.
- Rotate before exporting. Fix sideways pages in the editor first — rotation carries into the export automatically.
- Remember conversion flattens text. Images have no selectable text; keep the source PDF if you'll need to copy or search its contents later.
- Don't upscale a low-quality scan expecting sharpness — Print preset adds pixels, not detail the scan never had.
- Extract only what you need. One figure? Use current-page export instead of unzipping a full-document archive.