VSL progress bar: standard, hidden or smart, and how to test it honestly
Your VSL progress bar tells every viewer how long the video is before they've decided it's worth their time. This guide compares the three options, explains what research on progress indicators found, draws the ethical lines, and shows how to test which one earns more.
On this page
- What does a progress bar do to a VSL viewer?
- The three VSL progress bar options compared
- How a smart progress bar works
- What research says about progress bars and perceived time
- Is a fake progress bar deceptive?
- Should you hide the seek bar on a VSL?
- How to A/B test your VSL progress bar
- Which progress bar should you use?
- A progress bar checklist before launch
- Frequently asked questions
A VSL can show a standard progress bar, hide it, or use a smart bar that fills faster early and slower later. None wins everywhere: standard bars are honest and familiar, hidden bars protect the story, and smart bars make a long video feel shorter at the start. Keep pause available, disclose the real runtime if the bar isn't linear, and let revenue per visitor decide.
What does a progress bar do to a VSL viewer?
A progress bar does two different jobs, and most arguments about it mix them up. It's one of the controls covered in VSL player features, and it deserves more thought than it usually gets.
It signals length. In the first minute, the bar is the viewer's only clue to how big the commitment is. On a 40-minute VSL a standard bar moves 2.5% per minute, so after a minute it has barely left the start. A cold viewer who hasn't yet heard anything worth staying for reads that as "this will take forever".
It lets viewers navigate. If the bar is also a seek bar, viewers can drag ahead to the price or to the end. That gives them control, and it lets them skip the argument that justifies the price.
So separate the decisions. First, should viewers be able to seek? Second, what should the bar say about length? The three common setups are different answers to those two questions.
The three VSL progress bar options compared
Each option answers those two questions differently:
Standard, hidden or smart
What viewers see, the upside, the downside and where each fits best
Standard bar
What viewers see: the true share of the video played.
- Upside: honest, familiar, builds trust
- Downside: shows the full length; often seekable
Fits best: warm traffic, short VSLs, B2B and high-ticket.
Hidden bar
What viewers see: no bar and no seeking.
- Upside: keeps the story in order
- Downside: no sense of length; some viewers feel trapped
Fits best: long VSLs on cold traffic.
Smart bar
What viewers see: a bar that fills fast early, slower later.
- Upside: the first minutes feel lighter
- Downside: not a true clock; trust risk if misused
Fits best: long VSLs on cold traffic, used honestly.
Standard. The bar fills in proportion to time: halfway through the video, it's half full. Nobody can call it misleading, and experienced buyers expect it. On a long VSL, though, it advertises the length at exactly the moment a cold viewer is deciding whether to stay.
Hidden. No progress indicator and no scrubbing. Viewers can't skip to the price and can't see how long the video is. Some will stay longer for not knowing; others will leave because they can't tell. Pause, volume and captions stay visible regardless.
Smart (non-linear). The bar moves quickly through an opening phase, slows down for the rest of the video, and still reaches 100% at the true end. Marketers often call it a fake progress bar. The label matters less than how you use it, which is what the ethics section below is about.
How a smart progress bar works
A smart bar has two settings: how long the fast phase lasts and how far the bar fills during it. After that, the remaining share fills over the rest of the video.
Say your VSL runs 30 minutes and you set a fast phase of 3 minutes that fills 40% of the bar. For illustration, assume each phase fills evenly:
Standard bar vs smart bar on a 30-minute VSL
Illustrative: a 3-minute fast phase that fills 40%, each phase filling evenly. Share of the bar filled
- Standard bar
- Smart bar
Time into the video
Show the numbers
| Time into the video | Standard bar | Smart bar |
|---|---|---|
| 0:00 | 0% | 0% |
| 1:00 | 3% | 13% |
| 2:00 | 7% | 27% |
| 3:00 | 10% | 40% |
| 4:00 | 13% | 42% |
| 5:00 | 17% | 44% |
| 6:00 | 20% | 47% |
| 7:00 | 23% | 49% |
| 8:00 | 27% | 51% |
| 9:00 | 30% | 53% |
| 10:00 | 33% | 56% |
| 11:00 | 37% | 58% |
| 12:00 | 40% | 60% |
| 13:00 | 43% | 62% |
| 14:00 | 47% | 64% |
| 15:00 | 50% | 67% |
| 16:00 | 53% | 69% |
| 17:00 | 57% | 71% |
| 18:00 | 60% | 73% |
| 19:00 | 63% | 76% |
| 20:00 | 67% | 78% |
| 21:00 | 70% | 80% |
| 22:00 | 73% | 82% |
| 23:00 | 77% | 84% |
| 24:00 | 80% | 87% |
| 25:00 | 83% | 89% |
| 26:00 | 87% | 91% |
| 27:00 | 90% | 93% |
| 28:00 | 93% | 96% |
| 29:00 | 97% | 98% |
| 30:00 | 100% | 100% |
Look at what happens after the fast phase. From 3:00 to 30:00 the smart bar crawls, moving about 2.2% per minute where a standard bar moves 3.3%. It borrows speed from the middle and the end and spends it at the start. That's the whole design: a slower-looking middle in exchange for a lighter-looking opening, on the theory that the opening is where cold viewers decide whether to stay.
Set the fast phase to cover the stretch where your retention graph drops fastest early on, rather than picking a round number. Fill too much too early and the crawl that follows gets slow enough to notice. Read your own curve first: how to read a retention graph.
In RevvyScales the smart progress bar is a per-VSL setting with those two controls: how many seconds the fast phase lasts and how far it fills (VSL settings).
What research says about progress bars and perceived time
Two lines of research are relevant, and neither studied sales videos.
Human-computer interaction. Chris Harrison and colleagues ran an experiment on how people perceive different progress bar behaviors, presented at the ACM UIST conference in 2007, and used it to classify behaviors that make a process feel faster or slower (Rethinking the Progress Bar). A 2010 follow-up at CHI by Harrison, Yeo and Hudson extended the work from motion to visual styling, comparing perceived duration against a plain solid bar (Faster Progress Bars). The lesson: how a bar moves and looks changes how long a wait feels. But those studies measured waits for a computer task, not a choice to keep watching.
Web surveys. This is the closer match, because finishing a survey, like watching a VSL, is voluntary and quitting takes one click. A 2013 meta-analysis by Villar, Callegaro and Yang pooled 32 randomized experiments on progress indicators (Social Science Computer Review):
What 32 web-survey experiments found
Villar, Callegaro and Yang (2013), drop-offs by type of progress indicator
No significant reductionConstant-speed indicators
Did not significantly reduce drop-offs overall.
Fewer drop-offsFast-to-slow indicators
Move quickly on the first screens and slow down toward the end. They reduced drop-offs.
More drop-offsSlow-to-fast indicators
Increased drop-offs.
The authors' tentative explanation will sound familiar: a fast early indicator may give respondents the impression that they've already completed a large part, and that early sense of progress makes them less likely to quit.
They also flagged the catch. In their discussion, they called the fast-to-slow design questionable in its ethics because it's deceptive: it distorts actual progress on purpose. That's the honest summary: the pattern a smart bar uses has evidence behind it in a related setting, and the researchers who pooled that evidence raised an ethical flag about it. For a VSL, treat it as a reason to test, not a promise that it will work on your traffic.
Is a fake progress bar deceptive?
It can be. A progress bar is a statement about the video, so the question is whether viewers end up believing something false that matters to their decision. The FTC's 2022 staff report on dark patterns describes them as design practices that trick or manipulate users into choices they wouldn't otherwise make, and one of its categories is design elements that induce false beliefs (Bringing Dark Patterns to Light). A bar built to make people believe a long video is short belongs in that conversation.
Use these lines to keep a non-linear bar honest:
- State the real runtime. Put it on the page, near the video or in the FAQ, for example "Watch the full 28-minute presentation". Viewers who care about length can know it.
- Never pair the bar with time claims. No "this short video", "only a few minutes left" or "almost done" in the video, the headline or the ads. That turns a design choice into a false statement.
- Never show a clock built from the bar. No timestamps, remaining-time counters or "75% complete" labels that don't match the real video.
- Keep the offer untouched. The bar changes how long the video feels. It must never change what viewers believe about the price, the terms or the guarantee.
- Watch the guardrails. If refunds, chargebacks or complaints rise after a bar change, treat that as a signal, even if revenue went up.
Beyond ethics, deception is expensive: misled buyers ask for refunds, file chargebacks and complain in public, and none of that shows up on day one of a test. This isn't legal advice; for the basics, see VSL compliance.
Should you hide the seek bar on a VSL?
Hiding the seek bar is a separate decision from how the bar looks. It's about control, not perception.
- Reasons to hide it: viewers can't skip to the price before the argument, can't drag to the end to check the length, and your retention graph reflects real watching instead of jumps.
- Reasons to keep it: viewers can rewind a point they missed, skeptical buyers feel in control, and audiences such as B2B buyers or warm subscribers expect it.
- What never to hide: pause, volume and captions. WCAG success criterion 2.2.2 (Level A) asks for a way to pause moving content that starts automatically and lasts more than five seconds, and the W3C lists synchronized media among its examples (Understanding 2.2.2). Taking away pause isn't a conversion tactic; it's a barrier.
A decision rule: hide seeking on long VSLs for cold traffic if a test supports it, and keep it on short VSLs, warm traffic and anything sold on a call. Returning viewers lose little either way if your player resumes them where they stopped. In RevvyScales, hiding the seek bar is a per-VSL setting, and returning viewers resume from the deepest point they watched.
How to A/B test your VSL progress bar
Five steps, in order:
A clean progress bar test
- Change one thingBar type only: same video, same page, same pitch second.
- Split by visitor, and keep it stickyEach visitor sees one version on every visit, or returning viewers contaminate both arms.
- Run full weeksSo weekday and weekend visitors are both represented.
- Pick metrics in advancePrimary: revenue per visitor. Secondary: pitch reach. Guardrails: refund rate and complaints.
- Don't call it on pitch reach alonePitch reach settles faster than revenue, and it's revenue that pays.
A worked example: you split 12,000 visitors evenly between a standard bar and a smart bar. Pitch reach is 24% (1,440 of 6,000) with the standard bar and 27% (1,620 of 6,000) with the smart bar. A two-proportion test puts that gap well past 95% confidence (z is about 3.8). Revenue per visitor is $1.90 against $1.98, a smaller and noisier gap, so you keep the test running until revenue gives a clear answer, and you check refunds 30 days out before you decide.
If the smart bar lifts pitch reach but not revenue, it's bringing more viewers to the pitch without convincing more of them. Call that a draw, and a draw goes to the simpler, more transparent option.
In RevvyScales the practical setup is two versions of the VSL, same video and different bar settings, in one folder split 50/50. Folders assign each new visitor to one VSL and keep them there (folders and A/B testing). Sample sizes and stopping rules are covered in VSL A/B testing.
Which progress bar should you use?
These are starting points, not rules. Your retention graph and your test results outrank them. Pick your traffic or situation to find yours:
Which progress bar should you start with?
Starting points by traffic and situation, each with what to test it against
Which describes your traffic or situation?
How long is the VSL?
Best fit
A smart bar, seek hidden, runtime stated
Cold paid social and a VSL over 20 minutes. Test against: a standard bar, seek hidden. Why: early commitment is the risk.
Best fit
A standard bar
Cold traffic and a VSL under 10 minutes. Test against: seek hidden. Why: length isn't scary.
Best fit
A standard bar with seeking
A warm list or retargeting. Test against: seek hidden. Why: they know you; control builds trust.
Best fit
A standard bar with seeking
B2B, high-ticket or VSL-to-call. Test against: rarely worth testing. Why: skeptical buyers want control.
Best fit
A standard bar
Health or money offers under close scrutiny. Test against: seek hidden. Why: avoid anything that reads as misleading.
Speed is the other lever on how long a VSL feels; see the VSL playback speed guide.
A progress bar checklist before launch
Tick these off before the VSL goes live; the ticks stay in this browser:
A progress bar checklist before launch
0 of 7 done
Frequently asked questions
What is a fake progress bar on a sales video?
It's the nickname marketers give a non-linear progress bar: one that fills faster in the first part of the video and slower later, so a long video looks shorter at the start. It still reaches 100% at the true end. Whether it's deceptive depends on use. Paired with an honest runtime and no false time claims, it's a pacing design; paired with a 'short video' claim, it misleads.
Does hiding the progress bar increase conversions?
Sometimes, and sometimes it costs you. Hiding the bar stops viewers from skipping to the price or checking the length, which can keep more of them inside the argument. It also removes control, and some viewers leave when they can't tell how long is left. The only reliable answer is a split test on your own traffic, judged by revenue per visitor rather than watch time.
Is a non-linear progress bar legal?
This isn't legal advice. Legal risk in advertising comes from deception: what viewers end up believing and whether it matters to their purchase. A bar that changes pacing, with the true runtime disclosed and no false claims about length, is very different from one used to back up a false 'short video' claim. Keep your claims true and your offer terms clear, and check the FTC's guidance and your local rules.
Should viewers be able to skip ahead in a VSL?
On a long VSL for cold traffic, hiding seeking keeps the argument in order and stops viewers from judging the price without context. On short videos, warm audiences and B2B or high-ticket offers, letting viewers skip costs little and earns trust. Whatever you choose, never remove pause, volume or captions, and let returning viewers resume where they stopped.
How long should the fast phase of a smart progress bar be?
Long enough to cover the stretch where your retention graph drops fastest at the start, which you find by reading your own graph rather than picking a round number. Fill too much too early and the bar crawls for the rest of the video, which can feel worse in the middle. Test two settings against each other rather than guessing.
Does the progress bar matter for returning viewers?
Less than for first-time viewers. A returning viewer who resumes mid-video already knows roughly how long it is, and they came back by choice. What matters for them is resuming at the right point and finding the offer quickly once they reach it. Judge bar tests on first-time visitors if your analytics can separate them, since that's where the bar does its work.
Sources
- Where Am I? A Meta-Analysis of Experiments on the Effects of Progress Indicators for Web Surveys — Social Science Computer Review (2013)
- Rethinking the Progress Bar (UIST 2007) — Chris Harrison
- Faster Progress Bars: Manipulating Perceived Duration with Visual Augmentations (CHI 2010) — Future Interfaces Group
- Bringing Dark Patterns to Light (2022) — FTC
- Understanding Success Criterion 2.2.2: Pause, Stop, Hide — W3C