Drop in your PDFs
Several files at once is fine. Parsing, re-encoding and writing all happen in this browser.
ImgIng never round-trips a PDF through HTML or flattened page images. It optimizes the original structure locally, makes per-image decisions and reclaims resources that actual drawing operations do not use while preserving page geometry, text, links and vectors.
These facts describe the current product, not unshipped roadmap work.
Reviewed by the DataDance product and engineering team · Published · Updated
Confirm important settings before export; the processing location is always disclosed.
Several files at once is fine. Parsing, re-encoding and writing all happen in this browser.
Screen 72dpi, e-book 150dpi, print 300dpi, or lossless structure only. You can also name a target file size.
Switch between the original and the result in the page, then save to your device once it looks right.
A PDF contains text, vectors, fonts and bitmaps. Scans, photos and screenshots usually dominate its size. ImgIng finds ordinary Image XObjects and promotes safely parsed BI / ID / EI inline images into the same pipeline before deciding what each image deserves.
The same image can be reused at different sizes or placed with non-uniform scaling. ImgIng follows page and Form graphics matrices, aggregates the maximum horizontal and vertical placement independently, and chooses each target dimension separately. Component Decode arrays are applied before re-encoding, while colour spaces that require full colour management remain untouched when equivalence cannot be proven.
JPEG suits photographs but can be larger and blurrier for screenshots, charts and flat colour. ImgIng races JPEG, indexed-palette Flate, grayscale Flate, RGB Flate and the original. Palette dictionary overhead is included in the comparison, and only a genuinely smaller candidate wins.
Actual drawing operators drive conservative removal of unused fonts, images, graphics states, colour spaces, patterns, shadings and properties. Unknown operators or special streams keep their complete resource sets. Fragmented page content streams merge only across safe lexical boundaries and only when the result is smaller. Uncompressed, ASCII, LZW and existing Flate streams all race a fresh Flate encoding; unreachable-object collection, exact stream deduplication, metadata cleanup and object-stream packing then run as before.
Encrypted or permission-protected PDFs must be unlocked first. JPEG 2000, JBIG2, CCITT fax, CMYK print JPEG and images needing full ICC, Lab or DeviceN colour management remain original when the browser cannot re-encode them equivalently. Any image, structural stream or complete PDF that does not become smaller also keeps its original data.
Honest limits: ImgIng does not currently subset fonts, so text-only gains depend on unused resources and inefficient structural streams. The output is re-read to verify page count, every page box, selectable-text operators and link semantics; any mismatch keeps the source PDF. Rewriting a digitally signed PDF invalidates the signature.
Updated 2026-08-25 · Live capability detection inside the tool is authoritative
These visible answers match the current product behaviour and structured data.
No. Parsing, image re-encoding, structural rewriting and verification all happen in this browser, and no extra runtime needs to be downloaded.
Yes. ImgIng only re-encodes embedded bitmaps and rewrites the file structure. Pages are never flattened into images, so the text layer, bookmarks and links survive.
If the embedded images are already below the chosen DPI and sensibly encoded, or the file is mostly text and vectors, there is nothing to reclaim. ImgIng says so and keeps your original rather than manufacturing a number by lowering resolution.
Each task page documents real settings, limits and format advice—not keyword-swapped duplicates.