Paperweight user and administrator guide
Paperweight helps your team turn scans and incoming documents into consistent PDF or TIFF files. Capture pages from a scanner or use a watched folder, then let Paperweight apply your organization's settings, check the result, and deliver it to the selected destination folder.
Product 0.1.0 · Documentation revision 2 · 2026-09-12 · Public preview
Start here
- Operators: follow Scanner capture, then learn to read processing activity.
- Administrators: start with Install and configure, review the configuration reference, and choose a deployment strategy.
- Support staff: use Operations and recovery and Troubleshooting.
Prefer an offline reference? Download the Paperweight Manual to read this guide as a PDF.
Requirements
| Requirement | What to prepare |
|---|---|
| Endpoint | Windows 11 x64; a standard-user interactive session for operation |
| Installation | Administrator or SYSTEM access to install the per-machine MSI and deploy policy |
| Scanner | Separately installed vendor TWAIN or WIA driver for your scanner model |
| Working storage | Protected fixed local disk for each user's job store; no UNC spool or known OneDrive location |
| Destination | Existing local or SMB intake folder and a separate staging folder on the same filesystem root |
| Access | The signed-in operator needs the actual scanner, source, staging, and destination permissions |
The application includes its .NET runtime, so operators do not need to install it separately.
What you can do
Capture and review scanned pages, process incoming files, and track local activity and storage savings. Paperweight keeps each job's originals and settings for recovery, checks the processed document, and delivers files without overwriting existing documents. Use the Capture, Activity, Configuration, and About tabs to get around. Closing the window leaves Paperweight running in the notification area.
Folder intake considers PDF, TIFF, JPEG, and PNG files. The actual format is checked from content, not trusted from the extension. Profiles produce PDF or TIFF. There is no OCR, semantic classification, Windows service, EHR API, management server, or telemetry upload in this version.
Important
This guide covers the current Paperweight preview. See Release notes and limits for features and known limitations.
What Published means
Published means Paperweight completed a filesystem handoff. It does not mean a document was accepted by an EHR or another downstream application. An absent destination file after interruption can mean that a consumer already removed it. Reconcile uncertain delivery before taking action.