Limits and capacity
These limits apply to every drive. Plan storage, add-ons, and pricing are on plans and billing. The API’s /v1/limits endpoint returns the live values, and the MCP tool descriptions state the limits that apply to their inputs.
| Limit | Value |
|---|---|
| Files in one drive | 500,000 live files |
| Original content in one drive | 1 TB |
| One file | 10 GB |
| Indexed text from one file | 1 MiB (1,048,576 bytes) |
| PDF or DOCX source processed for text extraction | 1 GB |
| Files created by one import | 100,000 |
| Original content in one import | 100 GB |
| Folder depth | 64 levels |
| Results per grep or keyword search call | 100; continue with the returned cursor |
| Bytes returned by one MCP read | 32,768; read the next range to continue |
File size, storage capacity, and searchable file support are separate constraints. Supported UTF-8 text and code files, including Markdown, CSV, and JSON, can be indexed. PDF and DOCX files have their text extracted within the source-processing limit. Other files remain stored and can be found by path. Search indexing has its own text limit; storing a larger file does not make all its contents searchable. A drive also counts toward its organization’s pooled storage, so a plan’s storage can be reached before a drive’s own limit.
A stored file may still be processing before its contents can appear in search. Read its current upload and search status rather than assuming that a completed upload makes it immediately searchable.
Before a storage or plan change, review the available option and displayed price in the Console. Availability can depend on your plan and workspace role. For current product details, ask the connected agent to use the MCP product-help tool with your question.
See getting started for uploads, search for source checks, and troubleshooting for a refused request.