Free · Fast · Privacy-first

Merge PDF Files for Lawyers and Legal Professionals

Legal practice runs on assembled PDF bundles.

⚡

No watermark on court-ready bundles

🔒

Local-only processing protects privilege

✨

Drag-to-reorder for exhibit sequencing

⚡

Handles large discovery production volumes

Cost: Free forever
Sign-up: Not required
Processing: In your browser
Privacy: Files stay local

FreeNo signupWhite-label

Add this PDF Merger to your website

Drop the PDF Merger into any page — blog post, product docs, intranet, school portal — with a single line of HTML. Your visitors get the full tool, processed entirely in their browser. No backend, no uploads, no signup.

Files stay 100% in the visitor's browser
Responsive — adapts to any container width
Free forever, no API key needed

Embed code

<iframe
  src="https://www.fixtools.io/pdf/pdf-merger?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="PDF Merger by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

<iframe
  src="https://www.fixtools.io/pdf/pdf-merger?embed=1"
  width="100%"
  height="780"
  frameborder="0"
  style="border:0;border-radius:16px;max-width:900px;"
  title="PDF Merger by FixTools"
  loading="lazy"
  allow="clipboard-write"
></iframe>

Attribution-friendly: a small "Powered by FixTools" link appears in the embed footer.

Court filings, depositions, discovery: legal PDF assembly workflows

Court filings have specific bundle requirements that vary by jurisdiction but share common themes. Federal court electronic filing systems like CM/ECF require a single PDF per filing event with specific size limits (often around 35MB for most courts), proper bookmarking, and OCR-searchable content. State court systems vary but most enforce similar single-PDF requirements through their e-filing portals. The typical filing bundle includes a cover or motion document, supporting memorandum, declaration with exhibits, and certificate of service, all in a specific order. Assembling this through FixTools means dragging the four source PDFs into the correct order (cover first, memorandum next, declaration with exhibits next, certificate of service last) and producing one merge for upload. The order in the file list directly becomes the page order in the filed bundle, which is essential for the court to navigate the document.

Deposition packages add the dimension of exhibit numbering. A deposition transcript is one PDF, but the deposition often references thirty or forty exhibits each produced as a separate PDF during the deposition itself or supplied by counsel afterwards. The complete deposition package typically includes the transcript first, then each exhibit in numbered order, then any errata sheets. FixTools handles this by accepting upload of the transcript plus all exhibits in one selection, then letting the paralegal drag the exhibits into numbered order behind the transcript. For depositions with very large exhibits (forty or more), the multi-pass batched approach described on our bulk merge page may be more reliable than a single-pass merge, producing intermediate exhibit batch PDFs that consolidate into the final deposition package.

Discovery production is the highest-volume legal merge scenario, with productions ranging from dozens to thousands of Bates-stamped documents per delivery. The production order is typically determined by Bates number, which means files should be pre-named with Bates prefixes (such as SMITH_000001, SMITH_000002, etc.) so they sort correctly in the file manager and arrive in the FixTools merger in proper order. For productions over one hundred documents the multi-pass approach is the right choice, producing intermediate batch PDFs that get consolidated into the final production delivery. The output is a single PDF that can be uploaded to the opposing counsel secure transfer portal or burned to media for physical delivery, with the Bates sequence preserved and verifiable.

Privilege protection is the load-bearing reason legal users specifically need a local-only merge tool rather than a cloud service. Uploading privileged documents to a third-party cloud merger could in some jurisdictions be argued to waive privilege, depending on the terms of service of the cloud provider and the specific circumstances. FixTools runs entirely in the browser tab using the pdf-lib JavaScript library, with no document data ever transmitted to any server. You can verify this in your browser developer tools Network tab during a merge, no outbound traffic carrying document content appears. This local-only processing model is the strongest available posture for handling privileged material short of an air-gapped offline tool, and it preserves the privilege analysis that legal users need to defend if challenged later.

CM/ECF filing requirements Federal Rules of Civil Procedure

How to use this tool

💡

Upload pleadings, exhibits, and supporting documents. Arrange in court-required order, then merge into a single court-ready bundle. No watermark on output.

How It Works

Step-by-step guide to merge pdf files for lawyers and legal professionals:

