Receipts photographed on a phone, scanned certificates, snapshots of handwritten notes — turning these into one PDF is a recurring chore around expense claims and applications, not least because a single PDF is easier for the recipient to handle than a dozen loose photos.
OFFiler's image-to-PDF builds one document with your images laid out as pages, in order. It runs entirely in the browser, so photos of ID documents and receipts never have to be handed to a third party. Below: how images are embedded, how page size is decided, and which formats are accepted.
What happens inside
Images are embedded as-is, not re-encoded
Each image's leading bytes are inspected to identify PNG or JPEG, and it is embedded through the matching path. There is no quality-reducing re-compression: a JPEG stays that JPEG, a PNG stays that PNG, so photographs do not go soft in transit.
The consequence is that the output PDF weighs about as much as the images did in total. Ten high-resolution phone photos make a correspondingly large PDF. If the recipient imposes a size limit, compress the images before converting, or compress the PDF afterwards.
Page size follows the image's pixel dimensions
One image becomes one page, and that page is sized to the image's pixel dimensions — it is not fitted to A4 or any other standard. The upside is that the image never floats inside unwanted margins and is never rescaled, so nothing degrades.
The trade-off is that mixing images of different sizes and aspect ratios produces a PDF whose pages differ in size. That is fine on screen, but for printing or formal submission you may want them uniform — run the result through PDF normalisation in that case.
Format restrictions
PNG and JPEG only
PDF can embed PNG and JPEG directly, and this tool accordingly accepts only those two. If your iPhone photos are still HEIC, or your assets are WebP, they need converting first.
Send HEIC through the HEIC converter to get JPEG, and WebP or anything else through the format converter to get PNG or JPEG, then bring the result here. Both chain directly, so there is no saving and re-opening in between.
Photo metadata survives inside the PDF
Because the original JPEG is embedded without re-compression, whatever EXIF it carried — capture time, camera model, GPS coordinates — travels into the PDF with it. Strip EXIF before converting if the location should not be disclosed.
Related: if a photo only looks upright thanks to an EXIF orientation flag, it can end up sideways once embedded. Rotating the actual pixels first makes the result predictable.
The standard receipt workflow
Shoot → strip metadata → shrink → convert
Converting expense-claim photos straight to PDF gives you a heavy document full of geotagged, full-resolution images. Strip the EXIF, compress the images to the point where they are still legible, and then convert — the result is light and carries nothing you did not intend to send.
Specs and limits
- Input formats
- PNG and JPEG only (convert HEIC/WebP first)
- Size limit
- 50 MB per file
- Pages
- One image per page, in the order shown on screen
- Page size
- Taken from the image's pixel dimensions; not fitted to A4
- Quality
- No re-encoding; images embedded as-is
- Metadata
- Original EXIF travels into the PDF
- Network
- No file upload; all processing in-browser