# archive_too_large

> The compressed archive exceeds 10 MiB.

The compressed archive exceeds 10 MiB.

| | |
| --- | --- |
| Kind | Build or validation problem |
| Reported by | Archive validation (registry, room hosts, disko publish) |
| `disko` exit code | 1 (problems) |

The gzip-compressed release archive is larger than 10 MiB (10,485,760 bytes).
The limit applies to the `.tgz` bytes, not to the files on disk.

## Why it happens

- `disko publish` checks the size after compressing and fails before
  uploading. Its message lists the five largest files in the archive.
- The registry checks the same limit on upload. If it refuses the upload
  size (HTTP 411 or 413), the CLI fails with the CLI error `archive_too_large`.
- Assets are usually the cause: large audio and uncompressed images barely
  shrink under gzip.

## Wrong

```text
art/intro.wav      9,800,000 bytes
art/field.png      2,100,000 bytes
src/main.js           14,000 bytes
```

## Right

```text
art/intro.ogg        900,000 bytes
art/field.webp       300,000 bytes
src/main.js           14,000 bytes
```

Re-encode large assets (for example WAV to Ogg, PNG to WebP), then change
the imports to the new file names and run `disko publish --dry-run` again.

## See also

- [Assets](/games/assets)
- [`package_too_large`](/errors/package_too_large)