Digital asset management

useCase dam

Magnolia excels in digital asset management (DAM), offering standard features alongside seamless integration with common DAM tools. The platform provides excellent capabilities for organizing, storing, and retrieving digital assets efficiently. Magnolia’s flexibility extends to our compatibility with popular DAM tools, ensuring easy integration and interoperability.

The inclusion of useful modules, such as tagging, enhances the organization and discoverability of digital assets. This allows users to apply metadata and tags, streamlining the search and retrieval process. Whether leveraging our native DAM features or integrating with external tools, Magnolia provides a comprehensive solution for managing digital assets, catering to the diverse needs of users working with rich media content.

Our Digital asset management (DAM) stores all assets in one centralized location.

You can view, manage and edit assets in the Magnolia Assets subapp. You can use assets on pages and create links to them.


Assets stored in the DAM can be used on Web pages, for example, to display an image on the page or to link to a downloadable document.

  • Store all media types (image, video, audio, Flash, documents) in one place.

  • Use assets on Web pages and in custom content types.

  • Edit images.

  • Tag images. Image content is recognized automatically upon image upload and description tags attached to an image.

  • Metadata. By default, the DAM supports the Dublin Core metadata standard. Additional standards can be added.

  • Control access to assets and the editing functionality.

The DAM provides effective asset management and basic editing features. It is not intended to replace media tools that feature archiving and advanced edit functionality. The focus is on a convincing, consistent and easy-to-understand solution covering the everyday needs of companies running single or multiple websites with Magnolia.

If you need more extensive asset management features, our External DAM integration framework provides out-of-the-box connectors for S3 and Bynder.

You can also connect to another third-party tool by extending the DAM API.


The benefits of storing files in the DAM are:

  • Centralization: The DAM provides a centralized location for assets that can be used across different websites in a Magnolia instance.

  • Re-use: The same asset can be used in many locations of the site.

  • Consistency: Updating a single asset in the Assets app propagates to all pages where the asset is used.

  • Standardization: The same file properties are used each time the file is referenced. You can make the metadata fields mandatory to ensure editors include relevant content.

Digital asset management modules

Magnolia modules are shipped to you in different ways depending on your license:

  • Community Edition (CE): Modules are included as part of the free and open-source version.

  • DX Core: Modules are included as part of the DX Core enterprise product. These modules are in addition to those in the Community Edition license where bundled.

  • Special: Some modules need their own special license as they are not included with CE or DX Core licenses. In some cases, an additional license is required.

    For more details, see License.
Module CE DX Core Unbundled

Digital Asset Management module

Imaging module

Image Recognition module

Amplience DAM Connector module

AWS S3 extension

Bynder extension

Celum DAM Connector module

Cloudinary External DAM module introduction

External DAM integration framework

Frontify DAM connector

Hybrid Assets module

Image Focal module

Image placement module

Microsoft DAM Connector module


DX Core



This widget lets you know where you are on the docs site.

You are currently perusing through the DX Core docs.

Main doc sections

DX Core Headless PaaS Legacy Cloud Incubator modules
6.3 beta

Magnolia 6.3 beta

Magnolia 6.3 is in beta. We are updating docs based on development and feedback. Consider the 6.3 docs currently in a state of progress and not final.

We are working on some 6.3-beta known issues during this phase.