# Sites can now be up to 1 GiB, ten times the old limit

> One site's package can now be up to 1 GiB instead of 100 MiB. ee-cdn-cli 0.5.0 asks the CDN for the limit and streams uploads from disk. A large package interrupted on its way to a node resumes instead of starting over.

Date: November 4, 2026 · Type: Changed · Products: CDN, CLI, Edge Node · Version: 0.5.0

Source: https://changelog.evolvingedge.ai/2026/11/sites-up-to-1-gib/

Until now, one site could be at most 100 MiB once packaged. A photo blog or a site with a few videos went past that quickly. The limit is now 1 GiB, and from 0.5.0, `ee-cdn-cli` uses it.

## What changed

- **The CLI asks the CDN for the limit** before deploying, instead of assuming 100 MiB. If the CDN doesn't report one, the CLI assumes 1 GiB.
- **An oversized package is still refused before anything is uploaded**, so a site over the limit fails at once, not partway through an upload.
- **Uploads are streamed from disk.** The CLI no longer reads the whole package into memory to send it.
- **Transfers no longer have to finish within a fixed time.** Uploads, downloads and the copies nodes fetch fail only when they stop moving, so a large package on a slow connection gets there.
- **An interrupted copy resumes.** If a large package is cut off on its way to a node, the node picks up where it stopped instead of starting over.

This applies to `ee-deploy`, the Astro integration and the [Deploy to Evolving Edge CDN Action](https://changelog.evolvingedge.ai/2026/10/github-action-deploy/), which all upload through the CLI.

## For node operators

- **Packages over 500 MiB go only to nodes running v0.0.132 or later.** Older versions cut a fetch off at 500 MB, so they aren't given packages that large. Update your node to hold them.

## Limits

- **Portal deploys are covered separately.** Deploys from the portal get the 1 GiB limit in their own change.
- **Older versions of `ee-cdn-cli` still stop at 100 MiB.** The limit is checked by the CLI before uploading, so 0.4.1 and earlier refuse anything larger.

## What you need to do

- **If you run `ee-cdn-cli` yourself,** update to 0.5.0 or later.
- **If you use the Deploy to Evolving Edge CDN Action at `@v1`,** you get it with the next release, which runs 0.5.0.
- **If you've pinned the Action to an exact release,** change it to the first release that runs 0.5.0.