Cloudflare Workers
Cloudflare · ⚡ Serverless / FaaS
Run APIs and static sites on Cloudflare Workers with a daily free request allowance, scheduled tasks and usage-based upgrades.
Free-tier constraints
- Offer type
- Perpetual
- When idle
- Stays active
- Credit card
- Unknown
- Commercial use
- Unknown
- At the limit
- Service stops
- Data expiry
- Not published
Free-tier compatibility
- ✓Static hosting
- ✓Serverless
- —Long-running processes
- —Docker
- ✓WebSockets
- ✓Cron
- —Background workers
- —Persistent disk
- ✓Custom domains
Overview
Workers is a useful option when a static website needs a webhook, authentication callback or lightweight API. Static Assets can live alongside request handlers, while Cron Triggers invoke scheduled code without maintaining a server.
Plan around the runtime rather than treating it as a virtual machine. Keep CPU-heavy jobs elsewhere, store durable data in an appropriate bound service, and budget for those products separately. This entry is based on official documentation; we have not performed a deployment test.
Sources and verification
Checked 2026-10-02Pros
- ✓One deployment can serve files and dynamic routes
- ✓Built-in scheduling for periodic tasks
- ✓Bindings connect application code to Cloudflare storage
Cons
- ✕The free CPU allowance is small for computationally expensive handlers
- ✕A Worker is not a Docker host or an always-running Node.js server
- ✕Paid plans add metered charges beyond the base subscription
Best for
- →Lightweight APIs
- →Webhooks
- →Static sites with small dynamic features
Compare with
Getting started
- 1 Create a Worker project from the official getting-started guide
- 2 Implement a small handler and test it locally
- 3 Add only the storage bindings and scheduled triggers you need
- 4 Deploy and watch request and CPU usage in the dashboard
Features
- ✓HTTP handlers
- ✓Static assets
- ✓Cron Triggers
- ✓WebSockets
- ✓Storage bindings
Frameworks
Languages
FAQ
No. The dynamic allowance resets daily; paid allowances use monthly billing. Static asset requests are accounted for separately.
Not in the Workers runtime. Containers are a separate product with their own requirements and pricing.
No. Check each bound product's limits and pricing before storing application data.
Deploy these projects to Cloudflare Workers
Open-source projects and templates that run on Cloudflare Workers's free tier.