Free PDF to Image Converter

How It Works

1. Upload PDF: Drop or select a PDF file to convert.
2. Preview & Configure: See page thumbnails and choose format (PNG/JPG), scale (1x to 2x), and JPG quality.
3. Convert: Click "Convert All Pages" to render each page as an image. Single pages download directly; multiple pages download as ZIP.

Why Convert PDFs to Images?

Converting PDFs to images is useful for creating visual content, making documents easier to share on social media, embedding pages in presentations, or preserving documents as standalone images. Images are also lightweight and universally supported across all devices and platforms.

Features

• Multiple Formats: Export as PNG (lossless) or JPG (compressed).
• Flexible Scaling: Choose 1x, 1.5x, or 2x scale for the image quality you need.
• Quality Control: Adjust JPG quality from 60 to 100 percent to balance file size and appearance.
• Batch Downloads: Convert all pages at once. Single pages download immediately; multiple pages zip automatically.
• Privacy: All processing happens locally in your browser. Files never uploaded to any server.
• Fast: Real-time rendering with no waiting or queues.

Frequently Asked Questions

What's the difference between PNG and JPG?

PNG is lossless (no quality loss) and better for documents with text or diagrams. JPG is compressed and produces smaller files, ideal for photo-heavy PDFs. JPG offers quality adjustment (60 to 100 percent); PNG is always full quality.

What does the scale option do?

Scale increases the resolution of the rendered images. 1x uses the PDF's native resolution; 2x doubles it for sharper text and details. Higher scales produce larger files but better visual quality.

Can I download a single page?

Yes. Single-page PDFs download directly as an image file. Multi-page PDFs download as a ZIP archive containing all pages numbered sequentially (page-1.png, page-2.png, etc.).

What's the file size limit?

PDFs up to 50 MB are supported. Conversion speed depends on page count and scale; large PDFs may take a few moments to process.

Are my PDFs uploaded to a server?

No. All conversion happens locally in your browser using PDF.js. Your PDFs never leave your device, ensuring complete privacy and security.

Can I convert on mobile?

Yes. This tool works on desktop, tablet, and mobile browsers. Just tap to select a PDF and customize your conversion settings.

What "PDF to image" actually means

A PDF is a vector document. The text it contains is stored as character codes plus font resources, not as pixels. The vector graphics (lines, curves, fills) are stored as drawing operators in the content stream, not as pixels. Only the embedded photographic images are stored as compressed pixel arrays. When a viewer renders the PDF, it walks the content stream, draws the text and vector graphics to a pixel surface at a chosen resolution, and composites the embedded raster images on top. Converting a PDF to an image means picking a resolution, asking the renderer to produce a pixel surface of that size for each page, and writing the surface out as a PNG or JPEG file.

The output is a raster image: a fixed grid of pixels with no underlying text or vector data. The text is no longer selectable, the vector graphics no longer scale without aliasing, and the file size is determined entirely by the resolution and the format's compression efficiency. This is a one-way transformation: once rasterised, the document cannot be converted back to a vector PDF without an OCR or vectorisation pass that infers the structure from the pixels. Use PDF-to-image when you need the visual content as an image (for social media, presentations, blog posts, OCR feed-in) and accept that selectable text and scalable vectors are not part of the deal.

How this tool renders

This tool uses Mozilla's pdf.js, the same JavaScript PDF renderer that powers Firefox's built-in PDF viewer. The pipeline has four stages. First, the source PDF is read into the browser tab through the standard File API; no network traffic is generated. Second, pdf.js parses the document's cross-reference table and constructs an in-memory model of the pages, fonts, and embedded resources. Third, for each page, the tool calls page.getViewport({scale}) to compute the pixel dimensions at the chosen scale, allocates an HTML5 canvas of that size, and calls page.render({canvasContext, viewport}) to draw the page into the canvas.

Fourth, the canvas's toBlob() method produces a PNG or JPEG image, which is offered as a download or packaged into a ZIP through JSZip when there are multiple pages. The whole pipeline runs in your browser's tab; nothing is uploaded. The CDN load of pdf.js and JSZip when the page first opens is the only network traffic; after that, the conversion is fully local.

The scale parameter and what it means in DPI

The scale parameter controls output resolution. pdf.js measures PDF pages at a base scale of 1.0, which corresponds to 96 DPI (the CSS pixel definition). Scale 1.0 produces a canvas matching the original PDF's physical size on a 96-DPI screen. Scale 2.0 doubles both width and height, producing a canvas with four times the pixel count. A US-letter page (8.5 x 11 inches) at scale 1.0 is 816 x 1056 pixels; at scale 2.0, it is 1632 x 2112 pixels.

The mapping to print DPI is straightforward: scale 1.0 is approximately 96 DPI, scale 1.5 is 144 DPI, scale 2.0 is 192 DPI. Most workflows map cleanly onto these ranges:

