Short answer: Cloudflare Workers Free gives you 100,000 requests per day and a 10 ms CPU limit per invocation. Workers Paid costs at least $5 per account each month, includes 10 million requests and 30 million CPU milliseconds, and meters additional usage at $0.30 per million requests and $0.02 per million CPU milliseconds. Paid also raises the default per-invocation CPU ceiling to 30 seconds (configurable to five minutes) and expands several operational limits.
Request volume is only one sizing input. CPU consumed by active computation, subrequest fan-out, memory, bundle size, startup time, payload limits and quota behavior can determine whether an architecture is reliable. This guide shows how to estimate a bill, choose a plan and design around the limits that matter in production.
As an Amazon Associate I earn from qualifying purchases.
Cloudflare Workers plans at a glance
Cloudflare publishes two relevant service levels for ordinary Workers deployments: Free and Paid (also called Standard in the pricing material). The Free plan is a daily allowance, while Paid is primarily a monthly included-usage model with metered overage.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall| Limit or feature | Workers Free | Workers Paid / Standard |
|---|---|---|
| Requests | 100,000 per day, resetting at midnight UTC | 10 million per month included; then $0.30 per additional million requests |
| CPU time | 10 ms per invocation | 30 million CPU milliseconds per month included; 30-second default per invocation, configurable up to 5 minutes (300,000 ms) |
| Memory | 128 MB | 128 MB |
| Subrequests | 50 per invocation | 10,000 per invocation by default, with a documented maximum of up to 10 million |
| Workers per account | 100 | 500 |
| Cron triggers | 5 | 250 |
| Dynamic Workers | Not available | 1,000 unique Dynamic Workers included per month; additional units cost $0.002 per Dynamic Worker per day |
The figures above are Cloudflare’s published limits and pricing for 2026. A limit can apply per invocation, per day, per month or per account, so do not compare the numbers without their time and scope. For example, 100,000 Free requests is a daily cap; 10 million Paid requests is a monthly included amount.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
What Workers Paid actually costs
The $5 account minimum
Workers Paid has a minimum charge of $5 USD per month for an account. Cloudflare describes that plan as including Workers, Pages Functions, Workers KV, Hyperdrive and Durable Objects usage for the minimum account charge. The $5 is not a per-request fee and does not multiply by the number of deployed Workers in the account.
Within the Standard allowance, the account receives 10 million requests and 30 million CPU milliseconds each month. If either measure exceeds its included amount, that measure is billed separately. Cloudflare also states that there are no additional charges for data transfer (egress) or throughput (bandwidth) under this pricing model. Other Cloudflare products or features attached to an application can still create separate charges.
Two independent overage meters
Estimate requests and CPU milliseconds as separate lines on a bill:
- Request overage:
max(monthly requests - 10,000,000, 0) / 1,000,000 × $0.30. - CPU overage:
max(monthly CPU milliseconds - 30,000,000, 0) / 1,000,000 × $0.02. - Estimated Workers total: the $5 account minimum plus those two overage amounts, before any other Cloudflare products.
For a concrete calculation, 20 million requests in a month leaves 10 million requests above the included amount. That produces $3.00 in request overage. If the same account uses 50 million CPU milliseconds, 20 million are above the included 30 million and add $0.40. The resulting Workers usage estimate is $8.40 for that month ($5 minimum + $3 request overage + $0.40 CPU overage), excluding other products.
A workload can exceed one allowance without exceeding the other. An I/O-heavy API might process many requests while using little CPU; a compute-heavy transformation might use substantial CPU with comparatively few requests. Track both counters in your usage monitoring and budget.
Is the Free plan enough for production?
Free can be appropriate for a genuinely small, low-risk service whose traffic stays comfortably below 100,000 requests per UTC day and whose handler completes within 10 ms of CPU time per invocation. It is also useful for prototypes, personal tools, preview environments and infrequently used endpoints.
Production suitability changes when a missed request has a business or security consequence. A public API with bursty traffic can hit the daily cap even if its monthly average looks small. Authentication, authorization, payment, webhook validation and traffic-filtering Workers often need predictable enforcement rather than a route that silently stops running when the quota is exhausted. For those cases, Paid is usually the safer baseline because it removes the stated Free request cap and offers a much larger CPU allowance.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
What happens at 100,000 requests?
Cloudflare documents that Free accounts have a daily limit of 100,000 requests, resetting at midnight UTC. When a Worker exceeds that limit, Cloudflare returns Error 1027. The reset is tied to UTC, not your local time zone, so a service can remain over quota for part of a local morning or afternoon after the UTC boundary has passed.
Routes can be configured to fail open or fail closed when the Worker cannot run because of quota exhaustion:
- Fail open: Cloudflare bypasses the Worker and sends the request to the origin. This preserves availability but can bypass authentication, header checks, rate limiting, rewrites or other Worker-enforced controls.
- Fail closed: Cloudflare returns an error page instead of bypassing the Worker. This protects security and policy controls but makes the route unavailable until the Worker can execute again.
Choose per route, not globally by habit. A marketing page may reasonably favor availability, while an access-control or signed-webhook route should normally fail closed. Test the chosen behavior with a controlled quota or failure simulation before relying on it.
CPU time is not the same as request duration
Workers billing and CPU limits measure active CPU time, not the total wall-clock duration of a request. Waiting for a database, an upstream HTTP response or another network operation does not consume CPU milliseconds while the Worker is idle. Parsing the response, performing encryption, compressing data, rendering a template or transforming a large object does consume CPU.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteThis distinction makes an I/O-bound handler more economical than an equally long CPU-bound handler. A function that spends most of its lifetime awaiting a remote service may have low metered CPU even though the user waits several seconds. Conversely, a short request that performs intensive computation can hit its CPU ceiling quickly.
Per-invocation CPU ceilings
Free allows 10 ms of CPU per invocation. Paid uses a 30-second default CPU limit for an invocation and can be configured up to five minutes, or 300,000 ms. Cloudflare’s pricing material lists no additional duration charge or Standard duration limit, but the limits documentation still defines the CPU ceiling that an individual invocation must respect.
Cron Trigger and Queue Consumer invocations can use up to 15 minutes of CPU time. That longer allowance is for those invocation types, not a blanket increase for ordinary request handlers. Move batch work to a queue or scheduled consumer when it cannot fit safely inside a request’s CPU budget.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
What consumes CPU in practice?
- JSON parsing and serialization of large payloads.
- Cryptographic verification, signing and key derivation.
- Compression, decompression and image or document processing.
- Template rendering and large string or object transformations.
- Sorting, filtering or aggregating large result sets in memory.
Measure CPU for representative payloads, not only for a “hello world” route. A handler that stays below 10 ms with a tiny test body can exceed Free’s limit when a real customer sends a larger document.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Limits that shape a production architecture
Memory and Worker bundle size
Both Free and Paid provide 128 MB of memory. Memory includes the live JavaScript or WebAssembly runtime, parsed data, buffers, libraries and intermediate results. A Worker can therefore fail from memory pressure even when request count and CPU are low. Stream large bodies where possible, avoid retaining entire upstream responses, and release references before processing the next item in a loop.
The documented Worker size limit is 64 MiB, and startup time is limited to one second. Bundle size is the uploaded Worker artifact, not a license to load an unlimited dependency tree at runtime. Remove unused packages, choose edge-compatible builds, and keep initialization work outside the request path when the platform permits it. A large bundle can make deployments fail or leave too little startup budget for module initialization.
Subrequests and fan-out
A subrequest includes a Fetch API call and requests to Cloudflare services such as R2, KV and D1. Free permits 50 subrequests per invocation. Paid permits 10,000 by default, with a documented maximum of up to 10 million. These are per-invocation limits, so a loop that fetches one URL per item can exhaust the allowance even if the Worker receives only one client request.
Count every internal call when designing fan-out: cache lookups, authorization checks, API calls, object reads and writes all contribute. Prefer batching, parallel requests where safe, caching and pagination. A fan-out of 100 downstream calls per user request may be legal on Paid but still create latency, failure amplification and downstream rate-limit problems.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
URL, header and body sizes
Workers documents a 16 KB URL limit, a 128 KB total request-header limit and a 128 KB response-header limit. Cookie-heavy requests, large authorization tokens and generated header lists can cross those boundaries before application code runs.
Request-body limits depend on the account plan:
| Account plan | Maximum request body |
|---|---|
| Free and Pro | 100 MB |
| Business | 200 MB |
| Enterprise self-service | Up to 5 GB |
The Workers platform documentation does not state an enforced response-body limit. That does not remove practical constraints: upstream timeouts, client behavior, memory use and any limits of the service receiving the response still matter. For large uploads, direct-to-storage patterns and resumable protocols are generally safer than buffering the entire file in a Worker.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Account-level counts
Free accounts can have 100 Workers and five Cron triggers. Paid accounts can have 500 Workers and 250 Cron triggers. These are account-level capacity limits, so a multi-environment setup that creates separate Workers for development, staging, previews and tenants can reach them before any request or CPU allowance is exhausted.
Dynamic Workers and multi-tenant designs
Dynamic Workers are available only on Workers Paid. The plan includes 1,000 unique Dynamic Workers per month. Cloudflare charges $0.002 per additional Dynamic Worker per day, and the requests and CPU time generated by those Workers use the ordinary Workers Standard rates.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →This matters when a platform creates a Worker instance for each customer, project or generated configuration. Count unique Dynamic Workers over the billing month and model their daily lifetime, not just the number of customer requests. A design that stays under 10 million requests can still incur Dynamic Worker charges if it creates many instances beyond the included 1,000.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to estimate your monthly bill before launch
- Forecast requests by month. Start with expected daily traffic, add launch or seasonal peaks, and convert to a monthly total. Do not average away a Free-plan daily breach: Free enforcement is per UTC day.
- Measure CPU milliseconds per invocation. Test representative routes and payloads. Multiply the measured average CPU per request by expected requests, then add scheduled, queue and administrative invocations.
- Separate interactive and background work. Record request-handler CPU independently from Cron Trigger and Queue Consumer CPU, because their ceilings and traffic patterns differ.
- Compare each total with Paid inclusions. Subtract 10 million requests and 30 million CPU milliseconds, never allowing a negative overage.
- Apply the published rates. Multiply request overage by $0.30 per million and CPU overage by $0.02 per million CPU milliseconds.
- Add account minimum and other products. Start with the $5 monthly Paid minimum, then account for any non-Workers services on the same Cloudflare account.
- Model bursts and failures. Check the largest UTC-day request count, maximum CPU per invocation, subrequest fan-out and payload size. A monthly bill estimate cannot reveal an invocation that times out or exceeds a hard limit.
Example: a low-CPU, high-request API
Suppose an API handles 35 million requests in a month and averages 0.5 CPU milliseconds per request. CPU usage is approximately 17.5 million milliseconds, below the 30 million included amount. Requests exceed the included amount by 25 million, producing $7.50 in request overage. The Workers estimate is therefore $12.50 for the month: the $5 minimum plus $7.50, before other products.
Example: a compute-heavy endpoint
Suppose a document service handles 8 million requests but averages 6 CPU milliseconds each. That is approximately 48 million CPU milliseconds. Requests remain within the 10 million inclusion, while 18 million CPU milliseconds incur $0.36 of CPU overage. The estimate is $5.36 before other products. The low request count does not make the endpoint “free” on CPU, and the 6 ms average still needs a tail-latency check against the per-invocation ceiling.
Production architecture checklist
- Plan selection: confirm whether peak traffic can exceed 100,000 requests on any UTC day. If yes, do not depend on Free quota behavior for a critical route.
- Security posture: choose fail open or fail closed for every route. Use fail closed when bypassing the Worker would remove authentication, authorization or integrity checks.
- CPU budget: benchmark real payloads and record average and worst-case CPU milliseconds, not only wall-clock response time.
- I/O design: identify every Fetch, KV, R2 and D1 call and keep fan-out below the applicable subrequest limit.
- Memory: test peak simultaneous buffers, parsed JSON and cached data against 128 MB.
- Bundle and startup: keep the Worker below 64 MiB and startup below one second by pruning dependencies and initialization work.
- Payloads: validate URL, request-header, response-header and request-body sizes before clients reach production.
- Background processing: use Queue Consumers or Cron Triggers for work that does not fit a normal request CPU budget, and account for their invocation limits.
- Account capacity: reserve headroom below the 500-Worker and 250-Cron Paid limits when using multiple environments or tenants.
- Dynamic Workers: include the 1,000-per-month allowance and $0.002-per-additional-worker-per-day charge in a multi-tenant forecast.
- Observability: alert on daily requests, monthly requests, CPU milliseconds, Error 1027 responses, invocation CPU failures, memory errors and subrequest-limit errors.
- Load testing: test burst traffic, large bodies, slow upstreams, failed dependencies and quota exhaustion separately. Passing a normal-path test does not prove that fail-open or fail-closed behavior is correct.
Common failure modes and fixes
Error 1027 on an otherwise healthy route
Cause: a Free account exceeded 100,000 requests for the UTC day.
Free tools Windows power users keep installed
One-click scans. No signup required.
Fix: verify the account’s daily counter and UTC reset time, then move the workload to Paid or reduce traffic. Decide whether the route should fail open or fail closed during future exhaustion; do not assume the default matches your security requirements.
CPU limit reached with low latency
Cause: active computation, not waiting time, consumed the invocation’s CPU allowance.
Fix: profile parsing, cryptography, compression and transformations; reduce payload work, split the job, cache results or move long-running processing to a Queue Consumer or Cron Trigger. Increasing a Paid CPU setting helps only when the invocation type and plan allow it.
Subrequest limit reached unexpectedly
Cause: hidden service calls or an unbounded loop multiplied fan-out.
Fix: instrument each Fetch, KV, R2 and D1 operation, then batch or cache calls and cap the number of items processed per invocation.
Large uploads fail before application logic
Cause: URL, header or request-body limits were exceeded.
Fix: move large content to direct object-storage uploads, keep metadata in the Worker request, trim oversized headers and use a plan whose documented body limit supports the required object size.
Deployment or cold-start problems
Cause: the bundle is near or above 64 MiB, or initialization exceeds the one-second startup limit.
Recommended Free Tools
Fix: remove unused dependencies, choose smaller runtime builds, defer optional initialization and split unrelated functionality into separate Workers where account capacity permits.
Which plan fits common production scenarios?
| Scenario | Likely starting point | Reasoning |
|---|---|---|
| Personal tool or preview environment below 100,000 requests per UTC day | Free | The daily request and 10 ms CPU limits may be sufficient when failures are low impact. |
| Public API with unpredictable bursts | Paid | Paid removes the stated Free request cap and supplies monthly request and CPU inclusions. |
| Authentication, authorization or webhook verification | Paid, with fail-closed routing | Bypassing the Worker during quota exhaustion could bypass security controls. |
| Compute-heavy document or cryptography service | Paid, possibly with queued processing | CPU milliseconds and per-invocation ceilings matter more than request count. |
| Many customer-specific generated Workers | Paid | Dynamic Workers are Paid-only and have their own included count and daily overage charge. |
| Large file ingress | Plan selected by body-size requirement, often with direct storage upload | Free/Pro are limited to 100 MB, Business to 200 MB and Enterprise self-service up to 5 GB. |
Use the smallest plan that satisfies the strictest limit, not the one with the lowest nominal request price. A Free deployment that fails closed at a critical moment, exceeds 10 ms CPU or hits 50 subrequests can be more expensive operationally than a predictable $5 Paid account.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
