Disclaimer: my employer (but I don’t work on the project).
Once you start managing multiple properties and want to keep consistent branding across not only your website but all the social media sites and all the listing services like Yelp etc.
Constantly digging up the right asset, at the right resolution, and dealing with CompanyX-Logo-New222-Real.png like in the stone age before version management.
It's funny that you mention WordPress, because that's one of the main reasons why we developed Daminik. Many of our customers use WordPress, most of them are from the publishing industry. All of them use some kind of DAM, either a local one or one in the cloud. Some of the tools also provide a WordPress plugin. However, what all of these tools currently do is copy the assets into the WordPress media library instead of taking the URL/File from the DAM/CDN. This creates a lot of duplicates that nobody can maintain.
One of the most important things on our roadmap is the development of a WordPress plugin to fix this problem. Will be ready soon.
So, "digital asset managers" (DAMs) are basically fancy versions of the WordPress media library:
https://wordpress.org/documentation/article/media-library-sc...
Why might a fancy version be needed? Well, the basic media library bundled with WordPress just uploads files directly into a web server directory, and then serves them from your web server using its static HTTP serving configuration (e.g. typically via Apache Web Server). The uploads are simple and 1:1, whatever you upload through the browser ends up on the web server as a file.
But usually, a media library could "do more" with those assets -- it could resize them, convert them to web-optimized assets (e.g. WebP), could create thumbnails and crops for different page layouts, could serve the content from a CDN. And that's just images, but there's other things you could do for PDFs (create a searchable index), MSOffice files (auto-convert to PDFs), or videos (extract thumbnails, re-encode in other resolutions, serve from video CDN).
Of course, if you don't use WordPress, perhaps your CMS doesn't have a media library function at all, in which case a DAM might be even more helpful. This seems to be the case for a number of static site generators (SSGs), for example.
On a quick glance, it looks like Daminik is going after this with a separate open source project (written in PHP), and for its alpha is focusing on image management (using ImageMagick under the hood for image conversions). It also seems like it has built in support for uploading assets to Amazon S3, which would mean presumably you could very easily put the AWS CloudFront CDN on top.
(I run a personal WordPress site, and the way I personally handle this is to live with the built-in WP media library, but then put Cloudflare caching and CDN atop.)