How to read a retention graph: the drop that means something, and the drop that is just Tuesday
Every retention curve slopes down, so the steepest moment is usually not a finding. Here is the arithmetic that separates a real drop from ordinary decline.
Open any video's retention graph and your eye goes straight to the cliff. That instinct is wrong often enough to be worth correcting, because every retention curve slopes down. Viewers leave continuously, at every moment, in every video that has ever been uploaded. On a curve that declines steadily everywhere, the steepest point is just arithmetic.
A bucket that loses 3 points inside a video that loses 3 points per bucket is not a drop. It is Tuesday.
The only comparison that matters is with the video itself#
A drop worth acting on is a fall that is steep relative to that video's own background decline. The biggest number in the array won't tell you that, and neither will a comparison against some channel average, because a 20-minute explainer and a 45-second Short have nothing to say to each other about decline rates.
So the first thing to compute is the background rate: how much this particular video typically loses from one bucket to the next.
Two details in that calculation matter more than they look.
Use the median, not the mean. A video with three cliffs in it has a mean decline dragged upward by the very cliffs you are trying to find. Compare each cliff against that inflated average and they vanish behind their own severity. The median is unmoved by three outliers in forty buckets.
Count rises as zero instead of discarding them. A bucket where the curve goes up (replays, a re-watched moment) is a fall of zero. The measurement is still there. Dropping it shrinks the sample and biases the median upward.
Two thresholds, and why both are needed#
With a background rate in hand, a bucket has to clear two bars before it deserves a sentence written about it.
It must be at least twice the background rate. Twice is blunt and deliberately untuned. A threshold chosen to make a demo produce satisfying findings is precisely how a measurement tool starts lying to the person paying for it.
It must fall at least 3 points in absolute terms. This is the bar that stops the first one from generating nonsense. A beautifully held video declining 0.2 points per bucket turns any 0.6-point bucket into "three times the background rate". Telling a creator they have a problem at 0.6 points is worse than telling them nothing, because they will go and fix something that was never broken.
When there is no shape to read#
Below about eight buckets there is no curve, only a couple of numbers with a line drawn between them. Any "finding" from four data points is pattern-matching on noise.
A video can also have no drop points at all. That is the most useful finding available: the audience left evenly, so there is no single moment you can cut. The problem is the whole video: pacing, premise, or the fact that the video was never interesting after the hook promised it would be.
Any tool that always produces a drop point is inventing one to fill a panel.
Positions, not timestamps#
There is one practical trap here. YouTube reports the retention curve at relative positions, as fractions of the video, and never at seconds. A tool that shows you "the drop at 0:08" has multiplied a fraction by the duration, which is fine, as long as you know that is what happened. The bucket boundaries line up with percentages, and your script's beats will fall wherever they fall between them.
This also means the moment to look at is the start of the falling bucket, not its end. The bucket ending at 34% means people left during whatever was on screen before 34%. Looking at what happens at 34% is looking one beat too late, which is how creators end up rewriting the wrong sentence.
What the average actually tells you#
Average percentage viewed is the number that drives reach, and it is blunt enough to act on without a percentile table:
| Average watched | Read it as | What to do |
|---|---|---|
| 70% and up | Exceptional | Make more of this. Same format, new topic. |
| 55% to 70% | Strong | It works. Vary the topic, keep the structure. |
| 40% to 55% | Average | The hook is fine, the middle sags. Tighten the value beats. |
| 25% to 40% | Weak | Viewers leave early. Rewrite the hook, not the topic. |
| Under 25% | Poor | Drop this format for this niche. |
The 25% to 40% row does not tell you to change the subject. If all you look at is the average, a weak opening on a good topic reads identically to a good opening on a bad topic, and the two need opposite fixes. The curve is how you tell them apart.
One more discipline: five videos#
A single format's measured retention means nothing until about five videos have run it. Below that, one lucky video rewrites your entire theory of what works, which is how a feedback loop turns into noise.
This is the least popular rule in analytics and the one that saves the most wasted work. Two videos is an anecdote with a graph attached.
Before you publish the next one#
Reading a curve is diagnosis after the fact. Two things help earlier: the retention risk checker reads a script for the structural problems that produce an even decline, and how to write a hook covers the opening bucket, which is the one every curve loses most in. If the shape is wrong rather than the writing, the format library is a set of structures that have already been measured.