5 real-world use cases for merging PDF files

“Merge PDFs” sounds like a developer nicety, the kind of task you’d expect engineers to need and nobody else. In practice, it turns out to be one of the most universal office skills of the 21st century. Lawyers, accountants, students, teachers, recruiters, managers, parents dealing with schools — everyone eventually hits a situation where they need to combine PDFs, and most people don’t have a great tool for it.

Here are the five situations that come up most often in practice, and how to handle each cleanly.

1. Contract + appendices + signatures

You’ve negotiated a contract with a supplier. The main document is 8 pages. There are two appendices — terms & conditions, schedule of deliverables — and a signature page that came back scanned. Your client wants one file they can file away.

The output you want: everything in order, text still searchable, the signature page correctly oriented.

Watch out for these pitfalls. The signature page was scanned upside down or at a weird angle — check and rotate before merging. One of the appendices may have a different page size (US Letter vs A4), which usually merges fine but can look odd if the files will be printed. And if the main contract has a digital signature on it, merging will invalidate that signature. Sign the merged file, don’t merge a signed one.

Recommended workflow:

1. Collect files in order: main contract → appendices → signature page
2. Check each opens correctly in two viewers
3. Merge
4. Verify total page count and spot-check the transitions
5. Send as one file, typically named something like <Contract> - <Client> - executed.pdf

2. Expense report: receipts + summary

Month end. You need to submit an expense report. Your company wants a single PDF with a summary page on top and receipts on subsequent pages. Your receipts are a mix of emailed PDF receipts, screenshots saved as PDF, and photos of paper receipts.

The output you want: summary first, receipts in the order they appear on the summary, total size manageable enough to email.

Photos of paper receipts are huge — 10+ MB each — so compress them first. Receipts in varying orientations (portrait/landscape) are fine; merging preserves each original orientation, which is what you want. But if the final file size creeps above your company’s email limit, go back and compress more before you merge again.

Recommended workflow:

1. Compress large photo-based receipts — for JPG/PNG in a PDF, run them through an Image Compressor, re-save as PDF
2. Create the summary page (Excel → Export to PDF is common)
3. Merge in the correct order
4. Check final file size — if it’s above 10 MB, go back and compress more

3. Course materials / study packs

A teacher sends you (or you compile for your class) a pack of readings: a book chapter, a research paper, a handout, and a worksheet. Students want one file, not four.

The output you want: predictable page numbers, everything readable, all text selectable for students who use highlighters or text-to-speech.

Here’s where it gets fiddly. Journal articles sometimes have DRM or encryption — strip those before merging. Scanned handouts might not have OCR’d text, so run OCR first if text needs to be searchable (the merger preserves existing text layers but doesn’t add new ones). Also, page numbers in the merged document won’t match the originals’ own page numbers — consider adding a table of contents as the first page.

Recommended workflow:

1. Verify each source has selectable text (if not, OCR first using an offline tool)
2. Add a “Contents” page at the start showing what’s in the pack and what pages
3. Merge
4. Distribute as a single file named clearly, e.g. Week 4 - Reading Pack.pdf

4. Job applications: CV + cover letter + portfolio

You’re applying for a role. The job spec says “submit a single PDF containing your CV, cover letter, and portfolio.” You have three separate files.

The output you want: professional ordering (cover letter first, CV second, portfolio third — or whatever the job spec asks), consistent look where possible, total file size under the upload limit.

Recruiters usually expect cover letter → CV → portfolio, but some prefer CV first. Check the job description. Portfolio PDFs can be enormous (high-quality images), so compress the portfolio first. And don’t use a sketchy online merger for this — recruiters often find CVs through Google searches, and a random online tool that keeps your file could expose it.

Recommended workflow:

1. Export each document fresh (don’t re-use an old PDF that might contain previous versions’ tracked changes)
2. Compress the portfolio if it’s above ~5 MB
3. Merge in the order the job spec requests
4. Name the output professionally: John Smith - Application - Senior Engineer.pdf
5. Use a local tool — never upload a CV to a random online service

5. Legal or medical records for a case

This is the one where privacy matters most. A lawyer compiling evidence, a patient preparing records for a second opinion, an HR manager preparing an investigation file. The documents are highly sensitive. The case may involve years of correspondence, scans, memos.

The output you want: complete chronological ordering, no content loss, no chain-of-custody issues.

Files arrive in wildly different formats — mix of PDFs, Word docs, image scans. Standardise on PDF first. Incorrect ordering is a common problem at scale, so name files with leading zeros and dates: 2023-01-15 - Letter from Client.pdf, 2024-03-02 - Medical Report.pdf. And using an online tool here is not acceptable. It may violate professional confidentiality rules (attorney-client privilege, HIPAA, GDPR). Always use a local tool.

Recommended workflow:

1. Convert all inputs to PDF first
2. Rename with leading zeros + dates + clear descriptions for consistent sorting
3. Merge using a local tool — no uploads, no external servers
4. Verify the total page count exactly matches the sum of inputs
5. Store the output in encrypted storage; don’t leave it on a shared drive

The common thread

Every one of these scenarios has the same underlying need: take several related PDFs and produce one canonical file, with the right page order, no quality loss, no privacy compromise.

In each case, the constraints point to the same answer: a local, browser-based merger that works on any reasonable file size, preserves text layers, keeps page orientation and sizing intact, and doesn’t upload anything. That’s exactly what the PDF Merge tool does — it runs in your browser using WebAssembly, so no file leaves your device. Three files or fifty, the process is the same.

A few power-user tips

Name files for sort order. 01-intro.pdf, 02-chapter.pdf, 10-appendix.pdf — always use leading zeros so alphabetical sort matches numerical order.

Keep a master copy of inputs before merging, in case you need to re-order or re-merge later.

Add a cover page or table of contents as the first file when the merged PDF will be read by others. It costs you 30 seconds and makes the result dramatically more useful.

Compress large images inside the source PDFs first if the inputs are photo-heavy. Merging doesn’t compress; the output is roughly the sum of the inputs.

Test the output in two different viewers before sending. Adobe Acrobat, your browser’s PDF viewer, macOS Preview — if the file opens correctly in all three, it’s well-formed.

Merging PDFs is one of those small tasks you end up doing hundreds of times across a career. Getting the workflow right once saves you hours over time — and for the sensitive cases, keeping the work local saves you a lot more than time.