Image to PDF Converter

Image to PDF turns a mixed set of photographs, screenshots and scanned images into an image-based document. Use it when the recipient needs a PDF and your sources are not all the same format. JPG, JPEG, PNG, WEBP, GIF, BMP, HEIC and HEIF are accepted, with a limit of 10 files per batch and 10MB per file. Conversion takes place in the browser. The useful choice is not simply whether a picture can become a PDF, but how to preserve its reading order, proportions and legibility.

Choose the converter by the files you actually have

A mixed batch might contain an iPhone HEIC photograph, a PNG screenshot and a JPEG receipt. You can select those together here instead of first converting every file into JPG. The dedicated JPG to PDF, PNG to PDF and WEBP to PDF pages provide more focused guidance for those inputs; they use the same PDF settings.

Check the actual file rather than assuming its format from the device it came from. A photo shared from an iPhone may already be JPEG. A downloaded item may be a web page or a shortcut rather than image data. If the receiver wants an editable photograph instead of a document, use HEIC to JPG rather than adding a PDF container. A PDF organizes pages; it does not create new photographic detail.

Understand what is embedded in the PDF

The converter reads each image, draws its pixels onto a canvas and encodes the PDF image as JPEG at the selected quality. Transparent pixels are composited over white. HEIC export is decoded again from the source instead of reusing the compressed thumbnail. This preserves a distinction between the lightweight preview and the image used for export, but the resulting PDF still uses JPEG compression.

PNG and lossless WEBP inputs therefore do not make this a lossless PDF workflow. Vector information is not created from diagrams, text is not recognized, and animation is not preserved as a moving document. Keep a PNG or a source design file when transparent layers or editable text are important. For animated GIF or WEBP sources, export the required still images separately in another application before building a page sequence; this tool does not expand animation frames into PDF pages.

Select paper size according to the destination

Setting	Useful destination	What to check
A4	A recipient asking for standard A4 pages	White space around a photo with a different ratio
Letter	A form or office workflow specifying US Letter	The recipient's actual paper requirement
Fit	A digital document that should follow each image	Different page sizes inside a mixed batch

A4 and Letter use portrait pages here. Images are scaled proportionally and centered without cropping, so landscape photographs may leave substantial space above and below. Selecting no margin removes the chosen page padding, not differences between image and paper ratios. For example, a 3000 × 4000 portrait photo on A4 with no margins becomes approximately 210 × 280 mm, leaving 8.5 mm above and below. That is a layout calculation, not a device benchmark.

Match image quality to what people must read

Begin with Balanced and inspect the downloaded PDF at 100% zoom. Try Higher quality when fine print, handwriting or thin lines look worse than the source. Try Smaller file when a submission has a tight size limit, then inspect again. Those labels control JPEG encoding; they are not a promise of a particular percentage reduction or visual fidelity.

Compare critical content such as totals, dates, item codes and signatures rather than judging only a large preview. Making a blurred source larger will not restore missing information. If a page is difficult to read because the whole source contains too much irrelevant space, crop a copy before conversion instead of relying on a different quality setting to solve a layout problem.

Diagnose limits before repeating a large batch

File size and decoded size measure different things. A 4032 × 3024 photo needs about 46.5 MiB for one RGBA pixel buffer alone, calculated as width × height × 4 bytes. Canvases, previews and the PDF add more. This is not a measurement of the application's peak memory, but it explains why several small compressed files can still strain a phone.

If only one preview fails, remove or retry that file and test the remaining images. If every file fails, check that the browser is current and JavaScript is available, then try one ordinary JPG or PNG. If conversion succeeds but the download is not where expected, check the browser's download location and whether separate output produced a ZIP. Renaming an unsupported file or repeatedly selecting the same incomplete cloud original will not address a decoding problem.

Check that the output tells the intended story

A useful document has enough context to be understood. For a support report, order the overview screenshot before the close-up. For receipts, keep a clear relationship between each image and its transaction. Do not combine unrelated people's records just because they fit the same batch. When some sources are much taller or wider than others, inspect every page rather than assuming the first preview represents the whole document.

For background on image formats, see the MDN image format guide. The layout examples and workflow advice here are based on this converter's behavior, not a claim that every format variant or device has been tested.

Build the document in a predictable order

Select at most 10 supported images, each up to 10MB, and wait for the previews before converting. Use the up and down controls to set page order; selecting a batch does not establish the document's intended reading order. Remove unrelated pages. Choose one merged PDF when the images form one packet, or separate output when they belong to different recipients or records. Several separate PDFs are downloaded together as a ZIP; extract it before attaching a PDF to a form.

The converter creates one page per selected image. It does not split a tall screenshot into several pages, combine multiple photos on one page, perform OCR, or make the text inside a photograph searchable. Crop, rotate or redact the source in an appropriate editor before selecting it here. Always make a copy before changing an important original.

Local processing and keeping your originals

Selected images are decoded and converted on your device; they are not sent to a conversion server. The website still requests its application files and can run analytics, so local conversion is not the same as an entirely offline website. The privacy policy explains those distinctions. This tool does not verify removal of personal information. A face, address, signature or account number can remain visible in the picture even if metadata changes.

Keep the source files until you have opened the downloaded result in the application that will receive it. For an application or a document portal, check that portal's permitted format and file-size limit separately: accepting your source here does not guarantee that another service accepts the result. A successful conversion also does not confirm that the browser finished saving the download. Find the saved file, open it, and check the content before sending it. For a reproducible problem, contact us with the tool, browser and settings rather than attaching private photographs.