How to self-host Paperless-ngx for your documents

Your paperwork is probably split between email attachments, phone photos, downloads, and a drawer you keep meaning to sort.

Short version: To self-host Paperless-ngx, you run the Paperless-ngx app on your own server, give it storage for your documents, protect it with HTTPS, and make sure it is backed up. Paperless-ngx then reads your PDFs and scans with OCR, tags them, and turns a messy pile of files into a searchable document archive you control.

What is Paperless-ngx?

Paperless-ngx is a self-hosted document management app. Think of it as a private filing cabinet with a very patient assistant inside.

You give it invoices, letters, receipts, contracts, tax papers, and scanned PDFs. It stores the original files, extracts the text, and lets you search for things later — not just by filename, but by words inside the document.

The useful word here is OCR, short for optical character recognition. OCR is the part that looks at an image or scan and says, “this smudge is probably the word Total.” It is not magic, but it turns many dead scans into searchable records.

Paperless-ngx usually has a few moving parts: the web app you open in your browser, a database that remembers metadata, a background worker that processes files, and storage where the actual documents live. You do not need to love those details, but you do need to respect them. If one part goes missing, the filing cabinet stops feeling simple.

What do you need before you self-host Paperless-ngx?

You need a server with enough room to grow. Documents are not usually heavy like videos, but scans add up quietly. A few gigabytes can become hundreds if you scan every bill, statement, and letter for years.

You also need a domain name if you want a clean address like docs.example.com, plus HTTPS so your browser uses an encrypted connection. If domain and HTTPS are new to you, start with the basics: pointing a domain at your server is covered in /blog/point-a-domain-at-your-server, and HTTPS is explained in /blog/free-https-on-your-server.

Most Paperless-ngx setups also use containers. A container is like a lunchbox for an app: the app and its dependencies are packed together so they do not spill into everything else on the server. If that idea is new, /blog/docker-on-server-for-beginners gives the plain-English version.

Finally, plan backups before you upload important papers. With Paperless-ngx, the database and document storage belong together. Backing up only one is like keeping the labels from a filing cabinet but throwing away the folders. For the bigger picture, read /blog/back-up-your-server.

How do documents get into Paperless-ngx?

Paperless-ngx gives you a few paths into the same filing cabinet.

The simplest path is manual upload: you open the web interface and drop in a PDF or image. This is good for occasional documents.

The more useful path is a consume folder. That is a watched folder where Paperless-ngx waits for new files. When a file appears there, it picks it up, reads it, stores it, and sorts it. It is like leaving mail in an inbox tray and letting the office assistant file it.

Some people connect scanners, phone scanning apps, or email forwarding to that intake flow. The important habit is consistency. If every document enters through the same front door, your archive stays tidy. If half your files live in downloads, a quarter in email, and the rest in Paperless-ngx, you have only moved the mess.

Tags, correspondents, and document types help later. A correspondent might be “Electric Company.” A document type might be “Invoice.” Tags might be “tax,” “home,” or “warranty.” You do not need a perfect system on day one. Start with broad labels you will actually remember.

What can go wrong when you self-host Paperless-ngx?

The first common problem is storage filling up. Paperless-ngx may still open, but uploads fail or processing gets stuck. This feels confusing because the app looks alive while the filing clerk in the back room has no shelf space left.

The second problem is a broken HTTPS certificate. The literal browser warning might say “Your connection is not private.” For a document archive, that is not a small annoyance. You need to know whether the issue is an expired certificate, a wrong domain, or traffic going to the wrong place.

The third problem is losing the map of the setup. Six months later, you may not remember where the documents are stored, what depends on the database, or which address is supposed to open the app. That is how small maintenance becomes risky.

The fourth problem is weak backups. Paperless-ngx holds documents you may need during tax season, a house move, an insurance claim, or a legal dispute. A backup that has never been restored is more like a hopeful rumor than a safety net.

The shortcut

Server Manager helps you keep the Paperless-ngx setup understandable instead of turning it into a private puzzle. The real benefit is not avoiding every technical word; it is knowing what exists, what it is connected to, and what would break if something changed.

That matters for the exact failure modes above. A wrong or expired certificate is easier to spot. One project is less likely to break another. Months later, the setup is still legible enough that you can see where the app, domain, HTTPS, and storage fit together.

For a document archive, calm maintenance is the point. You want Paperless-ngx to feel like a filing cabinet you trust, not a box of loose cables you are afraid to touch.

FAQ

Is Paperless-ngx private? It can be, if you host it carefully. Your privacy depends on access control, HTTPS, server security, and backups.

Can Paperless-ngx read scanned documents? Yes. Paperless-ngx uses OCR to extract text from many scans and images, so you can search inside them later.

Do I still need the original PDFs? Yes. Paperless-ngx stores the originals and adds searchable information around them. The original files are still the core records.

How much storage do I need? It depends on how much you scan and at what quality. Start with room to grow, then watch storage use over time.

Can I use it for business documents? Yes, but treat it like important infrastructure. Use strong access control, HTTPS, clear backups, and a restore plan.

When Paperless-ngx is set up well, you stop hunting through inboxes and drawers. You get one private place for the papers you may need later, with enough structure that future you can still understand it.