Paperless-ngx is worth setting up on a NAS for most home users and small offices, but only if your NAS has enough CPU grunt for OCR processing and you are comfortable running Docker containers. The application itself is excellent: it scans, OCRs, tags, and makes your documents full-text searchable. The complexity is real but front-loaded. Once it is running, day-to-day use is straightforward. The question is whether your current hardware and patience for initial configuration make the investment worthwhile.
In short: Paperless-ngx on NAS is worth it if you have a mid-range or better NAS (quad-core CPU, 4GB+ RAM), a scanner or multifunction printer with network scan capability, and are comfortable with Docker. OCR performance varies substantially with document resolution, page count, OCR settings and other NAS workloads; benchmark representative documents on your hardware before relying on it for a regular scanning workflow. If Docker is unfamiliar territory and you want zero ongoing maintenance, a commercial service like Google Drive with document scanning is a faster path to the same outcome.
What Is Paperless-ngx?
Paperless-ngx is an open-source document management system descended from the original Paperless project. You feed it scanned documents (PDFs, images, emails) and it automatically runs optical character recognition (OCR) to make them full-text searchable, assigns tags and correspondents based on rules you define, and stores everything in a clean web interface accessible from any browser on your network.
Key capabilities include:
- Automatic OCR using Tesseract (supports 100+ languages including German and Japanese, important for multilingual households)
- Intelligent auto-tagging using machine learning trained on your own document history
- Full-text search across every document in your archive
- Bulk import from a watched folder, email inbox, or API
- User accounts with permission controls (useful for households where multiple people need access but not to each other's documents)
- Mobile-friendly web interface
- REST API for integrations with other self-hosted tools
Paperless-ngx stores unaltered originals on disk and may create separate PDF/A archive versions; filenames and folder layouts are managed by Paperless-ngx and are configurable. If you stop using Paperless-ngx tomorrow, your scanned PDFs are still accessible directly.
Hardware Requirements: What Your NAS Actually Needs
The limiting factor with Paperless-ngx on NAS is OCR processing, not storage. Tesseract is CPU-bound, and OCR on a multi-page PDF document can peg a weak processor for several seconds per page. OCR processing time varies with the CPU, document length and resolution, OCR options, and concurrent workloads; weaker processors can take substantially longer than newer multicore systems.
Paperless-ngx does not publish a universal CPU or RAM minimum for acceptable OCR performance; required resources depend on document volume, OCR settings, database choice and other NAS workloads. The Redis and PostgreSQL components that Paperless-ngx uses (when deployed via Docker Compose with the recommended stack) are not demanding, but they do add baseline memory overhead on top of your NAS operating system.
| Minimum CPU | No universal NAS hardware minimum is published; needs vary with document volume, OCR settings, parallel processing and other services running on the NAS |
|---|---|
| Minimum RAM | No universal NAS hardware minimum is published; needs vary with document volume, OCR settings, parallel processing and other services running on the NAS |
| Storage for application | 2GB for Docker images + your document archive size |
| Docker support | Recommended for the Docker Compose route; an advanced bare-metal installation is also supported |
| Network scanner | Optional; documents can also be uploaded through the web interface, API, consumption directory or a currently supported mobile scanning app |
| Container requirements | Typical recommended Compose services: paperless-ngx, a Redis-compatible broker (Valkey by default), and PostgreSQL |
Which NAS Models Handle Paperless-ngx Comfortably?
Based on the hardware requirements above, here is how current Australian-market NAS models stack up for Paperless-ngx:
NAS Models for Paperless-ngx: AU Availability
| Synology DS423 | Synology DS425+ | QNAP TS-433 | QNAP TS-464 | Synology DS925+ | |
|---|---|---|---|---|---|
| CPU | Realtek RTD1619B (4-core) | Intel Celeron J4125 (4-core) | Cortex-A55 (4-core) | Intel Celeron N5095 (4-core) | AMD Ryzen V1500B (4-core, 8-thread) |
| Base RAM | 2GB | 2GB | 4GB | 8GB | 4GB |
| AU Price (approx.) | $648.88 (market avg) | $857 (market avg) | From~$697 | From $1,039 (checked 29 August 2026) | $999 (market avg) |
| OCR Speed | Slow (ARM CPU) | Adequate | Slow (ARM CPU) | Good | Good |
| Verdict | Not recommended | Workable, upgrade RAM | Not recommended | Recommended | Recommended |
The ARM-based NAS models (DS423, TS-433, most entry Asustor models) will process documents, but the experience is frustrating for any regular scanning workflow. If you are scanning a few documents per week, it may be tolerable. If you are digitising a filing cabinet of old records, an ARM-based NAS will test your patience considerably.
Among Synology's current four-bay models, the DS425+ is the lowest-priced model here with an Intel Celeron J4125; the two-bay DS225+ uses the same processor and memory configuration. The current QNAP TS-464-8G uses an Intel Celeron N5095 and includes 8GB RAM. Both are readily stocked at major Australian retailers including Mwave, PLE Computers, and Scorptec.
Paperless-ngx can share a NAS with other containers, but its effect on normal operations depends on available CPU, memory, OCR concurrency and the existing workloads; monitor resource use during document processing.
The Setup Process: What It Actually Involves
Setup time varies substantially with Docker experience, NAS permissions, network-share configuration and scanner integration. It is not plug-and-play, but it is also not particularly difficult once you have done it.
The main steps are:
- Enable Docker on your NAS. Synology uses Container Manager (formerly Docker), QNAP uses Container Station. Both provide a GUI, though the Compose deployment is easiest done via SSH or the terminal.
- Create a Docker Compose file. The Paperless-ngx documentation provides a ready-to-use compose file. You copy it, adjust three or four environment variables (admin username, password, secret key, time zone), and place it in a folder on your NAS.
- Create shared folders for the consume directory (where scanned documents land), the media folder (where processed documents are stored), and the data folder (application database and configuration).
- Start the stack with
docker compose up -dvia SSH or the NAS terminal. - Configure your scanner to send scans to the consume folder via SMB share or FTP. Most network-capable scanners and multifunction printers support SMB scanning.
The step that trips most people up is the scanner configuration. If your multifunction printer or scanner does not support SMB (network folder) scanning, you have two alternatives: use a mobile scanning app that can upload to an SMB share, or configure the email consumption feature to pull documents from a dedicated email inbox. Both work well in practice.
Synology users: The Synology Container Manager GUI can deploy Paperless-ngx without SSH if you are comfortable editing YAML in the browser. Use the Project feature, paste in the official Docker Compose content, and set environment variables through the GUI. QNAP users can do the same via Container Station's Compose tab.
Common Setup Mistakes
Three mistakes account for most of the failed or frustrated Paperless-ngx deployments:
1. Using SQLite instead of PostgreSQL for any serious workload. The default Docker Compose file uses PostgreSQL because it handles concurrent access and larger archives reliably. Some guides suggest simplifying to SQLite to reduce the number of containers. SQLite is the default, while PostgreSQL is recommended for multi-user or higher-throughput deployments; performance depends on workload rather than a documented document-count threshold. Use PostgreSQL from the start.
2. Putting the consume folder on a different network share than the media folder. Paperless-ngx moves files from consume to media as part of processing. The consume and media paths may be separate, but each mount must be writable by the configured container user. Network filesystems without inotify support require consumer polling.
3. Not planning for storage growth. Scan file size and annual storage growth vary with page count, colour mode, resolution and compression. Measure a representative batch of your own scans before projecting archive growth. This is not large by NAS standards, but it is worth pre-allocating space and understanding how your existing RAID configuration handles incremental growth. See the NAS storage capacity planning guide for sizing guidance.
OCR Quality and Language Support
Paperless-ngx uses Tesseract for OCR, which is reliable for clean, high-contrast scans at 300 DPI or higher. For handwritten documents, the accuracy is poor and there is no configuration that fixes this reliably. Tesseract is designed for printed text and generally performs poorly on handwriting; reliable handwriting recognition requires a handwriting-focused system rather than ordinary Tesseract configuration changes.
For typed documents, receipts, invoices, and printed correspondence, Tesseract performs very well. The default configuration handles English without additional packages. If your household or business uses multiple languages, you add language data packages to the Docker image or configure the PAPERLESS_OCR_LANGUAGE environment variable to include the relevant language codes.
Australian users processing documents that contain mixed English and another language (common for businesses serving multicultural communities) should set the language variable to include both codes. Tesseract is significantly more accurate when it knows the target languages than when it is guessing.
Paperless-ngx vs Cloud Document Storage: The Real Trade-offs
The honest case against Paperless-ngx on NAS is that a combination of a flatbed scanner and Google Drive or OneDrive achieves 80% of the result with 5% of the setup effort. Google Drive's built-in OCR and search is excellent for most household document management needs. Microsoft 365 Personal includes 1TB of OneDrive storage for AU$159/year at Microsoft's current Australian list price.
The case for Paperless-ngx is the remaining 20%: full local control, no subscription fees, no third-party access to your documents, better automated tagging and classification, and the ability to process documents offline or on a slow NBN connection where uploading to cloud storage would take minutes per document.
For Australian households on NBN 25 or lower plans (common in regional areas), the upload speed constraint is genuinely relevant. Uploading a 5MB scanned PDF to Google Drive on a 5Mbps upload connection takes about 8 seconds per document. If you scan 10 documents at once, that is 80 seconds of upload wait before they appear on other devices. Local processing does not depend on your NBN upload tier, but the time until a document is searchable depends on NAS performance, document size and OCR settings.
NBN 50 and NBN 100 plans with typical FTTN upload speeds of 15-20Mbps make this less of an issue, but for anyone on HFC or FTTN with variable upload speeds, local processing has a real practical advantage.
Pros
- Full local control: documents never leave your network
- No ongoing subscription cost after initial NAS investment
- Automated tagging and correspondent matching improves over time
- Full-text search across your entire document archive
- Works offline and on slow NBN upload connections
- REST API for integration with other self-hosted tools
- Unaltered originals retained on disk, with optional PDF/A archive versions
Cons
- Requires Docker and basic command-line familiarity to set up
- Slow or unusable on entry-level ARM-based NAS hardware
- No reliable handwriting recognition
- You are responsible for backups (your NAS IS NOT a backup)
- Updates and maintenance are your responsibility
- Initial document import of existing archive is time-consuming
- Setup complexity is real, especially for scanner configuration
Backing Up Your Paperless-ngx Archive
This point deserves its own section because it is where many self-hosted document management setups fail. Your NAS with Paperless-ngx is not a backup. A RAID array protects against drive failure, but it does not protect against ransomware, accidental deletion, a NAS unit failure, or a house fire. Your document archive needs a separate backup strategy.
The minimum viable backup for a Paperless-ngx installation is an automated offsite copy. The options for Australian users:
- Synology Hyper Backup to Backblaze B2 or Wasabi: Backblaze's affiliate program ended in March 2026, so NTKIT no longer links to it commercially, but the service itself remains a cost-effective option. Wasabi advertises no egress or API-request fees and provides S3-compatible storage starting at USD $7.99/month per TB.
- QNAP HBS 3 (Hybrid Backup Sync) to any S3-compatible service: Same capability as Hyper Backup but for QNAP NAS models.
- A second NAS at another physical location: The most robust option for serious document archives. Synology and QNAP both support NAS-to-NAS sync.
- pCloud with its Australian-friendly pricing: pCloud offers lifetime storage plans and integrates with NAS backup tools. Consider it as an alternative to subscription-based cloud storage.
Warranty and consumer-guarantee resolution times vary with the retailer, fault assessment, remedy and replacement stock, so maintain a separate accessible backup while a claim is being resolved. If your document archive exists only on that NAS, you are without it for that entire period. A cloud backup copy keeps your documents accessible while the hardware issue is resolved.
Australian Buyers: What You Need to Know
Hardware availability: The NAS models best suited to Paperless-ngx are all readily stocked at Australian retailers. Both models are listed by multiple Australian retailers, but live stock varies by retailer and location. No long lead times are expected for these mid-range consumer models, though stock can fluctuate given the ongoing global NAS supply constraints in 2026.
ACL and warranty context: Under Australian Consumer Law, the retailer is responsible for resolving problems with products it sells and cannot simply direct you to the manufacturer. For some consumer guarantees, consumers may instead choose to seek a remedy from the manufacturer, although the remedies available can differ. Neither brand has a service centre in Australia. Warranty resolution time and process vary by retailer, fault assessment, available remedy and replacement stock. For a NAS holding your document archive, plan accordingly. Australian Consumer Law protections apply when purchasing from any Australian-registered retailer, including online specialists like Mwave, PLE, and Scorptec.
Support: Neither Synology nor QNAP have local phone support in Australia. Paperless-ngx is open-source community-supported software, meaning official support is limited to GitHub issues and community forums. This combination means that if you encounter a problem, you are largely on your own. The Paperless-ngx community is active and responsive on GitHub and Reddit, but there is no paid support tier. For small businesses where document access is operationally important, factor this into your risk assessment.
Scanner compatibility: Network-folder scanning is model-specific across Brother, Fujitsu, Canon and Epson ranges; verify explicit SMB scan-to-folder support for the exact scanner or multifunction printer. Verify that your existing multifunction printer or scanner has this capability before committing to the Paperless-ngx setup. Budget models sold through JB Hi-Fi and Harvey Norman sometimes omit network scan features to hit a lower price point.
Is It Worth It? The Honest Verdict
Paperless-ngx on NAS suits users who already have a capable NAS running Docker, a network-capable scanner, and enough patience for a few hours of initial configuration. The ongoing experience after setup is genuinely good: documents are searchable, automatically tagged, and accessible from any browser on your network.
The setup complexity is a genuine barrier, not marketing spin. The first-time Docker user who has never edited a YAML file or connected to a NAS via SSH will spend more time on this than they expect. That does not mean it is beyond them, but it does mean setting aside a weekend afternoon rather than an hour.
The clearest cases where Paperless-ngx makes sense:
- You already run Docker on your NAS for other applications (Jellyfin, Home Assistant, etc.) and adding another container is routine
- You handle invoices, tax records, or compliance documents and want them searchable, retained locally, and accessible without a cloud subscription
- Your NBN upload speed is slow enough that cloud-based document storage is a friction point
- You have privacy concerns about storing financial or personal documents on a third-party cloud service
The clearest cases where it probably does not make sense:
- You have an entry-level NAS with an ARM CPU (DS223J, DS423, TS-233) and do not plan to upgrade
- You scan documents infrequently and Google Drive or OneDrive search meets your needs
- You have no existing backup strategy for your NAS and are not prepared to build one
For the right setup, Paperless-ngx is one of the most practically useful self-hosted applications available. The complexity is real but not prohibitive, and the payoff is a searchable, organised, locally-controlled document archive that improves with use.
Related reading: our NAS buyer's guide, our Synology vs QNAP comparison, and our NAS explainer.
Use our free Plex Media Planner to check if your NAS can handle your library.
See also: our complete Synology NAS Australia guide.
See also: our complete QNAP NAS Australia guide.
See also: our full Plex and Media guide.
Can Paperless-ngx run on a Synology DS223J or other entry-level NAS?
Technically yes, but the OCR performance is poor enough that most users abandon it. The DS223J uses a Realtek RTD1619B ARM processor, which is significantly slower than an Intel Celeron at CPU-bound tasks like OCR. Processing a 10-page scanned PDF may take several minutes. If you scan occasionally and are patient, it can work. For regular scanning workflows, a mid-range NAS with a quad-core Intel CPU is the practical minimum.
Does Paperless-ngx require a dedicated NAS, or can it run alongside other Docker applications?
It runs alongside other Docker containers without issues on any NAS with adequate RAM. Memory use depends on the database, broker, OCR concurrency and other services. Paperless-ngx can share a NAS with other containers, but monitor actual CPU and memory use under representative document-processing loads. If you are already running Jellyfin or a similar application, Paperless-ngx is a reasonable addition. Watch your RAM usage during the first week to confirm nothing is competing for memory.
What happens to my documents if I stop using Paperless-ngx?
Nothing bad. Paperless-ngx stores original documents on disk in their original formats and may also create PDF/A archive copies. By default it uses numeric identifiers for filenames, although title- and date-based folder and filename templates can be configured. If you stop using the application, your documents remain accessible as ordinary PDF files in the media folder. You do not lose your archive. This is one of Paperless-ngx's most important design decisions: no proprietary format, no lock-in.
Does Paperless-ngx work with a phone camera instead of a scanner?
Yes, with some limitations. Mobile scanning tools such as Adobe Scan, OneDrive's built-in scanner, and iOS's built-in document scanner can produce PDFs from phone camera captures. The OCR quality depends on the image quality and lighting. For occasional use and informal documents, phone scanning works fine. For receipts, invoices, and documents requiring high accuracy, a dedicated flatbed scanner at 300 DPI produces better results. The Paperless-ngx consume folder accepts files from any source, so you can mix scanner input and phone app uploads freely.
Can multiple people in a household or small office use Paperless-ngx?
Yes. Paperless-ngx has a proper multi-user permission system. You can create accounts for each user, assign ownership of documents, and control which users can view or edit specific documents. For a household where you want financial documents separate from general household paperwork, the permissions model handles this well. For a small office with 2-5 staff, it is adequate for most document management needs.
Is remote access to Paperless-ngx possible from outside the home network?
Yes, but it requires additional configuration and carries security considerations. The recommended approach is to put Paperless-ngx behind a VPN, so access from outside your network goes through an encrypted tunnel rather than exposing the application directly to the internet. For vendor-hosted VPN access, Synology provides the separate VPN Server package and QNAP provides QVPN; QuickConnect and myQNAPcloud Link are distinct remote-access services. Alternatively, Tailscale (a zero-config VPN service) is a popular choice in the self-hosted community. Directly exposing Paperless-ngx on a public port without authentication hardening is not recommended. Note that Australian NBN connections on some ISPs and CGNAT configurations may complicate direct inbound access; a VPN service sidesteps this entirely.
If you are assessing whether your current NAS has enough capacity for Paperless-ngx alongside your existing workloads, the NAS Capacity Growth Planner can help you model storage growth over time.