Hierarchical File System Attachment Storage

The way attachments are stored changed significantly in Confluence 3.0.  If you are upgrading from Confluence 2.10 or earlier see Upgrading Confluence for recommended upgrade paths, and read the version of the Hierarchical File System Attachment Storage page in our Confluence 3.0 documentation which provides more detail about migrating to the new file system structure.

Confluence stores attachments, such as files and images, in a file system.  Confluence's attachment storage layout is designed to:

  1. Limit the number of entries at any single level in a directory structure (as some file systems have a limit on the number of files that can be stored in a directory).
  2. Partition attachments per space making it possible for a system admin to selectively back up attachments from particular spaces.

Attachments in Confluence have a number of identifying attributes: idspace id and content id. This means the attachment logically belongs to a piece of content which logically belongs in a space (not all content belongs to a space). For attachments within a space in Confluence, the directory structure is typically 8 levels, with the name of each directory level based on the following algorithm:


Derived From

1 (top)

Always 'ver003' indicating the Confluence version 3 storage format


The least significant 3 digits of the space id, modulo 250


The next 3 least significant digits of the space id, modulo 250


The full space id


The least significant 3 digits of the content id, modulo 250


The next 3 least significant digits of the content id, modulo 250


The full content id


The full attachment id

Within the 8th level will be a file for each version of that attachment, named to match the version number e.g. 1

An example:

To find the directory where attachments for a particular space are stored, go to <confluence url>/admin/findspaceattachments.jsp and enter a space key. It will return the directory on the file system where attachments for that space are stored.

Attachment D in the above diagram is stored in a slightly different structure. Attachments that are not conceptually within a space replace the level 2 - 4 directories with a single directory called 'nonspaced'. Examples of such attachments are the global site logo and attachments on unsaved content.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport