paperless-ngx v3.2.0 released on 19-09-2026
paperless-ngx v3.2.0 is out now. Administrators and power users will see improved search relevance and text indexing, reduced memory and CPU overhead for classifier and background tasks, and a string of UI and workflow quality‑of‑life fixes.
Visit the project’s GitHub release page and the full changelog for complete details, installation instructions and compatibility notes.
What’s in this release
- Search and indexing: in‑place fuzzy‑term matching inside parsed queries, CJK terms matched via bigram fields, and an advanced search parser with whoosh‑compat (removing the handwritten translation layer); a Tantivy full‑text fallback adapter for taxonomy candidates and improved matching for correspondents, storage paths and labels.
- Classifier, AI and performance: classifier preprocessing moved to Tantivy, classifier loading/saving now streams and uses memory views with dropped fields to reduce memory and pickle size, prefetching and query reductions cut DB load during training, and AI/workflow behaviour tightened (apply‑AI‑suggestions skips empty content, runs async in the workflow editor, and auto‑suggestions can be disabled for inbox documents); regex timeout is configurable.
- UI and workflow quality‑of‑life: deselect single items after using “select all”, hideable sidebar items, centralised management of share links and bundles, a duplicates filter and numerous frontend fixes (thumbnail overflow, truncated long mail subjects, date‑picker firstDayOfWeek localisation attempt and broader v3 UI/icon cleanups).
Upgrade notes
- Dependency and compatibility: the release includes extensive dependency bumps (notable changes include djangorestframework → 3.18.0, ng-select → v24 and sentence‑transformers → 6.0.0, plus multiple docker/service image updates). Review the full changelog on GitHub for compatibility notes before upgrading.
- Rollback guidance: if you encounter regressions, revert to your previous deployment or restore from backups using your usual procedures and test the new version in staging first.
Share your experience upgrading or using v3.2.0 — report issues or feedback on the project’s GitHub so maintainers and the community can follow up.
