What to use for file uploads in a React app in 2026: UploadThing vs Vercel Blob vs Upstash Blob vs Cloudinary vs Supabase
Disclosure: I work at Upstash, which makes Upstash Blob. Every fact below comes from each vendor's own docs and pricing page (November 2026), so you can check all of it. Adding file uploads to a React app sounds like on
Disclosure: I work at Upstash, which makes Upstash Blob. Every fact below comes from each vendor's own docs and pricing page (November 2026), so you can check all of it.
Adding file uploads to a React app sounds like one decision, but it's really two:
- The file picker. react-dropzone is a hook that gives you a drag-and-drop zone and nothing else. Uppy is a full upload dashboard with plugins for S3 and resumable tus uploads. FilePond is a polished file input that sends files to the endpoint you configure. None of them stores anything.
- Where the files go. A storage service, plus the logic around it: who's allowed to upload, how the file gets there, and what your database records once it lands.
Any picker works with any storage option, so use whichever UI you like. Storage is the choice that's hard to undo later, so that's what this post compares.
The options side by side
| Option | Upload code you get | Free plan | Paid pricing |
|---|---|---|---|
| UploadThing |
UploadButton and UploadDropzone components; server adapters for Next.js, React Router, Express, Fastify and more |
2GB stored | $10/mo for 100GB, or $25/mo for 250GB then $0.08/GB |
| Vercel Blob |
upload() in the browser plus a handleUpload route |
1GB stored, 10GB downloads (Hobby) | $0.023/GB stored, $0.05/GB downloaded, or downloads covered by Flat Rate CDN on Pro |
| Upstash Blob |
useUpload React hook; upload handler in TypeScript, Python or Go |
1GB stored, 10GB downloads | $0.02/GB stored, downloads free up to 1TB/mo, then $0.02/GB |
| Cloudinary | Upload Widget (local files, URL, camera, Google Drive) | 25 credits | Plus: $99/mo for 225 credits (1 credit = 1GB stored, 1GB delivered or 1,000 transformations) |
| Supabase Storage |
supabase-js uploads, tus resumable uploads, access through Postgres RLS |
1GB stored, 5GB egress, 50MB max file | Pro from $25/mo: 100GB stored and 250GB egress, then $0.0213/GB and $0.09/GB |
| Firebase Storage |
uploadBytesResumable, access through Security Rules |
Needs the Blaze plan: 5GB stored and 100GB/mo downloads at no cost | Google Cloud Storage rates past that |
| Cloudflare R2 | None: you write presigned URLs, CORS and multipart | 10GB stored | $0.015/GB stored, downloads free |
So which one
-
Upstash Blob, for user uploads in most React apps. The
useUploadhook uploads from the browser straight to storage, with progress, retries, and resumable multipart for big files. The server side is an upload handler that checks who is uploading and records the file once it lands. It mounts in Next.js, React Router, Hono, SvelteKit, Cloudflare Workers, FastAPI or Go'snet/http, so a Vite SPA talking to a Python or Go API works the same way as a Next.js app. Downloads are free up to 1TB a month, and buckets are S3-compatible, so the AWS SDK and CLI work too. - Cloudinary, when the files are images or video you transform. Resizing, cropping and format conversion are parameters in the delivery URL, and the Upload Widget handles camera and Google Drive sources for you. It's priced in credits, so heavy delivery adds up: Plus is $99/mo for 225 credits.
- Supabase Storage or Firebase Storage, when your auth already lives there. Access rules sit next to your data (RLS on Supabase, Security Rules on Firebase). Supabase recommends its tus resumable upload for files over 6MB. Firebase Storage needs the pay-as-you-go Blaze plan; projects on the free Spark plan lost access to their buckets in February 2026.
-
Vercel Blob, for a Next.js app on Vercel Pro where files are a side feature. With Flat Rate CDN turned on, Blob downloads count toward the 1TB a month Pro includes. That 1TB is shared with the rest of your team's traffic, and Vercel excludes apps where file delivery is most of the bandwidth. Its
onUploadCompletedcallback can't reach localhost, so local development needs a tunnel like ngrok. - Cloudflare R2, for many terabytes of downloads. Free egress wins at that scale. You write the upload side yourself (presigned URLs, CORS, multipart), or pair it with Uppy's S3 plugin.
-
UploadThing, for a drop-in button on a small Next.js project.
UploadButtonandUploadDropzoneleave very little to write. Theuploadthingpackage hasn't had an npm release since 7.7.4 in August 2025, so decide whether you're fine depending on it.
The upload flow they all share
Whatever you pick, don't send the file through your own server. Vercel Functions cap request bodies at 4.5MB, AWS Lambda at 6MB, and Next.js Server Actions at 1MB by default. The hosted options above all use the same three steps instead:
- The browser asks your server for permission, and your server checks who the user is.
- The browser sends the file straight to storage with a short-lived token or signed URL.
- Your server saves the object key (not the file) in your database once the upload lands.
On a Vite SPA, step 1 is one route on the API you already run. Supabase and Firebase fold it into their own auth and access rules. Cloudinary can skip it with an unsigned upload preset, though its docs call signed uploads the more secure option.
How I compared them
- Prices: list prices from each vendor's pricing page on November 18, 2026, US regions, monthly billing.
- Vercel Blob: iad1 (US East) rates for storage and Blob Data Transfer; cache misses and origin transfer are billed on top.
-
Firebase Storage: the no-cost amounts apply to
*.firebasestorage.appbuckets in us-central1, us-west1 and us-east1. - Supabase: the $25 Pro plan covers the whole project, database included.
- Upload features: from each SDK's docs; UploadThing's last release date from npm.
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.