Drop up to 50 images and they come back as one combined PDF. We compress each page first, in the order you dropped them. Runs on our servers, no signup.
Drop images or browse
JPEG · PNG · WEBP · AVIF · HEIC · max 30 MB
Auto tunes each image.
A hard cap for “under 50 KB” portals.
Empty side keeps the ratio. Never enlarges.
JPEG · 184 KB
JPEG · 73 KBCombining is the default, not a feature. Drop several images and one PDF comes back, one page per image, in the exact order you dropped them. Formats mix freely in a single batch. The JPGs from your camera roll, the PNG screenshots, the WebP a website gave you and the HEICs straight off an iPhone all land in the same file. The same engine that powers the rest of Blinkimg compresses every page before we embed it. That is why the next section's numbers look the way they do.
The wrapper is nearly free: 1.8 KB across a three-page file. Everything else is the pages. That is why compressing them first is the whole game:
| Recipe | Each page | Final PDF |
|---|---|---|
| Auto quality | 74.7 KB | 226 KB |
| Quality 85 (print-safe) | 108.2 KB | 326.3 KB |
| Pages capped at 100 KB | 90.6 KB | 273.6 KB |
| One HEIC, one page | 72.9 KB | 72.9 KB (from a 199.7 KB photo) |
Three-page PDF from three copies of the 188.3 KB reference photo, assembled by the same code that builds your file. The HEIC row is one iPhone photo → one page.
How these numbers are measured: every byte count on this page is the size of the actual encoded file our engine produced from the named source image. Those are the same bytes you would download, not an estimate or a best case. Rerun any of them yourself: drop your own file into the tool above and the meter reports your real result.
The market leaders' own pages document this gap. One top converter's FAQ concedes its generated PDFs come out very large, then points you at a second tool. Another wrote a separate blog post for the 200 KB question its converter can't act on. Here the arithmetic is a control: cap the pages and you have capped the PDF. Set Max file size to a portal's per-page budget (50/100/200 KB presets included). The engine quality-searches every page to fit under it, never over. Our measured five-page run with 100 KB caps assembled to 455.6 KB. Even with every page sitting exactly at the cap, the file tops out just past 500 KB (2.6 KB of wrapper, measured). A page that can't make its cap fails with a clear error, and the result reports it as left out. It never silently blows the budget. Application portals, expense systems, court filings and university submissions all stop being a convert-then-compress two-step.
Every page is a standard A4 sheet (595×842 points) with a white background, the layout portals and printers expect. Your image fills the sheet as far as its shape allows and sits centred. The sheet's orientation follows the image: landscape photos get landscape pages instead of floating tiny in a portrait frame. Sideways phone photos straighten automatically from their EXIF orientation. Transparent PNGs flatten cleanly onto the white sheet, since the engine flattens transparency to white for every JPEG it makes. Not offered, said plainly: US Letter, custom margins and drag-to-reorder. Drop order is page order, and no portal we know of has rejected A4.
People convert passports, tenancy contracts, bank statements and medical forms on pages like this one. A photographed document carries EXIF, including the GPS location of the room it was shot in. We strip metadata by default from every page we embed, an angle you will not find mentioned by any of the big converters. We process and wipe the files themselves automatically: we keep nothing, never archive, never reuse. No account is attached to any of it, and no sign-in wall stands between you and the download.
Rotating a page first? Rotate image. Trimming margins off a photographed document? Crop image.
Short answers specific to this tool. Drop a couple of images above and see for yourself.
Drop them in above. The pages combine into one PDF on their own.