Merge PDF
Merge PDF is built for the common case where several related files need to become one clean packet. Signed-in runs save the merged output into Documents so the combined file can be downloaded, shared, or reused in later PDF workflows.
Best for
Diligence rooms
Primary user task this route is designed to explain.
Output
Combined PDF
What the logged-in workspace will hand back after processing.
Workspace
Login required
Public pages explain the workflow; the signed-in workspace runs it.
This page is written for search and discovery. The actual file work happens in the signed-in PDF workspace so preview, versions, sharing, and job history stay in one place.
How it works
Understand the job here, then finish it inside the workspace.
The public route stays simple on purpose: explain the use case, show the output, and route signed-in users into the workspace where the file can be previewed, edited, versioned, and shared.
What this route does
Multi-file intake tuned for proposal and diligence workflows
Merged outputs can land as new workspace documents
Modeled after lossless merge assembly for multi-file jobs
Workflow in the app
01
Select the PDFs that belong in one bundle
02
Review file count and total page count
03
Create a single combined document for sharing or downstream work
Signed-in workspace
Open the file once, then keep every action attached to the same document.
What happens after login
Upload the source file into the document library.
Open the file in the full-screen PDF workspace.
Run the action against the saved document directly.
Keep versions, outputs, and share links tied to that same file.
Why this is simpler
No duplicate public-vs-private execution flows to learn.
The workspace runs actions against the saved file, not a throwaway upload.
Job history and version history stay readable from the same document.
Workspace outcomes
Combined PDF
Job ledger
Documents handoff
Related routes