Paperless-ngx 3.5 moves bulk operations to async and adds a manual workflow trigger
Version 3.5.0, released on November 17, 2026, hands bulk operations to a queue so large archives no longer freeze the UI. Before upgrading, check the PAPERLESS_ALLOWED_HOSTS variable: its default behavior has changed.
November 17, 2026. Paperless-ngx ships version 3.5.0. November 17, 2026. The release notes open with a warning that some users will need to adjust PAPERLESS_ALLOWED_HOSTS. November 17, 2026. Bulk operations leave the web request for an async queue. Why it matters: the reference self-hosted document manager keeps maturing for large archives, and this release bundles both a real usability gain and a trap to check before you pull the image.
Bulk operations leave the interface
The core change fits in one sentence: every bulk operation — editing metadata, applying tags, correspondents, or document types, batch deletions — now runs in the background instead of inside the web request. In practice, selecting thousands of documents and applying a tag no longer freezes the interface while the server churns.
Who this changes things for is anyone whose archive has passed a few tens of thousands of documents. On a grown database, a synchronous bulk operation could keep the user waiting for seconds at a time, sometimes until the web server’s timeout hit. Handing the work to Paperless-ngx’s task queue — the same one that already handles OCR and document consumption — makes the interface instantly responsive and lets you watch progress in the task queue instead of staring at a frozen screen.
The release also adds markdown rendering for document notes. A note containing lists, links, or bold text now displays formatted instead of raw — an interface detail that matters once notes become where you record a document’s context.
A manual trigger for workflows
The other functional addition is the manual workflow trigger. Until now, Paperless-ngx workflows fired on automatic conditions — on consumption, on modification, on tag or correspondent matches. 3.5.0 lets you run a workflow on demand, without waiting for a condition to materialize.
That is a bigger operational gain than it looks. A well-built workflow can reclassify a pile of documents, rename files, apply permissions, or push an export. Being able to trigger it manually turns what was a black-box automation into an administration tool: you catch up on a misclassified batch, or replay a processing chain over a selection, without rebuilding anything.
The release also cleans up sessions by purging them automatically — hygiene that shrinks the blast radius of a stolen session on a multi-user instance — and fixes the queue processing of saved view widgets.
The fixes that concern AI chat
For several releases, Paperless-ngx has shipped an AI chat feature: an LLM index built over your documents lets you interrogate your archive in natural language. 3.5.0 fixes three points of that feature, and they reveal where it stands.
The first is a hard limit around 32,700 documents: chat filters failed beyond it, excluding precisely the large archives. The fix lifts that bound. The second releases the LLM index’s read lock before streaming the answer — the index is no longer held while the response is written, avoiding slowdowns on busy instances. The third makes document retrieval happen once per question instead of repeatedly.
The three fixes paint the same picture: Paperless-ngx’s AI chat is leaving demo territory and entering real use on real archives, where volume limits are paid immediately.
The thing to check before upgrading
The release notes open with a warning: some users will need to adjust PAPERLESS_ALLOWED_HOSTS. This release fixes the default value of that variable, the list of hostnames allowed to reach the instance. If you access Paperless-ngx behind a reverse proxy with a domain name and never set it explicitly, you risk a 400 after the upgrade.
The fix is one line in your docker-compose.yml, adapted to your real domain:
environment:
PAPERLESS_ALLOWED_HOSTS: "docs.example.com,paperless" Check this variable before you pull ghcr.io/paperless-ngx/paperless-ngx:3.5.0, not after the first production error.
The verdict
Upgrade, but set PAPERLESS_ALLOWED_HOSTS first if you run behind a reverse proxy. 3.5.0 is not a rewrite — it is a maturation release, and that is exactly what you want from a tool that manages multi-year archives: bulk operations no longer freeze the UI, and the manual trigger makes workflows governable.
If your archive exceeds a few tens of thousands of documents, this release is a priority, both for the async work and for the lifted 32,700-document limit on AI chat. If you run a small, recent instance, the urgency is lower, but the upgrade is risk-free once the host variable is checked. For the tool choice itself, our Paperless-ngx overview remains the entry point.