What to Put Above the Fold on a SaaS Homepage
The fold isn't a fixed line anymore, but the first screen still does most of the work. The four jobs of a hero section, the headline and subhead that actually convert, and whether the visual should be a screenshot, a video, or a live demo.
The fold isn't a fixed line, but the first screen a visitor sees before scrolling still does most of the work — it decides whether they scroll at all. A SaaS hero section has four jobs: say what the product does and for whom (the headline), add the how or the proof (the subhead), give one clear next action (the primary CTA), and show the actual product (the visual). A light trust signal — logos, a rating, a usage number — helps. The headline should be readable in a glance and answer "what is this and is it for me?" without leaning on the subhead. For the visual, a screenshot is clear but static; a video needs a play decision; an embedded interactive demo lets the visitor experience the product on the spot, which is the strongest option when the value is in the interaction.
"The fold" in practice
There's no universal fold because there's no universal screen. But every visitor has a first screenful, and eye-tracking and scroll-depth data consistently show it gets the most attention by a wide margin, with a steep drop after. So:
- The primary message and primary CTA go on the first screen.
- The first screen should also make it obvious there's more — a partial next section visible, a scroll cue — so people keep going.
- Don't cram. A first screen with six competing elements communicates nothing.
The four jobs of a hero
1. Headline — what and for whom
Under ten words. "Interactive product demos for sales teams" tells a visitor immediately whether to keep reading. "Reimagine how you connect with buyers" makes them work for it, and most won't.
2. Subhead — the how or the proof
One or two lines that add substance: how it works, what's different, or a concrete result. This is where a specific claim ("publish a demo in two minutes, no code") earns its place.
3. Primary CTA — one clear action
One primary button. A secondary link is fine ("or see how it works"), but two equally-weighted CTAs split attention. Match the CTA to the visitor's likely readiness — "Start free" for a self-serve product, "See a demo" for a considered purchase.
4. Visual — show the product
Not a stock illustration, not an abstract graphic. The actual interface. A visitor's real question is "what is this thing," and a picture of it answers faster than a paragraph.
Screenshot, video, or interactive demo
- Screenshot — loads instantly, always "playing," zero interaction cost. But it's a still; the visitor can't get a feel for how it works.
- Video — shows motion and flow, but the visitor has to decide to press play, and an autoplaying hero video can read as an ad and hurt load time.
- Interactive demo — the visitor clicks through the real product in the hero, at their own pace, with no signup. It communicates more than a screenshot or a video, and it's a first experience rather than a picture of one:
Use a demo when the product's value lives in the interaction (most SaaS). Use a clean screenshot when the value is more about output than flow, or when load speed is critical.
If you use an interactive demo in the hero, keep it short — the single most important flow, five to eight steps. It's a hook, not the full tour. Link a longer demo for the visitor who wants more.
What waits for the scroll
Everything else: the feature grid, social proof in depth, the comparison, pricing, the FAQ. The hero earns the scroll; the rest of the page does the convincing.
For the full-page view, see SaaS landing page conversion; for using a demo across the site, see demo-first marketing and how to embed a demo on a website.
Frequently asked questions
Does 'above the fold' still matter?
Yes, though it is not a fixed pixel line. It is whatever a visitor sees before scrolling on their device. That first screen still gets by far the most attention and determines whether people scroll at all, so the highest-value content and the primary call to action belong there.
What should a SaaS hero section contain?
A headline that states what the product does and for whom, a subhead that adds the how or the proof, one primary call to action (and at most one secondary), a visual that shows the actual product, and a light trust signal — a customer logo row, a rating, or a usage stat. Everything else can wait for the scroll.
Should the hero visual be a screenshot, a video, or an interactive demo?
A screenshot is fast and clear but static. A video shows motion but people have to choose to play it and it can feel like an ad. An embedded interactive demo lets the visitor click through the real product immediately, which communicates more than either and doubles as a low-commitment first experience. Use a demo when the product's value is in the interaction.
How long should a hero headline be?
Short enough to read in one glance — usually under ten words. It should answer 'what is this and is it for me?' Clever or abstract headlines that require the subhead to explain them lose people who do not read the subhead.