Programmable Media

Where are my uploaded assets stored? Can I keep uploading to my own storage bucket?

Last updated: Oct-31-2023

Once uploaded to Cloudinary, your assets are safely stored on Cloudinary’s cloud storage, powered by Amazon S3 or Google Cloud, with multiple backups and multi-region redundancies.

Asset Backup

You can also choose to automatically back up your assets. This enables you to restore old versions of an asset after overwriting it with newer ones.

  • On the Free plan, your backups will also be stored by Cloudinary and will count against your Cloudinary storage credits.

    Alternatively, you can use the Get resources API method to return a listing of all assets and then write a script to iterate through your existing assets and copy them to your own storage solution programmatically.

  • On any paid plan, you can optionally choose to back up your assets to your own storage bucket.

    Additionally, Enterprise customers can choose to store their Cloudinary original assets on their own cloud storage, managing redundancies and availability themselves.

Data center locations

By default, Cloudinary uses storage data centers in the US. Enterprise accounts can request storage in different geographical locations, such as EU or AP data centers, for regulatory reasons.

Uploading to your own storage bucket

To use Cloudinary's management, analysis, optimization, transformation and delivery features, your assets must be stored with Cloudinary.

However, if you already have production code that uploads to another location and you want to continue that process and keep your originals in that storage bucket (in addition to storing in and delivering from Cloudinary), you can take advantage of the auto-upload feature, which enables you to map between remote locations (including storage buckets) and Cloudinary folders, and then automatically upload assets to the defined Cloudinary folder path from the corresponding remote location, the first time a new asset is delivered.

Note that if the bucket isn't public, you'll need to whitelist it.


← View all Onboarding FAQ questions

✔️ Feedback sent!

Rate this page: