Claude Files API graduates to general availability

On 20 August 2026, Anthropic moved the Claude Files API to general availability. The practical upshot is a small but meaningful simplification: you no longer need to send the anthropic-beta: files-api-2025-04-14 header on requests to /v1/files endpoints, or on Messages API requests that reference an uploaded file. The beta tax is gone.

What changed and what did not

Before this graduation, every request touching the Files API had to carry that beta header. Forget it, and the request would fail. It was a deliberate gate Anthropic uses to signal that an API surface is not yet stable enough to build production systems on without opt-in acknowledgement.

From 20 August 2026, the header is optional. Requests that omit it are served the current GA response format. Requests that still include it continue to work and return the previous beta response format, so existing integrations will not break while you migrate.

The GA response format brings two changes worth noting:

• File expiration. You can now set expires_in_seconds when uploading a file. The file object will report an expires_at timestamp. After that timestamp, the file content is no longer retrievable and is released from your storage quota. The underlying content may be held briefly for safety review before permanent deletion, and file metadata stays visible for up to 30 days after expiration.
• Pagination. The list endpoint now uses page and next_page cursors rather than the previous format, and accepts an ids[] filter. Each response returns up to 1,000 files (20 by default), ordered newest first. Pass next_page back as the page parameter to walk through results.

Beyond the format changes, the GA release also raises the rate limit to 500 requests per minute and sets the storage ceiling at 1 TB per organisation.

What the Files API actually does

The Files API lets you upload a document or image once and reference it by file_id across multiple Messages API calls. Instead of re-encoding and re-transmitting the same PDF or image in every request, you upload it once and pass the identifier.

This is worth being precise about: the Files API does not reduce the number of tokens Claude processes. When a file is referenced, Claude still reads the full content and bills based on the file’s token count. The saving is in network transfer and encoding overhead, not in inference cost. If you want to reduce token cost, combine the Files API with prompt caching.

Images work through a file source type alongside the existing base64 and url options. Documents work the same way through document content blocks.

What this means for you

If you are already using the Files API in production, the immediate action is to remove the beta header from your requests when you are ready to adopt the new response format, particularly if you want to use file expiration or the updated pagination. There is no hard deadline to migrate; the header still works.

If you have been holding off building on the Files API because beta APIs carry integration risk, that reason is now gone. The surface is stable, documented, and production-ready.

If you are starting a new integration, you can build against the GA format from the start. The Files API documentation reflects the current format.

One security note worth keeping in mind regardless of GA status: any API key in the same workspace can access any file uploaded to that workspace. Never accept file_id values from end users or untrusted sources. Keep the mapping between users and their files in your application layer, and treat file IDs as server-side references only.

What else graduated at the same time

The Files API was not the only thing Anthropic moved out of beta on 20 August 2026. The Skills API (/v1/skills) also graduated, dropping the skills-2025-10-02 beta header requirement. Computer Use and Browser Use also moved to general availability. The Admin API user-management endpoints for Claude Enterprise organisations (members, invites, groups, and custom roles) dropped their own beta header as well.

The Skills API and Files API are available through the Claude Platform and Microsoft Foundry. Updated computer use and browser use tools are coming to Google Cloud’s Vertex AI.

Together these GA announcements give the Claude API a more complete and stable foundation for agent-oriented applications: files for persistent document context, skills for reusable capabilities, computer use for software interaction, and browser use for structured web access. None of these individually are new features, but having them all on stable API surfaces at the same time makes building production systems considerably more straightforward.

The release notes and the beta headers reference on the Claude Platform have been updated to reflect all of these changes.