Storage plugins for Payload CMS

Storage adapters for Payload CMS: upload to S3, Cloudflare R2, Google Cloud, Azure Blob and Cloudinary. Offload media from your server.

Storage plugins move Payload CMS uploads off the local disk into object storage — S3, Cloudflare R2, Google Cloud, Azure Blob or Cloudinary — with CDN delivery and signed URLs. Essential for serverless and multi-instance deployments where local disk isn't persistent.

What these plugins cover

  • S3 / R2 / GCS / Azure Blob adapters
  • Cloudinary and Mux media pipelines
  • CDN delivery and signed URLs
  • Image transforms on upload
  • Per-collection adapter configuration
  • Private files and access control

Choosing a storage backend

Pick R2 or S3 for general object storage, Cloudinary for image-heavy sites that want transforms built in, and combine with media plugins for WebP and resizing.

Pair with media tooling, caching and integrations.

Frequently asked questions

Which storage backends work with Payload CMS?

Community adapters cover Amazon S3, Cloudflare R2, Google Cloud Storage, Azure Blob and Cloudinary, configured per upload collection.

Do I need cloud storage for serverless hosting?

Yes — on serverless or multi-instance hosts the local filesystem is ephemeral, so a storage adapter is required to persist and serve uploads reliably.

Are these storage plugins free?

The adapters are open-source and free; you pay only your cloud provider's storage and egress costs.