How the Amazon Flex 40-Hour Cap Actually Works (2026 Guide)

Almost every Amazon Flex driver has hit the same wall: you open the app, the marketplace looks empty, and you have no idea why. Most of the time, the answer is the 40-hour cap — and most drivers have it wrong.

The cap isn't a calendar-week limit. It doesn't reset Sunday at midnight. Scheduled blocks count even though you haven't worked them yet. And during three specific windows of the year Amazon quietly raises it without telling anyone. Here's how the rule actually works, the math that decides which offers you see, and how to know exactly where you stand.

1. The rule, in one sentence

You may have a maximum of 40 hours of completed and scheduled blocks summed across any rolling 168-hour window.

Every word of that sentence matters:

• “Completed AND scheduled”— the count includes blocks you finished AND blocks you accepted but haven't started yet. A 4-hour block accepted for Saturday already counts as 4 hours against your cap on Tuesday.
• “Rolling 168-hour window” — Amazon looks at every block whose start time is within the trailing 168 hours (7 days × 24). The window slides forward continuously. There is no fixed reset day.
• “Summed” — block durations add directly. A 3-hour block + a 4-hour block + a 6-hour block = 13 hours used.

2. The rolling 168-hour math

The single biggest misconception is that hours reset at midnight Sunday. They don't. Each block's hours fall off the count exactly 168 hours after that block's start time, individually.

Concrete example:

The math is continuous. Every minute, the window slides one minute forward. Hours from old blocks evaporate in the same order they were earned, one block at a time. There is no batched weekly reset.

3. Why scheduled blocks count (the cap trap)

This is where most drivers get burned. The moment you tap “Accept” on a block for tomorrow, Amazon adds those hours to your running total immediately. You haven't earned a dollar yet — the cap math doesn't care.

The practical result: you can have completed only 18 hours of actual work this week and still see “no offers available.” If you also accepted 17 hours of future blocks, your cap math reads 35 — and Amazon won't show you anything that would push you to 40.

4. The hidden buffer — why you can't actually hit 40

The cap is published as 40, but Amazon enforces a buffer underneath. Drivers consistently report being blocked from accepting new blocks once their running total hits around 39 to 39.5 hours. The remaining ~30 minutes of headroom is reserved by Amazon — most likely to absorb block-duration rounding and prevent any race condition where a driver could exceed 40 by a sliver.

In practice, plan around 39.5 as the realistic ceiling. If you're sitting at 35 and you see a 5-hour block, expect Amazon to silently filter it out of your marketplace before you can tap accept.

5. Peak season: when the cap quietly rises to 50

Amazon raises the cap to 50 hoursduring three predictable windows of the year. They don't pre-announce it — drivers discover it by being able to accept a ninth-hour block:

• 📅Tax season — typically early February through mid-April. Amazon needs the throughput to handle returns/refunds traffic.
• 📦Prime Day — roughly the 10-14 day window straddling each Prime Day event. Both the run-up and the post-Day delivery wave.
• 🎄December holiday surge — typically early November through Christmas Eve. The longest of the three windows.

Exact dates vary year to year and sometimes by market. The cleanest signal that elevation has kicked in: you accept a block that puts you above 40 and Amazon allows it. If you're actively tracking the rolling sum, you'll notice the moment the ceiling changes.

6. Canceling a block — yes, the hours come back

When you cancel a scheduled block, Amazon removes those hours from your rolling count immediately. They're available to spend on a different block right away.

The hard rule to know: canceling within 45 minutes of the block's start time is treated as a forfeiture and damages your standing. Outside that 45-minute window, cancellation is hours-neutral and your tier is unaffected.

The strategic move: if you accepted a low-value block earlier in the week and a high-value block surfaces, cancel the cheap one outside the 45-minute window and grab the better one. The cap math allows it — Amazon's standing system doesn't punish it.

7. State and local overrides

The federal Amazon Flex 40-hour cap is consistent across the US program. But some states and municipalities impose stricter limits on independent-contractor driving hours, and Amazon honors them where they apply. Drivers in California, New York, and Washington in particular should verify their local cap — the Amazon cap won't override a stricter jurisdictional rule. If you drive in multiple markets, the lowest cap that applies to any of your driving wins.

8. How to actually track your hours

Amazon's driver app does not show a running hours-remaining counter. There is no dashboard, no progress bar, no notification. The only way to know your number is to track every block as you accept and complete it, age each one out at the 168-hour mark per its individual start time, and keep a running sum.

The manual approach: a spreadsheet with one row per block, columns for start time, end time, duration, and a formula that drops the row from the sum once >168 hourshave elapsed. Some drivers maintain this. Most don't — which is why most drivers run into the cap blind, without warning.

Frequently asked questions

The bottom line

The Amazon Flex 40-hour cap isn't a calendar-week limit — it's a continuously rolling 168-hour window where every block, past and future, occupies a slice of a fixed pool. The drivers who consistently maximize their earnings are the ones who know exactly how much of the pool is consumed at any moment, and which scheduled blocks they could cancel to free up space for higher-paying ones.

Amazon doesn't show you the math. That's the gap FlexDash was built to close — the only mileage tracker that implements the rolling cap correctly, including peak-season elevation and state overrides.