Frequently Asked Questions: PDF to Images

Turning a PDF into a set of images takes under a minute for most documents.

Upload and choose a format
Drag and drop your PDF onto the upload area or click to browse; Google Drive is also supported. One PDF at a time, up to 50MB and 100 pages. Then pick your output format: JPG or PNG.

Convert
Click convert. Each page is rendered server-side at a true 300 DPI, high enough for printing, and the pages appear as previews in your browser as soon as the conversion finishes.

Download
Hover over any page to preview it larger, download single pages individually, or download everything at once as a ZIP file with the images named in page order. No account or email is required; an optional email-delivery choice exists if you want the ZIP sent to an inbox.

Both are rendered from the same 300 DPI source, so the difference is purely in how each format stores the result.

Choose PNG for documents
PNG is lossless: text edges, thin lines, and diagrams stay perfectly crisp with no compression artifacts. The trade-off is larger files, especially for pages containing photographs.

Choose JPG for photos and smaller files
JPG compresses photographic content efficiently, and our quality setting of 95 keeps artifacts barely perceptible. On pages that are mostly text you may notice slight softness around letters if you zoom in, which is normal for JPG.

Rule of thumb
Text, forms, diagrams, anything you might print: PNG. Photo-heavy pages, web use, or email attachments where size matters: JPG. You can convert the same PDF twice with different formats if you need both.

Pages are rendered at a true 300 DPI, and "true" is worth emphasizing: the render scale is computed exactly from the PDF's own page dimensions, so 300 DPI means 300 real dots per inch of page, not an upscaled lower-resolution render.

What that means in pixels
An A4 page (8.27 x 11.69 inches) becomes an image of roughly 2480 x 3508 pixels; a US Letter page becomes about 2550 x 3300 pixels. That is the same resolution print shops typically request, so the images are suitable for printing, archiving, or zooming into fine detail.

Vector content shines
Text and vector graphics in a PDF have no inherent resolution, so rendering them at 300 DPI produces genuinely sharp output. Embedded photos, on the other hand, can only be as sharp as they were in the PDF; rendering cannot invent detail that is not there.

Yes on both counts. The images you download are clean, exactly what was on the PDF page, with no watermark, badge, or footer added, at full 300 DPI resolution.

No sign-up, no paywall
There is no account system, no trial that expires, and no premium tier holding back quality or page count. The real limits are technical: 50MB per file, 100 pages per conversion, and roughly 10 conversions per 15 minutes per user so the service stays responsive for everyone.

Here is precisely how your file is handled, so you can judge for yourself.

Processing and deletion
Your PDF is uploaded over an encrypted HTTPS connection and rendered to images automatically on the server; no person views your document, and document contents are never read for any purpose beyond the conversion, never stored long-term, and never shared. The temporary page images created during processing are removed immediately after the ZIP is built, and all files are deleted from our servers within one hour.

What we measure
We use Google Analytics for aggregate, anonymous usage statistics, like how many conversions ran, never anything involving document contents. No account is needed, and downloading never requires an email address.

Up to 100 pages per conversion, with each page becoming one image file.

Why the limit exists
Rendering at 300 DPI is memory-intensive, roughly 25 megapixels per A4 page, and the limit keeps conversions fast and reliable rather than failing halfway through. If your PDF has more than 100 pages, the tool tells you before doing any work instead of silently truncating.

Converting longer documents
Split the PDF into chunks of up to 100 pages with the BlendPDF split tool, convert each chunk, and you will have a complete image set. The zero-padded filenames within each ZIP keep the ordering unambiguous.

Two ways, and you can use both in the same session.

Everything at once: the ZIP
All pages are packaged into a single ZIP download. Inside, images are named page-001.jpg, page-002.jpg, and so on (or .png), zero-padded so they sort in correct page order in any file manager, which matters once a document passes page 10.

One page at a time
After conversion, every page appears as a thumbnail in the browser. Hover to see a larger preview, and click the download button on any thumbnail to save just that page, handy when you only need page 7 of a 60-page document but want to eyeball the rest first.

There is no page-range picker on this tool; it converts every page of whatever PDF you give it. But you have two practical options.

