Cloudflare R2 to TeraBox: Move Bucket Files Into a Free Consumer Cloud

Move Cloudflare R2 objects to TeraBox's 1 TB free tier for casual browsing and sharing. S3-compatible client download or cloud-to-cloud transfer with CloudsLinker.

Introduction

TeraBox gives a personal account 1 TB of free storage with an app made for browsing and sharing, which is a different audience from Cloudflare R2 — zero-egress, S3-compatible object storage aimed at developers serving assets to applications and websites. R2's strength is that reading data out is free, which makes it cheap to pull files elsewhere; its weakness, for a casual user, is that it is an API-first bucket with no consumer browsing experience. When an R2 bucket holds personal media or documents you would rather flick through on a phone than fetch programmatically, TeraBox is the friendlier home. The size limit to plan around is TeraBox's 4 GB free per-file cap. R2 connects with an API token (access key and secret) against an account-specific endpoint; TeraBox connects by browser cookie. This guide covers an S3 client download and a cloud-to-cloud transfer with CloudsLinker.

Method 1: S3-Compatible Client Download, Upload to TeraBox
Method 2: Cloud-to-Cloud Transfer with CloudsLinker
Cloudflare R2 vs TeraBox
Method Comparison
Practical Tips
FAQ

About Cloudflare R2

Cloudflare R2 is S3-compatible object storage with zero egress fees, built for developers serving assets to apps and websites from Cloudflare's network.

Model: buckets and object keys (S3-compatible).
Egress: zero egress fees.
Use case: app assets, web content, developer storage.
Access: R2 API token (access key + secret) + account endpoint.
Endpoint: https://<account_id>.r2.cloudflarestorage.com.

About TeraBox

TeraBox is a consumer file locker from Flextech Inc. with a 1 TB advertised free tier and a friendly app for browsing and sharing smaller files.

Free quota: 1 TB advertised; ~80 GB practical (20-file cap).
Per-file cap: 4 GB free / 20 GB Premium.
Model: plain folder tree with a consumer app.
Audience: people, not applications.
Access: browser cookie (ndus, ndut_fmt); no OAuth.

Comparison: Cloudflare R2 vs TeraBox

R2 is developer object storage optimized for serving assets cheaply; TeraBox is a consumer app for files a person browses. The move suits personal, browsable content under the free per-file cap — not application assets.

Feature	Cloudflare R2	TeraBox
Primary use	App/web asset storage	Personal browsing and sharing
Egress fees	Zero	None
Per-file size	Large (S3-class)	4 GB free / 20 GB Premium
Interface	API, S3 clients, Workers	Consumer app and web
Third-party access	R2 API token + endpoint	Browser cookie only

Preparing to Move Cloudflare R2 to TeraBox

On the R2 side

Pick browsable files: leave application assets and large objects in R2; pull personal media and documents.
Create an R2 API token: R2 → Manage R2 API Tokens → Create. Note the Access Key, Secret, and your account endpoint https://<account_id>.r2.cloudflarestorage.com.
Note files over 4 GB for the TeraBox free cap.

On the TeraBox side

Create a TeraBox account at terabox.com.
Create a target folder such as /R2-Import/.

Method 1: S3-Compatible Client Download, Upload to TeraBox

Step 1: Download from R2

Configure rclone or Cyberduck with your R2 API token (access key + secret) and account endpoint. Pull the files you want into a local folder. R2's zero egress means the download costs nothing on Cloudflare's side.

Download files from a Cloudflare R2 bucket with an S3-compatible client

Step 2: Filter and Upload to TeraBox

Set aside anything over 4 GB on a free account, then open terabox.com and drag the rest into your /R2-Import/ folder.

Method 2: Cloud-to-Cloud Transfer with CloudsLinker

Move Objects Server-Side, Egress-Free

CloudsLinker connects R2 with its API token and TeraBox by session cookie. With R2's zero egress, a server-side pull is free on Cloudflare's side — the only real constraint is TeraBox's per-file cap.

