Cloudflare Worker 64 MiB limit and the Sume SDK bundle
Cloudflare now checks only a 64 MiB uncompressed Worker bundle. @sume-com/sdk has no runtime dependencies and runs on Workers; measure with a dry run.
Adding @sume-com/sdk is unlikely to be what pushes a Worker toward the new limit. Cloudflare removed the 3 MB (Free) and 10 MB (Paid) compressed limits on September 4, 2026 and now checks only the uncompressed bundle against 64 MiB. The SDK has no runtime dependencies and lists Cloudflare Workers as supported. Measure your own bundle to be sure.
Cloudflare facts are from its changelog; SDK facts from the TypeScript SDK page, read 2026-09-30.
What exactly changed on Cloudflare?
Wrangler bundles and compresses code before upload. Previously Cloudflare checked the compressed size and rejected deploys over 3 MB (Free) or 10 MB (Paid). That limit is removed. Only the uncompressed bundle size is checked, 64 MiB on all plans. The gzip figure Wrangler prints is for reference and no longer a limit.
| Check | Before | Now |
|---|---|---|
| Compressed size, Free | 3 MB | Not checked |
| Compressed size, Paid | 10 MB | Not checked |
| Uncompressed bundle | Not the limit stated | 64 MiB, all plans |
What does the Sume SDK add to a bundle?
The docs describe @sume-com/sdk as MIT licensed with "no runtime dependencies". It needs fetch and WebCrypto, on Node 18+, Bun, Deno or Cloudflare Workers. verifyWebhook uses WebCrypto rather than node:crypto, which keeps it importable from Workers. The docs give no byte size, so this page does not either; the number comes from your build.
How do I measure it?
Use the command from the changelog and read the Total Upload value, which is the uncompressed size counted against the limit.
wrangler deploy --outdir bundled/ --dry-runDo I need the SDK on a Worker at all?
No. The public API is plain HTTP, so fetch with Authorization: Bearer works with no package. The SDK is worth it for typed operations and helpers such as waitForJob and verifyWebhook. Start from the SDK quickstart if you add it.
Sources
Related posts
More in Developers
- Cloudflare Workflow schedules: one Sume Idempotency-Key per tick
A scheduled Cloudflare Workflow that submits a Sume job should derive the Idempotency-Key from the tick, so a replayed step returns the same job.
- Workflows keeps state 7 days now: store your Sume job ids
Cloudflare Workflows on Workers Paid now keeps finished instance state 7 days by default. Save the Sume job id and result URL in your own store.
- Workflows instance limits vs Sume queue headroom: which binds?
Cloudflare lists 50,000 concurrent Workflow instances (Paid, April entry). Sume reports your own generation headroom; size fan-out by that formula.
- Workflows .subscribe() vs Sume job events: push or pull?
Cloudflare Workflows can stream instance events with subscribe(). Sume has no SSE stream for jobs: use a signed webhook, or poll status and the events snapshot.
Written by Sume