Cloudflare Shared Dictionaries: Delta Compression for the Agentic Web 2026

Web pages grow heavier every year, deploys happen faster than ever, and agentic bots now generate nearly 10% of all HTTP requests — traditional compression is no longer keeping up. Cloudflare's shared dictionary support changes the equation by sending only the diff between asset versions instead of the full file on every deploy.

For most of the web's history, compression has been stateless: every response is compressed as if the client has never seen the resource before. This worked well enough when deploys were infrequent and pages were lighter. Today, AI-assisted development teams ship multiple times per day, bundlers re-chunk on every commit, and agentic crawlers fetch full pages repeatedly just to extract fragments. The result is massive, avoidable data transfer — bandwidth wasted on bytes the client already has cached.

What was announced

On April 17, 2026, Cloudflare published a detailed preview of its upcoming shared dictionary compression support, along with confirmed beta availability. The feature implements RFC 9842: Compression Dictionary Transport at the CDN edge, making delta compression accessible without origin-side engineering effort.

Instead of downloading an entire JavaScript bundle after every deploy, the browser signals to the server which version it already has cached via an Available-Dictionary header. The server then compresses only the diff between the old and new versions and sends that — a process called delta compression. The previously cached file becomes the dictionary.

Cloudflare's internal lab results demonstrate the scale of the improvement:

• Uncompressed asset size: 272 KB
• After gzip: 92.1 KB — a 66% reduction
• After shared dictionary compression (DCZ): 2.6 KB — a 97% reduction over the already-gzipped size
• Phase 2 demo result: 94 KB bundle reduced to ~159 bytes — a 99.5% reduction over gzip
• Download time on cache miss: 31 ms (DCZ) vs. 166 ms (gzip) — 81% faster
• Download time on cache hit: 16 ms (DCZ) vs. 143 ms (gzip) — 89% faster

The rollout is structured in three phases. Phase 1 open beta is confirmed for April 30, 2026. Phase 2 moves dictionary management to the Cloudflare edge entirely. Phase 3 introduces fully automatic dictionary generation with no customer configuration required.

Why this matters for CEE

For CIOs, CISOs, and IT directors across Central and Eastern Europe, this announcement is relevant on two levels: performance and operational cost.

CEE markets include a significant share of users on mobile connections and in regions where bandwidth costs remain meaningful. Reducing asset transfer size by 97–99% on incremental deploys directly translates to faster page loads for end users and lower egress costs for platform operators. Organizations running SaaS products, e-commerce platforms, or media-heavy applications on Cloudflare stand to benefit immediately from Phase 1 without changes to their origin infrastructure.

From a security architecture perspective, the new standard addresses the vulnerabilities that caused Google's earlier SDCH attempt to fail in 2017. RFC 9842 enforces same-origin dictionary usage, eliminating the cross-origin conditions that enabled CRIME and BREACH-class compression side-channel attacks. Enterprise security teams can evaluate the feature with a well-specified threat model already addressed in the standard.

For development teams adopting AI-assisted workflows and shipping more frequently, shared dictionaries remove the performance penalty of high-velocity deploys — meaning product velocity no longer comes at the cost of user experience or bandwidth bills.

Technical details

How shared dictionary compression works

• Use-As-Dictionary header: Server instructs the browser to cache the current response as a future compression reference
• Available-Dictionary header: On subsequent requests, the browser advertises the hash of its cached version
• Delta compression: The server compresses the new version against the cached version and sends only the diff
• Supported encodings: DCB (Brotli-based) and DCZ (Zstandard-based) content encodings
• Browser support: Chrome 130+, Edge 130+; Firefox support in progress

Phase 1 — Passthrough (Beta: April 30, 2026)

• Function: Cloudflare forwards shared dictionary headers and encodings without stripping or recompressing
• Cache key extension: Varies on Available-Dictionary and Accept-Encoding to cache dictionary-compressed responses correctly
• Who it serves: Customers managing dictionaries at their own origin
• Requirements: Cloudflare zone with feature enabled, origin serving DCB/DCZ responses with correct headers, Chrome 130+ or Edge 130+ visitors

Phase 2 — Edge-managed dictionaries

• Function: Cloudflare injects Use-As-Dictionary headers, stores dictionary bytes, delta-compresses new versions, and serves correct variants per client
• Origin impact: Zero — origin continues serving normal responses
• Configuration: Customer defines which assets should be treated as dictionaries via a Cloudflare rule

Phase 3 — Automatic dictionary generation

• Function: Cloudflare identifies versioned URL patterns automatically and generates dictionaries without any customer configuration
• Signal source: Network-wide traffic visibility across millions of zones and billions of requests
• Validation: RUM beacon confirms compression improvement before dictionaries are committed to production serving
• Target audience: All Cloudflare zones, including those without dedicated engineering resources

Security model

• Same-origin enforcement: RFC 9842 restricts dictionary use to same-origin responses, closing the cross-origin attack surface that affected SDCH
• CRIME/BREACH mitigation: Same-origin constraint prevents the content injection conditions required for compression side-channel attacks
• Fallback behavior: Clients without a matching dictionary receive standard compressed responses transparently

Softprom and Cloudflare

Softprom is the official distributor of Cloudflare in the CEE region. As a distributor, Softprom provides access to the full Cloudflare portfolio — including performance, security, and network services — along with local technical expertise, pre-sales support, and partner enablement across Central and Eastern Europe.

Shared dictionaries give compression a memory. For teams shipping frequently and serving users across bandwidth-constrained markets, this is a meaningful infrastructure upgrade — not a marginal one.

Organizations evaluating Cloudflare's shared dictionary compression for their web infrastructure can engage Softprom for guidance on Phase 1 readiness assessment, origin configuration requirements, and integration with existing Cloudflare deployments. Softprom's team works directly with Cloudflare engineering and can provide early access context as the beta launches on April 30, 2026.

This content was prepared as part of the Softprom DistriFlow project — an automated system for monitoring and adapting vendor news. Original source: original article.