Assemble one PDF from pages spread across many files

Six documents from three places, one upload field

Amara is applying for a student visa. The online application has a single field for supporting documents, accepts one PDF, and its guidance lists the order the officer expects. What she has is scattered across her laptop, her phone and her inbox:

• a scan of her passport photo page, already a one-page PDF;
• a three-page admission letter emailed by the university;
• a 12-page bank statement, of which the checklist only wants the final page with the closing balance;
• a two-page sponsor letter her uncle wrote in Word;
• a phone photo of a signed declaration;
• a hostel booking confirmation that exists only as a web page.

None of those is a "page" yet in the sense the upload field needs. This guide turns each one into a PDF page, then assembles them. Joining whole files that are already finished is a simpler job, covered in the guide to joining a stack of PDFs.

Where each page lives now, and how it becomes PDF

For the bank statement, Amara types 12 into the page box in Extract PDF pages and gets a one-page file. The declaration photo goes through Images to PDF on A4 with a narrow margin, so it ends up the same size as the printed letters around it.

Put the packet together in PDFGym

1. Collect the finished PDFs in one folder, named so you can recognise them: passport.pdf, admission.pdf, statement-p12.pdf and so on.
2. Open Multiple PDF to one PDF and add them all at once.
3. Read each row. It shows the page count of that file, and the line underneath gives the total. For Amara's six parts, 1 + 3 + 1 + 2 + 1 + 1 should read 9 pages.
4. Move rows with the up and down arrows until they follow the checklist exactly.
5. Look for a notice under any row. If a file has form fields, bookmarks or attachments, the tool says the merged copy may not keep them.
6. Merge, wait for the check to finish and download. The file is called after the top row with "-merged" on the end, so rename it to whatever the guidance asks, such as surname-supporting-documents.pdf.

Check the packet against the checklist

The merge tool has already compared the page count, the page sizes and the text of every page with the sources. What it cannot judge is whether you followed the checklist. Open the file and go through it once:

• The page total matches what you expected from the list.
• Each checklist item starts on a page that looks like its own first page.
• No page appears twice, and nothing the checklist did not ask for slipped in.
• Photos and scans are upright and readable at normal zoom.
• Signatures are visible on every page that needs one.

If a page is out of place, open the merged file in Organize pages. Pages can be dragged or moved with arrows, deleted, and undone if you change your mind, without going back to the sources.

Errors that get a packet sent back

A whole document where one page was asked for. The merge always copies complete files. Twelve pages of statement in place of one makes the officer hunt, so extract first or delete afterwards.

A locked file stops the merge. Some banks protect statements. The tool refuses password-protected PDFs, so unlock a copy first.

A filled-in form loses its answers. Interactive fields may not survive the merge. Run a completed fillable form through Flatten PDF first, so the answers become part of the page.

Pages of wildly different sizes. A photo turned into a page with Match image can be huge next to A4 letters. Rebuild it on A4 or US Letter, as in the table.

Merging a digitally signed document. The merged copy is a new file, so an embedded digital signature no longer validates. Visible handwritten signatures are fine.

When to ask for the documents in another form

If the portal offers a separate upload field per item, use it. Officers and admissions teams often prefer that, and it removes any doubt about order. If an institution can issue a single official PDF, such as a bank letter confirming the balance, that is cleaner than a page extracted from a statement, and it carries their own formatting.

Where a document must keep a verifiable digital signature, send it as its own file and mention it in the main packet. And if the merged file is over the size limit, compress it as the very last step, after you have checked every page.