Files SDK

Files SDK 2.0 adds a gateway module, browser clients, server adapters, and a shadcn/ui registry around one storage API. The release turns a server-side wrapper into a full-stack file layer with scoped auth, range downloads, and versioned operations.

Files SDK 1.9 shipped a Neon adapter plus plugins for audit logging, caching, failover, signed URL policy, soft delete, tiering, and ZIP workflows. The release makes the storage API more production-ready for multi-backend uploads and safer presigned URL handling.

Files SDK 1.8 shipped cross-adapter search plus typed plugins for compression, encryption, dedup, tracing, usage metering, validation, and versioning. Use it to compose storage hooks and power CLI and MCP search flows.

Files SDK 1.7 adds resumable uploads, provider-to-provider sync, read-only clients, directory-style list(), and MCP adapter hardening. The release matters for long-running transfer jobs and safer file access patterns in agent workflows.

Files SDK 1.6 added cross-provider transfer() streaming and byte-range downloads for partial reads. The release matters because large-file migrations, resumable flows, and media-style UIs no longer need full-file buffering.

Files SDK 1.4 shipped nine new storage adapters, a CLI for agents, an installable skill, and optional peer dependencies. The update broadens storage coverage while sharply shrinking install weight, though adapter dependencies now need explicit installation.

Files SDK 1.3 shipped 12 new storage adapters, an exists() helper, and a Files.file(key) handler. It expands the number of storage backends agents and sandboxed jobs can address through one file abstraction.

Files SDK launched a unified storage API across 18 backends including S3, R2, Vercel Blob, and Google Drive. It also ships tool bindings for OpenAI, Vercel AI, and Claude agent SDKs across Node, Bun, Deno, edge runtimes, and browsers.