Paperless-ngx
Compare VPS plans to self-host Paperless-ngx. providers advertising 2GB+ RAM from $4/mo. Paperless-ngx server hosting comparison.
Find the best and cheapest VPS plans to self-host Paperless-ngx.
Minimum Requirements
These VPS plans meet the minimum requirements to run Paperless-ngx. Suitable for testing or light usage.
Recommended Requirements
For optimal performance, we recommend these VPS plans that exceed the minimum requirements.
Source: self-hosted-tools.json
Paperless-ngx VPS Sizing: Storage, Sync, and Scale
Paperless-ngx turns a VPS into a document archive that ingests files, runs OCR, queues background work, and stores a growing searchable corpus. Hosting choice affects how fast documents clear the ingestion queue and whether archive growth becomes a storage and backup problem before users notice.
Resource Profile Classification
The primary resource profile is Mixed because Paperless-ngx hits both sides of the bottleneck table early. OCR is CPU-intensive, while the archive itself is I/O-bound and storage-hungry as scans, thumbnails, indexes, and metadata accumulate. self-hosted-tools.json doubles Paperless-ngx from 2 CPU cores and 2 GB RAM at minimum to 4 CPU cores and 4 GB RAM in production, which matches a workload where OCR throughput and archive growth are both operational constraints.
Paperless-ngx is I/O-bound and CPU-hungry at the same time: OCR, Redis queue processing, PostgreSQL writes, and archive growth all matter once scanning becomes routine.
Storage and Network Interpretation
Treat Paperless-ngx as an archive, not just a web app. The Redis queue, PostgreSQL, and document store all need responsive SSD or NVMe storage, while the archive keeps growing with every imported PDF, image, or email attachment. OCR also means CPU pressure lasts beyond upload time. Storage sizing has to separate the system disk from long-term document retention and backups.
Minimum vs Production vs Scale
| Stage | Source | CPU | RAM | Storage | Interpretation |
|---|---|---|---|---|---|
| Minimum | requirements.minimum |
2 Cores | 2 GB | 10 GB | The 2-core, 2 GB, and 10 GB floor is enough for installation, testing, or a very small archive. OCR throughput and retention headroom are limited immediately. |
| Production | requirements.recommended |
4 Cores | 4 GB | 50 GB | The 4-core, 4 GB, and 50 GB production tier is the baseline for a live Paperless-ngx deployment where OCR, indexing, and archive growth all happen together. |
| Scale | editorial interpretation |
Use stronger sustained CPU for OCR workers and document ingestion rather than assuming bursty shared vCPUs will clear the queue. | Add RAM for PostgreSQL, Redis queue workers, and large-document handling once imports become continuous. | Plan separate fast application storage and a larger retention strategy because the document archive keeps growing long after the system is installed. | At scale, Paperless-ngx needs both better OCR throughput and better archive discipline. Keep Redis queue work flowing, protect the database on fast storage, and move from root-disk thinking to a retention plan built around backups and ongoing storage growth. |
Anti-Patterns
- Do not call Paperless-ngx a simple 4 GB web app; OCR and archive growth define the buying logic.
- Do not equate a large disk with a healthy Paperless-ngx setup when the OCR queue still needs CPU and fast storage.
- Do not ignore Redis queue behavior, because document ingestion becomes slower and less predictable when background work piles up.
- Do not size only for today's archive; Paperless-ngx is storage-hungry and the retention problem compounds over time.
Who It Fits
For: Good fit for users who want a private searchable document archive and can budget for production CPU headroom, fast SSD-backed storage, backups, and a plan for ongoing storage growth.
Not for: Avoid an entry-level VPS if you expect frequent OCR imports, large backlogs of scanned documents, long-term archive retention, or need ingestion to stay fast during continuous background processing.
FAQ
Why is Paperless-ngx heavier than BookStack or Joplin Server?
Because Paperless-ngx runs OCR, background processing, indexing, and archive retention. It is not just serving pages or syncing notes.
What breaks first on an undersized Paperless-ngx VPS?
Usually OCR throughput or storage pressure. Documents pile up in the Redis queue, indexing slows down, and archive growth starts competing with the system disk.
What should I check before buying?
Check sustained CPU for OCR, SSD or NVMe behavior for PostgreSQL and the document store, backup strategy, how fast storage growth will compound, and renewal pricing before trusting a low first-term plan.
Quality Checks
- Engineering-Check: Yes, the page names the first bottleneck and its failure mode.
- Trade-off-Check: Yes, it states who should avoid an entry-level VPS.
- Renewal-Price-Check: Yes, buyers are warned that low first-term prices can distort VPS selection.
- Keyword-Anchor-Check: Yes, internal anchors on the page use VPS and self-hosting terms instead of generic labels.
- Data-Link-Check: Yes, Minimum and Production values map to
self-hosted-tools.json. - Uniqueness-Check: Yes, the analysis is tied to Paperless-ngx bottlenecks rather than a name-swap template.
What is Paperless-ngx?
Paperless-ngx is a community-supported document management system that converts physical documents into a searchable digital archive. It performs OCR (optical character recognition) on scanned documents, supports over 100 languages, and uses machine learning for automatic tagging and correspondent detection. Features include full-text search, metadata editing, document classification, and integration with email for automatic importing. Suitable for going paperless while maintaining a private, organized archive.
Why Server Specs Matter
Paperless-ngx combines several resource-intensive operations: OCR processing, machine learning classification, PDF generation, and full-text indexing. The stack includes Python/Django, Redis, PostgreSQL, and optional Tika for advanced file parsing. CPU is heavily used during document consumption for OCR and ML operations. RAM is needed for processing large documents and running the web interface. The consumption process can take significant time per document.
Problems with Undersized Servers
With insufficient resources, document consumption takes excessively long or fails. OCR quality may suffer if processing is rushed or memory-constrained. The consumption queue backs up during bulk imports. Search becomes slow with large archives. The web interface lags when viewing documents. ML training fails to complete. Document previews timeout.
Our Recommendation
Minimum 2GB RAM and 2 CPU cores for light use. Regular use with ML features enabled needs 4GB RAM and 4 cores. Heavy scanning (50+ pages daily) benefits from 8GB RAM. Plan 10-50GB storage for documents and OCR data. SSD improves consumption speed significantly. Consider batch processing documents overnight if running on limited hardware. Disable ML features if resources are constrained but you still need OCR functionality.
Minimum Requirements - VPS Plans
These VPS plans meet the minimum requirements to run Paperless-ngx. Suitable for testing or light usage.
| Provider | Plan | CPU | RAM | Storage | Features | Price/mo | Actions |
|---|
Recommended Requirements - VPS Plans
For optimal performance, we recommend these VPS plans that exceed the minimum requirements.
| Provider | Plan | CPU | RAM | Storage | Features | Price/mo | Actions |
|---|
Some links on this page are affiliate links. If you make a purchase through these links, we may earn a small commission at no extra cost to you. This helps us keep the site running and provide free comparison tools.