Cloudflare Workers now enforce a single 64 MiB uncompressed bundle limit for every plan, replacing the previous compressed‑size caps of 3 MiB (free) and 10 MiB (paid). This change lets engineers ship larger dependencies, richer frameworks, and more code without hitting a hard upload ceiling.
What Changed in Size Enforcement
When a Worker is deployed, the Wrangler tool bundles the source, compresses it, and uploads the result. The platform used to reject uploads whose gzip payload exceeded the plan‑specific thresholds. The new policy discards the compressed check entirely and only validates the raw bundle size, which must stay under 64 MiB regardless of plan.
Impact on Build and Deployment Pipelines
CI/CD scripts that previously enforced a 3 MiB/10 MiB compressed limit will need to be updated. The wrangler deploy --outdir bundled/ --dry‑run command still reports two numbers:
Total Upload: 259.61 KiB / gzip: 47.23 KiB
The “Total Upload” figure now represents the metric that matters. Teams should adjust any size‑gate logic to compare this value against the 64 MiB ceiling.
Operational and Security Considerations
- Bundle growth. Larger bundles can increase cold‑start latency and memory consumption on edge nodes, even though the platform does not limit compressed size.
- Dependency surface. Adding heavier frameworks expands the attack surface; regular dependency audits remain essential.
- Monitoring. Existing alerts that watch the
gzipsize become obsolete. Replace them with checks on the uncompressed “Total Upload” metric. - Cost awareness. The limit applies uniformly to free and paid accounts, so cost‑related planning around plan upgrades is no longer a factor for size.
Related CloudNinjas coverage: hands-on guides.
What This Means For Practitioners
Adopt the dry‑run command as a standard pre‑deploy step, and re‑configure any automated size gates to use the uncompressed bundle size. Treat the 64 MiB ceiling as a hard ceiling for all new code and dependency additions, and incorporate regular bundle‑size reviews into your CI pipeline. Keep an eye on edge performance metrics, as larger bundles may affect latency even though they now pass the platform’s size check.
