PDF to Image

Share:

Convert PDF pages to JPG or PNG images in your browser. Choose pages, DPI, and format.

RT-IMG-007 · Image & File

PDF to Image

Ready — drop a PDF to begin.
🔒 PDFs stay on your device. Rendering happens entirely in your browser via the self-hosted pdf.js library — nothing is uploaded.
Advertisement
After results · AD-W1 Responsive · Post-tool — peak engagement

How to convert PDF pages to images

Drop your PDF

Drag a PDF onto the dropzone or click to choose one. The file loads into pdf.js — Mozilla's open-source PDF renderer — entirely in your browser. The status line shows total pages and file size once loaded.

Pick page range and format

Leave the Pages field blank to render every page, or type a range like 1-5 or 1,3,7-9. JPG is the universal default. PNG preserves transparency and detail (bigger files). WebP is the modern small-file alternative.

Set DPI

72 DPI matches what's displayed on screen (smallest files). 150 DPI is sharp for thumbnails and previews. 300 DPI matches print quality (largest files — use sparingly for many-page conversions). Higher DPI = larger image dimensions and more memory.

Convert and download

Click Convert pages. Each rendered page appears as a thumbnail with a per-file Download button, or use Download all to save everything at once. Files are named filename-page-NNN.jpg so they sort correctly.

Advertisement
After how-to · AD-W2 Responsive

PDF to image — when raster beats vector

A PDF is fundamentally a vector document: text and graphics are described mathematically, not as pixel grids. That's why PDF is great for printing (scales to any size without losing quality) and good for screen reading (fonts stay crisp at any zoom). But sometimes you need a PDF page as a flat image — for embedding in a slide deck, posting on social media, attaching to a CMS that doesn't accept PDFs, or saving a snapshot that's hard to edit. This conversion is technically called "rasterising" — turning vector instructions into a fixed pixel grid. Once a page is rasterised, the embedded text is no longer selectable and the file size depends entirely on dimensions and compression, not the original document complexity.

The pdf.js story

pdf.js is the PDF rendering engine that ships inside Firefox — Mozilla open-sourced it in 2011 specifically so browsers wouldn't need Adobe's plugin. The same code now powers PDF preview in Chrome (via PDFium, derived from pdf.js work), Edge, Safari, and almost every JavaScript-based PDF tool. It's about 1.5 MB compiled and handles the same PDF spec as Adobe Acrobat — every feature from forms to fonts to embedded JavaScript. This tool uses pdf.js to render each page onto an HTML canvas, then the canvas is exported as JPG or PNG. The entire pipeline runs in your browser tab; nothing touches our servers.

At 300 DPI, a single A4 PDF page renders to roughly 2480×3508 pixels — about 8.7 megapixels per page. A 50-page PDF at 300 DPI generates ~430 megapixels of image data — handle with care on phones.

DPI — the only setting that matters most

DPI ("dots per inch") controls how detailed the rasterised image is. Standard screens display at 72-110 DPI; mobile retina displays at ~330 DPI; print at 300-600 DPI. For most web uses (CMS embeds, social posts, slide decks), 150 DPI is plenty — the resulting image is sharp on retina screens at the document's intended display size and stays reasonable in file size. Bump to 300 DPI only if you'll print the output or need detail (small text legibility, fine-grained diagrams). Going above 300 DPI is rarely worth the file-size cost unless the document is meant to be enlarged.

JPG vs PNG vs WebP for PDF pages

JPG works for almost everything but introduces lossy compression artefacts around sharp text and lines — usually invisible at 85%+ quality. PNG preserves every pixel exactly (no artefacts) but files are 2-4× larger; use for documents with lots of fine text or screenshots where text legibility matters. WebP at quality 80 typically matches JPG quality at 85 with 30% smaller files — the modern default for any context where you control the consuming software.

The APAC document-conversion landscape

PDF-to-image conversion is a daily operation in many APAC workflows. India, Bangladesh, Indonesia, Vietnam, Philippines see massive use in government and education sectors — Aadhaar, NIC, student ID cards, exam certificates all arrive as PDFs but get embedded into systems that require JPG/PNG. China has its own PDF rendering ecosystem (WPS Office dominates over Adobe) but the conversion need is identical; Tencent Docs and DingTalk both ship in-app PDF-to-image converters. Singapore, Hong Kong, Malaysia, Australia, New Zealand commonly need this for financial services: turning bank statements, invoices, and tax forms into images for ticketing systems and back-office workflows that don't render PDF inline. Japan and South Korea have strong scan-then-process cultures — paper documents become PDFs become images become OCR-ready inputs for ERP systems. Thailand's growing e-commerce sector needs PDF receipts converted to images for messaging platforms (LINE, Facebook Messenger) that compress better than PDFs. Across the region, the common pattern is the same: someone has a multi-page PDF, someone else's system accepts only images, and the conversion has to happen without uploading sensitive content to a stranger's server.

