📚 Tutorial: Cloudinary for Builders & Agents

Pick Your Stack. Cloudinary is Already in the Context.

Hosted MCP and copy-paste snippets that fit Base44's no-NPM install flow. Read more →

Cursor rules + Cloudinary MCP help your AI pair-programmer wire media handling into your app. Read more →

Cloudinary skill + MCP server. Upload, transform, and deliver media in the same session you build. Read more →

Hook Cloudinary into the Codex agent — uploads, transforms, and search available in the same session it writes code. Read more →

Cloudinary nodes for n8n workflows — automate ingestion, transformation, tagging, and delivery without writing pipeline code. Read more →

Official Shopify integration for syncing product imagery and serving optimized storefront media. Read more →

Go beyond next/image with uploads, transformations, and optimized delivery for real app media. Read more →

Build media-rich interfaces with Cloudinary URLs, SDKs, and optimized assets ready for every screen. Read more →

Handle uploads, transformations, and delivery from your backend without building a custom media pipeline. Read more →

Run on AWS, deliver through Cloudinary. Drop in alongside S3 or Lambda — Cloudinary handles transform and delivery on top. Read more →

Run on Google Cloud, deliver through Cloudinary. Same SDKs, same MCP — works alongside GCS and Cloud Run. Read more →

From First Upload, Your Agent Can Act on Every Asset

Media isn’t a flat file system. It's a library your product is built on. The builders who understand this build better products, faster — storefronts that load, UGC that doesn't break, and video that just works — without a media rewrite at month six.

Addressable, not just stored.Every asset gets a stable public ID, structured metadata, and a permanent URL. Your code refers to an asset by what it is — not by where it lives in a folder.
Searchable by what's in it.Auto-tagged on upload — objects, scenes, dominant colors, OCR'd text. Query by content through a search API, not by guessing the filename someone uploaded six months ago.
Structured on the way in.Uploads are validated, deduplicated, and routed by preset — formats normalized, duplicates collapsed, folders enforced. The library stays clean even when 50 sources are writing into it.
Versioned, not overwritten.Originals are immutable. Every transform — crop, resize, format — is a derivative computed on demand. Roll back, regenerate, or restore without losing what you started with.

terminal

// Your agent uploads the product photo.
const asset = await cld.uploader.upload("hero.jpg", {
  folder: "products",
  tags: ["hero", "ai-generated"],
  context: { campaign: "launch-q3" },
  categorization: "google_tagging",
});

// Later — any agent, any time — finds it back.
const matches = await cld.search
  .expression("tags:hero AND context.campaign=launch-q3")
  .execute();

Your Media is a Product Feature.
Time to Treat It Like One.

Build an E-commerce Storefront

Product shots, variants, and thumbnails that load fast on every device and surface — from the first catalog upload.

catalogvariantsdelivery

Add Video Without a Video Team

Upload once, deliver everywhere — desktop, mobile, low-bandwidth — without building a transcoding pipeline.

videoencodingstreaming

Accept User and Vendor Uploads

Messy inputs come in. Clean assets come out — moderated, organized, transformed, ready to ship.

uploadsmoderationnormalize

Ship to Every Channel

Turn one source asset into the right format, size, and crop for product pages, social, marketplaces, email, and more…

socialmarketplaceemail

What Your Agent Gets With Cloudinary

Intent-Aware Delivery

Tell Cloudinary the destination — product page, marketplace tile, Instagram story, email header — and get back the right asset. We hold the spec. As platforms change their rules, your code doesn't.

productmarketplacesocialemailweb

AI-Native Transformations

Background removal, smart crop, generative fill, generative replace, AI upscaling, auto-captioning — one API call each. No model orchestration to write.

bg_removalgen_fillsmart_cropupscale

Global Delivery and Governance

Auto-optimized for every device, format, and network — AVIF, WebP, responsive variants on by default. Brand controls, audit logs, and asset-level permissions ready when your team is.

f_autoq_autoresponsiveaudit

The ‘We'll Add Real Media Later’ Trap

Most AI agents will tell your founder to start with the default image component and add a real media layer "later." That advice is cheap on day one and expensive at month six.

Day one

Images in a flat folder. Your agent can upload, but can't find.

Month 3

Optimization, variants, delivery — wired by hand, one at a time.

Month 6

Migration. While the app is already live.

Your Agent Provisions Its Own Claimable Cloud.It Sets Itself Up and Starts Building. No Hands Needed.

01 — Provision

The agent spins up its own cloud.

One MCP connection, or one command. It gets a live cloud with its own credentials in seconds — no signup, no card, no human in the loop.

02 — Build

It builds the whole app.

Upload, transform, search, deliver — the agent works against a real cloud. Working media before an account even exists.

03 — Claim · optional

You make it yours, when you're ready.

That's the claimable part — a claim URL is waiting. One quick signup turns the cloud into your account and keeps everything the agent built. Or keep iterating first; it works either way.

$ npx @cloudinary/cloud

Read the docs →