If an app server is copying every avatar or media byte, the storage choice is already wrong. Put the bytes on object storage and let the app authorize a short-lived pre-signed URL. For a developer-tools product that handles large files, I would choose an object store with pre-signed upload and download support, then keep the application server on the control path only.
TL;DR: pre-signed URLs reduce proxy bandwidth and keep storage credentials out of the browser. AWS S3 is the reference point. Cloudflare R2 is attractive when its edge and S3-compatible interface fit your footprint. Vercel Blob is the quickest fit for a Vercel-shaped application. Infrai is a reasonable option when a plain REST API and one integration surface matter more than advanced storage controls.
What changed the decision?
The constraint was throughput, not the upload form. A 500 MB file should travel from browser to object storage, not browser to API server and then from API server to object storage.…