1
Verify the court bundle requirements
Check the specific court local rules and the e-filing portal documentation for required bundle structure, page numbering conventions, bookmarking requirements, OCR mandate, and maximum file size. Federal CM/ECF generally requires 35MB per filing event with proper OCR, state courts vary. Knowing the requirements before merging prevents rejected filings and resubmission delays.
2
Pre-name source files with order prefixes
Rename your source PDFs with numeric prefixes that match the intended bundle order, such as 01_Motion, 02_Memorandum, 03_Declaration_Smith, 04_Exhibit_A, 05_Exhibit_B, 06_Certificate_of_Service. This pre-sorting ensures files arrive in the merger in correct order, minimising manual drag work and reducing the risk of ordering errors.
3
Upload to FixTools merger
Open the FixTools PDF Merger and upload all source files in one selection. Verify in the file list that every expected file is present and the count is correct. Missing files at this stage are easier to fix than after merging. Add any missing files using the additional upload control before proceeding.
4
Verify and adjust the order
Confirm the file list order matches your intended bundle structure. Drag any out-of-order files to their correct positions. For complex bundles with many exhibits, walk through the list against your index or table of contents to catch ordering issues before merging. This verification step is faster than detecting and correcting issues after the merge completes.
5
Merge and prepare for filing
Click Merge. The browser produces the consolidated bundle PDF as a download. Rename the file to match the court e-filing naming convention if one applies. Verify the page count against your expected total, open the bundle to check critical sections, and apply Bates numbering or bookmarks using separate tools if the court requires them before uploading to the e-filing portal.

Real-world examples

Common situations where this approach makes a real difference:

Civil litigator filing summary judgment motion

A litigation associate is filing a motion for summary judgment in federal court. The filing bundle includes the motion, a fifty-page memorandum of law, the declaration of the client with twelve exhibits, and the certificate of service. The associate uses FixTools to combine these into one bundle in the required order, producing a 180-page filing-ready PDF under the 35MB CM/ECF limit. The output is then OCRed and bookmarked using separate tools before upload.

Litigation support paralegal building deposition exhibits binder

A paralegal is producing the complete deposition package for the deposition of a key witness. The package includes the 250-page transcript and forty-five referenced exhibits collected during and after the deposition. Using the multi-pass approach in FixTools, the paralegal merges exhibits in batches of fifteen producing three intermediate exhibit packets, then merges the transcript with the three intermediates into one final 800-page deposition package for the trial team.

Discovery production for opposing counsel delivery

A litigation team is producing 750 Bates-stamped documents in response to a discovery request. The documents are pre-named with Bates prefixes (BAKER_000001 through BAKER_000750) which sorts them correctly in the file manager. Using the multi-pass batched approach, the team produces eight intermediate batch PDFs of around 100 documents each, then merges those into one final consolidated production for upload to the opposing counsel secure transfer portal.

Transactional lawyer assembling closing binder

A corporate associate is producing the closing binder for an acquisition transaction with sixty executed documents (purchase agreement, ancillary agreements, board resolutions, officer certificates, third-party consents, opinion letters). Each document is its own PDF with executed signature pages. The associate uses FixTools to merge in table-of-contents order producing a single closing binder PDF that gets distributed to all parties at closing as one definitive record.

Pro tips

Get better results with these expert suggestions:

Pre-name files with the bundle order prefix

Use numeric prefixes that match your court bundle index, such as 01_Motion, 02_Memorandum, 03_Declaration. When you select and upload all files at once, they arrive in the merger in correct order, eliminating most manual reordering work. For bundles with subsections (such as Exhibit A having Sub-exhibits A.1, A.2, A.3) use decimal prefixes that sort consistently like 04.01, 04.02, 04.03.

Verify privilege posture before merging

Before uploading any privileged documents to FixTools (or any other web tool), confirm using browser developer tools that no document content is transmitted to a server during the merge. Open the Network tab, perform a test merge with non-sensitive files, and observe that no outbound traffic carrying file payload appears. Once verified, the same local-only behaviour applies to your privileged merges, supporting the privilege analysis you need to defend if challenged.

Keep working copies until the matter closes

Do not delete source files or intermediate batch PDFs until the matter for which the bundle was prepared has fully closed and any deadlines for appeal or post-judgment motions have passed. If a sealed exhibit needs to be added or a section needs to be replaced after the original filing, having the source files available means you can rebuild the bundle quickly rather than reconstructing it from the final merged document.

Bookmark after merging if the court requires it

