How to Merge PDF Files Without Losing Formatting

Proposal packs often mix Canva covers, Excel pricing exports, and Word terms. Individually each file can look fine. Merged into one PDF, type size and fonts can shift when sources used different generators or unembedded fonts — for example a pricing table sitting half a point smaller, or a cover font falling back to a generic substitute.

Nothing was "broken" in a technical sense. The merge worked. The document just looked unprofessional — and that's the problem most people hit when they combine PDFs without thinking about how those PDFs were built.

The real problem merging solves

You're not merging because you love PDFs. You're merging because someone — a hiring manager, a university portal, a client — wants one attachment, not four. Maybe you're bundling a resume and cover letter. Maybe you're stitching invoice pages with supporting receipts. Maybe you're assembling a report that different people edited separately.

The goal is simple: one file, correct page order, no surprises when the recipient opens it on their phone, their Mac, or a dusty office PC running an old Acrobat build.

Formatting loss usually shows up as:

• Font substitution (letters look slightly wider or thinner)
• Margin shifts (content sits higher or lower on the page)
• Resolution changes (scans turn soft or overly sharp)
• Color profile mismatches (blues look dull on screen)

Understanding where your PDFs came from prevents most of this.

When merging is the right move

Merge when all sections are final and you need a single deliverable. Good fits:

• Job applications (resume + cover letter + portfolio excerpt)
• Client packets (statement of work + rate sheet + signed NDA)
• Course submissions where the portal accepts one upload
• Internal archives ("Project X — complete record")

Skip merging when recipients only need one section, when files exceed upload limits even after compression, or when you still expect tracked changes in Word. Edit first, export to PDF, then merge.

Step-by-step: merge without mangling layout

1. Start from the best source each time

Export PDFs from the original application when you can. A Word doc saved as PDF embeds fonts more reliably than printing to PDF from a browser window. Excel exports preserve table lines better than screenshots pasted into Docs.

If a section already exists only as a scan, treat it as fixed pixels — you won't fix typography later without OCR.

2. Embed fonts before export

In Word: File → Options → Save → Embed fonts in the file. In InDesign or Affinity, use PDF export presets that include font embedding. Canva's PDF export generally embeds outlines for text elements, but double-check on a machine that doesn't have Canva installed.

3. Normalize page size where it matters

US Letter (8.5×11) and A4 differ by enough to create awkward jumps when combined. If your audience is North American, stick to Letter throughout. For EU clients, A4. Mixed sizes can merge, but readers notice the visual jump.

Use Rotate PDF if any export arrived sideways from a phone scan before you merge.

4. Merge in deliberate order

Open Merge PDF, upload files, and drag them into sequence. Think like a binder: cover → main content → appendices → signed page.

For large projects, merge in chunks:

1. Merge chapters 1–3
2. Merge chapters 4–6
3. Merge those two results with appendices

That beats uploading twenty files at once and losing track of order.

5. Open the result on a second device

Your laptop may have fonts installed that your client lacks. Check the merged PDF on a phone or ask a colleague to open it cold. Font substitution shows up immediately.

6. Compress only after you verify layout

Once pages look correct, run the merged file through Compress PDF if email size is tight. One compression pass on the final file beats compressing each source separately.

Worked example: freelance proposal packet

Inputs

• cover.pdf — Canva, A4, full-bleed background
• scope.pdf — Google Docs export, A4, text-heavy
• signature.pdf — scanned PNG saved as PDF, 300 dpi

Workflow

1. Re-export scope.pdf from Docs with embedded fonts.
2. Crop the scan's white borders in an image editor, then save as PDF (or use JPG to PDF if you only have photos).
3. Merge: cover → scope → signature.
4. Preview on phone — signature page should not look zoomed compared to scope text.
5. Compress to under 8 MB for Gmail.

Total time: about twelve minutes. Much less than re-doing the layout after a client complaint.

Common mistakes (and fixes)

Merging editable Word files instead of PDFs
Word's "combine documents" is not the same operation. Export each section to PDF first, then merge PDFs. You'll avoid section break chaos.

Using "Print to PDF" for everything
Browser print routes often rasterize content. Use native export buttons.

Ignoring rotation on phone scans
Sideways pages rotate in the viewer but still confuse print shops. Fix rotation pre-merge.

Merging locked files
Password-protected inputs fail silently or produce partial output. Unlock, merge, re-lock.

Assuming merge fixes blank pages
If a source file has an accidental blank page, merge preserves it. Run Split PDF to drop blanks first.

Browser compatibility notes

Modern Chromium, Firefox, and Safari handle merged PDFs consistently when sources were digital exports. Scanned pages are images — they display anywhere, but text won't be selectable unless OCR ran before merge.

Mobile viewers sometimes reflow reflowable PDFs; most merged business PDFs are fixed layout and look identical across devices.

Privacy considerations

Browser-based merge tools like Vertex Solutions process files locally when implemented client-side — bytes don't need to sit on a server for the operation to complete. Still avoid uploading confidential contracts on unknown websites. For sensitive material, use offline tools you trust, or merge inside your organization's approved suite.

Read more in our guide on how browser PDF tools protect privacy.

Alternatives to merging

• Zip archive — Send multiple PDFs when recipients pick sections independently.
• Portfolio links — Notion or Google Drive folders for large media-heavy packets.
• PDF packages with bookmarks — Some desktop apps add navigation without flattening sources; heavier workflow, better for 100+ page manuals.

Page numbers after merge

Merge tools concatenate pages; they rarely rewrite footer text. If each source PDF already has “Page 1 of N” baked into the content, the merged file will show multiple “Page 1” footers even when physical order is correct.

Before merge:

1. Prefer exports without sectional page numbers, or use one authoring template with continuous numbering
2. Name files 01-…, 02-… so order matches narrative
3. Fix rotation first — Rotate PDF

After merge:

1. Skim section boundaries for restarted footers
2. If one section is wrong, re-export that source without footers and merge again (Split PDF helps extract it)
3. Apply continuous numbers or Bates stamps after assembly when the packet requires them — browser merge does not replace legal Bates tooling

PDF reader sidebar page indexes (physical sheets) can differ from printed footer numbers when covers suppress numbering — say which system you mean when you cite “page 12.”

Related reading

• How to Merge PDF Files Into One Document — baseline merge walkthrough
• Legal PDF Page Numbering Conventions — Bates and filing habits
• Word to PDF Conversion Tips — cleaner exports before merge
• When Should You Compress a PDF? — sizing the final attachment

Conclusion

Merging PDFs without losing formatting is less about the merge button and more about what you feed into it. Embed fonts, match page sizes where you can, fix scans and rotation early, verify on a second device, then compress once at the end.

Do that and merge stays boring — which is exactly what you want when someone's judging your proposal by how polished page three looks.