Storage adapters for Payload CMS 27

Store Payload CMS uploads in S3, R2, Vercel Blob or Azure with an official adapter. Community adapters add Bunny, Cloudinary, GitHub and Alibaba OSS.

Stores Payload upload files in Cloudflare R2 buckets instead of local disk

Stores collection uploads in Vercel Blob Storage instead of local disk

Stores Payload uploads in Google Cloud Storage buckets, with optional direct browser uploads

Stores Payload uploads in UploadThing file hosting

Stores Payload uploads in Azure Blob Storage, with optional direct browser uploads

Stores Payload uploads in Amazon S3 buckets with optional presigned downloads

Routes Payload upload collections to a custom or third-party cloud storage adapter

Stores Payload uploads in Cloudinary with CDN delivery and on-the-fly transforms

Stores Payload uploads and streams video on Bunny.net's global CDN

Stores Payload uploads in Cloudinary with direct browser uploads and public IDs

Stores Payload uploads on the local filesystem of your own server

Stores Payload upload files on IPFS by pinning them through an ingest API

Stores Payload uploads in Nextcloud over WebDAV with optional public share links

Syncs Payload media uploads to an ImageKit account with optional AI auto-tagging

Stores Payload uploads in Cloudinary with optional folder prefixes per collection

Stores Payload uploads in a GitHub repository instead of the local disk

Stores Payload uploads in a GitHub repository through the REST API

About these packages

Storage adapters move files from Payload upload collections off the local disk. They write them to object storage or a media service instead. You add an adapter to the plugins array and list the upload collections it should handle.

What these adapters cover

  • Official adapters for Amazon S3 and S3-compatible buckets
  • Official Cloudflare R2, Google Cloud Storage and Azure Blob adapters
  • Vercel Blob, UploadThing and Payload Cloud for hosted projects
  • Bunny.net storage for uploads and video, with signed links
  • Cloudinary, ImageKit and Cloudflare Images for CDN image delivery
  • SFTP servers, Supabase Storage, GitHub repositories and Alibaba Cloud OSS

Choosing a storage adapter

Start from where you deploy. Vercel projects often use Vercel Blob, and Cloudflare projects use R2. Anything else can use S3 or an S3-compatible bucket. Pick Cloudinary, ImageKit or Cloudflare Images when images should be served from that service's CDN. Community adapters also keep files in a GitHub repository or in Alibaba Cloud OSS. Check the supported Payload version on each card before you install. File browsers and folder pickers are storage plugins, and crop tools are media plugins.

Frequently asked questions

Do I need a storage adapter for Payload CMS?

Only if uploads cannot stay on the server's disk. Serverless and multi-instance deployments need one. On those hosts, files written to local disk disappear on redeploy or stay on a single instance.

Can different collections use different storage?

Yes. Each storage adapter takes a list of the upload collections it should handle. You can send media to one bucket and documents to another, or keep some collections on local disk.

Which storage adapters support direct uploads from the browser?

The official S3, Vercel Blob, Google Cloud Storage and Azure Blob adapters offer optional direct browser uploads. Enable the adapter's clientUploads option and configure the provider's upload permissions as its documentation requires.