--- title: "Do you still need Cloudinary if your CMS bundles an image CDN?" description: "If your headless CMS bundles an image CDN (resize, format conversion, edge delivery), you usually don't need Cloudinary. Add it only for full DAM, video, or AI editing. Paying for both is common only..." url: "https://adaptocms.com/articles/headless-cms-image-cdn-vs-cloudinary/" category: "Tutorials" date: "2026-07-01" source: adaptocms.com --- # Do you still need Cloudinary if your CMS bundles an image CDN? ## TL;DR If your headless CMS bundles an image CDN (resize, format conversion, edge delivery), you usually don't need Cloudinary. Add it only for full DAM, video, or AI editing. Paying for both is common only when a CMS's media handling is weak or unbundled. **Short answer: no, not for most content-driven sites.** If your headless CMS bundles an image CDN, it's already doing the job Cloudinary is best known for: resizing, format conversion, and edge delivery. You'd still bring in Cloudinary on top of that for real digital asset management, video, or AI-driven tagging and editing across assets that live outside the CMS. For a blog, marketing site, or product catalog where images are authored and served through the CMS, a bundled CDN is enough. Keep reading for where the line sits. ## What a bundled CMS image CDN gives you An image CDN built into a CMS does three things, and they cover most of what a typical site needs: - **On-the-fly transforms.** Request an image with `?w=800&h=400&fit=crop` (or the CMS's equivalent syntax) and get back a resized, cropped version. No separate build step, no pre-generating twelve sizes of every hero image. - **Format negotiation.** The CDN reads the browser's `Accept` header and serves WebP or AVIF instead of the original JPEG/PNG when the browser supports it, without you writing `` fallbacks by hand. - **Delivery.** Images are cached and served from edge nodes near the visitor, the same job any CDN does, wired directly to the CMS's asset storage instead of a separate bucket you have to manage. That's the entire job for a site where images are things editors upload through the CMS and the frontend renders them at a handful of sizes. It's a substantial job, but a bounded one. ## When you'd still want Cloudinary Cloudinary (and Imgix, in the same category) earns its keep once you're past "resize and serve." Reach for it when you need: - **Digital asset management (DAM).** Tagging, search, approval workflows, and usage tracking across thousands of assets, especially assets shared across the CMS, email, ads, and print, not just the one website. The distinction Cloudinary draws is the right one: a CMS manages content, a DAM manages the asset lifecycle across every channel that touches it. - **Video.** Transcoding, adaptive bitrate streaming, and video-specific transforms are a different engineering problem than image resizing, and most bundled CMS media pipelines don't attempt it. - **AI-driven editing at scale.** Auto-tagging, content-aware cropping, background removal, and generative fill across a large, growing library. These matter once managing thousands of assets by hand becomes the bottleneck. - **Assets that outlive the CMS.** If the same product photo needs to ship to a print catalog, three regional sites, and a partner's storefront, a dedicated asset platform earns its bill. A CMS-bundled CDN is scoped to what that CMS serves. If none of that applies (if "media pipeline" for you means "editors upload images, the site renders them responsively"), you're paying for capability you won't use. ## The "paying twice" trap This is where two CMSs in particular put customers in a bind: the CMS's own media handling is thin enough that most teams add Cloudinary as the workaround. **Contentful.** Its Images API handles the basics (resize, crop, format conversion via URL parameters) through documented reference endpoints. But it stops at "basics": no video, no asset tagging or search at DAM scale, no built-in AI cropping. Cloudinary in front of Contentful assets is a common enough pairing that it's a well-documented integration pattern. Teams on Contentful's Lite tier ($300/mo, per [contentful.com/pricing](https://contentful.com/pricing)) are already absorbing the "$300 cliff" from the free tier cut in April 2025; a second Cloudinary bill stacks directly on top of that. Our [Contentful cost breakdown](/contentful-alternative/) walks through the full math. **Strapi.** The Media Library's default upload provider writes to local disk. That's fine for local development, but it has no CDN, no on-the-fly transforms, and (depending on where you deploy) doesn't reliably survive a redeploy at all, per Strapi's own upload-provider docs. There's no bundled media CDN; Strapi's documented fix is to configure a separate third-party provider: S3, Google Cloud Storage, or Cloudinary. So a self-hosted Strapi stack is already three bills before you've written a line of frontend code: the CMS license or Cloud hosting tier, the media provider, and whatever CDN sits in front of it. Our [Strapi alternative](/strapi-alternative/) page walks through the full cost stack. In both cases, the second bill covers for media handling that's incomplete enough that most production deployments need it. ## The media CDN bundled into Adapto CMS Adapto bundles a media CDN with image optimization into every tier. Resize, format conversion, and edge delivery are part of the product rather than a second SaaS you wire in after the fact. There's no separate Cloudinary or Imgix bill: assets are served straight from `media.adaptocms.com`, and the same transforms described above (resizing, format conversion, edge caching) happen inline, built into the CMS instead of layered on top of it. If your media needs grow into DAM territory (video, AI tagging, multi-channel asset reuse), that's a real reason to add a dedicated tool. But that's not why most teams end up paying for one. ## FAQ **Do I still need Cloudinary with a headless CMS?** Usually not, if the CMS bundles an image CDN: that covers resizing, format conversion, and delivery for content-driven images. You'd add Cloudinary for real DAM workflows, video, or AI-based tagging and editing across assets used outside the CMS. **What does a bundled image CDN do?** It resizes and crops images on the fly via URL parameters, converts them to modern formats like WebP or AVIF based on the requesting browser, and serves the result from an edge cache near the visitor. No separate storage service or transformation layer to wire up. Check the [pricing page](/#pricing) for what's included at every tier: media CDN included, no add-on required.