Merge Images to PDF Locally

Compile multiple photos into a single secure document without data transfer.

or drag and drop files here

The 'Single Upload' Constraint

A common bureaucratic frustration involves upload portals—university applications, insurance claims, or banking verification—that require multi-page documentation but restrict you to a single file upload. If you have photographed your documents (contracts, receipts, ID cards), you are left with several loose .JPG files that cannot be submitted together.

This tool solves the 'Multiple Photos, One Slot' problem. It acts as a local compiler, taking loose raster images and binding them into a single, standardized Portable Document Format (PDF) file. This allows for the submission of multi-page records in a format accepted by virtually every digital system.

Privacy Architecture: The Sandbox Model

When converting sensitive documents like Passports, Driver's Licenses, or Financial Statements, Data Sovereignty is paramount. Most free online converters operate on a 'Send-and-Return' model, requiring you to upload your private files to a temporary cloud server.

This tool utilizes a Sandbox Model. It leverages the jsPDF JavaScript library to generate the PDF binary stream entirely within your browser's allocated memory (RAM). The image data flows from your hard drive to your browser's canvas, and then directly to the new PDF file. No network request is ever made. You can verify this by inspecting the Network tab in your browser's Developer Tools, or by using this tool while disconnected from the internet.

Technical Logic: Raster Encapsulation

Technically, a PDF is a vector-based container format (PostScript), while your photos are raster-based (pixel grids). This tool does not 'convert' the pixels into vectors; rather, it performs Encapsulation.

  • Containerization: The script calculates the pixel dimensions of your input images and generates a PDF page of corresponding aspect ratio (or fits it to A4).
  • Embedding: The raw pixel data (Base64 encoded) is embedded as an 'Image Object' within the PDF stream.
  • Result: The output is a valid PDF document that visually displays the image, but retains the raster nature of the source. This is why the file size of the PDF is often the sum of the input images plus a small overhead for the PDF headers.

Operational Limitations

While client-side processing ensures privacy, it introduces hardware-based constraints:

  • No OCR (Optical Character Recognition): This tool wraps an image in a PDF page. It does not convert the visual text into selectable, searchable text. The resulting PDF is essentially a 'digital photocopy.'
  • Memory ceilings: Because the browser must hold the uncompressed image data in RAM to build the PDF, attempting to merge 50+ high-resolution photos (e.g., 20MB raw files) may cause the browser tab to crash due to memory exhaustion.

Frequently Asked Questions

Is it safe to convert my ID card or Passport here?
Yes. This is the primary use case for this architecture. Because the code runs locally (client-side), your sensitive documents are never uploaded to our servers or any third-party cloud. The privacy is mathematically guaranteed by the browser's sandbox.
Why isn't the text in the PDF selectable?
This tool performs 'Image Encapsulation,' not 'OCR' (Optical Character Recognition). It takes a picture of your document and puts it inside a PDF page. To the computer, it is still just a picture, not text code.
Can I combine JPG and PNG files?
Yes. The compiler accepts mixed formats (JPG, PNG, WebP) in a single batch. It will normalize them and merge them into a single multi-page PDF document in the order you upload them.
Why is the generated PDF file size large?
A PDF containing images is essentially a wrapper around those images. If you add five 4MB photos, the resulting PDF will be roughly 20MB. The tool does not aggressively compress the images to preserve document legibility.
Does this work on mobile?
Yes. The underlying JavaScript is compatible with mobile browsers (Chrome on Android, Safari on iOS). However, processing very large batches of photos may drain the battery faster than on a desktop due to CPU usage.