flockfs

Large files

On flockfs, a file can be up to 5 GiB. Text files up to 2 MiB are live: everyone's edits merge as they type. Larger text files and all other files are kept as versions of the whole file. Large files are stored in chunks, so a new version of a big file only stores (and only uploads) the parts that changed, and the same file in two places is stored once. Your plan's storage and history limits apply on top of this; see Plans and limits.

A write past a limit is refused with 413: file_too_large for one file that is too big, quota_exceeded when the drive or org is full, with a message such as "This drive is full: 200 GB of 200 GB used. Delete files to make room." Deleting, moving and shrinking files always works and frees space at once. GET /api/usage reports the limits (limits.file_bytes, limits.live_text_bytes, limits.bytes) and current usage; the web app shows them in Drive settings, and the SDK has storageOf(usage). Files that are already larger than a lowered limit stay readable, but restoring an older version must fit the current limit.

Large files stream everywhere: flockfs put and get, sync (files above 16 MiB sync as whole files; concurrent changes become conflict copies), the mount (reads use range requests) and the SDK's upload and rawResponse. flockfs put, sync and the mount upload files over 8 MiB in parallel chunks, send only the chunks the drive does not have, and pick up where they left off after an interruption (Chunked uploads).