What is PDF to Image?
Extracting pages from a PDF into shareable images is surprisingly tedious. Our tool uses PDF.js to render each page of your document onto an HTML5 Canvas, allowing you to instantly save them as high-res JPGs or PNGs. Because it happens client-side, your document is never transmitted anywhere.
A note about file privacy
PDF to Image is built to handle your file entirely in the browser. You can confirm the data path in DevTools: during processing, your file should not show up as a network upload request. For the broader risks of fake or untrusted converters, see theFBI Internet Crime Complaint Center warning.
Treat PDF to Image like a small desktop utility, not an upload service. Your browser may fetch the code needed to do the work, but the selected file stays in local memory while it is processed. That is why the Network panel is worth checking whenever the file is confidential.
- Before processing: strip metadata, comments, and form fields you would not want shared, since these can carry author names, paths, and internal notes into the output.
- While processing: watch the Network tab. A library download is expected; a request carrying your file bytes is an upload.
- After downloading: scan unfamiliar results before opening them. A file that looks converted can still be malicious.
Supporting guidance: Malwarebytes on malicious converters andKaspersky's safe conversion guidance.
Deep Dive: PDF to Image
Related Articles
Learn more about this tool and related topics in our blog.
Why Developers Prefer Offline File Tools in 2026
Privacy isn't a perk, it's a requirement. See why top developers are ditching cloud converters for local-first browser utilities.
How Browser-Based File Tools Work (WebAssembly Explained)
Peek under the hood of Filemint. A practical look at WebAssembly, Web Workers, and the browser APIs behind our private file tools.
How to Process Files Privately Without Uploading Them
Your files stay on your device. This guide explains how Filemint processes them in the browser instead of sending them to a server.
“”
Azeem Mustafa
Privacy Architect
Core Capabilities
- Convert PDF pages to PNG, JPEG or WebP format
- Resolution control: 72, 96, 150 or 300 DPI output
- Quality slider for JPG and WebP compression
- Convert all pages, a custom range, or specific pages
- Download single images or all pages as a ZIP archive
- Instant in-browser rendering, no server, no uploads
- Filmstrip thumbnail grid with per-page download buttons
- Works offline after initial page load
Why It Matters
- Privacy first: your PDF remains locally on your computer.
- High fidelity: up to 300 DPI for print-quality images.
- Flexible: pick exactly the pages you need.
- Fast: no server upload queue, renders instantly on your machine.
Quick Start Guide
Drop your PDF: Drag and drop your PDF file onto the upload area or click to browse your computer.
Choose format & DPI: Select PNG for lossless quality, JPEG or WebP if you need smaller file sizes. Set the resolution: 72 DPI for quick screens, 150 DPI for high quality, 300 DPI for print.
Pick pages: Convert all pages at once, enter a range like 2-8, or list specific pages like 1, 3, 5.
Convert: Click "Convert to Images" and watch each page render in real time with a progress indicator.
Download: Click any thumbnail to open the full-size preview, then download that page, or download all pages as a ZIP with one click.
Usage Examples
Export a slide at 300 DPI as PNG
Scenario 01A clean slide with text and a chart, saved for printing or for a high-quality handout.
PDF page 5, single page selected
page-5.png, 2480 x 3508 px, 300 DPI, lossless PNG
A scanned page to JPEG
Scenario 02A photo-like scan where file size matters more than perfect pixels. JPEG keeps it small.
PDF page 1 of 12, range 1-1, quality 80
page-1.jpg, 1275 x 1650 px, 150 DPI, ~280 KB
Batch export a report as WebP
Scenario 03Twenty pages turned into web-ready images for a site, with smaller files than JPEG at the same look.
PDF, all 20 pages, WebP quality 85
page-01.webp... page-20.webp, ZIP archive, ~4 MB total
Zip a whole deck at 150 DPI
Scenario 04Every slide as a PNG inside one archive, ready to share or back up.
PDF, pages 1-10, PNG 150 DPI
pdf-pages.zip containing page-01.png... page-10.png
Common Scenarios
Turn a slide into a shareable image
You built a deck in a PDF and want one slide as a picture for a message or a post. Export that single page at 150 DPI as PNG and drop it anywhere.
Send a document page by email
Some email apps choke on PDFs or block them. A JPEG of the page almost always goes through, and it is small enough to attach without a second thought.
Print a single page at full quality
You only need one page on paper. Render it at 300 DPI so the text and lines stay crisp on the page.
Embed a page in a report or doc
Word processors and note apps take images more happily than PDFs. A PNG keeps the layout exact and lets you crop later.
Post a page on social media
Social sites love images and often shrink or block PDFs. A WebP or JPEG of the page uploads fast and looks clean in a feed.
Archive a paper as a picture
You scanned a form into a PDF and want a flat copy for your records. PNG keeps every pixel so the archive stays faithful.
Build a presentation thumbnail
A small preview lets viewers scan a stack of PDFs without opening each one. Render at 72 DPI to keep thumbnails light.
Batch export a whole report
You need every page as its own image for a gallery or a course. Convert all pages and download them together as a ZIP.
Questions?
Technical Architecture
How pdf.js rasterizes a page
pdf.js reads the PDF and builds a render task for each page. It paints the page onto an HTML canvas using the 2D context. A canvas is a grid of pixels, so the vector content of the PDF becomes a flat raster image. The viewport sets the size in pixels at the PDF's base of 72 DPI, and a scale factor grows that to your chosen DPI.
DPI to pixel math
A PDF page is described at 72 units per inch. To render at a target DPI, multiply the page size in inches by that DPI. A US Letter page is 8.5 x 11 inches, so at 300 DPI it becomes 2550 x 3300 pixels. The scale factor passed to pdf.js is your DPI divided by 72, so 300 DPI uses a scale of about 4.17.
Canvas and the output file
Once the page is on the canvas, the tool calls the canvas toDataURL or converts it to a blob. PNG uses lossless compression, JPEG uses lossy compression with a quality slider, and WebP supports both plus transparency. The blob is then offered as a download.
Everything stays on your device
The PDF is loaded from your file picker into browser memory. No part of the file is sent to a server. This local-only path avoids the upload, processing, and retention steps that a cloud converter has to perform.
What ISO 32000 means here
PDF is defined by the ISO 32000 family of standards. ISO 32000-2:2020 (PDF 2.0) is the current core spec, available at no cost from the PDF Association. It describes the page model that pdf.js reads, so a conforming PDF renders the same way across viewers.
Text becomes pixels
After rasterization, the words on the page are no longer selectable text. They are painted pixels. If you need the words as editable text instead of a picture, use the PDF to text tool before or instead of converting to an image.
Pick the format that fits what you are doing. PNG keeps every pixel and transparency. JPEG stays small. WebP does both and tends to be smaller still.
| Feature | PNG | JPEG | WebP |
|---|---|---|---|
| Compression | Lossless | Lossy | Both |
| Transparency support | |||
| Best for text and charts | |||
| Smallest file size | |||
| Wide compatibility |
Same page, same format. Higher DPI means more pixels and a bigger file. Numbers are typical for a text and chart page saved as PNG.
Load PDF
In your browser
Render page
pdf.js to canvas
Save image
PNG/JPEG/WebP
Choosing the right DPI
DPI stands for dots per inch, and it tells the renderer how many pixels to pack into each inch of the page. A PDF is built at 72 units per inch, so the base render is already 72 DPI. When you ask for 300 DPI, the tool scales that up by about 4.17 times. The math is simple: width in inches times DPI equals pixels across. A Letter page at 300 DPI is 2550 x 3300 pixels.
Higher is not always better. If the image will only ever sit in a chat or on a web page, 150 DPI looks clean and keeps the file small. Save 300 DPI for print and for times you expect someone to zoom in. If your device feels slow on a big job, drop the DPI before you drop pages.
When you are done here, a few related tools are worth a look. Pull the words out first with the PDF to text tool, shrink the source with PDF compress, or tune the result with the image compressor and image resizer. Our best image formats for the web in 2025 guide explains when WebP beats PNG and JPEG, and the client-side processing and privacy guide covers why keeping files on your device matters under the GDPR.
Why render in the browser at all
The short version is trust. When a PDF leaves your machine, you are asking a stranger to hold your data, even for a minute. Cloud converters also set limits, add watermarks, or keep files for a while before deletion. Doing the work locally with pdf.js from Mozilla sidesteps all of that. The page is painted on a canvas and saved by you, with no middle step.
If you want to go deeper, the PDF Association on ISO 32000-2 explains the standard that defines how a PDF page is built, and ISO 32000-2:2020 at ISO is the official listing. For the privacy side, the GDPR text from the EU sets out the rules on personal data, and the Adobe JPEG vs PNG guide breaks down the format tradeoffs in plain terms.
Keep Exploring
Power up your workflow with related utilities.
Related Tools
PDF to Text
The professional choice for document recovery. Pull text from research papers, legal briefs, and reports locally in your browser without ever uploading a file.
Use free →PDF Split
Upload a PDF, specify page ranges like 1-3,5, and download a new PDF containing only those pages or individual page files.
Use free →Image Compressor
Compress your images locally in your browser. Reduce file sizes for JPG, PNG, and WebP images without noticeable quality loss.
Use free →Related Articles
Learn more about this tool and related topics in our blog.
Why Developers Prefer Offline File Tools in 2026
Privacy isn't a perk, it's a requirement. See why top developers are ditching cloud converters for local-first browser utilities.
How Browser-Based File Tools Work (WebAssembly Explained)
Peek under the hood of Filemint. A practical look at WebAssembly, Web Workers, and the browser APIs behind our private file tools.
How to Process Files Privately Without Uploading Them
Your files stay on your device. This guide explains how Filemint processes them in the browser instead of sending them to a server.
Founder & Lead Developer at FileMint
Building privacy-first browser tools powered by WebAssembly. Focused on making file processing fast, secure, and accessible — without ever uploading your data to a server.
View full profile →