Paperless-ngx storage paths: folders without moving files by hand

Decide what you want the folders to do

A year-and-correspondent structure can make exported or stored documents easier to browse. It does not replace the database, permissions, or search interface. Choose a layout that serves a real retrieval or handover need. Trying to encode every tag in a folder name often makes the result harder to understand.

Use the supported naming mechanism

Paperless documents PAPERLESS_FILENAME_FORMAT and per-document storage paths. Its examples use placeholders to assemble directories and filenames. This simple example groups documents by year and correspondent; check the placeholder syntax for your installed version.

PAPERLESS_FILENAME_FORMAT={{ created_year }}/{{ correspondent }}/{{ title }}

Do not rename or move files directly in the media folder. Paperless tracks their locations in its database.

Test missing and repeated metadata

Try a document without a correspondent, two documents with the same title, and a title containing punctuation. Check the actual generated path. Do not assume the path will preserve every character or remain unique without adjustment. Keep directory depth short enough for the systems that will back up and browse the archive.

Apply changes through Paperless

The project explains that changing the global filename format requires the document renamer to update existing files. Storage-path changes have their own documented handling. Follow the procedure for your version after taking a backup; changing a configuration value does not mean every old document immediately moved.

Check both access routes

Open sample documents through the application, then inspect the resulting storage layout without editing it. Verify that backups still include the correct directories. If the real objective is a portable folder archive for someone else, test a supported export as well: a live managed media directory and a handover copy have different jobs.