Bucket Object Too Large

bucket-object-too-large · 400

The file is larger than the 5 GiB the upload routes take, so the API signed nothing for it.

These come from the upload routes the console's file browser calls; an app writing with its own S3 keys talks to the store and never meets them. sizeBytes is the size the call gave and maxBytes the most per file, both in bytes.

Besides the members every error carries, this type adds code, key, sizeBytes and maxBytes.

Common causes

  • The file is over 5 GiB, such as a disk image or a large archive.
  • The call sent a wrong sizeBytes, such as a size in another unit.

How to fix the call

  • Split the file into pieces under 5 GiB, or compress it, then upload each piece.
  • Check that sizeBytes is the file's size in bytes.

Example response

json
{
  "type": "bucket-object-too-large",
  "title": "Bucket Object Too Large",
  "detail": "'backups/site.tar' is 6442450944 bytes; the most per file is 5368709120",
  "code": "BUCKET_OBJECT_TOO_LARGE",
  "key": "backups/site.tar",
  "sizeBytes": 6442450944,
  "maxBytes": 5368709120,
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/buckets/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/upload-batches/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402/uploads",
  "method": "POST",
  "instance": "POST /v1/buckets/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/upload-batches/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad402/uploads",
  "status": 400,
  "docs": "https://ghaym.me/docs/errors/bucket-object-too-large"
}