PDF to Images

How PDF to Images Works

ConvertUnlimited uses PDF.js, a powerful rendering library developed by Mozilla, to decode PDF documents directly in your browser. Our tool iterates through every page of your PDF, draws it onto an HTML5 Canvas at your selected resolution (scale), and then exports that canvas as a high-quality image file.

Because the rendering happens entirely on your own device's CPU and RAM, selected document contents are processed locally in your browser. This local-first approach provides local browser-based processing and allows for fast extraction of pages even from large PDF files.

When to Convert PDF Pages to Images?

• Social Media Sharing: Easily post specific pages of a report or document as images on platforms that don't support PDF uploads.
• Web Presentations: Embed document pages directly into blog posts or websites as standard image files for better browser compatibility.
• Extracting Content: Quickly grab a specific graph, chart, or text section from a long PDF without needing complex PDF editing software.
• Organization: Bundle extracted pages as a ZIP for easy archival or distribution.

Resolution, render scale, and DPI math

PDF pages are defined in points, where 1 point equals 1/72 inch. PDF.js renders at a scale you choose, where scale 1 means one rendered pixel per PDF point — so scale 1 corresponds to roughly 72 pixels per inch (PPI) of the page's physical size, scale 2 to roughly 144 PPI, and scale 3 to roughly 216 PPI. An A4 page (595 × 842 pt) rendered at scale 2, for example, produces a canvas of about 1190 × 1684 pixels; the same page at scale 3 produces about 1785 × 2526 pixels.

Use Standard for mobile-friendly thumbnails, High for readable text and clear photos on screen, and Extra High for print or detailed diagrams where individual pixels matter. Because PDF pages are vector-based, choosing a higher scale re-renders the page at more pixels rather than upscaling a fixed bitmap, so text and vector graphics stay sharp at any of the three settings; only embedded raster images in the source PDF are limited by their own original resolution.

What PDF.js does when rendering

This tool uses PDF.js (version 3.4.120), Mozilla's PDF renderer, to parse and draw each page onto an HTML5 canvas at the chosen scale; canvas.toBlob() then exports that canvas as JPG, PNG, or WebP. JPG and WebP are written at a fixed 92% quality; PNG output is always lossless. Pages are processed and exported one at a time, so peak memory during rendering is limited to roughly one page's canvas rather than the whole document at once — the tool holds compressed image blobs for finished pages, not their raw canvases.

Failure modes and limits

• Encrypted or password-protected PDFs. This tool currently does not implement a password-entry prompt: pdfjsLib.getDocument() is called without a password callback, so an encrypted source fails to load with a generic error rather than asking for a password. Decrypt the file first with a dedicated tool.
• Very large page counts. Rendering itself is lean per page, but the "Download All (ZIP)" step holds every page's exported image in memory at once while it builds the archive, so converting hundreds of pages at Extra High scale can use significant memory right before the ZIP download starts.
• Mobile devices. Phones and tablets have less available memory and are more likely to struggle with Extra High scale across many pages; Standard or High scale is more reliable on mobile.
• PDFs with no extractable page content, or corrupted files. A damaged or non-standard PDF can fail a given page's render; the tool reports that specific page as failed and continues with the rest.

Frequently Asked Questions

Can I convert encrypted PDFs?

Not currently. This tool does not implement a password-entry prompt, so a password-protected PDF fails to load with a generic error. Decrypt the file with a dedicated tool before converting it here.

Will my images lose quality?

JPG and WebP are exported at a fixed 92% quality; PNG export is lossless. Because PDF pages are vector-based, choosing a higher render scale (High or Extra High) produces genuinely more pixels for text and vector content rather than upscaling — embedded raster images in the source are the exception, since they cannot exceed their own original resolution.

What does render scale actually change?

Scale sets pixels rendered per PDF point (1 point = 1/72 inch): scale 1 is roughly 72 PPI, scale 2 roughly 144 PPI, scale 3 roughly 216 PPI. Higher scale means a larger output image and a longer render time per page, not a different crop or format.

Can I extract only some pages?

Yes. Set the "Page from" and "Page to" fields before converting to render only that range instead of the whole document.

Which output format should I choose?

JPG is usually smallest for photographic scans. PNG is lossless and better for text-heavy or diagram pages where sharp edges matter. WebP is a middle ground: often smaller than JPG at comparable quality, with broad but not universal support in older software.

Does converting change the page size or orientation?

No. Each page renders at the dimensions and orientation defined in the source PDF; the tool does not normalize pages to a common size.

What happens with very large or many-page documents?

Pages render and export one at a time, so per-page memory use stays modest. The "Download All (ZIP)" step is the exception: it holds every exported page in memory while building the archive, which is the most likely point to strain memory on a long document.

Browser Support

This tool works in all modern browsers supporting the HTML5 Canvas API and WebAssembly, including Chrome, Firefox, Safari, and Edge.