Workers for Platforms now supports Static Assets
Workers for Platforms customers can now attach static assets like HTML, CSS, JavaScript, and images directly to User Workers, eliminating the need for separate infrastructure. This enables serving full front-end applications and full-stack applications from Cloudflare's global edge with built-in caching and automatic scaling.
Workers for Platforms customers can now attach static assets (HTML, CSS, JavaScript, images) directly to User Workers, removing the need to host separate infrastructure to serve the assets.
This allows your platform to serve entire front-end applications from Cloudflare's global edge, utilizing caching for fast load times, while supporting dynamic logic within the same Worker. Cloudflare automatically scales its infrastructure to handle high traffic volumes, enabling you to focus on building features without managing servers.
What you can build
Static Sites: Host and serve HTML, CSS, JavaScript, and media files directly from Cloudflare's network, ensuring fast loading times worldwide. This is ideal for blogs, landing pages, and documentation sites because static assets can be efficiently cached and delivered closer to the user, reducing latency and enhancing the overall user experience.
Full-Stack Applications: Combine asset hosting with Cloudflare Workers to power dynamic, interactive applications. If you're an e-commerce platform, you can serve your customers' product pages and run inventory checks from within the same Worker.
index.jsjsexport default {
async fetch(request, env) {
const url = new URL(request.url);
// Check real-time inventory
if (url.pathname === "/api/inventory/check") {
const product = url.searchParams.get("product");
const inventory = await env.INVENTORY_KV.get(product);
return new Response(inventory);
}
// Serve static assets (HTML, CSS, images)
return env.ASSETS.fetch(request);
},
};index.tstsexport default {
async fetch(request, env) {
const url = new URL(request.url);
// Check real-time inventory
if (url.pathname === '/api/inventory/check') {
const product = url.searchParams.get('product');
const inventory = await env.INVENTORY_KV.get(product);
return new Response(inventory);
}
// Serve static assets (HTML, CSS, images)
return env.ASSETS.fetch(request);
}
};
Get Started: Upload static assets using the Workers for Platforms API or Wrangler. For more information, visit our Workers for Platforms documentation. ↗
Source: original entry ↗
More from Cloudflare
Follow Cloudflare to get its new changes in your feed and email digest.
Cloudflare One Client for macOS 2026.8.2100.0
GA release for macOS Cloudflare One Client with improved split tunnel handling that no longer briefly blocks traffic during reconnects, support for non-RFC 1918 local IPv4 networks, faster connects with lower memory use, and numerous reliability fixes across DNS, reauthentication, and client stability.
Cloudflare One Client for Windows 2026.8.2100.0
This GA release improves split tunnel reliability, adds support for non-RFC 1918 local networks, optimizes connection performance with faster reconnections and lower memory usage, and includes numerous bug fixes for DNS, registration, and network handling. The client now features a service recovery mechanism that automatically restarts on system unlock and better handles large hosts files without blocking traffic.
Cloudflare One Client for Linux 2026.8.2100.0
New GA release for Linux with improved split tunnel handling that no longer briefly blocks traffic during reconnects, support for non-RFC 1918 local IPv4 networks, faster tunnel reconnections, and lower memory usage. Includes numerous stability and reliability fixes for DNS, reconnection behavior, and crash issues.