Step 1: Connect Cloudflare R2

In CloudsLinker, click Add Cloud → Cloudflare R2. Enter a display name, your R2 Access Key and Secret, and the account Endpoint https://<account_id>.r2.cloudflarestorage.com. Confirm to connect.

Connect Cloudflare R2 to CloudsLinker with API token and account endpoint

Step 2: Connect TeraBox (Browser Cookie)

TeraBox has no OAuth, so use the session cookie:

Install EditThisCookie (V3) in Chrome.
Open www.terabox.com in the same browser, signed in.
Click EditThisCookie → Export and paste the cookie JSON into CloudsLinker.

Or copy the Cookie header (ndus=...; ndut_fmt=...) from DevTools (F12) → Network.

Connect TeraBox to CloudsLinker with the browser session cookie

Step 3: Configure the Transfer

In the Transfer section, set Cloudflare R2 as the source, browse to the bucket and prefix, and set TeraBox as the destination with your /R2-Import/ folder. Apply a 4 GB size filter and type filters. Copy keeps the R2 bucket intact.

Configure Cloudflare R2 to TeraBox transfer in CloudsLinker

Step 4: Start and Monitor

Start the task and track it in the Task List. If the TeraBox cookie expires, the task pauses for a fresh one. Verify in TeraBox before deleting anything in R2.

Method Comparison

Method	Ease of Use	Speed	Best For	Uses Local Bandwidth	Skill Level
S3 Client + Upload	★★★☆☆	★★☆☆☆	A few objects, ad hoc pulls	Yes	Intermediate
CloudsLinker	★★★★★	★★★★☆	Larger sets of suitably sized files	No	Beginner

Practical Tips for Cloudflare R2 to TeraBox

Egress is free, so pulls are cheap: R2 does not charge to read data out, which makes moving files to TeraBox cost nothing on Cloudflare's side.
Get the account endpoint right: R2 uses an account-specific endpoint https://<account_id>.r2.cloudflarestorage.com — copy your account ID exactly.
The 4 GB cap decides fit: personal media and documents are fine; large application assets are not on a free TeraBox tier.
Scope and delete the API token: create a read-only token limited to the relevant bucket, and remove it afterward.
Refresh the TeraBox cookie before long jobs: re-login right before exporting it.
Keep R2 for app assets: TeraBox has no API or Workers integration — it is a browsable convenience copy, not a serving layer.

Frequently Asked Questions

Object key prefixes become folders under your TeraBox target, recreating the bucket layout.

Yes. CloudsLinker maps R2 prefixes to TeraBox folders; an S3 client preserves them if you keep the downloaded structure intact.

They fail on free TeraBox. Upgrade to Premium (20 GB cap), split them, or keep large assets in R2. CloudsLinker's size filter skips them.

With an R2 API token (access key + secret) against your account endpoint https://<account_id>.r2.cloudflarestorage.com. Use a scoped token and delete it afterward. TeraBox connects by browser cookie.

No egress fees — R2 does not charge to read data out. You only pay R2's standard storage and any request costs, which are minimal for a one-time move.

Yes. CloudsLinker filters by prefix, type, size and date — pull browsable files and leave app assets in R2.

Data travels over TLS. R2 uses a scoped API token (delete it afterward). TeraBox stores files server-side under its own keys; log out and back in to invalidate the cookie afterward.

Conclusion

For a few objects, an S3-compatible client pointed at your R2 endpoint downloads them for upload to TeraBox — and with zero egress, the pull is free on R2's side. For a larger set of suitably sized files, CloudsLinker connects R2 with its API token and TeraBox by session cookie and runs the move server-side. R2 stays the better home for application assets and large objects; TeraBox suits the smaller, browsable files. Watch the 4 GB cap and verify the copy before deleting anything in R2.

Start Your Free Trial at CloudsLinker