PDF to Image

About PDF to Image Converter

This tool converts PDF pages to image files (JPG or PNG). Each page is exported as a separate image file. You can customize the format, quality, and resolution. All processing happens in your browser for complete privacy. See also our PDF to Text and Merge PDFs.

Will PDF-to-image preserve text clarity at typical screen sizes?

Yes — at the default 150 DPI the rasterised text is crisp on standard displays, and 300 DPI is sharper than printed magazine quality. Inside the tool, PDF.js renders each page to an HTML canvas, then exports as PNG or JPEG. PNG is lossless and ideal for documents with text and line art (rendering stays pixel-perfect even when zoomed); JPEG is smaller for pages dominated by photographs. The trade-off is that once you convert to an image, the text is no longer selectable, searchable, or accessible to screen readers — that information lived in the PDF text layer, not in the pixels. If you need searchable images, keep a copy of the PDF and feed any image you later edit through an OCR tool to rebuild a text layer.

What DPI should I choose for screen, print, and OCR use cases?

For screen reading and web display, 96–150 DPI is plenty — that matches the pixel density of most laptops and phones, and produces small files. For office printing on Letter or A4 paper, choose 300 DPI; that is the resolution at which the human eye stops distinguishing individual dots at normal reading distance. For high-quality print (magazines, books, photo prints) use 600 DPI. For feeding the output into OCR, 300 DPI is the sweet spot recommended by every major OCR engine (Tesseract, Google Vision, Adobe) because anything lower starves the recogniser of glyph detail and anything higher just slows it down without improving accuracy. The tool's DPI selector applies uniformly to every page.

Can I extract specific pages instead of converting the whole PDF?

Yes — enter a page range like `1-5,8,12-15` in the Pages field before clicking Convert. Each listed page becomes one image file, and all of them are bundled into a ZIP for download. Use this to pull a single chart out of a long report, or to convert only the cover page of a book to a thumbnail. The page numbering follows the PDF's own ordering, which is usually the visual order shown by readers but may differ for documents with reordered page indices. If you leave the field blank, every page is converted. To extract pages while keeping them as PDF (not images), use the Extract PDF Pages or Split PDF tools instead — they are lossless.

What's the difference between PNG and JPEG output for PDF conversion?

PNG uses lossless DEFLATE compression and supports alpha transparency, making it ideal for documents with sharp text, line art, screenshots, and diagrams — every pixel is identical to what was rendered. File sizes can be large for photographic content because PNG cannot exploit perceptual redundancy. JPEG uses lossy DCT-based compression that exploits how human vision tolerates small high-frequency errors; it produces files 5–10× smaller for photographs but introduces blocky artefacts around sharp text edges, especially at low quality settings. Rule of thumb: pick PNG for office documents, contracts, and slides; pick JPEG only when the page is predominantly a photograph. Many users start with PNG and only switch to JPEG if file size is a problem.

Does the conversion preserve embedded ICC colour profiles?

The tool renders each page using PDF.js, which respects embedded ICC profiles during rasterisation — colours appear on the canvas the same way Adobe Reader would show them. However, the output PNG or JPEG is written in the sRGB colour space by default, because that is the only profile every browser, web service, and OS reliably interprets the same way. If the source PDF used CMYK with a press-specific ICC profile (e.g., FOGRA51 for European offset), the colours will be converted to sRGB for display — perceptually similar but not exact. For colour-critical workflows (proofing print artwork), do not use a browser-based rasteriser; use Adobe Acrobat or Ghostscript with `-sDEVICE=tiff32nc -sOutputICCProfile=USWebCoatedSWOP.icc` to keep CMYK colour fidelity.

How do I handle very large PDFs without crashing the browser tab?

Each rasterised page lives in browser memory as RGBA pixels before being encoded; a 300 DPI Letter page is 2550×3300 pixels × 4 bytes = ~34 MB of raw pixel data. A 100-page document at 300 DPI therefore needs about 3.4 GB peak memory, which exceeds what most browser tabs allow. The tool processes pages sequentially and frees each canvas after encoding, which keeps peak usage to roughly one page at a time plus the growing ZIP. If you still crash, lower the DPI to 150 (cuts memory 4×), convert in batches using the page-range field, or switch to JPEG which encodes faster and frees memory sooner. For 1000+ page archives, use a desktop tool like pdftoppm or `mutool draw -o page-%d.png` instead.

Can I get vector SVG output instead of raster PNG or JPEG?

Vector SVG output is on the roadmap but not yet supported in this tool. The challenge is that PDF content streams include features (advanced shading patterns, embedded ICC, masked images, blend modes) that SVG 1.1 cannot represent faithfully; PDF.js does have an experimental SVG backend, but the output often differs subtly from the canvas rendering for complex pages. If you specifically need vector-preserving output, the best path today is to keep the PDF in PDF format (it is already a vector container) and view it with a PDF reader; or use Inkscape's PDF import (uses Poppler under the hood) which converts page-by-page to SVG with reasonable fidelity for simple pages. We will enable an SVG mode once the underlying library matures.

Will the converted images include the OCR text layer for accessibility?

No — rasterisation drops the text layer entirely. The PDF's invisible OCR text lives in the content stream as Tj/TJ operators with positioning data; once you render to PNG or JPEG, only the visible pixels survive. This breaks Ctrl+F search, screen-reader access, and copy-paste. If you need image-format pages that retain searchable text, the workflow is two-step: first convert with PDF to Image to get your PNGs, then run those PNGs through an OCR tool like Tesseract or Google Vision to generate a sidecar text file or an HOCR file with bounding boxes. For embedding-back into a PDF, OCR PDF on the original file is the cleaner path — it keeps the vector content and adds a text layer in place.