BASALT · JOURNAL
How to merge PDF files on a Mac without losing anything
Combining PDFs on a Mac is easy right up until the merged file is missing something. Form fields stop accepting input, bookmarks vanish, internal links land on the wrong page, and nobody notices until the file is with the client. The merge itself is mechanical; what makes it lossy is everything in a PDF that lives above the page level.
What a merge actually does to the file
A PDF's pages are not a list. They live in a page tree: a root /Pages node whose /Kids array points at further nodes and at individual /Page objects, each carrying its own content stream, resources, and geometry. Merging means building a new page tree that references page objects from both sources.
Every object has a numeric identifier, and two documents both start at 1, so a merger renumbers one document's objects, rewrites every reference to them, and emits a fresh cross-reference table mapping each object to a byte offset.
Then there is the document catalog: /AcroForm for form fields, /Outlines for bookmarks, /Names for named destinations, /StructTreeRoot for tagged reading order. Each source has its own, a merge requires a decision about each, and the quiet failure is a tool that decides by discarding.
What Preview does, and where it stops
Preview genuinely merges PDFs, and it is worth saying so plainly. Open a file, choose View then Thumbnails, drag another PDF's icon into the sidebar, reposition, then File then Export as PDF. For three scans that carry nothing but ink, use it.
The limits appear on structured documents. Preview's page-level editing has no mechanism for carrying a source file's outline across, so those bookmarks are generally lost, and an AcroForm is document-level, so a merge that does not reconcile two of them can leave you with fields that no longer respond.
Preview also tends to save by appending: the changed objects go at the end of the file with a new cross-reference section pointing at them, which is the incremental update mechanism the format defines. The earlier revision is still in the bytes, which matters for anything sensitive and is covered in what is hiding inside your PDFs.
Order is a decision, not a default
Most merges are sequential. Two others come up often enough to matter.
The first is interleaving, or weaving. Your scanner does one side at a time, so the fronts are in one PDF and the backs in another, and the correct output is front 1, back 1, front 2, back 2. By hand in a thumbnail sidebar on a fifty-page document, that is a hundred drags and at least one mistake.
The second is the same job when the backs were fed through in reverse, so that file has to be consumed from its last page. Check the backs file's first and last pages before committing to a weave.
Bookmarks, and why generated ones beat inherited ones
The outline holds a title and a destination per entry, either an explicit page reference or a named destination resolved through the /Names dictionary. Explicit destinations survive a correct page copy. Named destinations are looked up by string, and two documents can both define chapter1, so concatenating name trees without resolving collisions produces links that go to whichever one survived.
For anything that will be read rather than filed, the useful behavior is a fresh top-level bookmark per source file. A hundred-page bundle built from twelve exhibits is navigable when the outline reads Exhibit A through Exhibit L, and a wall of pages when it does not.
Scans merge differently from generated documents
A PDF exported from Pages or Word carries text as glyph runs with embedded font subsets, so merging is cheap. A scan is a full-page image per page, usually a DCTDecode stream, which is JPEG, or JPXDecode, which is JPEG 2000. Merging fifty of those produces a file the size of the sum of its images, and nothing about the merge changes that. Shrinking it is a separate decision about downsampling, covered in compressing a PDF without wrecking the scans.
A merged scan also has no text layer. Run OCR after merging so recognized text is generated against final page numbering.
Doing it from the command line
qpdf is the honest scripting tool, since it operates on object structure rather than re-rendering:
qpdf --empty --pages a.pdf b.pdf 1-5 c.pdf -- merged.pdfIt will not reconcile two AcroForms and will not build an outline you never had.
Frequently asked questions
How do I merge two PDF files on a Mac?
Open the first PDF in Preview, choose View then Thumbnails, drag the second PDF from Finder into the sidebar where you want its pages, then File then Export as PDF to write a new file. That covers simple documents. If either file has form fields or bookmarks you need to keep, use an application that reconciles document-level structures instead of dropping them.
Does merging PDFs in Preview lose quality?
No. A merge does not re-encode page content, so text stays text and image streams are copied byte for byte. Quality loss on a Mac comes from a separate step, usually the Reduce File Size Quartz filter, which downsamples and re-encodes every image at one fixed setting. Merging alone changes no pixels.
Why did my form fields stop working after merging?
Form fields live in a document-level /AcroForm dictionary, so merging two documents means merging two of those. A tool that copies pages without reconciling them can leave fields orphaned and non-interactive. Field names are also global, so two files that both contain a field named Signature can end up sharing a single value. Always test the merged file by typing into a field.
Can I combine PDFs without Acrobat on a Mac?
Yes. Preview handles ordinary merges with nothing installed, qpdf does structural merges from the command line, and native Mac PDF applications cover what Preview does not, including interleaving and per-file bookmarks. Acrobat is not required, and for work that must stay on your machine a local app beats a browser upload.
How do I merge scanned fronts and backs into one PDF?
Use an interleaved merge, which takes page 1 of the fronts, then page 1 of the backs, then page 2 of each, until the pages run out. Doing it by hand means one drag per page and near-certain error on a long document. Check first whether the backs were scanned in reverse, because then that file must be read from its last page forward.
Will merging PDFs keep my bookmarks?
Not automatically. The outline is document-level, so a merge either combines both trees, keeps one, or discards both, and Preview's page editing does not carry the second file's outline across. The better outcome is a merger that creates a top-level bookmark named for each source file and nests that file's existing outline underneath it.
Is it safe to use a free online PDF merger?
It means uploading your document to a server you do not control, held for a retention period you cannot verify. For a train timetable that is nothing. For client data, medical records, or unfiled work product it is a disclosure. The reasoning is set out in what you agree to with cloud PDF tools, and a local application removes the question.
What if I merged the wrong pages?
Split the result apart or rearrange it, since both are non-destructive operations on a file you can rebuild. Splitting a PDF on a Mac covers extracting the ranges you meant to keep, and fixing sequence in place is a page-organizing job. Keep the sources until the output is checked.
Doing it in Basalt
Basalt merges files in the order you set, or weaves them page by page for scanned fronts and backs, and can add a bookmark for each source file so an assembled bundle is navigable. Every tool writes a new file, so the originals are never modified. The engine runs in a sealed process with no network entitlement, enforced by macOS at the code-signature level, so documents never leave the Mac and there is no account and no telemetry. Merging is one of 18 tools in one window, alongside splitting, OCR, and redaction. It is $29 once for up to three Macs, with a 24 hour free trial, at basaltformac.com.
Redaction that proves itself
Basalt destroys the content you mark, then re-opens the file it wrote and proves the content is gone before it saves anything. Your documents never leave your Mac.