Saving to S3
Persist renders directly into your own cloud storage bucket.
Configure Urlbox to upload every render straight to your bucket — Amazon S3, Cloudflare R2, Google Cloud Storage, DigitalOcean Spaces, Backblaze B2, or Azure Blob Storage.
Choose your provider
Configure S3
Public S3 bucket setup.
Configure private S3 bucket
Same as above, but with bucket access locked down.
Cloudflare R2
S3-compatible storage on Cloudflare.
Google Cloud Storage
Upload to a GCS bucket.
DigitalOcean Spaces
S3-compatible storage on DigitalOcean.
Backblaze B2
S3-compatible storage on Backblaze B2.
Azure Blob Storage
Upload to an Azure Blob Storage container.
How it works
- Create a bucket with your provider and an access key that can write to it. Each guide above walks through this step by step.
- Add the bucket name, region, endpoint and credentials to your project's storage settings in the dashboard.
- Pass
use_s3: trueon a render. Urlbox uploads the file to your bucket, and therenderUrlin the response points to it there.
Set s3_path to choose the file name and folder, or s3_bucket to save to a different bucket for a single request. Renders saved to your own bucket don't expire after 30 days the way Urlbox-hosted renders do. See Saving to S3 for the full set of options, including private bucket mode.