What this tool doesn't do

It doesn't OCR — if your PDF is a scan of a handwritten letter, the output is still a picture, not editable text. It doesn't preserve PDF layer information (the rasterised image flattens everything). It doesn't read text from password-protected PDFs (decrypt first in Adobe Reader). It doesn't crop, rotate, or composite multiple pages onto one image. For those operations, render the pages here, then process the JPGs in our Image Format Converter, our Watermark Maker, or a dedicated tool.

10 Things You Didn't Know About PDF Rendering

01

Mozilla released pdf.js in 2011 — it's now the PDF engine in Firefox, and most browsers' built-in PDF viewers are derivatives of it.

02

Chrome's PDFium is a Google fork of Foxit's older PDF engine, not pdf.js — but both convergently implement the same PDF/ISO 32000 standard.

03

72 DPI is the "screen standard" because that was the resolution of the original Apple Macintosh display in 1984.

04

An A4 page at 300 DPI renders to 2480 × 3508 pixels — about 8.7 megapixels, comparable to a mid-range smartphone photo.

05

PDF/A (the archival standard) requires all fonts to be embedded so the document renders identically 50 years from now — even after the original fonts are extinct.

06

PDF supports vector and raster content in the same page — text and lines are vector, photos are embedded raster. Conversion turns it all into one big raster image.

07

Adobe Acrobat's "Export PDF to JPG" feature uses the same rendering engine as Acrobat's screen display — exactly what pdf.js replicates in the browser.

08

The CSS pixel density on retina displays is reported as 1, but each CSS pixel is 4 physical pixels (2×2) — meaning what looks like 150 DPI is actually rendering at 300+ DPI on screen.

09

PDF text is stored with positioning down to 1/1000th of a point — that's why text in a rendered PDF image looks subtly different from the same text typed fresh in an image editor.

10

Rendering a 1000-page PDF in pdf.js takes about as long as scrolling through it in Acrobat — both are bottlenecked by the same vector-to-raster math.

FAQ

  • No — pdf.js runs in your browser, the canvas runs in your browser, the resulting JPG/PNG/WebP is generated in your browser. Nothing touches RECATOOLS servers. Verify in DevTools → Network: zero outbound requests when you convert.

  • 72 for thumbnails. 150 for web (default). 300 for print or sharp on-screen detail. Above 300 only for very small text on documents you'll enlarge. Higher DPI = bigger files and more browser memory — slow on phones.

  • Currently no — pdf.js requires the password to decrypt the content stream before rendering. Remove the password first in Adobe Reader/Preview/Acrobat, then upload here.

  • Soft limit only — your browser's memory. Hundreds of pages at 150 DPI is fine on a desktop browser. Phones may struggle past ~50 pages at high DPI. If your browser hangs, retry with a smaller page range or lower DPI.

  • No — rasterised text is just pixels. If you need selectable text in the output, you need OCR (optical character recognition), which this tool doesn't include. For OCR, look at Tesseract.js or Adobe Acrobat.

  • Same as printing: 1 single page, 1-5 range, 1,3,5 list, 1-3,8,10-12 mix. Blank field or "all" = every page.

  • PNG is lossless — every pixel preserved exactly, no quality knob to turn. Quality only matters for lossy formats (JPG, WebP). PNG file size depends on image complexity and dimensions, not a slider.

  • WebP at quality 80 typically produces files 25-35% smaller than JPG at 85 with no visible quality loss. Use WebP if you control where the image will be consumed (your own website). Use JPG for maximum compatibility (email, third-party CMS, anything older than 2020).

  • Yes on iOS Safari and Chrome on Android. Tap "Choose file" rather than drag-and-drop. Keep DPI at 100-150 on phones — 300 DPI on a 50-page PDF will likely crash the tab.

  • Not in this version — one PDF at a time. For multi-PDF workflows, merge the PDFs first using our PDF Merger, then convert the merged result here.

Related News

You may be interested in these recent stories from our newsroom.

View all news →
Advertisement
Pre-footer · AD-W3 728 × 90

75 more free tools

Calculators, converters, security tools — no signup.