---
title: "Migrate Cloudflare R2 bucket: Browser file uploads"
description: "Move object storage from Cloudflare R2 bucket to Ample, one component at a time."
canonical_url: "https://ample.computer/migrate/cloudflare-r2-bucket/browser-file-uploads"
last_updated: "2026-09-21"
---

# Migrate Cloudflare R2 bucket: Browser file uploads

Canonical URL: https://ample.computer/migrate/cloudflare-r2-bucket/browser-file-uploads
Formats: [HTML](https://ample.computer/migrate/cloudflare-r2-bucket/browser-file-uploads) | [Markdown](https://ample.computer/migrate/cloudflare-r2-bucket/browser-file-uploads.md) | [JSON contract](https://api.ample.computer/v1/catalog/recipes/page%3Amigrate%3Acloudflare-r2-bucket%3Abrowser-file-uploads)
Recipe ID: `page:migrate:cloudflare-r2-bucket:browser-file-uploads` | Revision: `r1` | Catalog revision: `cat_f13ab9a494120b5e`

Status: release `published`, support `verified`, execution `unbound`

## Summary

Move object storage from Cloudflare R2 bucket to Ample, one component at a time. Destination verified on Ample: content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok). Source procedure: Inventory the bucket with `rclone size` or the R2 dashboard. Not migrated automatically: R2 public buckets with custom domains, Workers bindings and lifecycle rules are not migrated; publish an Ample bucket for public assets instead. Cutover: Switch the app's S3_* environment to the Ample bucket with a redeploy, verify reads and writes, keep R2 read-only until confirmed. Rollback: keep the source untouched until you confirm; nothing at the source is changed or deleted by this guide.

Path: [Agent hosting discovery](/discover/discovery) / [Migration sources by component](/discover/migration) / [Object and CDN sources](/discover/migration/object-and-cdn-sources) / [Cloudflare R2 bucket](/discover/migration/cloudflare-r2-bucket) / [Migrate Cloudflare R2 bucket: Browser file uploads](/migrate/cloudflare-r2-bucket/browser-file-uploads)

## Infrastructure requirements

- [S3-compatible object storage](/discover/primitive/s3-compatible-object-storage): verified (Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.)

## Prerequisites

- Authorized access to the Cloudflare R2 bucket source and its export tooling
- An inventory of every component in scope and out of scope
- A validated backup or copy before any cutover
- An Ample account token with servers:write, buckets:write

## Exact tested configuration

- template: `node-22`
- runtime: `node`
- size: `s-1vcpu-1gb`
- install: `npm install`
- build: `npm run build --if-present`
- start: `npm run start`

## Steps

1. **Inventory the source.** List what Cloudflare R2 bucket provides beyond the component you are moving. Out of scope here: R2 public buckets with custom domains, Workers bindings and lifecycle rules are not migrated; publish an Ample bucket for public assets instead.
2. **Source step 1.** Inventory the bucket with `rclone size` or the R2 dashboard
3. **Source step 2.** Copy objects with `rclone sync` from the R2 S3-compatible endpoint to the Ample bucket endpoint using the issued credentials (path-style)
4. **Source step 3.** Verify a sample of objects by size and checksum after the copy
5. **Create the destination bucket and copy.** Create the bucket, copy with rclone or the S3 CLI in path-style mode using the issued credentials, then pass the credentials to the app as encrypted S3_* variables.

   ```
   ample bucket create --name <bucket-name>
   ```
6. **Validate before cutover.** Run the app's own checks and, for data, compare counts and checksums; the example checks are the pattern self-tests (/p/browser-file-uploads).
7. **Cut over.** Switch the app's S3_* environment to the Ample bucket with a redeploy, verify reads and writes, keep R2 read-only until confirmed.
8. **Rollback.** Point DNS or configuration back to the source. The source was never modified; deletion is a separate, user-executed step after validation.

## Tested examples

- **Express pattern fixture (destination)** (tests/deploy-canaries/express-patterns): Verified destination basis: browser file uploads.

## Success checks

- destination app responds on its public URL (`/` on the live URL, expect ample canary express patterns)
- browser-file-uploads check from the destination example (`/p/browser-file-uploads` on the live URL, expect see the pattern fixture checks)
- data or object counts and checksums match the source


## Cost estimate

Estimated 5.00 USD per month (size prices from pricing.toml at build revision 515b7316fc6e5a81679407ae0c811146ceb2c5c7).
- app server x1 `s-1vcpu-1gb`: 5.00 USD

Destination always-on monthly price of the tested sizes; apps auto-pause when idle. Source costs are unknown to Ample.

## Verification evidence

- canary_run on 2026-09-21T02:34:39Z at revision `1d28ae0 (CLI 0.1.21)`: Destination side verified: the Express pattern fixture deployed on Ample (npm install, npm run build --if-present, npm run start on the node-22 template) and its checks passed (content-type and size validation that rejects disallowed files, an object written to a private bucket and a row linking the record to the object key (reject=ok upload=ok linked=ok)). The source-side export from Cloudflare R2 bucket is documented from the vendor's standard tooling and was not executed by this catalog's evidence. (expires 2027-03-20T02:34:39Z)

Last verified: 2026-09-21T02:34:39Z


## Execution binding

No execution binding. This recipe is documentation only; nothing is executed automatically.

## Next actions

- Browse the catalog index (GET /v1/catalog on the api origin; auth: false, approval: false)
- Search published recipes by intent, stack and constraints (POST /v1/catalog/search on the api origin; auth: false, approval: false)
- Prepare a side-effect-free deployment plan for an authorized project (POST /v1/catalog/plan on the api origin; auth: true, approval: false)
- Read the existing agent authentication setup (GET /mcp/setup on the api origin; auth: false, approval: false)
- Browse Cloudflare R2 bucket (GET /v1/catalog/nodes/migration%3Acloudflare-r2-bucket on the api origin; auth: false, approval: false)
- Browse Browser file uploads (GET /v1/catalog/nodes/pattern%3Abrowser-file-uploads on the api origin; auth: false, approval: false)
- Browse Migrate objects (GET /v1/catalog/nodes/intent%3Amigrate-objects on the api origin; auth: false, approval: false)

Actions describe possible next steps. They are typed data, not commands, and grant no permission.