Paperless-ngx review: open-source document management that replaces filing cabinets
8.5Paperless-ngx delivers robust OCR and search for self-hosted document archives, but setup complexity and maintenance demand technical comfort with Docker.
Free and open source; managed hosting from approximately $16/month
- ✓Completely free with no per-user licensing or recurring subscription fees
- ✓Data remains on your own infrastructure with no third-party access or cloud dependencies
- ✓Tesseract OCR processes scanned documents into fully searchable text across many languages
- ✓Machine learning auto tagging improves over time as the system learns from your filing habits
- ✓Active community with over 42,000 GitHub stars, frequent updates, and responsive maintainer team
- ✓Full REST API enables custom integrations with scanners, automation platforms, and workflows
- ✗Docker Compose setup requires technical knowledge; installation scripts ask configuration questions that assume infrastructure familiarity
- ✗Ongoing maintenance burden includes image pulls, database migrations, and manual troubleshooting of consumer folder permissions
- ✗OCR performance on low-end hardware like Raspberry Pi can be painfully slow without tuning worker and thread settings
- ✗No official mobile app; web UI works on phones but third-party community apps are needed for convenient document capture
- ✗Initial auto tagging accuracy is poor until the system builds sufficient training data from manually corrected documents
- ✗Security documentation warns system should never run on untrusted hosts as documents are stored unencrypted on disk
What Paperless-ngx does and where it came from
Paperless-ngx is a community supported open source document management system designed to transform physical documents into a searchable digital archive. The software performs optical character recognition on scanned files, extracts metadata, and organizes everything through tags, correspondents, document types, and storage paths. Data is stored locally on your own server and is never transmitted externally.
The project is the official successor to the original Paperless and Paperless-ng efforts. In 2017 Daniel Quinn released the first version motivated by a desire to stop searching through dusty folders for documents. After the original maintainer stepped away, the community forked the project; Paperless-ngx emerged in 2022 and has since become the actively maintained continuation, designed to distribute responsibility among a team rather than relying on a single developer.
Under the hood, Paperless-ngx is a Django web application that uses Tesseract for OCR with support for over one hundred languages. Documents are saved in the PDF/A archival format alongside unaltered originals. Machine learning algorithms automatically suggest tags, correspondents, and document types based on how you have classified existing documents. The system supports PDF, images, plain text, and optionally Office formats when the Tika integration is enabled.
Installation demands and hardware reality
The recommended deployment method is Docker Compose. An install script automates the process by asking configuration questions about URL, port, time zone, storage folders, OCR languages, database choice, and admin credentials, then downloads compose files, pulls container images, and starts the stack. Manual setup involves downloading the compose YAML for your chosen database backend, editing environment variables, and running the containers. The official documentation states that Docker and Docker Compose must be installed, and macOS users need GNU sed and wget.
Bare metal installation is supported but significantly more complex, requiring manual installation of Python dependencies, Redis or Valkey, PostgreSQL or MariaDB, Tesseract with language packs, ImageMagick, Ghostscript, and numerous other system libraries. The documentation confirms Paperless runs on Linux only; Windows is not supported for bare metal installs.
Hardware requirements are workload dependent. Community reports indicate a Raspberry Pi 3B will run the system but OCR becomes painfully slow; the FAQ recommends 4 GB RAM as a practical minimum. Users report comfortable performance on repurposed thin clients with dual core processors and 4 GB RAM for typical household document volumes. For heavier workloads or faster processing, a quad core system with SSD storage is recommended. The software runs on ARM and x86 architectures.
Daily use and the interface
The web UI is a single page application built with modern web technologies designed to be fast and responsive. The dashboard displays saved views, and documents can be uploaded via button or drag and drop anywhere in the application. The interface provides three different list styles for browsing, extensive filtering by tags, correspondents, types, and dates, bulk edit operations, and side by side document editing.
Documents are consumed either by dropping files into a monitored folder, uploading through the web UI, or configuring email accounts to automatically ingest attachments. The consumption process runs OCR, applies matching rules, and files the document. The system watches the consumption directory using inotify on supported filesystems; network shares without inotify support require enabling polling mode instead. A built in tour feature highlights key interface elements for new users.
Mobile access works through the responsive web UI, but the experience is not optimized for phone based document capture. The community maintains third party mobile applications for iOS and Android that provide better scanning workflows. Search is powered by full text indexing with autocomplete, relevance ranking, and result highlighting. Saved views allow customization of frequently used filters and can be pinned to the dashboard.
Exit strategy and data portability
Paperless-ngx stores documents in a straightforward filesystem structure managed by Docker volumes or user specified bind mounts. Original files are preserved with checksums verified by a scheduled sanity checker to detect any corruption. The system never modifies your original documents. Filenames default to internal document IDs but can be customized through configurable filename format templates.
A built in document exporter creates a portable archive containing original files alongside JSON metadata for tags, correspondents, dates, and custom fields. This export can be used for migration to other systems or as part of a backup strategy. The REST API provides full programmatic access to all document metadata and file content, enabling custom export scripts or integrations with other tools.
Because everything runs in Docker containers or on your own Linux system, there is no vendor lock in. Data lives in standard PostgreSQL, MariaDB, or SQLite databases that can be backed up independently. Moving to a different server or infrastructure is a matter of copying volumes and restarting containers. The GPL license ensures the source code remains open regardless of future project direction.
Community health and update track record
The GitHub repository has accumulated over 42,000 stars with more than 370 contributors. Commit activity is steady with frequent pull requests merged by a team of maintainers. Releases follow a regular cadence; version 2.20.15 shipped in late April 2026 addressing a security issue, and a version 3.0 beta release candidate appeared in May. The project actively addresses reported bugs and security issues with prompt patch releases.
Community support is available through GitHub Discussions where users share configuration help, troubleshooting steps, and feature requests. A Matrix chat room provides real time assistance. The documentation is comprehensive and includes setup guides for Docker, bare metal, NAS platforms like Synology and Unraid, and migration from older Paperless versions. Translation efforts coordinate through Crowdin with the interface available in many languages.
The project maintains a transparent security posture. The README explicitly states that Paperless should never be run on untrusted hosts because document storage is unencrypted, and recommends local server deployment with backups. Security issues are tracked publicly, and the maintainer team responds to community reported vulnerabilities with fixes and coordinated disclosure.
- +Home users digitizing years of receipts, tax records, and household documents
- +Small businesses needing affordable, self-hosted document archiving with full data control
- +Homelab enthusiasts comfortable running Docker stacks and performing periodic maintenance
- +Privacy-conscious users unwilling to send sensitive documents to cloud providers
- −Teams wanting plug-and-play software without Docker, reverse proxies, or server administration
- −Organizations needing enterprise SLAs, vendor support contracts, or compliance certifications
- −Users expecting instant mobile capture without configuring third-party companion apps
- −Anyone uncomfortable troubleshooting database locks, container networking, or OCR language packs
Paperless-ngx is a capable self-hosted document management system that excels at transforming paper into searchable, tagged digital archives. The feature set is thorough: Tesseract OCR with support for over one hundred languages, machine learning driven auto tagging, full text search, and a modern web interface. The catch is the operational footprint. Installation requires Docker Compose proficiency, ongoing maintenance includes image updates and database migrations, and the official documentation explicitly warns that the system should only run on trusted local infrastructure with backups in place. For those willing to learn the stack, the payoff is significant: zero licensing costs, complete data control, and a mature community continually improving the project.
| License | GNU GPL v3.0, open source |
| OCR engine | Tesseract, 100+ languages |
| Deployment method | Docker Compose (recommended), bare metal supported |
| Database support | PostgreSQL (recommended), MariaDB, SQLite |
| File format support | PDF, TIFF, JPEG, PNG, plain text; Office docs via optional Tika |
| Minimum hardware | Raspberry Pi 3B+ supported; 4 GB RAM recommended for typical use |
| API | Full REST API for automation and integrations |
| Platform | Linux (bare metal), Docker on Linux/macOS/Windows, various NAS systems |