Word to PDF
Word to PDF closes the loop between editable drafts and governed PDF outputs. DOCX files can be converted directly in the app, while legacy DOC files still require an office runtime on the host.
Best for
Contracts
Primary user task this route is designed to explain.
Output
Converted 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
Lets teams move from editable drafts back into PDF workflows
Feeds the same Documents workspace and job history surface
DOCX works directly; legacy DOC requires an office runtime on the host
Workflow in the app
01
Upload the Word document
02
Run the conversion
03
Review the resulting PDF inside Documents or download it directly
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
Converted PDF
Documents-ready PDF output
Job ledger entry
Related routes