October 6, 2026
The new, optional storage layer stores each binary or image file only once, using SHA-512 based deduplication. Content can stay in the database or be moved to S3-compatible object storage.
New storage layer for binary content
OpenCms 22 introduces a new, optimized storage layer for media files such as images, PDFs, and Word documents. Binary and image files can now be stored in deduplicated form, significantly reducing storage requirements, especially for larger OpenCms installations.
The new storage layer supports different storage backends. Content can be stored within the OpenCms database or moved to an S3-compatible object storage. Switching between different storage backends at a later point is also supported.
The database footprint shrinks considerably: deduplication alone reduces the database size by about 40%, and moving binaries to S3 storage cuts it by 80% or more.
For editors and users, nothing changes: All content continues to be managed in the OpenCms Workplace just as before. The new storage layer operates transparently in the background and only determines how and where binary data is physically stored.
Gradual introduction and full control
For new OpenCms 22 installations, the new Storage VFS driver is enabled by default. Initially, however, it operates in compatibility mode, where binary and image files continue to be stored in the same way as before. The new storage functionality is only used once it is explicitly activated.
Activation is controlled through a storage policy. The standard configuration provided by OpenCms stores all non-empty binary content using the new storage layer. If necessary, the storage policy can be adjusted for specific technical requirements.
Existing installations can also be switched to the new Storage VFS driver as part of an upgrade. Here, too, the driver can initially be operated in compatibility mode, with the new storage layer activated at a later point. Existing media files can be migrated afterwards if required.
Database or S3
Using the new storage layer does not require an external storage system. The database storage backend provides deduplication of media files without requiring any additional storage infrastructure.
For installations with large or rapidly growing media collections, an S3-compatible object storage can be used instead. This makes it possible to separate large volumes of binary data from the OpenCms database and manage them more flexibly.
Security and access control
Using an external storage backend does not change the OpenCms security model. Media files remain part of the OpenCms VFS and continue to be protected by the OpenCms ACL permission system. The storage backend only determines where the binary data is physically stored – it does not make protected content publicly accessible.
As with any external storage service, the storage backend itself must be configured securely.
Further information
With the new storage layer, OpenCms 22 provides the foundation for more efficient and flexible storage of large media collections – fully transparent to editors and users, with no changes to the familiar way of working with the OpenCms VFS.
For more information about the new storage layer, including configuration options, storage policies, available backends, and the migration of existing content, please refer to the OpenCms documentation.