Introduction to Assets and DAMs

Last modified: September 11th, 2024

Assets are often the most visually important part of your site. They are also usually the largest. Storing assets in a Git repository can quickly become an issue. Git repositories usually max out around 2GB of storage. The size and number of files can also contribute to a slower build. It is a good idea to investigate an alternative storage for assets. To help, CloudCannon can seamlessly connect to your external asset storage. This allows your editors to upload/choose images from any editing interface.

External asset storage is often referred to as a DAM (Digital Asset Manager) and they can do a lot more than just store the files. DAMs can attach extra metadata to your assets, add complex sorting and even do handy image transformations on the fly. Alternatively, they can just store your assets and serve them from a CDN (Content Delivery Network).

A diagram showing code changes going to the GIT repository and large files going to your DAM

CloudCannon integrates with several DAMs:

  • Azure Blob Storage
  • Cloudflare R2
  • Cloudinary
  • Digital Ocean
  • Google Cloud Storage
  • S3
  • Tenovos

If you require a DAM we do not currently support, please reach out to our support team.

Related Articles

Open in a new tab