The Chyron Timeline: Deciding How Long On-Screen Text Must Live to Be Read
When viewers say an overlay felt too fast, the real problem may be timing, not just typography. This guide focuses on the part most chyron advice skips: temporal choreography—when text appears, how long it stays, and when it leaves relative to speech, captions, and motion on screen.
By VideoCue · Created with AI assistance and automated editorial checks.

Why this is a timing problem, not another typography post
Most advice about chyrons falls into three familiar buckets:
- Typography/readability: font, size, contrast, stroke, safe margins
- Lower-third design: branding, hierarchy, animation style
- Chapter-card pacing: how long full-screen cards should sit between sections
Those are useful, but they are not the same problem as temporal choreography.
Temporal choreography is about when on-screen text arrives, how long it remains available for reading, and when it exits relative to narration, captions, and picture changes. That is the part creators often feel in comments as “too fast” even when the text itself is large, high-contrast, and well designed.
In other words: a chyron can be perfectly legible and still be poorly timed.
That matters because viewers do not read overlays in isolation. They are reading while also listening, watching motion, following faces, and deciding what deserves attention first. Research on multimedia learning has long warned that presenting multiple streams at once can create split-attention costs when the viewer has to coordinate them mentally; see Richard Mayer’s summary of the modality and redundancy principles in multimedia learning and the earlier split-attention work cited in the Adobe paper’s discussion of cognitive load from juggling multiple representations. Those sources do not give you exact chyron durations, but they do support the core editorial problem: reading, listening, and visual scanning can compete.
A second piece of the puzzle is reading speed itself. Screen reading is often a bit slower than reading from paper, according to the systematic review and meta-analysis in Delgado et al., “Don’t throw away your printed books”. Again, that does not tell us a universal number of seconds for every overlay, but it supports a conservative editing stance for general audiences: if text contains actual details to parse, especially on a screen and under time pressure, assume less reading slack than you feel as the editor.
So this post is not trying to answer “What is the one correct duration?” There isn’t one. It is giving you a practical way to choose between three timing patterns:
- Simultaneous: text and speech start together
- Staggered reveal: speech leads, text follows
- Post-line hold: text stays available after the line ends
That choice depends less on word count alone than on three things:
- Information density
- Whether the text is redundant or complementary
- How visually busy the underlying shot is
One quick limitation before we go further: this framework is for general audiences watching at standard playback without pausing. It is less predictive for specialists who already know the material, for instructional videos designed to be paused, or for viewers watching at 1.25x to 2x speed.
What the sources actually support
A lot of bad timing advice sneaks in by sounding precise without evidence. Better to separate what the sources clearly support from what remains editorial judgment.
The University of North Georgia’s video guidelines support two very practical points:
- text should stay on screen long enough to be read
- post-production graphics should not overlap the closed-caption area
They also offer a simple rule of thumb: read the text aloud twice and keep it up that long. Treat that as an accessibility-minded baseline, not a law of nature.
Cloudflare’s video workflow page supports a different set of points:
- scripts should plan narration, on-screen text, and visuals together as one workflow, per their video production workflow
- on-screen text in screen recordings should be large enough to read in the final video, again from the same workflow page
What Cloudflare does not establish is a cognitive-load theory or best-practice hold times for overlays. So we should not make it carry that weight.
For the cognitive side, it is safer to say this: multimedia-learning research supports the idea that synchronized but competing streams can increase mental coordination demands, and screen-reading research supports a cautious approach to dense text on displays. That is enough to justify timing decisions like staggered reveals or post-line holds when overlays carry real informational load.
A practical framework for on-screen text duration
1. Start with information density, not seconds
The first question is not “How many seconds?” It is “How much parsing work is the viewer doing?”
A handy editorial sort:
- Low density: a name, role, label, or very short phrase
- Medium density: one sentence, one number with context, one date with a qualifier
- High density: multiple figures, dates, conditions, comparisons, or exceptions
The important detail here is that some items are slower to parse than plain spoken-language phrases. Numbers, dates, percentages, slashes, and conditionals are often less glanceable than a simple noun phrase. That is not because viewers are bad readers; it is because these elements are visually compact but semantically dense.
This is where the screen-reading evidence matters. If reading on screens is often a bit slower under many conditions, you should be especially cautious when the overlay contains the exact kinds of details viewers cannot infer from context.
2. Decide whether the text is redundant or complementary
This is the biggest practical lever.
- Redundant text mostly repeats what the voiceover already delivers.
- Complementary text adds something the voiceover does not fully carry.
If the overlay is redundant, viewers can miss part of it and still understand the point from audio. If it is complementary, missing it may change the meaning.
Mayer’s multimedia-learning work is useful here in a broad sense: more concurrent information is not automatically better, especially when two channels partially compete. That does not mean “never show text with speech.” It means redundant overlays can work because audio already carries comprehension, while complementary overlays often deserve either a delayed entry or a post-line reading window.
3. Check background complexity before blaming hold time
A text timing problem is sometimes a shot-selection problem wearing a fake mustache.
If the underlying footage has:
- fast motion
- busy textures
- a talking face
- chart animation
- rapid cuts
- other text already on screen
then the overlay becomes harder to read even if the duration looks reasonable on paper.
That is why UNG’s guidance about leaving text up long enough and avoiding caption-zone overlap matters in practice. Readability is not only duration. Placement and visual competition matter too.
4. Choose the timing pattern deliberately
Once you know density, redundancy, and background complexity, pick one of these patterns.
Simultaneous
Best for low-density, mostly redundant overlays on calm footage.
Staggered reveal
Speech introduces the idea first; text arrives after the viewer knows what to look for. This can reduce split attention because the audio establishes context before the eye has to parse specifics.
Post-line hold
The text remains on screen after the narration finishes. This gives the viewer a cleanup pass, which is especially helpful when the overlay contains dates, percentages, or conditions that require slower parsing.
Notice the wording here: these are not universal timing laws. They are editorial defaults for a general-audience explainer.
Worked example: Rei’s 45-second policy explainer
Rei is cutting a 45-second explainer covering three policy changes. Each beat needs a chyron with dates and percentages. The audience is broad, not specialist. The video will likely be watched once, at normal speed, without pausing.
Here is the fictional script base:
VO 1: "First, the small-business tax credit rises to 35 percent on July 1."
VO 2: "Second, the home-energy rebate drops to 12 percent for households above the income cap, effective September 15."
VO 3: "Third, filing deadlines move to October 31 for new applicants."
Now instead of choosing one timing style for all three, Rei evaluates each chyron separately.
| Chyron | Density | Redundant or complementary? | Background complexity | Chosen pattern | Why this choice | Why other options were rejected |
|---|---|---|---|---|---|---|
| Small-business tax credit / 35% / July 1 | Medium | Mostly redundant | Moderate motion B-roll | Staggered reveal | Audio names the topic first; text then confirms the percentage and date | Simultaneous felt crowded against moving footage; long post-line hold felt too slow for a point already mostly spoken |
| Home-energy rebate / 12% / above income cap / Sept. 15 | High | Complementary | Busy chart-and-footage composite | Post-line hold | The condition and effective date need a second reading pass after narration ends | Simultaneous overloaded attention; staggered-only still ended too quickly once the line finished |
| Filing deadline / October 31 | Low to medium | Redundant | Static background | Simultaneous | Short, simple, and easy to absorb on a calm shot | Delay was unnecessary; extended hold added dead air visually |
Here is the same decision as a rough timeline.
00:08-00:11 VO 1 starts: "First, the small-business tax credit rises..."
00:09 Chyron 1 appears: "SMALL-BUSINESS TAX CREDIT / 35% starting July 1"
00:11.2 Chyron 1 exits
Reason: medium density, mostly redundant, moderate motion underneath
00:20-00:24 VO 2: "Second, the home-energy rebate drops to 12 percent..."
00:20.3 Chyron 2 appears: "HOME-ENERGY REBATE / 12% above income cap / Effective Sept. 15"
00:26 VO 2 ends
00:27.5 Chyron 2 exits
Reason: highest density, complementary detail, busiest background, needs cleanup window
00:33-00:35 VO 3: "Third, filing deadlines move to October 31..."
00:33 Chyron 3 appears: "FILING DEADLINE / October 31"
00:35 Chyron 3 exits
Reason: short, redundant, calm shot
The point is not that these timestamps are industry benchmarks. They are starting-point decisions for Rei’s specific edit.
What the evidence supports is the logic behind them:
- competing channels can create split attention
- screen reading is not frictionless
- semantically dense items like numbers and dates often need more care than plain labels
- a post-line hold can help because it gives the viewer access to the text after the narration stops competing for attention
One failure mode where hold time is not the real fix
Suppose a creator sees “too fast” feedback and responds by simply holding a lower-third longer.
But the real problem is this:
- the overlay sits in the same lower area as captions
- the shot underneath is a handheld street scene with lots of detail
- the text is small and thin
In that case, adding another second may not help much. The viewer is still trying to read two text layers in one zone, over busy footage.
The better fix is to:
- move the chyron away from the caption area, consistent with UNG’s caption-overlap guidance
- simplify or replace the underlying shot
- increase visual separation and size
- then reassess timing
This distinction matters because otherwise you overcorrect by stretching every overlay when the real issue is placement or shot choice.
A step-by-step workflow you can use on your next edit
Step 1: Tag each overlay for density
Before keyframing anything, label each overlay low, medium, or high density.
If it includes multiple numbers, dates, conditions, or exceptions, call it high even if the word count is short.
Step 2: Mark it redundant or complementary
Ask one blunt question: if the viewer misses this text, do they still get the point from the voiceover alone?
- Yes: redundant or mostly redundant
- No: complementary
Complementary overlays are your best candidates for staggered entry or post-line hold.
Step 3: Audit the shot underneath
Look for motion, faces, competing graphics, captions, and screen detail.
If the shot is busy, consider changing the shot or freezing the motion briefly rather than only adding time.
Step 4: Use an accessibility-minded baseline
Start with the UNG guideline: leave text on screen long enough to be read, with their spoken-twice rule of thumb as a baseline.
Then adjust from there:
- trim for very short redundant labels
- add time for complementary details
- add time for busy backgrounds
- add time when the overlay includes dates, percentages, or qualifiers
Step 5: Plan timing with the script, not after the fact
Cloudflare’s workflow is useful here because it treats the script as the blueprint for narration, on-screen text, and visuals together. If you script overlays early, you can catch where audio and text are competing before you are patching it in the edit.
Two tools from VideoCue fit that workflow without turning this into a tool ad:
- the Script Word Counter helps you spot whether the narration itself is already compressed enough that every overlay will be fighting for breathing room
- the Storyboard Builder is handy if you want to note, shot by shot, which overlay is simultaneous, staggered, or held after the line
Step 6: Preview like a first-time viewer
Watch once at normal speed, no pausing, no scrubbing.
Ask:
- Did I finish reading before the text left?
- Did I have to choose between listening and reading?
- Did I miss the number, date, or condition?
- Did any hold feel visually stale?
If the answer is yes, change choreography before rewriting copy.
Pitfalls, tradeoffs, and a quick checklist
Common pitfalls
Using one default duration for every overlay
Consistent templates are tidy, but comprehension is not uniform.
Making text complementary by accident
If the voiceover says the headline and the overlay quietly carries the actual condition, your timing burden goes up fast.
Confusing design fixes with timing fixes
Better typography helps, but it does not erase split attention.
Treating numbers like ordinary words
Dates, percentages, and exceptions often deserve more breathing room than labels.
Letting captions and chyrons fight for the same zone
That is a placement problem first, not only a duration problem. For the design side, pair this with Lower-third typography that actually reads.
Quick checklist before export
- Is each overlay low, medium, or high density?
- Is it redundant or complementary?
- Is the underlying shot calm enough to read over?
- Does any important number or date disappear before a first-time viewer can parse it?
- Would a staggered reveal reduce split attention here?
- Would a short post-line hold help more than rewriting?
- Are captions and overlays occupying separate space?
- Did you watch once straight through at normal speed?
Conclusion: treat chyrons like timed editorial events
When viewers say your text was too fast, the fix is rarely “make everything stay up longer.” It is usually more specific than that.
Treat each overlay as a timed editorial event.
- If it is short and redundant, simultaneous may be fine.
- If audio should establish context first, use a staggered reveal.
- If the text carries numbers, dates, or conditions the viewer really needs, give it a post-line hold.
A good next step is simple: on your next video, pick three overlays and classify each one by density, redundancy, and background complexity. Then test all three timing patterns once. You will usually find that the “right” duration is not a fixed number. It is the amount of time your specific text needs to survive the competition already happening on screen.
