How to integrate cloud storage with Bubble

To integrate cloud storage with Bubble, you typically connect a service like AWS S3, Google Cloud Storage, or Uploadcare using Bubble’s built‑in file uploader or the API Connector. Bubble stores files on its own AWS S3 bucket by default, but when you need your own external storage (for compliance, organization, or custom workflows), you authenticate with that service’s API and send uploaded files to it.

Most common approach: Upload to Bubble → Send file to cloud storage via API Connector

This works because Bubble’s file uploader always generates a public file URL. You can then pass that URL to your cloud provider’s upload API. The flow is simple for beginners: user uploads → Bubble stores temp file → backend workflow sends file to S3/GCS/Uploadcare → provider returns final URL → you save that in the database.

• Bubble File Uploader gives you the file’s URL (for example: https://s3.amazonaws.com/appname/...file.js).
• API Connector sends that URL to the external storage service.
• Backend workflow receives the file url and handles the upload securely.

How to set it up (simple practical steps)

• Create an API in the API Connector. For AWS S3 you can use a “Pre‑signed URL” approach, which means S3 gives Bubble a temporary upload link.
• Bubble calls that endpoint, receives the presigned link, then uploads the file using a second API call.
• Finally, store the returned S3 URL in your database as a text field.

// Example: Uploading a file to AWS S3 using a presigned URL
// Step 1 (server): GET presigned URL from your backend (not Bubble)
// Step 2 (Bubble): PUT the file to that URL

PUT https://your-presigned-url-from-S3
Content-Type: image/png

<binary file data>

Simpler alternative: Uploadcare or Wasabi plugins

If you don’t want to manage presigned URLs, Bubble marketplace plugins for Uploadcare or Wasabi handle authentication and upload automatically. You place their uploader element instead of Bubble’s uploader and save the returned file URL.

• Element gives you the file URL directly.
• No backend workflow needed.
• Good for beginners; fewer API steps.

Privacy & security reminder

When you use external storage, Bubble’s privacy rules don’t apply to the file itself. The file’s visibility depends on your cloud provider settings. For private files, use S3 presigned URLs or similar temporary‑access mechanisms.