Will your PDF's images print sharp? Check every one before you send it.

Drop PDFs below — get every image listed with pixel size, placed size, effective DPI, colour space and compression, plus a print-ready verdict per file. Inspected entirely on your device.

  • Your file data never leaves the device
  • Batch up to 20 PDFs + reports
  • Print-ready verdict per file
  • Password-protected PDFs refused

Add your PDF files

Drag & drop PDF files here

or browse your files · you can also paste from clipboard (Ctrl+V)

Inspected in your browser with pdf.js — every image dictionary is read on your device and its placed size is worked out from the page content stream. Nothing is uploaded.

    No files yet. Everything stays on this device. Reports download instantly.

    Privacy you can verify, not just trust

    Most online DPI checkers upload your documents to their servers first — and several charge for the detailed report. This one can't: pdf.js opens your PDF and its image dictionaries are read entirely in your browser. Your file data never leaves the device — the only third-party requests are the site's own analytics, which count page views — and it uploads nothing, ever. There is no file fetched after load for the inspection itself. Don't take our word for it:

    New cross-origin requests during use: 0
    1. Press F12 to open developer tools, then the Network tab.
    2. Inspect any PDF above. Watch: apart from the site's analytics, nothing new is requested — no uploads, and no file data ever leaves your device.
    3. Extra credit: disconnect your internet after this page loads — inspection still works.

    How to check image resolution in a PDF without uploading it

    A PDF has no single DPI — each image inside it has its own. An image that looks perfect on screen can print soft, because what decides sharpness is not the pixel count alone but the pixels against the size the image is actually printed at. The usual advice is to open Acrobat Pro's Output Preview or run pdfimages on the command line, but neither gives you a verdict, a batch check, or a report you can send to the person who made the file.

    This tool does exactly that, where the file already is: on your own device. When you drop a PDF here, your browser:

    1. Checks the file is really a PDF — by its %PDF magic bytes, not its name — and that pdf.js can open it, so a corrupt or truncated file is refused with a clear message instead of producing a wrong report. A JPEG renamed to .pdf is refused the same way, and a PDF renamed to .txt still inspects.
    2. Reads every image dictionary the pages actually draw — including images stored in compressed object streams, which most modern producers use, images used only inside Form XObjects, and inline images — and executes each page's content stream to work out the size every image is placed at, so its effective DPI is pixels divided by placed inches, not a tag in the file.
    3. Gives each file a verdict — Print-ready, Needs attention, or Too low to print — with the weak images named and the pages they sit on, plus the largest size each image can print sharply at 300 DPI, so you know what to fix and where. A downloadable text report per file (or one combined report for the batch) carries the same detail to whoever needs it.

    What makes this inspector different

    The pages that top the results for this search mostly check a single image file, not a PDF — and the print-shop checker we found that does read every image inside a PDF gives green, yellow or red verdicts on a print shop's ordering page, with no downloadable report and no per-image colour space or compression detail, while the other print-file checker we found only reads the first page. This page is the only free, no-sign-up, fully client-side dedicated PDF image inspector we found that combines a batch of 20 PDFs with a print-ready verdict per file, per-image colour space, bits per component and compression, the pages each image sits on, and a free downloadable report for every file — with no daily limits, no account and no watermark — plus a live network-request counter so you can verify the privacy claim yourself. It runs entirely in your browser — there is no server to upload to.

    When is inspecting the right choice — and when is it the wrong one?

    Inspecting is right whenever a PDF has to print sharp somewhere else: a book interior or cover for KDP or IngramSpark, a brochure or flyer for a print shop, a portfolio sent to a client, or any file where a soft image would only be discovered after the proof comes back. It is the wrong choice for a screen-only PDF — a 72 DPI image looks fine on a monitor — and for a file of pure vector drawings, which have no pixels and always print sharp. If the destination accepts the source document, fix the images there instead of patching the PDF.

    Honest limitations

    Image dictionaries, not full preflight

    This tool reads image dictionaries and placed sizes — it is not a preflight engine. It cannot judge colour accuracy, overprint, bleed, or any other print condition.

    Sharpness is not resolution

    A blurry photo at 300 DPI still prints blurry. This tool measures pixels against placed size; it cannot tell whether the pixels themselves are sharp.

    Image pixels are not decoded

    The image streams are never opened, so a corrupt image stream is not detected — only whether the dictionary is present and what it says.

    Some images are invisible

    Images drawn only inside annotation appearances (for example filled form fields) or patterns are not always listed, because they live outside the page resources.

    No password-protected PDFs

    Password-protected PDFs are refused, and this tool never asks for a password. Remove the password in a desktop PDF tool first, then inspect the unlocked copy.

    Scanned PDFs report per image

    A scanned PDF is one image per page. Inspection correctly returns one row per scanned page, each with its own effective DPI — a whole book scan at 150 DPI is a real finding, not an error.

    Frequently asked questions

    Do my PDFs upload anywhere?

    No. Your PDFs are opened and their images are read entirely in your browser with pdf.js — your file data never leaves the device, and the only third-party requests are the site's own analytics, which count page views. You can verify it yourself with the network-request counter in the privacy section below the inspector.

    How do I check the DPI of images in a PDF?

    Drop the PDF on this page and read the table: every image is listed with its pixel size, its placed size on the page, and its effective DPI — pixels divided by placed inches. In Adobe Acrobat Pro, the same information is under Print Production, then Output Preview, then Object Inspector, which shows each image's effective resolution. On the command line, the pdfimages utility lists the images and their sizes, but not the DPI at their placed size.

    What is effective DPI — and why does the DPI tag not matter?

    Effective DPI is an image's pixel width divided by the width it is actually printed at, in inches. A 3000-pixel photo printed 10 inches wide is 300 DPI, whatever its file says. The DPI tag stored in an image file only suggests a starting size when nothing chooses one — the moment a layout app scales the image to fill a frame, the effective DPI is what it is. That is why this tool ignores the tag and works from pixels and placed size, and why changing the tag never adds a single pixel.

    What DPI do I need for print?

    For anything held in the hand — a book page, a flyer, a business card — aim for 300 DPI at the final print size. Between 150 and 299 DPI is fine for a poster or banner seen from a metre or more, because the eye cannot resolve the same detail at that distance. Below 150 DPI, softness or pixelation will be visible up close. KDP and IngramSpark both ask for 300 DPI for book interiors and covers, so this tool flags anything under 300 as needing attention and anything under 150 as too low to print.

    Will this help with KDP or IngramSpark book files?

    Yes — that is the main use case. Self-publishing authors upload a PDF interior and cover to KDP or IngramSpark, and a low-resolution image is the most common reason a proof comes back soft. Drop the same PDF here first: every image is checked at its placed size against the 300 DPI target both platforms ask for, and the downloadable report lists exactly which images to replace and how big they can print sharply.

    Can I inspect several PDFs at once?

    Yes. Drop up to 20 PDFs at a time, up to 25 MB each, and inspect them all in one go. Every file gets its own verdict and image table, the summary strip totals the batch, and Download all reports collects every file's report into one text file (or a ZIP). There is no daily limit, no account and no watermark — a 200-page cap per PDF applies because very page-heavy PDFs are memory-bound in the browser.

    Can I inspect a password-protected PDF?

    No. Password-protected PDFs are refused with a clear message, and this tool never asks for a password. Remove the password in a desktop PDF tool first, then inspect the unlocked copy here.

    What does this tool NOT check?

    It reads image dictionaries and placed sizes; it is not a full preflight engine. It cannot judge colour accuracy, overprint, bleed, or whether an image is actually sharp — a blurry photo at 300 DPI still prints blurry. It does not decode the image pixels, so a corrupt image stream is not detected, and it cannot see images drawn only inside annotation appearances such as filled form fields, or inside patterns. For a full preflight, use Acrobat Preflight or a dedicated validator.

    Why does my PDF show no images at all?

    Because the PDF draws no images — it is most likely a text-only document, where every picture is a vector drawing (shapes and lines, not pixels) rather than an embedded image. Vectors have no DPI and always print sharp, so No images found is the correct result, not an error. If the document should have photos, it was probably exported with the pictures as vectors, or the pages are scanned images this tool could not read — try re-exporting from the original application.