PaperlessZen™ Desktop
Every digitization effort hits the same bottleneck, and it is not search or storage. It is intake. The documents that matter arrive on paper, from a copier, a scanner, or a fax line, and someone has to turn each one into a file the institution can actually find. That someone has better things to do, so the paper waits.
PaperlessZen™ Desktop is being built to end that wait. It is a small Windows app that lives in the system tray, watches the folders your scanners and copiers already write to, and reads each page on the machine itself. A scan becomes a searchable PDF before it ever leaves your desk.
Capture where the paper is
The office copier already scans to a network folder. The desk scanner already has a button. PaperlessZen Desktop is designed to sit behind both: point it at the folders your devices write to, and every page that lands there is read, cleaned up, and turned into a searchable PDF automatically. Drop a file on it, or send one from Explorer, and the same thing happens.
Scan
The copier or scanner does what it already does: writes a file to a folder.
Read locally
The app picks it up and reads every page on your machine. Nothing is sent anywhere.
File
A searchable PDF lands in your folders, named and findable. The source file is never destroyed.
Find
A global hotkey opens search across everything the app has read. The answer is a keystroke away.
Scan
The copier or scanner does what it already does: writes a file to a folder.
Read locally
The app picks it up and reads every page on your machine. Nothing is sent anywhere.
File
A searchable PDF lands in your folders, named and findable. The source file is never destroyed.
Find
A global hotkey opens search across everything the app has read. The answer is a keystroke away.
Local first, by design
In single-user mode, nothing ever leaves the machine. There is no account to create, no server to run, and no telemetry watching how you work. The words inside your scans are read on your own hardware, and the searchable files live in your own folders, where any other tool can also find them. That portability is deliberate. Your documents are not moved into a vault, and the app’s index is a rebuildable cache, never the place your files live.
For an office that handles donor agreements and estate files, this is the posture that matters: the sensitive pages you scan are processed on the machine in front of you. There is a page written for the people who will ask the sharpest questions about that: PaperlessZen for IT.
Free, forever
The single-user edition is called Desktop Lite, and it is free. Not free during beta, not free until a pricing page quietly changes: free, forever. There is no trial clock, no feature that gets clawed back later, and no account standing between you and using it.
We can be this plain about it because the desktop app is not a product we sell separately. It is how paper gets into PaperlessZen, and charging for capture would be taxing the thing that makes everything else useful. The same rule holds when a team connects a workspace: the desktop app is included, and the platform is priced per institution and archive, never per seat, so every scanner in the building can feed the archive without a meter running.
When the team is ready, it becomes the front door
On its own, PaperlessZen Desktop is a capture tool for one person. Connected to a PaperlessZen workspace, it becomes the intake edge of the whole system: every copier and scanner in the building feeds documents into the same intake that classifies, files, and tracks them.
And because the app has been reading your pages locally all along, the archive you built before connecting is not stranded. The design goal is that connecting a workspace carries your existing library up through the same queue, files untouched, duplicates recognized. The migration project that kills most document systems is the thing the desktop app will have quietly already done.
Where this is today, honestly
PaperlessZen Desktop is in development. The tray shell is built, and capture, local reading, and search are being built in the open order we have described here. We are not going to imply a download that does not exist: there is no public build yet, and anything on this page described as designed or planned is exactly that.
If the intake bottleneck is the one you live with, join the early access list and tell us about your scanners. Early builds go to the teams whose paper fits what the app does first, and advancement teams are at the front of that line. If your interest is the wider system, the archive, obligations, and governance behind the capture, book a demo of the PaperlessZen platform and bring a box of your own documents.
Frequently asked questions
Can I download PaperlessZen Desktop today?
Not yet. The app is in development, and we would rather say that plainly than ship something half-built. Join the early access list and we will reach out as builds open up, starting with advancement teams.
Does it need the cloud or an account?
No. The single-user edition, Desktop Lite, runs entirely on its own: no account, no server, no cloud. Your files become searchable PDFs in your own folders, and everything is read on your machine. Connecting to a PaperlessZen workspace is a choice you make later, if you make it at all.
How much does it cost?
Desktop Lite is free, forever. That is the price, not a promotion: no trial clock, no features clawed back later, no account required to keep using it. When a team connects the app to a PaperlessZen workspace, the desktop app is included with the platform, which is priced per institution and archive, never per seat.
Will it work on a locked-down office machine?
That is a design requirement, not an afterthought. The app is built to install per user, without administrator rights, because we know the standard-issue advancement office machine is admin-locked.
What happens to our files?
They stay yours, in your own folders, exactly where they were. The app never moves documents into a vault, never alters a source file, and its search index is a rebuildable cache over your folders, not a place your documents live. If a page cannot be processed, the file is left untouched and flagged for a look, never silently dropped.
How does it handle handwriting?
Honestly: local text recognition is weakest on handwriting, and donor correspondence is often handwritten. Pages the app is not confident about are flagged for review rather than quietly indexed wrong. Heavier recognition models run on the server side when a workspace is connected.