Paperless-ngx 3.4.1 cuts idle memory use with lazy imports, fixes UI and schema bugs

Paperless-ngx, the popular open-source document management system, released version 3.4.1 with six targeted fixes and improvements. The release addresses a schema placement issue for id__ fields, removes redundant permission checks on card open buttons, and corrects light-mode display problems for checksums alongside mobile positioning for custom field dropdowns. A notable operational improvement comes from contributor stumpylog, who introduced more lazy imports to reduce idle memory consumption.

The UI refinements include making new PDF controls mostly hidden by default and repositioning the preview button in document lists for better workflow. All changes were contributed by maintainers shamoon and stumpylog, reflecting focused maintenance on stability and resource efficiency rather than feature expansion.

Memory and UI fixes in Paperless-ngx 3.4.1

• Lazy imports for idle memory reduction: Contributor stumpylog implemented additional lazy imports to decrease the application's memory footprint when idle, improving resource efficiency for long-running deployments.
• Schema correction: The id__ schema was relocated to the correct position in the codebase, fixing a structural issue that could affect document indexing or API behavior.
• Permission check optimization: Redundant change permission checks on the cards open button were removed, streamlining access control logic in the web interface.
• PDF viewer UI refinement: New PDF controls were changed to be mostly hidden by default, reducing interface clutter in the document viewer.
• Mobile and display fixes: Checksum display in light mode and custom field dropdown positioning on mobile devices were corrected, addressing responsive design gaps.

Why it matters

For self-hosters and small organizations running Paperless-ngx on constrained hardware like Raspberry Pi or NAS devices, the idle memory improvement directly reduces resource contention and extends deployment viability. The UI and mobile fixes maintain the project's competitiveness against proprietary document management alternatives, reinforcing its position as a practical open-source replacement for services like Google Drive or Evernote document workflows.