Do Son 
According to the changelog published by Cloudflare, from today both the free and paid Workers subscription plans support uncompressed code bundles of up to 64 MiB. Previously, Workers judged whether a deployment exceeded the limit by the size of the compressed bundle. That was capped at 3 MB for the free tier and 10 MB for the paid tier.
No Longer Reckoned by Compressed Size
Formerly, when a developer deployed, the relevant tooling would package and compress the code and dependencies before upload. Even if the original project built without fault, the deployment would be rejected the moment the compressed size surpassed 3 MB on the free tier. Likewise, the deployment would be rejected if it surpassed 10 MB on the paid tier.
The new rule instead inspects only the uncompressed bundle size, with the limit set at 64 MiB for both the free and paid tiers alike. The GZIP-compressed size is now displayed merely as reference information. Therefore, one cannot simply reckon the change as a twenty-one-fold increase for the free tier. This is because the method of measurement differs between the old scheme and the new.
Checking by Command
Before deploying a project, developers can verify the bundle size with the Wrangler tool. There, Total Upload is the uncompressed size that counts toward the 64 MiB limit, while the GZIP field no longer determines whether a deployment may proceed.
Large Dependencies and Frameworks Deploy More Readily
This adjustment chiefly resolves the problem of Workers failing to deploy on account of large JavaScript dependencies. It also resolves the problem for frameworks and generated code. In the past, some applications had to delete dependencies, split their Workers, or move data into KV, R2, or D1, merely to satisfy the lower bundle limit.
The 64 MiB, however, denotes only the size of the code bundle. It does not signify a commensurate increase in the Worker’s runtime resources. The free tier still permits at most 100,000 requests per day, 10 milliseconds of CPU time, and 128 MB of memory. The paid tier likewise offers 128 MB of memory, though its request count and CPU time run more generously.
Cloudflare also reminds developers that a larger Worker may increase startup overhead. There is thus no need to bundle static files, configuration, and large binary data directly into a Worker.
Support Our Threat Intelligence
Find our tech and OS security coverage helpful? Support our work today and unlock a 100% ad-free reading experience!
Buy Me a Coffee
