How to Extract Images from a PDF in Chrome

The workflow is the same in Chrome regardless of your operating system. Chrome's file picker connects to your OS's native file browser — File Explorer on Windows, Finder on Mac, Nautilus on Linux — so navigating to your PDF feels natural. You can also drag a PDF file directly from your desktop or file manager onto the upload area.

1. 1Open Chrome (on any OS) and go to lazy-pdf.com/en/extract-images
2. 2Drag your PDF from your file manager onto the upload area, or click to open the native file picker and select the PDF
3. 3The file is uploaded to LazyPDF's server — a progress bar shows upload and extraction status
4. 4When complete, click 'Download ZIP' to save the archive of extracted images to your Downloads folder
5. 5Open the ZIP using your OS's built-in tool (File Explorer on Windows, Archive Utility on Mac) and access the individual image files

Chrome's PDF renderer (PDFium) is designed for displaying PDFs — it rasterizes each page for screen rendering but doesn't expose the underlying binary image data embedded in the PDF. When you see an image in Chrome's PDF viewer, you're seeing a rendered representation of the page, not direct access to the original embedded JPEG or PNG. Extracting the actual embedded images requires parsing the PDF's cross-reference table, locating each image object (XObject), decoding its filter (JPEG, Flate, JBIG2, etc.), and combining any associated transparency streams. This is a full PDF parsing operation that Chrome's viewer intentionally doesn't perform — it's outside the scope of a viewer. LazyPDF's server runs a dedicated PDF parser that performs this extraction correctly.

Images are extracted exactly as they were embedded by the document's creator. A photograph embedded as a high-resolution JPEG will be extracted as a high-resolution JPEG — the tool doesn't re-encode or reduce quality. Icons and logos embedded as PNG will be extracted as PNG, preserving any transparency. The naming convention in the ZIP follows the order images appear in the PDF's structure: image_001.jpg, image_002.png, and so on. If the PDF has 50 embedded photos, you'll get 50 image files. Small images like bullets or watermark patterns are also extracted if they are stored as embedded image objects — you can simply delete any that aren't relevant to your workflow.

On ChromeOS, downloaded files go to the Files app rather than a traditional Downloads folder. Open the Files app (launcher → Files), look for the ZIP in the Downloads section, and use ChromeOS's built-in ZIP extraction to unpack it. Extracted images can be added to Google Drive from there, or opened directly in apps like Google Slides. On Linux, Chrome typically downloads to ~/Downloads. If you're using a browser with strict sandbox settings (like Chrome in a Snap package on Ubuntu), the file picker may be restricted. In that case, move your PDF to ~/Downloads first, then use the file picker to select it from there. All other Chrome platforms — Windows and macOS — handle file access without restrictions.

The extract-images tool requires uploading your PDF to LazyPDF's server because extraction must happen server-side. LazyPDF's server is configured to delete all uploaded files immediately after the download link is generated. This is not a retention policy that happens 'eventually' — it's an immediate programmatic deletion as part of the processing pipeline. For PDFs containing sensitive images — medical scans, engineering schematics, legal exhibits — consider whether the document contains non-image text data you'd prefer not to transmit. If you only need images from specific pages, using the LazyPDF Split tool to extract just those pages before uploading for image extraction reduces the amount of data sent to the server.