BrowserTools
Advertisement
Home / PDF / Images to PDF

Images to PDF

Combine PNG, JPG and WEBP images into a single PDF document — in your browser, no uploads.

Loading Images to PDF… If nothing happens, please enable JavaScript.

Frequently asked questions

Are my images uploaded to a server?
No. The PDF is built entirely in your browser using pdf-lib. Images are read from your local disk, embedded into the PDF document in memory, and the file is downloaded directly to your device. No image data is transmitted over the network at any point.
What is the maximum number of images or total file size?
There is no fixed limit. The practical constraint is your browser's available RAM — the PDF is assembled in memory before download. Most desktop browsers handle dozens of high-resolution images without issue. If the browser freezes, try processing a smaller batch and merging the resulting PDFs afterwards.
Does this work with HEIC or TIFF images from my iPhone?
HEIC and TIFF are not natively supported by web browsers' Canvas API, so they cannot be directly embedded. Convert these images to JPEG or PNG first using your device's built-in photo app or a free image converter, then use this tool.
Will image quality be reduced when embedding into the PDF?
JPEG and PNG images are embedded natively without re-encoding, so their quality is fully preserved. WEBP images are converted to PNG by the browser's Canvas API before embedding, which is a lossless step. The only quality reduction would be if you manually selected a smaller page size with 'fit' or 'fill' scaling that stretches or compresses the image.
How does this compare with scanning software or Adobe Acrobat?
Dedicated scanning software and Acrobat offer additional features like automatic page detection, perspective correction, and OCR text recognition. This tool focuses on clean, privacy-first image-to-PDF conversion from photos you have already taken, with zero setup and no cloud dependency.
Can I mix portrait and landscape images in the same PDF?
Yes. The 'Auto' orientation option sets each page to match the orientation of the image it contains — portrait images get portrait pages and landscape images get landscape pages. You can also force all pages to portrait or landscape, in which case images are scaled to fit accordingly.
Which image formats are supported?
PNG and JPEG are supported natively and embedded without re-encoding. WEBP is supported by converting to PNG via the Canvas API before embedding. GIF, BMP, TIFF, and HEIC are not currently supported — convert them to PNG or JPEG first.
What page sizes are available, and can I use custom dimensions?
The tool offers common standard sizes including A4, A3, A5, Letter, and Legal, in both portrait and landscape orientation, plus an 'Image size' option that creates each page at exactly the image's pixel dimensions. Custom arbitrary page sizes are not currently available through the UI.
Can I automate image-to-PDF conversion for large batches?
The browser UI processes files interactively. For batch automation, pdf-lib is available as an npm package and can be scripted in Node.js to convert and combine hundreds of images into PDFs programmatically. Third-party command-line tools like ImageMagick can also convert image sequences to PDF at scale.
Is the resulting PDF compatible with all PDF viewers and standards?
The output is a standard PDF 1.7 document (ISO 32000-1) compatible with all major viewers including Adobe Acrobat, macOS Preview, Chrome, Firefox, Edge, and mobile PDF apps. The file is not PDF/A-compliant by default, but for the vast majority of submission and sharing purposes, standard PDF 1.7 is universally accepted.

About Images to PDF

Converting images to PDF means embedding one or more bitmap images into a structured PDF document, where each image becomes the content of a dedicated page. The PDF format stores images as compressed XObject resources referenced by page content streams, which means the image data is preserved — not re-encoded from scratch — when you embed a JPEG or PNG. This tool lets you select multiple images, arrange their order, choose a target page size (A4, A3, Letter, or match each image's natural dimensions), and control how the image is scaled within the page: fit (preserve aspect ratio within the margins), fill (cover the full page), or original size. The result is downloaded as a standard PDF immediately, without any upload.

The most frequent real-world use is digitising physical documents. You photograph pages with a smartphone, transfer the images to your computer, and need to combine them into a single submittable PDF. Government offices, banks, universities, and HR departments routinely require documentation in PDF format. Other common uses include packaging a set of screenshots into a report, assembling scanned receipts for expense reimbursement, combining architectural photographs into a project portfolio, creating a photo book layout, or turning a sequence of exported chart images into a presentation-ready PDF for colleagues who need a static document rather than a live dashboard.

The entire conversion runs inside your browser using pdf-lib. JPEG and PNG images are embedded directly as native PDF image objects — no re-encoding, no quality loss for images that were already in those formats. WEBP images, which are not natively supported by the PDF specification, are first decoded by the browser's Canvas API and then embedded as PNG — a lossless conversion that preserves full quality. Because everything happens locally, your photographs of sensitive paperwork, identity documents, and financial statements are never transmitted to any server or third party.

For best results, ensure your images are oriented correctly before adding them — use the rotate tool on individual images if needed, since rotating an image inside the PDF after the fact requires a separate step. If you are scanning physical pages, aim for at least 150 DPI for readable text and 300 DPI for documents that may later be OCR-processed. Choosing 'fit' scaling with an A4 or Letter page size produces the most professional-looking output for document submissions, while 'original size' is best when precise pixel dimensions matter, such as for technical diagrams.

Scanning to PDF: How a Format Designed for Print Became the Language of Digital Documents

When PDF was first designed in the early 1990s, the dominant document workflow was print: create in a desktop application, print to paper, distribute physically. Adobe envisioned PDF as a way to distribute 'electronic paper' — documents that looked as good on screen as they would when printed. The decision to embed images as high-fidelity objects within the PDF, rather than linking to external files, was a deliberate choice to make PDFs self-contained and portable. This same architectural decision is what makes the images-to-PDF workflow so natural four decades later.

The rise of flatbed scanners and later smartphone cameras transformed PDF from a print-output format into an ingestion format — a way to bring physical documents into the digital world. By the mid-2000s, the 'scan to PDF' function had become standard on office multifunction printers, and PDF became the default output format for digitised paperwork worldwide. Government agencies, banks, and legal firms gradually shifted their submission requirements from fax to PDF, cementing the format's role at both ends of the document lifecycle: creation and archival.

An often-overlooked detail is that the PDF specification defines images using the same colour space and compression primitives as PostScript, which means a JPEG embedded in a PDF is stored using DCT (Discrete Cosine Transform) compression — the same algorithm as a standalone JPEG file. When a PDF viewer renders the page, it decompresses the DCT stream exactly as a JPEG decoder would. This equivalence means that embedding a JPEG into a PDF is essentially a zero-loss operation: the image data is placed inside the PDF container with only a few hundred bytes of header overhead, and no re-encoding or quality degradation occurs.

Advertisement