• 72 to 96 DPI (scale 1x): web and screen quality. Adequate for thumbnails, blog illustrations, social media previews, and email attachments.
• 150 DPI (between 1x and 2x): standard archival quality. Good for on-screen reading, document repositories, OCR feed-in, and most office printing.
• 192 DPI (scale 2x): retina display quality. Sharp text on high-DPI laptop and phone screens, acceptable for general-purpose printing.
• 300 DPI and above: professional print quality. Not directly available in this tool; use a desktop tool (Adobe Acrobat Pro, pdftoppm with -r 300, or ImageMagick with -density 300) for print-final output.

Format choice: PNG versus JPG

PNG is lossless. Every pixel the renderer produces is encoded exactly, with no quality reduction. The compression is similar to ZIP: efficient for images with large flat regions, repeating patterns, or sharp edges, less efficient for photographic content. PNG also supports transparency. JPEG is lossy: the compression discards high-frequency detail that the human eye does not perceive, producing smaller files at the cost of visible artefacts around sharp edges and high-contrast regions. The quality slider controls the trade-off: 100% produces near-lossless output 3 to 5 times larger than 60% output; 60% output is much smaller but shows visible ringing around text.

The decision rule for almost every PDF: if the page is text, diagrams, charts, or line art, use PNG. The sharp edges of text and vectors produce ringing artefacts in JPEG that are obvious even at high quality, and PNG's lossless compression handles flat regions (white backgrounds, solid fills) extremely efficiently, so the file size penalty is smaller than the general rule of thumb suggests. If the page is photographic (a scanned magazine spread, a photo album, a brochure with large product photos), use JPEG at 85 to 90 percent quality. If the document mixes the two, PNG is the safer default because text artefacts are obvious while photo artefacts are subtle.

Real-world workflows that drive PDF-to-image conversion

• Social media and web publishing. Sharing a PDF on Twitter, LinkedIn, or a blog post requires converting at least the cover page or key spreads into images, because the platforms do not embed PDFs as inline previews. Marketing teams convert PDF reports, white papers, and case studies into image previews; book publishers convert the cover and a sample spread of an e-book to PNG for the product page. PNG at scale 1.5x to 2x is the typical choice.
• Presentations and slide decks. PowerPoint, Keynote, and Google Slides can embed images but not PDF pages directly. Anyone preparing a slide that needs a figure, chart, or excerpt from a PDF will convert the relevant page first. PNG is preferred because the figure typically contains text or vector content that JPEG would compromise.
• OCR feed-in. Some optical-character-recognition pipelines work better on rasterised images than on PDFs with already-extracted text layers. The workflow is to rasterise the PDF at 150 to 300 DPI, run OCR on the resulting images, and either use the OCR text directly or feed it back into a new PDF with the OCR'd text as a hidden layer.
• Court and legal evidence. Exhibits filed in jurisdictions where the court's case-management system accepts only image formats need PDF-to-image conversion before upload. Each page becomes an individual image, named with the exhibit number and the page number, packaged into a ZIP for upload.
• Accessibility and archival. Some institutional repositories require that long-term archival copies of documents be stored in a raster format (PNG or TIFF) in addition to the original PDF, on the theory that the PDF format may eventually become unreadable but the raster will always be. A controversial archival strategy, but the practice exists at scale.
• Email and chat attachments. Some corporate email or chat clients strip or block PDF attachments for security reasons but allow images. Converting the PDF to PNG before sending is the standard workaround.

Common pitfalls and workarounds

• File size grows quadratically with scale. Doubling the scale quadruples the pixel count, which roughly quadruples PNG file size and triples JPEG file size. A 20-page PDF at scale 2x PNG can easily produce a 50 to 100 MB ZIP. The practical upper limit on input PDF size scales inversely with the chosen output resolution. If the ZIP is too large, drop to scale 1x or 1.5x, or switch to JPEG.
• Text becomes uneditable. After rasterisation, the text is pixels. Copy-paste no longer works, screen readers no longer announce the content, and search-within-document fails. If the use case needs selectable text after the round trip, run OCR on the output images, which introduces its own error rate.
• Transparency is lost in JPEG. PDFs can contain pages with transparent backgrounds (typically a watermark layer or an overlay graphic). JPEG flattens transparency to a solid background colour, typically white. PNG preserves it. If the document has transparency that matters to the output, choose PNG.
• Vector graphics pixelate under enlargement. The original PDF can be zoomed indefinitely without losing crispness, because the renderer rasterises afresh at each zoom level. The output image is fixed at its rendered resolution; zooming beyond 100 percent displays pixels rather than re-computed graphics. For any workflow where the consumer might zoom in (large monitors, projectors, print enlargements), pick the highest scale that fits in memory.
• Browser-to-browser antialiasing differences. Different browsers apply slightly different text antialiasing strategies in their canvas implementations. The same PDF rendered at scale 2x in Chrome, Firefox, and Safari produces visually similar but not pixel-identical output. For most use cases the differences are invisible; for forensic or archival applications where exact reproducibility matters, server-side rendering with a fixed renderer (Ghostscript, pdftoppm) is the better choice.
• Encrypted PDFs cannot be parsed. A PDF with an open password cannot be read by pdf.js until the password is supplied. This tool does not currently expose a password prompt. The workflow is to unlock the PDF first through the PDF Unlock tool, then convert the unlocked copy.

