PDF to Image
Render every page of a PDF into a PNG, JPG, or WebP image using the browser's built-in pdf.js. Everything runs locally — the file never leaves your device. You can convert the whole document or only export a few pages by range, pick a resolution anywhere from 96 DPI for screen sharing up to 600 DPI for print, keep transparent regions in PNG, or fine-tune JPG quality. Common reasons people reach for this: a support portal that only accepts image uploads, sending slides to social media as single-page cards, generating preview thumbnails for design files, or turning a CV or portfolio into images the recipient can flip through without opening a PDF reader.
- Every page is rendered locally with pdf.js — the PDF bytes never leave your device
- Supports PNG (with optional transparent background), JPG (quality 1-100), and WebP output
- Choose any resolution from 72 DPI to 600 DPI to match screen, Retina, print, or press use
- Export only the pages you need with range syntax like 1-3, 5, 7-9 instead of the whole document
- Reads page count and first-page dimensions on upload as a sanity check
- Download all images as a single ZIP, or grab any individual page from the result list
- Output keeps the original aspect ratio — A4, A3, letter, or custom sizes are not squashed
- Encrypted PDFs are flagged with a clear error during load instead of silently producing blank images
Drop a PDF here, or click to choose a file
Pick one PDF — every page is rendered locally in your browser.
Lossless, sharpest text and lines, larger files
Higher is sharper but bigger. Typical values: 96 (screen), 150 (Retina), 300 (print), 600 (press).
Leave empty to export everything. Otherwise use range syntax: single pages, ranges, and multiple segments separated by commas.
Source pages
—
Output images
—
Total size
—
Choose a PDF and set the options. The rendered images will appear here.
Overview
Renders every page of a PDF to an image with predictable options for format, resolution, and which pages get exported.
- 01
Three common formats
PNG keeps text and lines sharp and supports transparent regions. JPG is smaller, better for scans and photo-heavy PDFs. WebP is usually smaller still and opens in every modern browser.
- 02
Configurable resolution
Pick anywhere between 72 DPI and 600 DPI, with one-click presets for 96, 150, 300, and 600. Low for the screen, high for press — adjust to taste.
- 03
JPG quality slider
JPG mode exposes a 1-100 quality slider. 85 is the usual sweet spot; pushing it lower gives noticeable banding and block artefacts. Estimated file size helps you decide.
- 04
PNG transparent background
PNG mode can keep transparent regions intact. Most office documents have a solid white fill, so this matters for logos, vector art, and design files lifted out of a PDF.
- 05
Export a page range
Use range syntax like 1-3, 5, 7-9 to convert only the pages you need. Much faster than re-rendering everything when you only want a cover thumbnail.
- 06
Aspect ratio preserved
Output dimensions are derived from the PDF page's physical size — A4, A3, letter, or custom sizes are never squashed or stretched.
- 07
Local processing
Pages are rasterised in the browser by pdf.js. The PDF bytes never leave your device, so the tool is fine for contracts, IDs, medical records, and other sensitive material.
- 08
Encrypted PDFs detected
Password-protected PDFs fail loudly during load, so you can switch tools or remove the password instead of waiting for silent blank output.
- 09
ZIP download
Pack every rendered image into a single ZIP. Files are named with zero-padded numbers like page-001.png, so file-manager sort order matches page order.
- 10
Single-image download
Each result row has a Download button, so you don't need to package everything just to grab one or two pages.
How to use
Upload to download usually takes a few seconds to a couple of minutes, with no installs.
- 01
Click "Choose PDF" or drag a file onto the upload area. The tool reads the page count and first-page dimensions automatically.
- 02
Pick an output format. PNG for text and transparency, JPG for scans and photo-heavy pages, WebP for the smallest files.
- 03
Pick a resolution. 96-150 DPI for screen, 200 for Retina, 300 for print, 600 for press.
- 04
If you only need some pages, enter them under "Pages to export" using range syntax (1-3, 5, 7-9). Leave it empty to export everything.
- 05
JPG mode also takes a quality value (1-100). PNG mode has a checkbox for a transparent background.
- 06
Click "Convert". Each page is rendered locally — the progress indicator shows which page is in flight.
- 07
When it's done, scroll through the thumbnails. Hit "Download ZIP" for everything in one file, or use the Download button on a row to save a single image.
Details
Designed around a single, common need: turning a PDF into images that another system or person can actually consume.
- Switch freely between PNG, JPG, and WebP output
- Any DPI from 72 to 600, with quick presets for 96 / 150 / 300 / 600
- JPG quality slider (1-100) for fine-tuning size vs. fidelity
- PNG transparent-background option
- Range syntax (1-3, 5, 7-9) for selective export; empty means everything
- Automatic page count and first-page dimensions on upload
- Zero-padded output names like page-001.png keep sort order intact
- Progress indicator shows the page currently being rendered
- Thumbnail previews after rendering, click to see full size
- ZIP download for the whole batch, or per-image Download buttons
- Live total output size in the summary panel
- Original PDF is never modified — retry with different settings as much as you like
- Encrypted PDFs get a clear error during load
- Aspect ratio preserved for A4, A3, letter, or any custom page size
- Works in Chrome, Edge, Firefox, Safari, Brave on desktop and mobile
Use cases
These are the everyday situations where converting a PDF to images is the easiest path.
-
Support portals that only accept images
Plenty of banking, insurance, healthcare, and government ticket systems only allow jpg or png uploads. Convert your scanned contract once and submit it directly.
-
Sending pages over chat
PDFs in Slack, Teams, or WeChat usually show as attachments people have to open. Images preview inline, which is much friendlier for "look at this before the meeting" moments.
-
Design review and markup
Designers can drop the rendered PNGs into Figma, Miro, or a chat thread for annotation, instead of expecting reviewers to install a PDF tool.
-
Slides as social cards
Export your slide deck as a PDF, render the pages, then post the individual images as carousel cards on LinkedIn, X, or Instagram.
-
CVs and portfolios that previewable
Recruiters who skim sometimes never open the PDF. Including a JPG preview in the email body or shared folder raises the chance of being seen.
-
PDF cover thumbnails
When a site, blog, or document system needs a preview image for each PDF, render the first page to PNG and use it as a thumbnail.
-
Reading on devices without a PDF viewer
Drop the images into your phone's photo library and you can flip through them on an old device, offline, or on a plane.
-
Sample sheets before printing
Render at 300-600 DPI so you can do a final colour, bleed, and trapping check in a graphics tool before the print job goes out.
-
Thesis screenshots and defence slides
Quoting paragraphs, capturing figures for a defence deck, or sharing excerpts — image exports skip the reader chrome and any built-in watermarks.
-
OCR pre-processing
Some OCR engines prefer crisp images to PDFs. Render the pages at the right DPI first, then feed them to Tesseract, PaddleOCR, or an online OCR service for better results.
-
Sharing scans with people who only do images
Some clients, family members, or executives only want image attachments. Converting receipts, boarding passes, or forms saves a back-and-forth.
-
Archives that prefer images over PDFs
A handful of archive systems handle images more reliably than PDFs. Rasterising before storing can avoid PDF version compatibility headaches years later.
See also
Once you have the images, you can shrink them further with Image Compressor , or switch them between WebP, AVIF, JPG and other formats using Image Converter . For more PDF and image utilities, check the File category page.
Best practices
Picking a format and DPI looks trivial, but there are a handful of trade-offs worth knowing up front.
- For screen sharing and web embeds, PNG at 96-150 DPI keeps text crisp at around 100-500 KB per page.
- For print, go to 300 DPI at least. For high-end press output (magazines, art books) use 600 DPI, but expect 10+ MB per page.
- For plain white-background scans, JPG at quality 80-85 is typically half the size of PNG with text still legible.
- For pages with vector art, logos, UI screenshots, or design work, prefer PNG — JPG will introduce edge artefacts.
- When you need to drop the result onto a dark background or composite with other elements, use PNG and tick "Transparent background".
- Rendering a few hundred pages at 600 DPI in one go will run out of browser memory — split into ranges instead.
- Range syntax expects ASCII punctuation. Copying from a word processor sometimes brings full-width commas, which will fail validation.
- If you only need the cover page, just put 1 in the page range — much faster than rendering everything and deleting later.
- Use a meaningful filename prefix (contract-acme-page, slides-2026Q2) so the files are easy to find later.
- For non-standard sizes (large design files, posters, CAD output) anything above 500 DPI can produce 20-50 MB per image. Try 200-300 DPI first.
- When you're feeding the images into a video, keynote, or slide deck, work out the target pixel size first (say 1920x1080) and back-calculate the DPI.
- Handling sensitive material? Run it in a private window or offline, and clear your browser download history afterwards.
Limitations
Converting a PDF to images is a "keep the look, lose the structure" operation. A few things to know in advance:
- Text in the output is now pixels — you can no longer search or copy it. Keep the original PDF if you need text retrieval.
- Links, table of contents, bookmarks, form fields, annotations, and digital signatures all disappear in image form.
- At 600 DPI a large page can produce a 50 MB image. Devices with limited RAM (especially phones) may struggle or fail.
- Encrypted PDFs, corrupted files, strict PDF/A and PDF/X variants, and DRM-protected files may not load or render at all in pdf.js.
- A few embedded fonts render slightly differently in pdf.js than in Acrobat — rarely visible, but worth checking for unusual scripts or symbols.
- Transparent backgrounds only apply to PNG. JPG and WebP (default lossy mode) have no alpha channel.
- Vector graphics become raster, so further enlargement will show aliasing. If you still need vectors, keep the PDF or export to SVG instead.
- pdf.js anti-aliasing and font substitution differ subtly from Acrobat, Foxit, or Apple Preview. Day-to-day documents look the same.
- Pages that the PDF has rotated (90° landscape scans, for example) export the way they appear, not in their raw orientation.
FAQ
Quick answers to the format, sizing, and comparison questions that come up most often.
Which format should I use — PNG, JPG, or WebP?
PNG for text, UI screenshots, design files, and anywhere you need a transparent background. Lossless but bigger. JPG for scans, photos, and full-page documents — small files with mild compression artefacts. WebP is usually smaller than JPG and works in every modern browser, but older software may not open it.
What DPI should I pick?
96-150 for screen viewing, around 200 for Retina or 4K displays, 300 for regular printing, 600 for press. Starting at 150 and adjusting up if the output looks soft is a safe default.
Why isn't my 600 DPI image 4000+ pixels wide?
Pixel count equals the page size in inches times the DPI. A4 is about 8.27 × 11.69 inches, so 600 DPI yields roughly 4960 × 7016 pixels. If the PDF was scaled or uses a non-standard page size, the numbers shift accordingly.
What does the "Transparent background" option actually do?
When the box is ticked, PDF regions without a fill colour render as transparent pixels. Most office documents have a solid white background fill, so the option has no visible effect for them. It mainly matters for logos, vector graphics, and design files that genuinely have no underlying colour.
Does the tool upload my PDF?
No. Everything is rendered locally with pdf.js. The bytes never reach any server. It works offline, and closing the tab releases the in-memory copy.
Can I convert an encrypted PDF?
No — password-protected PDFs fail during load. Remove the password first using a PDF decryption tool, then come back.
How do I export just one or two pages?
Type the pages into the "Pages to export" field. 3 exports only page 3. 1-3, 7 exports pages 1, 2, 3, and 7. Leave the field blank for the whole document.
Can I batch-process multiple PDFs at once?
The current version handles one PDF at a time. Upload them one by one — each run produces its own ZIP.
Can the resulting images be compressed further?
Yes. The tool has no built-in second-pass compression, but the images go straight into the image compression and image conversion tools on this site if you want to push the size down further.
Why is my scanned PDF blurry after conversion?
A scanned PDF is already a raster image — its resolution is locked in by the original scan. Asking the tool for 600 DPI does not invent extra detail; it just makes the file bigger. Scan at the right resolution first, then convert at a matching DPI here.
Will page order and orientation match the original?
Yes. Pages come out in pdf.js page order, and rotated pages render the way you see them in a viewer — the tool doesn't silently rotate or reorder anything.
How large a PDF can I convert?
There's no hard limit, but browser memory is the real constraint. A few tens of megabytes at 300 DPI is fine; multi-hundred-megabyte scans or thousand-page documents are best converted in ranges.
Does it work on mobile?
Yes — iOS Safari and Android Chrome both work. Mobile RAM is tighter, so 50+ MB scans or 600 DPI runs can fail. Stick to PNG / JPG at 150 DPI on phones.
Is the output identical to Adobe Acrobat's image export?
Not bit-for-bit. pdf.js and Acrobat differ in anti-aliasing, font substitution, and sub-pixel handling. Differences are usually invisible to the eye but can show up with unusual embedded fonts or complex vector art.
How does this compare to SmallPDF, iLovePDF, or Adobe Acrobat?
The biggest difference is where it runs: locally, in your browser, via pdf.js — bytes don't leave your device, which matters for sensitive material. Online services typically upload to their servers and send images back; you pay for network speed and accept their privacy terms. Feature-wise, this tool focuses on PDF → image only — no OCR, no PDF-to-Word — but you can pair it with the PDF split, merge, organize, and watermark tools on this site.
Related tools
Converting a PDF to images is often a step in the middle. Pair it with image compression to shrink the output, image conversion to switch to WebP or AVIF, or the PDF split, merge, and organize tools if you also need to edit the original.