Option 1: download selectively
Convert the whole document, then download only the individual pages you need from the preview grid. Simple, and fine for short documents.

Option 2: trim the PDF first
For long documents, extract the pages you want using the BlendPDF split tool (or remove unwanted ones with delete-pages), then convert the trimmed PDF. This is faster, keeps you well under the 100-page limit, and produces a ZIP containing exactly the pages you care about.

Yes, and this is one of the tools where Arabic support is at its strongest, for a structural reason worth understanding.

Rendering does not touch the text
Converting a page to an image is a visual snapshot: the renderer draws the page exactly as a PDF viewer would, then saves the pixels. There is no text extraction, no reordering, and no reflowing, which are the steps where right-to-left text goes wrong in other tools. Arabic, Hebrew, Persian, and Urdu pages come out looking exactly like the original, ligatures and all.

One caveat about fonts
If the PDF did not embed its fonts, the renderer substitutes standard ones, which can subtly change letterforms. Nearly all professionally produced PDFs embed their fonts, so this is rare in practice, but it is the one case where the image may differ slightly from what you see in a viewer using the same missing font.

Yes. Unlike our PDF to Word and PDF to Excel tools, which need a text layer and therefore cannot handle scans (there is no OCR yet), converting to images works perfectly on scanned PDFs, because a scan is already an image wrapped in PDF pages.

Quality expectations
The output mirrors the original scan. If the document was scanned at 200 DPI, rendering at 300 DPI will not add detail; you will get a faithful copy of what the scanner captured, slightly resampled. Crooked or dark scans stay crooked and dark, since this tool reproduces pages rather than enhancing them.

A common use case
Extracting scanned pages from a PDF back into standalone image files, for example to re-crop them, run them through an external OCR tool, or insert single pages into a presentation, is exactly what this tool is for.

No. This is inherent to the format, not a limitation we could toggle off: JPG and PNG files contain pixels only. Once a page becomes an image, there is no text layer to search, select, or copy.

If you need the text
For a text-based PDF, use the BlendPDF PDF to Word tool, which produces an editable document. For scanned PDFs, neither tool can extract text today because BlendPDF has no OCR yet; an external OCR tool is the way to go.

Sometimes pixels are the point
The absence of a text layer is occasionally exactly what you want: an image of a page cannot have its text quietly edited, which is why some workflows share critical pages as images deliberately.

No; an encrypted PDF cannot be rendered without being decrypted first.

The fix
If you have the password and the right to use the document, remove the protection with the BlendPDF unlock tool, then convert the unlocked copy. The unlock tool requires the correct password; it does not crack or bypass encryption, and we do not offer anything that does.

For a single page you need quickly at modest quality, a screenshot is fine, and we will not pretend otherwise. For anything beyond that, rendering wins on three counts.

Resolution
A screenshot captures your screen, which caps a full page at roughly 100-150 effective DPI on typical displays, and less if the page does not fit the window. Rendering at 300 DPI produces two to three times the linear detail, the difference between text that survives printing and text that turns fuzzy.

Consistency and effort
Screenshots inherit whatever zoom, window size, and cropping you had at the moment of capture, so page 3 rarely matches page 14. Rendering produces identically sized, perfectly cropped images for every page, and converting 80 pages takes one click instead of 80 careful captures.

Ordering
The ZIP names files page-001, page-002, and so on. Screenshots named "Screen Shot 2026-08-10 at 14.03.22" do not sort themselves.

Most problems trace back to a short list of causes.

Conversion fails outright
Confirm the file is a valid PDF under 50MB and 100 pages, and not password-protected (unlock it first if you have the password). If the PDF is damaged and fails repeatedly, run it through the BlendPDF repair tool, which attempts recovery with qpdf and pypdf; it fixes many structural issues, though not every file can be saved.

The ZIP is larger than expected
300 DPI PNGs of photo-heavy pages are big; that is the cost of lossless print quality. Switching to JPG typically cuts the ZIP size dramatically with little visible difference on photographic content. Converting fewer pages at a time (see the split-first workflow) also helps.

"Too many requests"
The rate limit is about 10 conversions per 15 minutes per user. Wait a few minutes and continue; nothing is lost.