Why the output is the size it is

Output file size depends on three factors: page count, chosen scale, and the format's compression efficiency. For a typical text-and-diagram PDF page, PNG at scale 1.0 is roughly 50 to 200 KB per page, PNG at scale 2.0 is 200 to 800 KB per page, JPEG at quality 85 percent and scale 1.0 is 30 to 80 KB per page, and JPEG at the same quality at scale 2.0 is 100 to 300 KB per page. Photo-heavy pages produce larger files in both formats, with JPEG maintaining a 3 to 5 times advantage over PNG. A 100-page PDF converted at scale 2x PNG can produce a 20 to 80 MB ZIP; the same PDF at scale 1x JPEG 85 percent produces a 3 to 8 MB ZIP. Most users want something in between, which is why scale 1.5x at JPEG 85 percent is the de-facto sensible default for general use.

Browser-only versus cloud conversion

The cloud PDF-to-image converters that fill the top of search results (Smallpdf, ILovePDF, Adobe Acrobat Online, PDF24, Sejda, PDF2Go) all upload your source PDF to their servers, run conversion through server-side renderers (typically Ghostscript or proprietary libraries), and serve the output as a ZIP download. Their privacy policies state uploaded files are deleted within a few hours, but the files transit the operator's network, exist on their disks for the processing window, and pass through whatever logging the operator maintains for abuse detection. Free tiers cap the number of operations per day; paid tiers remove the cap.

This tool does not upload. Your PDF is read into the browser tab through the standard File API, parsed and rendered by pdf.js in the same tab, and the output ZIP is assembled locally by JSZip before being saved to disk through the download API. You can verify it: open the browser's developer tools to the Network tab, run a conversion, and watch that no requests fire with your file content. The trade-off is rendering capability: pdf.js handles the vast majority of real-world PDFs correctly, but the server-side renderers have access to mature commercial libraries that handle some edge cases better (unusual font encodings, complex overlapping transparency groups, rare PDF features). For 95 percent of input PDFs, the output is interchangeable; for the remaining 5 percent, the cloud services have an advantage.

More frequently asked questions

Can I get 300 DPI output for print?

Not directly. The tool's maximum is scale 2x, which corresponds to approximately 192 DPI. For 300 DPI output, the right options are a desktop tool (Adobe Acrobat Pro's Export to Image, pdftoppm with -r 300, or ImageMagick with -density 300) or a cloud service that exposes arbitrary-DPI rendering (Adobe Acrobat Online, Smallpdf paid tier). For most workflows that are not strictly print-final, scale 2x is sufficient: 192 DPI is sharp enough that the difference from 300 DPI is invisible at normal viewing distances.

Can I select specific pages to convert?

Not in this tool directly. Use the PDF Split tool first to extract the pages you want, then run the conversion on the extracted PDF here. Page selection in a single step is a planned feature; for now, the two-step workflow handles the use case.

Why does the output look different from what Adobe Acrobat produces?

The tool uses pdf.js, the JavaScript renderer Firefox uses for its built-in PDF viewer. pdf.js handles 95 percent or more of real-world PDFs identically to Adobe Acrobat. The remaining few percent involve unusual fonts, complex transparency groups, recent PDF features that pdf.js has not yet implemented, or specific colour-management edge cases. For those documents, Adobe Acrobat or a server-side tool will produce more accurate output. For everyday PDFs, the difference is invisible.

Can I OCR the output images?

Not directly in this tool. The output images can be fed into a separate OCR tool (Adobe Acrobat's OCR, Tesseract, online OCR services). Many users do exactly this: convert a scanned PDF to images here, OCR the images elsewhere, then rebuild a searchable PDF with the OCR'd text as a hidden layer. For OCR to work well, render at scale 2x (the closer to 300 DPI you can get, the better OCR accuracy will be).

Why are the colours slightly different from the PDF?

Colour management. PDFs can carry ICC colour profiles that specify how colour values map to screen or print output. The browser's canvas API does not fully implement ICC colour management; the renderer interprets colours as sRGB. For most documents this is invisible; for colour-critical work (graphic design, photography portfolios, print proofing), a desktop tool with proper colour management is the right choice. Adobe Acrobat Pro and Adobe Photoshop's "Save for Web" workflow handle ICC profiles correctly.

Does it work on phones and tablets?

Yes, within the constraints of mobile browser memory. JavaScript heap limits on phones are typically a few hundred megabytes per tab, which is enough for most PDFs but can be exceeded by very large documents at scale 2x. As a rough guide: PDFs under 50 MB convert well on phones at any scale; PDFs over 100 MB may run out of memory at scale 2x and should be converted at scale 1x or 1.5x, or processed on a desktop. The page-by-page processing model means the tab does not load the entire output at once, so memory usage stays roughly proportional to the size of a single rendered page rather than the whole document.

Related Tools