Many courts require PDF bundles to include internal bookmarks linking to each major section of the filing for easier judge and law clerk navigation. FixTools merger does not currently add bookmarks (this is a planned feature). After merging, use a separate PDF bookmarking tool to add the bookmarks before filing. The bookmarks typically link to each exhibit and to the start of the memorandum, declaration, and certificate of service sections.

FAQ

Frequently asked questions

Yes, with the standard understanding that you should verify the local-only processing posture for your own use case. FixTools runs entirely in the browser tab using JavaScript and the pdf-lib library, with no document data transmitted to any server during the merge. You can verify this independently using browser developer tools Network monitoring during a test merge. This local-only processing posture is the strongest available short of an air-gapped offline tool, and it supports the privilege analysis that legal users need to defend if challenged in court. Many law firms have approved FixTools for privileged work after this verification.

FixTools produces a clean merged PDF without watermarks, which meets the basic court bundle requirement. Specific court formatting requirements such as bookmarks, Bates numbering, OCR-searchable content, and signed metadata are handled by separate tools applied to the merged output. The typical legal workflow is: merge in FixTools to produce the consolidated bundle, then apply Bates numbering using a Bates tool, then OCR using an OCR tool, then bookmark using a bookmarking tool, then upload to the court e-filing system. Each step uses the right specialized tool for that requirement.

Yes, using the multi-pass batched approach for productions over 100 documents. Single-pass merges work fine up to about 100 documents on a typical workstation. For productions of 500 to 5000 documents, work in batches of 100 producing intermediate batch PDFs, then consolidate the intermediates into the final production delivery. This approach is reliable, resumable, and produces output identical to a single-pass merge would have. The multi-pass workflow is described in detail on our bulk merge 1000 page and applies directly to discovery production volumes.

Digital signatures on source documents do not validate in the merged output. This is because a digital signature mathematically binds to the specific bytes of the file it was applied to, and merging creates a new file with different byte content. The visual representation of the signature remains in the merged PDF but the underlying cryptographic seal is broken. For legal contexts where signature validation matters (such as a signed declaration filed with a court), file the signed source document separately or as a standalone exhibit, or have the signer re-sign the merged bundle itself if that meets the procedural requirement.

Not directly in the merger itself. After merging, use the FixTools PDF Page Numberer or a dedicated Bates numbering tool to apply Bates stamps to the merged bundle. Bates numbering for production typically requires a specific prefix and starting number agreed with opposing counsel (such as SMITH_000001 onwards). The Bates tool overlays these numbers on each page of the merged bundle, producing a Bates-stamped version ready for production delivery. The merge step and the Bates step are separated because they serve different purposes and use different tools.

The merged bundle is a standard PDF that conforms to general PDF specifications. Specific format requirements like PDF/A (for archival), text-searchable content, or particular metadata profiles need to be applied as additional steps after merging. For PDF/A conversion, use a dedicated PDF/A converter tool on the merged output. For text searchability, run OCR on the merged bundle using an OCR tool such as ocrmypdf or Adobe Acrobat. The merger itself does not change the underlying PDF content, so OCR text layers from source files are preserved in the merged bundle.

FixTools is designed for use by anyone in the legal team including paralegals, legal assistants, litigation support specialists, and lawyers. The role-appropriate use of the tool depends on firm policy and case-specific delegation, not on any tool restriction. In typical practice, paralegals and litigation support staff handle the bulk of merger work for bundle assembly, with lawyers reviewing the final output before filing or production delivery. The tool itself imposes no user role restrictions because it is a standard web tool open to anyone with browser access.

When the same exhibit is referenced in multiple sections of a bundle (such as Exhibit A appearing as part of both Volume 1 and Volume 2 of a multi-volume filing), upload that exhibit twice to the merger, once for each position where it should appear. The merger treats each upload as a separate file, so the same source exhibit can appear in multiple positions in the merged output. This produces a self-contained bundle where every reference is accompanied by the exhibit content, which is usually preferred over cross-references that require the reader to flip backward through the document.

Most state bar cloud computing guidance focuses on data residency, privilege protection, and reasonable security practices. FixTools local-only processing model addresses these concerns by ensuring no document data is transmitted to any server. The standard practice is for the firm to verify FixTools posture independently through the browser developer tools Network monitoring approach, document the verification in the firm cloud computing policy, and use the tool consistent with that policy. Specific state bar opinions vary, so consult your firm general counsel or your state bar ethics guidance for the definitive analysis for your jurisdiction.