BASALT · JOURNAL
How to merge PDFs without duplicate pages
Merging files from several people often creates duplicate covers, repeated signatures, or the same exhibit in different folders. A clean merged PDF begins with a page inventory rather than a blind append operation.
Build a source list
Record each filename, version, page count, and intended position. Compare titles and page thumbnails for repeated covers or scans. Check whether a file includes an attachment or appendix that another source already contains.
Merge and normalize carefully
Preserve meaningful page labels and bookmarks, but avoid carrying draft comments and unnecessary metadata into the combined file. Review different page sizes, orientations, and scanned quality after the merge.
Verify the final packet
Compare expected and actual page counts, search for duplicate identifiers, inspect attachments, and test bookmarks. Keep the component files and final version separate so the packet can be reconstructed.
Frequently asked questions
Should duplicate covers always be removed?
Usually, but preserve a cover when it identifies a distinct exhibit or required section.
Can duplicate pages expose inconsistent data?
Yes. One copy may contain a later or less-redacted version. Compare them before merging.
Should merged PDFs share metadata?
Update title and version metadata intentionally; do not blindly keep the first file’s author or path.
Doing it in Basalt
Basalt merges PDFs locally and keeps page order, attachments, and document properties available for review before export. Download Basalt.
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.