PDF Image Extractor

Photos and scans stored inside the PDF as JPEG (the technical name is DCTDecode) or JPEG 2000 (JPXDecode) - which covers the large majority of real photographic images found in PDFs, since JPEG is by far the most common way authoring tools embed photos. Each one is pulled out as its exact original compressed bytes, byte-for-byte identical to what was embedded, with zero re-encoding.

A PDF can store an embedded image in several different internal encodings, and not all of them are already a complete, standalone image file the way JPEG is. Raw uncompressed bitmaps, indexed-color (palette-based) images, and black-and-white fax-style compression (common for text-heavy scans) all need real pixel decoding to turn into a usable file - this tool deliberately doesn't attempt that, to avoid silently producing a corrupted or misleadingly-named file. Instead, it reports exactly how many images were skipped and which encodings they used.

No - for the JPEG and JPEG 2000 images this tool extracts, the output file is byte-for-byte identical to the original compressed data the PDF authoring tool embedded. Nothing is decoded and re-saved, so there's no extra generation of quality loss the way there would be from, say, taking a screenshot of the rendered PDF page or converting the page to an image.

It depends on how the scan was saved. Many scanners and "scan to PDF" apps save each page as one full-page JPEG, which this tool extracts cleanly as a single image per page. Some scanning software instead uses a lossless or fax-style encoding specifically to keep black-and-white text sharp, which falls into the skipped category here since it isn't a photographic JPEG - the tool will tell you if that happened.

No. Vector paths, drawn shapes, and text aren't embedded image files at all - they're drawing instructions the PDF viewer executes on the fly, with no raster data to pull out. Only actual embedded bitmap (raster) images are extracted here. To capture a page's overall visual appearance as an image, or to pull text out instead, this site's other PDF tools (like PDF to JPG or the various PDF to text tools) are the right fit.

Sequentially, in the order they're stored inside the PDF's internal structure (image-1.jpg, image-2.jpg, and so on) - which usually roughly follows the order images were added to the document, but isn't guaranteed to exactly match top-to-bottom visual reading order on the page, since a PDF's internal object order and its visual layout are technically independent of each other.

No. The file is opened and every embedded image is located and extracted entirely in your browser. Nothing is uploaded anywhere, so it's safe to use on documents you'd rather not send to a third-party server.

Only if it isn't actually locked with a passphrase - a PDF with owner-level restrictions but no open password will generally still work. A PDF that genuinely requires a password just to open won't extract correctly here, since that needs real decryption with the password, which this tool doesn't perform. Remove the password first with this site's PDF password remover, then run the result through this tool.

Well-optimized PDFs often reference a single embedded image object from several pages rather than storing duplicate copies of the same photo, to keep file size down. This tool extracts each distinct embedded image object once, so a photo reused across many pages appears once in the results rather than once per page it's shown on.

Almost always, since JPEG (DCTDecode) is by far the most common way PDFs embed photographic images. Occasionally a PDF - particularly high-resolution scans, medical imaging exports, or some technical/print workflows - embeds images as JPEG 2000 instead, which this tool also extracts, saved as a .jp2 file. Not every image viewer or operating system opens .jp2 natively, so if you get one and it won't open, a dedicated JPEG 2000 viewer or a converter tool will read it.

Resolution and quality. A screenshot is limited to whatever resolution the PDF happened to be rendered at on your screen, then gets re-compressed again by whatever tool captured it - two extra, avoidable steps that degrade quality below what's actually stored in the file. The embedded image itself is very often a much higher resolution than what you'd see rendered on a normal screen (print-ready photos in particular are usually saved well above screen resolution), and extracting it directly skips both the rendering-resolution cap and the second compression pass entirely. That matters most when you need the photo for something that will actually show the difference - printing, further editing, or sending someone the original asset instead of a lossy copy of it.

Yes - the whole document is scanned in one pass and every extractable image is added to the results grid, whether that's two photos or two hundred. For a PDF with a genuinely large number of images, downloading them as a single .zip rather than one at a time is the faster option, and that button appears automatically whenever more than one image was found.