Files SDK

Files SDK asks a simple question: why should switching from S3 to R2—or supporting both requer rewriting your entire upload pipeline? They're building a universal adapter layer for object and blob storage, a single API that speaks web standards and lets you swap backends without touching your code.

It supports S3, Cloudflare R2, Google Cloud Storage, Azure Blob, MinIO, DigitalOcean Spaces, Supabase Storage, UploadThing, Netlify Blobs, Box, Dropbox, OneDrive, and Google Drive. That's 13+ providers with one npm install and one consistent interface. Need to migrate from AWS to Cloudflare R2 to save on egress fees? Change one line. That's the escape hatch—when you need the native client, it's there. But for most use cases, you never do.

The storage backend market is fragmented AF. Every provider has slightly different APIs, different auth flows, different quirks. Companies want to avoid vendor lock-in but don't want to maintain adapters for every service. Files SDK says write once, store anywhere. v7.0 just dropped. It's developer ergonomics tooling for teams who'd rather ship features than debug S3 signature errors.