How Many Seconds Should Each Feature Stay on Screen?
Timing guidelines for feature visibility in product videos: the 4-second rule for simple features, complexity-based timing, and how to use visual hierarchy to guide duration.
Too short and viewers can't process what they saw. Too long and they get bored and check out. Feature timing in product videos is a science with clear rules.
The 4-second rule for simple features
Any feature that can be understood from a single visual (a button, an icon, a status indicator) needs exactly 4 seconds on screen:
- 1 second: viewer notices the new element
- 2 seconds: viewer reads associated text/label
- 1 second: viewer absorbs and moves on
Shorter than 4 seconds: viewers feel rushed and can't process. Longer: they've understood it and are now waiting for the next thing.
Timing by feature complexity
| Feature Complexity | On-screen Time | Examples |
|---|---|---|
| Single element | 3-4 seconds | New button, badge, toggle, icon |
| Simple interaction | 5-7 seconds | Click → result, drag and drop, toggle |
| Multi-step flow | 8-12 seconds | Form fill → submit → confirmation |
| Complex transformation | 12-18 seconds | Data import → processing → visualization |
| Full workflow demo | 20-30 seconds | End-to-end user journey across multiple screens |
These are total times including transitions and any text overlays. The feature itself is a subset of this time.
The "two reads" principle
For any text overlay accompanying a feature, the viewer needs enough time to read it twice. Not because they're slow — because the first read is partially consumed by context-switching from watching the UI to reading the text.
Calculating minimum time for text: count the words, divide by 3 (average reading speed for on-screen video text: 3 words/second), multiply by 1.5 (the "two reads" buffer).
Example: "Create custom reports in one click" = 6 words → 2s reading time → 3s on screen minimum.
Visual hierarchy affects timing
Not all features deserve equal time. Your timing should reflect importance:
- Hero feature (your differentiator): Gets 2x the standard timing. Let it breathe. Add a slight pause before and after. This is where you want viewers to think "oh wow."
- Supporting features: Standard timing from the table above.
- Nice-to-have features: 70% of standard timing. Quick flash — present but not lingered on.
If every feature gets equal timing, none feel important. Variable timing creates emphasis without requiring text to say "this is the important one."
Transitions eat into feature time
A 500ms transition before and after a feature takes 1 full second from your feature's visible time. Account for this:
- If a feature needs 5 seconds of visibility and has transitions on both sides, the total allocated time should be 6 seconds
- Use faster transitions (200-300ms) for less important features to give them more visible time within a short total allocation
- Use no transition (hard cut) when you want maximum feature visibility in minimum time
The "can I pause and screenshot" test
For any feature shown in your video, pause at a random frame during its visibility window. Can you clearly see what the feature is and what it does? If yes, your timing is sufficient. If the feature is mid-animation or partially obscured by a transition, extend its static hold time.
Common timing mistakes
- Equal time for everything: Makes the video monotonous. Vary timing by importance.
- Text appears and disappears simultaneously with the feature: Text should appear 300ms AFTER the visual (let the eye land first) and disappear 300ms BEFORE the next transition (let the brain close the thought).
- Showing a feature during a camera move: If you're zooming or panning, the feature is partially invisible. Arrive at the framing, THEN show the feature.
- Rushing the final feature: Videos often run long and the last feature gets compressed. Cut a less-important feature from the middle instead.
Create polished product animations in minutes
No keyframes. No After Effects. No motion design experience required.
Try mmotion free