Merge the documents by converting photos and scans to PDF first, then combining the PDF files in one browser tab, setting the order by hand and checking the page count before you submit. Nothing is uploaded, so passport pages and bank statements stay on your device.
Most problems at this stage are mechanical rather than legal: a missing page, a sideways scan, a file named scan_0042.pdf, or an attachment field that asks for one document and receives six. A single PDF also settles the question of order, because a reviewer reads your file from page one instead of opening attachments in whatever sequence the mail client shows them. Two facts shape the work. Pages keep the size they arrived with, so a mixed set never becomes uniform, and encrypted files have to be unlocked before anything can be merged.
An application pack is usually assembled from five to ten items produced by different people: a passport photo taken on a phone, a form downloaded as a PDF, a bank statement exported by an app, an invitation letter that arrived as a scan. Combining them is the last step, and the one most people rush. This guide covers the pipeline, the order reviewers tend to expect, and the limits of what a browser tool can honestly do.
Merge PDF
Add the PDFs, drag them into order, merge, download. Pages are copied rather than re-encoded, and the files never leave your device.
Why an application asks for one PDF
A single file is easier to route. Many portals attach one upload field per document type, and some embassies, universities and landlords ask for supporting documents as one PDF. One file has one page count, one file name and one place to look, so a reviewer can confirm nothing is missing without cross-checking a list of attachments.
It also changes what the reviewer sees first. With six attachments, the order depends on the mail client and the file names. With one file, page one is the page you chose, and the sequence after it is the sequence you built.
This article does not tell you which documents a specific country or school requires. Those lists are set by the recipient and published on the portal where you apply. What follows is only about turning that list into one clean file.
The four step pipeline
Work in this order. Merging before converting means merging twice, which is the usual way a pack ends up with duplicate pages.
- Turn photos and scans into PDFs. Anything that is not already a PDF, including a phone photo of a passport or a screenshot of a bank balance, has to become one first. Set the page size at this stage, not later.
- Merge the PDFs. Add every file, then arrange the list. The list order is the final page order, so this is where the structure is decided.
- Fix individual pages if needed. A sideways scan, a blank page or a misplaced page is handled by rotating, deleting or moving that page, not by rebuilding the pack.
- Compress only if there is a cap. If the portal states a size limit your file exceeds, run a lossless structural rewrite. If no limit is stated, skip it.
Image to PDF
Turn phone photos and scans into pages, one image per page, with A4, Letter or fit to image sizing and a choice of margin and fit.
The conversion step deserves attention because page size is still under your control there. Image to PDF accepts JPG, PNG, WebP, AVIF, GIF and BMP. JPG and PNG are embedded as they are, and the other formats are converted in the browser first. Each image becomes one page, and the list order is the page order.
Set A4 before you add anything if the pack is going to a European, Asian or African recipient, and Letter if a United States institution asks for it. Keep the margin at none unless the reviewer needs room for notes, and keep the fit at contain so nothing is cropped. Cover fills the page and cuts the overhang, which is fine for a photograph and a bad idea for a bank statement.
On a phone, the workflow in merging and splitting PDFs on a phone covers the same steps. The constraint is memory: a dozen photo pages are comfortable, and a hundred high resolution scans are not.
What order should the documents go in
There is no universal order, and any article that presents one as an official rule is guessing. A pattern that appears often enough to be a sensible default: identity first, then the request, then the evidence that supports it, then correspondence.
| Position | Document | Why it usually sits there |
|---|---|---|
| 1 | Passport or photo ID page | Lets the reviewer match a face and a name to the application immediately |
| 2 | The application form itself | Carries the reference number that the rest of the pack supports |
| 3 | Financial evidence | Answers the question the form raises first: can this application be funded |
| 4 | Invitation, admission or booking letter | Explains the purpose and the dates of the trip or course |
| 5 | Everything else, in checklist order | Anything the recipient listed but did not assign a place to |
Follow the recipient's checklist whenever the two disagree. A pack that starts with a bank statement because the applicant preferred it reads as careless even when every page is present. If the portal asks for a file name like surname_firstname_application.pdf, use that and add nothing else.
Keep multi-page items together. A six page bank statement should sit as six consecutive pages, not be split so that its first page follows the form. Merging follows the file list rather than the logic inside each file, which is why this mistake is common.
What happens when the page sizes do not match
A merged PDF does not have to be uniform, and this tool will not make it uniform. Each page is copied at its original dimensions, so an A4 scan, a 3:4 phone photo and a Letter form all sit in the same document at their own sizes. The file is valid and most portals accept it.
The problem appears when someone prints it. A viewer jumps between page shapes as you scroll, and a printer either scales each page to the paper or centers it with uneven white space. The pack stays readable, but it looks like a stack of documents rather than one file.
| What you need | Where to do it | What actually happens |
|---|---|---|
| Photos become same size pages | Image to PDF | Choose A4 or Letter before creating the PDF |
| A sideways page straightened | Organize PDF | The page rotates, its dimensions stay as they were |
| A blank or duplicate page removed | Organize PDF | The page is dropped from the export |
| Page numbers added | Organize PDF | Numbers are drawn on export, with a starting number and a position |
| Existing PDF pages resized to A4 | Not available | No tool here rescales the contents of an existing page |
If uniformity matters, decide before the merge. Rebuild the image pages at a fixed A4, and accept that PDFs issued by a bank or a government portal keep their own size. Those are usually A4 or Letter already, so the mismatch is normally between a properly sized document and a phone photo, which is the part you control.
Unlock protected files before you start
An encrypted PDF cannot be merged. The pages are locked behind a password, so the merge has nothing to copy and the file is rejected rather than skipped. Bank statements are the usual culprit, because many banks send them encrypted with a partial account number or a date of birth.
Unlock it first, in your PDF reader or with the unlock tool, which asks for the password and writes a decrypted copy in the browser. Delete that copy once the pack is built: an unprotected bank statement in a downloads folder is the file you do not want to forget.
Once the merged file exists, the situation reverses. If you email it rather than upload it, protect the result; the steps are in password protecting a PDF before emailing it, including sending the password through a different channel. A password in the same email as the document protects nothing.
Checks to run before you submit
Five minutes of checking prevents the most common rejection reasons, and none of them require the original documents again.
- Count the pages against the checklist. The merge tool reports the total, so compare it before uploading. A missing attachment is invisible once everything is one file.
- Open the first page and the last page. Confirm the pack starts where you intended. A file dragged to the bottom of the list by accident is easy to miss.
- Check orientation on every scanned page. A page rotated 90 degrees is unreadable on paper. Rotate it in Organize PDF and re-export.
- Confirm the size limit, if there is one. The limit is set by the recipient, not by this site. The compress tool accepts files up to 50 MB and rewrites the structure losslessly, so it will not rescue a file that is large because of high resolution photos.
- Name the file as instructed. With no instruction, use the applicant name and the document type, with no spaces and no version numbers like final2.
- Do not expect OCR or a certificate signature. A scanned page stays an image of text, and the signature tool places a picture of your handwritten signature rather than adding a certificate.
Privacy when the pack contains identity documents
A passport page, a national ID, a bank statement and a medical letter are the documents that make identity theft straightforward, and a pack usually contains three of them. That is the reason to care where the merge happens: a copy on an unknown server is a copy you cannot delete.
Here the merge runs in the page. The PDFs are read into the memory of the tab, combined with pdf-lib and written back as a download. There is no upload, no queue and no retention period, because no server holds the file. You can verify it: open the developer tools, switch to the network panel and watch while a merge runs.
The honest limits are about your environment. Files stay in the tab, so a large pack is bounded by device memory. A shared computer keeps its download history, extensions with page access can see what the tab sees, and a phone will struggle sooner than a laptop. Close the tab, delete the working copies, and keep the final file somewhere you control.