Two thresholds, one date
A monetisation programme almost never gates you on one number. The long-form YouTube Partner Programme route asks for 1,000 subscribers and 4,000 valid public watch hours in the previous 12 months; the Shorts route swaps the watch hours for 10 million Shorts views in 90 days. Whatever the pair, the date you can apply is the date the later of the two arrives. Everything before that is waiting.
That structure has an unintuitive consequence. Your two requirements are fed by the same traffic but converted by different multipliers. Views turn into subscribers through a subscribe rate — a fraction of a percent for most channels. The same views turn into watch hours through average view duration. Because those two multipliers are unrelated, a channel can sit at 3,900 subscribers with 900 watch hours, or 300 subscribers with 6,000 watch hours, and each of those channels needs a completely different fix.
This calculator does not predict growth. It answers a narrower and more useful question: if the last month repeats, when do both thresholds clear, and which one lands last? That second answer is the one that changes what you do on Monday. If watch hours land last, another burst of subscribers changes nothing about your eligibility date. If subscribers land last, making videos longer changes nothing either.
Why the formula is a maximum of two ratios
Each threshold is a simple shortfall divided by a rate. The subscriber branch is (S_target − S_now) ÷ (V × c), where V is monthly views and c is your subscribe rate expressed as a decimal. The watch-hour branch is (H_target − H_now) ÷ (V × d ÷ 60), where d is average view duration in minutes. The division by 60 is the only unit conversion in the whole model: analytics reports duration in minutes and programmes count hours.
Notice that V appears in both denominators. Doubling your views halves both waiting times, so it moves the eligibility date by the same proportion no matter which requirement binds. That is why traffic growth is the only lever that is never wasted. Every other lever moves exactly one branch. Raising d — longer videos that hold attention, better pacing, chapters that keep people past the two-minute drop — only shortens the watch-hour branch. Raising c — an end screen, a spoken ask, a channel page that explains the promise — only shortens the subscriber branch.
The two shortfalls are floored at zero. If you have already passed one threshold, its branch contributes zero months and the other branch alone sets the date. That is deliberate: a channel at 1,400 subscribers and 2,000 watch hours has a purely watch-hour problem, and the calculator should say so rather than average the two.
The model is linear because monthly rates are the only data you actually have. It will read pessimistically for a channel whose back catalogue is compounding, and optimistically for a channel whose watch hours are about to age out of a rolling 12-month window. Both distortions are discussed under the assumptions below.
Worked example: 22,000 views a month, 3.4 minutes, 0.6% subscribe rate
Take the default channel: 420 subscribers, 950 watch hours banked in the window, 22,000 views a month, an average view duration of 3.4 minutes, and 0.6 new subscribers per 100 views. The targets are 1,000 subscribers and 4,000 hours.
- Watch hours per month. 22,000 × 3.4 = 74,800 minutes. Divide by 60: 1,246.67 hours a month.
- New subscribers per month. 0.6% of 22,000 = 0.006 × 22,000 = 132 subscribers a month.
- Subscriber shortfall. 1,000 − 420 = 580 subscribers.
- Watch-hour shortfall. 4,000 − 950 = 3,050 hours.
- Months to the subscriber threshold. 580 ÷ 132 = 4.39 months.
- Months to the watch-hour threshold. 3,050 ÷ 1,246.67 = 2.45 months.
- Months until eligible. The later of the two: 4.39 months, set by subscribers.
So this channel has a subscriber problem, not a watch-time problem, and it is a gap of 4.39 − 2.45 = 1.94 months. Making videos longer would close a gap that is already closed. Lifting the subscribe rate from 0.6% to 0.9% instead gives 0.009 × 22,000 = 198 subscribers a month, and 580 ÷ 198 = 2.93 months. That is still later than the 2.45-month watch-hour branch, so subscribers continue to bind and the eligibility date becomes 2.93 months — a saving of 4.39 − 2.93 = 1.46 months from one change to an end screen.
How to read the result
Look at the gap between the two branches before you look at the headline. A gap under about half a month means neither requirement dominates and you should simply keep publishing. A gap of several months means one lever is doing all the work and the other is free.
A useful sanity check is the ratio of the two branches. Divide months-to-watch-hours by months-to-subscribers. In the worked example that is 2.45 ÷ 4.39 = 0.56, so the watch-hour requirement is a little over half as demanding as the subscriber requirement for this channel. Any figure far from 1.0 is telling you the channel is unbalanced relative to the programme's design.
There is a structural reason most small channels find subscribers bind first. At the standard 1,000-subscriber and 4,000-hour pair, the two branches take equal time when c × 4,000 = (d ÷ 60) × 1,000, which rearranges to d = 240 × c with c as a decimal. At a 0.6% subscribe rate that break-even duration is 240 × 0.006 = 1.44 minutes. Any channel holding viewers longer than about a minute and a half per view will hit 4,000 hours before it hits 1,000 subscribers — which is most channels, and which is why the subscriber count is the usual bottleneck despite the watch-hour figure looking more intimidating.
If the headline reads as unanswerable, one of your rates is zero. That is a real answer, not an error: a channel with no views accrues neither requirement.
Where the crossover sits: break-even view duration by subscribe rate
| Subscribe rate (per 100 views) | Break-even view duration | Which binds at 3.4 min duration |
|---|---|---|
| 0.20% | 0.48 min | Subscribers |
| 0.40% | 0.96 min | Subscribers |
| 0.60% | 1.44 min | Subscribers |
| 0.80% | 1.92 min | Subscribers |
| 1.00% | 2.40 min | Subscribers |
| 1.40% | 3.36 min | Subscribers (only just) |
| 1.50% | 3.60 min | Watch hours |
| 2.00% | 4.80 min | Watch hours |
| 3.00% | 7.20 min | Watch hours |
The third column assumes a channel starting from zero on both counts with a 3.4-minute average view duration. A channel part-way to one threshold can flip the answer, which is what the calculator above accounts for.
Assumptions and limits you should know about
- Rolling windows expire. The 4,000-hour requirement counts the previous 12 months. If a video that earned most of your banked hours is now eleven months old, hours will leave the window while new ones arrive, and this straight-line model will read optimistically. Compare your window total this month against last month: if it is falling, you are losing a race the calculator does not model.
- Not every view counts. Programmes count valid public watch time. Private and unlisted videos, deleted videos, ad campaigns and some Shorts surfaces are excluded from the long-form total. Take the watch-hour figure from the eligibility card in your dashboard rather than from the analytics overview.
- Subscribe rate is not stable across formats. A viral Short can multiply views while collapsing the subscribe rate per view, so a month with ten times the traffic may deliver only twice the subscribers. Use a rate from a normal month, not a spike.
- Unsubscribes are ignored. The subscriber branch models gross additions. Channels that regularly cross into unrelated topics can see net growth well below gross, so enter a net figure if yours differs materially.
- Eligibility is not the same as approval. Crossing both thresholds opens an application; it does not guarantee acceptance. Reused content, community-guideline strikes and an inactive AdSense association all block monetisation at numbers that qualify on paper.
- Thresholds change. The subscriber and watch-hour fields are inputs precisely because platforms revise them, and lower entry tiers for fan funding sit well below the ad-revenue bar. Enter the pair your programme currently publishes.
What to work out once you are eligible
Eligibility is a date, not an income. The moment both thresholds clear, the useful question changes from when to how much, and the arithmetic is completely different: your ad income depends on the share of views that carry ads, the CPM advertisers pay in your niche, and the split the platform takes. Run those numbers with the YouTube ad revenue calculator before you make any decision about quitting a job.
For most channels reaching the threshold, ad revenue is also not the largest line. A single brand integration frequently pays more than a month of ads at the same view count, and it is priced off the same views figure you entered here — see the sponsorship rate calculator for how that quote is built. Direct audience support is the third route, and the tier arithmetic is unforgiving once fulfilment costs enter: the membership tier break-even calculator shows which tiers actually clear.
It is worth costing the other side of the ledger at the same time. If a video costs more to make than it earns, eligibility just means you are now losing money with a revenue line attached. The video production cost per finished minute calculator puts a number on that, and it is the number that decides whether a format is worth continuing.
If your growth comes mostly from a paid subscriber base rather than ads, the retention side matters more than the acquisition side; the subscriber churn and lifetime value calculator covers how long a paying subscriber actually stays.
Key terms
- Valid public watch time
- Watch time on public, monetisable videos that the platform counts toward the eligibility threshold. It excludes private and unlisted videos, deleted uploads, and traffic from paid promotion.
- Average view duration
- Total watch time divided by total views — the minutes an average view lasts. It is not the runtime of the video and not the audience-retention percentage, though the three are related: duration ≈ runtime × retention.
- Rolling window
- A qualifying period that moves with the calendar, such as the previous 365 days. Watch hours enter the window when earned and leave it exactly one year later, so the total can fall without any drop in traffic.
- Binding constraint
- Of two simultaneous requirements, the one that is satisfied last. Effort spent on a non-binding constraint does not move the date at all.