Merge & submit
The form wants one PDF. Don’t upload a photo per page
Registration portals, visa packs, and admin uploads often reject “one image, one file.” The fix is not exporting many PDFs — it is stacking your pages into a single document, in the order a reviewer will read.
Exam signup, onboarding paperwork, a visa pack, or phone photos of a contract: the portal asks for one PDF, and a zip of JPGs or “one file per page” usually fails. Reviewers also bounce packs when page 3 arrives before page 1.
Decision in one line: stack the images in reading order, then export a single PDF — not one PDF per photo.
1. Why a pile of images is the wrong answer
Most forms are built for a document, not a gallery. They want ID front → ID back → diploma → photo in one attachment. Uploading each shot separately looks like an incomplete pack; a zip often is not accepted at all.
That is also why this job is unlike compression or format conversion. Those tools process many files and return many files. Images to PDF is a merge: many images in, one PDF out.
Selecting 10 photos does not create 10 PDFs. Each photo becomes one page of the same document. If you truly need separate PDFs, split the set and generate each batch on its own.
2. Put pages in order, then generate once
Open Images to PDF and treat the list as the table of contents a reviewer will flip through:
- Collect the pages — JPG, PNG, WebP, or GIF; about 20MB each, up to 50 images in one merge.
- Straighten crooked shots first — a sideways ID or scan should go through Rotate & Mirror before it enters the list.
- Drop the images in — multi-select is fine. Each row is one PDF page. Drag a row or use the arrows if the order is wrong; replace or delete a page without clearing the rest.
- Pick a page size — A4 portrait plus a standard margin fits most formal submissions. Use landscape for wide tables, or auto-fit when the pack is only for on-screen viewing.
- Generate and download one file — the tool assembles the PDF in the browser. Check the page count, then attach that single file.
3. A short check before you hit generate
- Reading order matches the form (front before back, page 1 before page 2).
- No page is sideways or upside down.
- You are about to download one PDF, not a folder of singles.
- If the portal also caps file size, lower the quality slider — or compress the source images first, then merge again. When a KB number is printed on the form, follow the target-KB walkthrough.
The merge stays on your device. Application scans and ID photos are assembled in the browser; they are not sent to an upload backend just to become a PDF.
Wrap-up
When a form says “PDF only,” the job is order plus a single file — not a batch of look-alike documents. Line the pages up, generate one PDF, and only then worry about a size cap. That sequence matches how most submission portals actually read your pack.
Extra
After you merge
If I add many images, do I get one PDF per photo?
No. Images to PDF always outputs a single file: each image becomes one page, in list order. That is a merge, not the same “one result per file” behavior as compress or convert. Need several independent PDFs? Split the photos into separate batches and generate each pack on its own.
The pages came in the wrong order. Can I fix that before export?
Yes. Drag a row, or use the up/down arrows, then generate. You can also replace or delete a single page without starting over.
A scan is sideways or upside down. Should I rotate after the PDF is built?
Rotate first. Use Rotate & Mirror on the crooked shot, then drop the straightened image into the merge list. Fixing orientation before you generate saves a second export.
The portal still says the PDF is too large. What next?
Lower the in-tool image quality and generate again. If it is still over the cap, compress the source photos first — the target-KB guide walks through that — then merge once more.