ScreenshotNeo

BlogHow-to

How to troubleshoot screenshots that cut off the bottom of a webpage

A screenshot that stops at the visible screen may be a viewport capture, not a failure. Learn full-page capture options and how to investigate a persistent cutoff.

By the ScreenshotNeo team4 October 20265 min read

A screenshot that ends at the bottom of the visible browser window may be working as designed: it may capture only the viewport. To capture content below the screen, choose a full-page or entire-page screenshot option. If that result still cuts off, the cause depends on your browser, device, capture method, and the page; there is no single confirmed fix for every setup.

1. Check whether you need a viewport or full-page screenshot

A viewport screenshot records the part of the page currently visible in the window. A full-page screenshot is intended to include content beyond that window. Firefox explicitly offers separate options to save the visible part or the full page, so a viewport-sized image can be expected behavior rather than an error. Mozilla’s Firefox screenshot guide describes both choices.

Before changing settings, check the saved image’s dimensions and compare its bottom edge with the browser viewport. If it ends at roughly the visible window height, check that you selected a full-page capture rather than a visible-area one.

2. Use Firefox’s built-in full-page capture

  1. Open the page you want to capture.
  2. Right-click an empty area of the page and choose Take Screenshot. Alternatively, press Ctrl+Shift+S on Windows or Linux, or Command+Shift+S on macOS.
  3. Choose Save full page to capture beyond the visible area. Choose Save visible only when you want the current viewport.
  4. Save the image or copy it if that is the option you need, then inspect the bottom of the result.

The exact interface can vary by Firefox version and platform. If the menu or shortcut differs, check Mozilla’s current support instructions for your release.

3. Capture the entire page from Firefox Developer Tools

Firefox Developer Tools provide another documented route. The screenshot button may need to be enabled first.

  1. Open Developer Tools and go to Settings.
  2. Under Available Toolbox Buttons, enable Take a screenshot of the entire page.
  3. Use the screenshot button in the toolbox and inspect the saved capture.

Firefox also documents a Web Console screenshot helper. Enter :screenshot --fullpage in the Web Console to capture page portions outside the current window bounds. See Firefox Source Docs: Taking screenshots for the Developer Tools options and additional screenshot arguments.

4. Capture a full webpage on iPhone

Apple’s iPhone guide documents a Full Page option in the screenshot workflow, with capturing an entire webpage in Safari as an example:

  1. Take a screenshot while viewing the webpage.
  2. If the screenshot thumbnail appears, tap it to open the screenshot editor.
  3. Choose Full Page, then save the result using the available controls.

Apple’s instructions are for the iPhone guide for iOS 27; controls may differ on other versions. See Apple Support: Take a screenshot on iPhone.

5. If the bottom is still missing

The browser and device are not specified here, and the available documented methods do not establish a universal cause or fix for persistent cutoffs. Gather these details before diagnosing further:

  • Browser name and version, or device model and operating system version.
  • The capture method and whether you explicitly chose a full-page option.
  • The page URL, if it is safe to share.
  • Where the saved image ends: at the viewport boundary, at a particular section, or after a blank region.
  • Whether the same page ends at the same point when captured through a second documented full-page workflow available on your platform.

Save the result and inspect the actual image, rather than relying only on its preview. Comparing another documented workflow is a troubleshooting step; it does not by itself identify the cause. Avoid assuming that page length, lazy-loaded content, or a particular browser bug is responsible without evidence from the affected setup.

6. Choose the capture method that fits

Method Best for What to check
Firefox screenshot menu Quick visible-area or full-page capture Select Save full page for content beyond the viewport.
Firefox Developer Tools button Capturing an entire page from the toolbox Enable the screenshot button in toolbox settings if it is missing.
Firefox Web Console A command-based full-page capture Use the documented :screenshot --fullpage helper.
iPhone screenshot workflow A full-page capture on iPhone, such as a Safari webpage Open the screenshot editor and select Full Page.

These instructions cover the methods verified in the cited documentation. They do not establish current steps for Chrome, Edge, Android, or macOS Safari.

7. Or skip the browser setup

If you need a repeatable capture from code, ScreenshotNeo is a website screenshot API and MCP server. One GET request can return an image or PDF. For full-page capture, pass full_page=true as an option; the API also supports waiting for a selector, delay, or network idle, which can help when a page needs time before capture. See the ScreenshotNeo documentation for request options.

curl -G "https://api.screenshotneo.com/v1/shot" \
  -d access_key=YOUR_API_KEY \
  --data-urlencode url=https://stripe.com \
  -d full_page=true \
  -o shot.webp
import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={
        "access_key": "YOUR_API_KEY",
        "url": "https://stripe.com",
        "full_page": "true",
    },
    timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)
const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://stripe.com',
  full_page: 'true',
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const image = Buffer.from(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', image));

ScreenshotNeo removes known cookie and consent banners, newsletter popups, and chat widgets before capture. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed; response headers identify the page verdict and billing status. Its MCP server lets AI agents use screenshot tools. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots. Sign up for 1,000 free screenshots a month, with no card required.

8. Common questions

Why does my screenshot stop exactly at the browser window?

It may be a visible-area screenshot. Select the browser’s full-page option when you need content below the viewport.

Does a full-page screenshot guarantee every page will fit in one image?

The cited instructions describe full-page capture, but they do not promise a universal result for every page or setup. If content is missing, record the browser, device, method, and cutoff location before looking for a specific cause.

Where are the Chrome and Android steps?

The research sources used for this guide do not verify full-page capture instructions for Chrome or Android. Check the documentation for your exact browser and operating system version.