An above the fold screenshot captures only the part of a web page a visitor sees before scrolling, so paste a URL below, pick desktop, tablet, or mobile, and click Capture Above the Fold to download that first screen as a PNG, JPG, or WebP. ScreenshotAPI.net renders the page in a real browser at 1680 x 867, 624 x 866, or 425 x 812 pixels with cookie banners and ads removed, free and with no signup.
Free to try. No account required.
Your above the fold screenshot will appear here.
Only the first 867 pixels of the page are captured. Nothing below the fold is included.
Above the fold is the part of a web page that is visible as soon as it loads, before any scrolling. Everything that needs a scroll to reach is below the fold.
above the fold
also written above-the-fold/ opposite below the fold
Viewport heights the tool captures at. Above the fold on mobile is the smallest of the three, and once the address bar shows it drops to about 730 px, so a phone shows one headline and one button where a laptop shows the whole hero.
What sits there
The header, the headline, the hero image or product shot, and the main call to action. It is the only part of the page every visitor sees.
What decides it
The viewport height. Screen size, browser tabs and the address bar all change it, so the same page has a different fold on a laptop and on a phone.
What it is not
A fixed number of pixels. There is no single fold, which is why this tool captures at three real viewport sizes instead of one.
The two halves of a page have different audiences and different jobs. The fold line between them is the bottom edge of the viewport, which is exactly where this tool stops capturing.
Above the fold
Visible on load. Captured by this tool.
Below the fold
Needs a scroll. Captured by the full page tool.
Who sees it
Every visitor, including the ones who leave after two seconds.
Below: Only visitors who decide the first screen was worth a scroll.
Only visitors who decide the first screen was worth a scroll.
Job
Say what the page is and give one clear next step.
Below: Prove the claim: details, proof, pricing, objections, FAQ.
Prove the claim: details, proof, pricing, objections, FAQ.
Loading
Loads first. Google measures the largest element here as LCP.
Below: Can load later. Lazy loading images here is the right default.
Can load later. Lazy loading images here is the right default.
Typical height
About 650 to 900 px, set by the device.
Below: Unlimited. Long pages often run past 5,000 px.
Unlimited. Long pages often run past 5,000 px.
Screenshot flag
full_page=false with a width and height.
Below: full_page=true, which includes the fold and everything under it.
full_page=true, which includes the fold and everything under it.
Neither half is more important. A page with a strong first screen and nothing underneath converts badly, and a long page with a weak first screen never gets read. Use this tool to judge the first screen and the full page screenshot tool to review the rest.
The first screen has to do three things: tell the visitor where they are, show them why they should care, and give them one thing to do. The checklist covers what earns a place in that space, and the short list underneath covers what usually should not.
Keep below the fold, or off the page
Visitors decide in a few seconds whether this page is for them. The headline should say what the product does and for whom, in plain words, large enough to read on a phone.
A landing page gets one button above the fold, not three. Secondary links can sit beside it in a lighter style, but the eye should land on a single next step.
A product screenshot, a short demo loop or the hero image itself. This is usually the largest element on the first screen, so it is also the element Google times for LCP.
Customer logos, a rating, a user count or a security badge. It does not need much space. A single row under the call to action is enough to answer who else uses this.
Keep the header to one row. A tall announcement bar plus a two row menu can push the headline below the fold on a laptop before the visitor has read anything.
On an article or a documentation page, the first paragraph should start above the fold. A full screen hero image with the text under it costs you readers on mobile.
Yes, but not in the way most articles suggest. Above the fold is not a keyword placement trick. It affects ranking through three real mechanisms: the page layout algorithm, Largest Contentful Paint, and whether visitors stay. Here is each common claim with a straight verdict.
How to check your own pages
Google penalises pages with too many ads above the fold
The page layout algorithm, announced in January 2012 and still part of ranking, lowers pages whose first screen is mostly ads. Content heavy pages are not affected.
Putting keywords above the fold boosts ranking
Google reads the whole document. Where a word sits on the screen does not change its weight. Write the first screen for people, not for the crawler.
The fold affects Core Web Vitals
Largest Contentful Paint measures the biggest element in the viewport, which is almost always the hero image or headline above the fold. A slow hero means a slow LCP, and LCP is part of the page experience signal.
Lazy loading images above the fold is good for SEO
Lazy loading the hero image delays the LCP element. Google's guidance is to load above the fold images eagerly and lazy load the rest. Add fetchpriority=high to the hero image.
Above the fold matters for ranking through engagement
A first screen that answers the query keeps people on the page instead of bouncing back to the results. Google does not publish how it uses that signal, but a page nobody reads rarely stays on top.
Above the fold is still relevant
People scroll more than they did in 2010, but studies still show the first screen gets several times the attention of any screen below it. The fold moved. It did not disappear.
Checking every landing page after a deploy, or comparing the first screen across devices every week? Send the same request the tool uses. full_page=false limits the capture to the viewport, and width and height place the fold. Pair it with the bulk endpoint to check hundreds of URLs in one job.
full_pagewidth / heightno_cookie_banners / block_adsretinadelay / wait_for_eventCommon questions about what above the fold means, where it sits on each device, whether it affects SEO, and how to automate the capture with the ScreenshotAPI.net API.
Don't see your question here?
Browse all help articles