Image to PDF
Turn a batch of images into one PDF — receipts into an expense report, screenshots into documentation, scans into a submission. Order the pages, pick a page size, and the PDF is assembled entirely in your browser by this site's own tested writer.
Combine images into a PDF
Add images (JPG, PNG, WebP, GIF, BMP), arrange them with the Up/Down buttons, then create the PDF.
How your images become pages
Each image occupies exactly one page, in your list order. With "match each image" the page is cut to the image's own proportions at the DPI you set — a 1920×1080 screenshot at 96 DPI yields a 1440×810-point borderless page (that figure is computed at build time by the same geometry code the tool runs). Choose A4 or Letter when the PDF is headed for a printer or a system expecting uniform pages: every image is scaled to fit within a half-inch margin and centered, never cropped or stretched.
A PDF writer we can show you
This tool does not bundle a PDF library. The file is assembled by a deliberately small writer built for this site: a catalog, a page tree, and for each image a page object, a drawing instruction, and the JPEG bytes embedded verbatim as a DCTDecode stream. Because the writer is pure code with no browser dependencies, its output is tested structurally — header, cross-reference table offsets, object counts, byte-for-byte JPEG embedding — and the tool re-checks the assembled bytes before the download appears. The honest flip side of the JPEG pipeline: transparency in PNG/WebP sources flattens onto white, animated sources contribute their first frame only (flagged in the list), and images are re-encoded at your chosen quality rather than copied untouched.
Practical notes
- Order before you build: the Up/Down buttons rearrange pages; Remove drops one without starting over. Adding more files appends to the list.
- DPI is labeling, not resolution: raise it to make pages physically smaller on paper; the embedded pixels never change.
- Size expectations: the PDF weighs roughly the sum of its re-encoded JPEGs plus a fraction of structural overhead — the result line reports the real size.
- Metadata: EXIF (including GPS) is stripped from images by re-encoding; the PDF carries no author or title metadata at all.
Related tools
Shrink oversized photos with the Image Resizer before combining — smaller inputs, smaller PDF. To fix formats first, the converters are in the sidebar: WebP to JPG and PNG to JPG pair naturally with PDF building.
Frequently asked questions
How are my images arranged in the PDF?
One image per page, in the order shown in the list — use the Up/Down buttons to reorder before creating. Files you add in one go keep their selection order.
What do the page size options mean?
"Match image" sizes each page to its image at your chosen DPI — a 1920×1080 screenshot at 96 DPI becomes a 1440×810-point page with no borders. A4 and Letter produce uniform printable pages with the image scaled to fit inside a half-inch margin, centered.
What does the DPI setting change?
Only the physical size the PDF claims, never the pixels. 96 DPI treats screen pixels as CSS pixels; 300 DPI makes the same image cover a print-appropriate smaller area. Your image data is identical either way.
Are the images recompressed?
Pages are embedded as JPEG at the quality you set (default 85), because the PDF is built around JPEG streams. Transparent areas of PNG or WebP inputs are flattened onto white — stated here, before you build. For documents of screenshots, quality 85–92 looks clean.
Which PDF library does this use?
None — the PDF is assembled byte-by-byte by this site’s own small, tested writer (about two hundred lines). Tests assert the header, page count, cross-reference offsets, and that each JPEG is embedded verbatim. Fewer dependencies, fewer surprises.
Do my images or the PDF touch a server?
No. The images are read, encoded, and assembled into the PDF inside your tab, and the download comes from browser memory. The methodology page shows how to verify zero network traffic.
Local processing: images and the finished PDF exist only in your browser until you save them. How the writer works — and how to verify nothing is uploaded — is on the methodology page.