How to Take a Full-Page Screenshot with BrowserStack Screenshots

To take a full-page screenshot with BrowserStack Screenshots, open its screenshot tool, enter the page URL, choose the browser and device configurations, adjust any relevant display or timing options, and generate the screenshots. BrowserStack says its tool captures full pages in most supported browsers, with documented exceptions: Opera and Safari 5.1 capture only the visible area before scrolling. Check the selected browser and version if an image shows only the viewport.

This is BrowserStack’s URL-based Screenshots workflow for comparing how a page renders across browser and device combinations. It is separate from taking a screenshot from a Selenium driver during an automated test.

Steps to capture the full page

1. Open BrowserStack Screenshots. Use the Screenshots web tool and provide the URL of the page you want to inspect.
2. Select browser and device configurations. Choose the combinations that matter to your users. BrowserStack’s product page says one user can generate screenshots for up to 25 combinations at once; verify the current limit in the product before planning a larger batch.
3. Review capture settings. The product page describes settings for resolution, quality, defer time, and mobile layout. Set them to match the rendering conditions you need to compare.
4. Generate the screenshots. Start the capture and review the resulting images for each selected configuration.
5. Check the full-page caveat. If an image stops at the initial viewport, check whether the selected browser is Opera or Safari 5.1. BrowserStack’s current FAQ says those configurations capture the visible area before scrolling; it does not state that every Safari version has this exception.

Browser support and product limits can change. BrowserStack’s FAQ and product page were checked for this guide on October 3, 2026; confirm the current documentation if these details affect a release or test plan.

What to do when the screenshot is not full-page

First identify whether the result is a screenshot from BrowserStack Screenshots, an API job, a Selenium test, or a Percy snapshot. These are separate workflows and the same diagnosis does not necessarily apply to each.

• BrowserStack Screenshots shows only the initial viewport: check the selected browser and version. The documented exceptions are Opera and Safari 5.1.
• You need a repeatable capture job: BrowserStack documents a Screenshots API that accepts a URL and browser, operating-system, or device configuration, then lets you retrieve job status and screenshot results. Its documentation says API access requires an Automate plan that includes browsers. Confirm your account has that access and use the current API documentation for request details and credentials.
• A Selenium test captures only the viewport: that is a code-driven browser automation workflow, not the Screenshots web tool. BrowserStack’s Selenium guide describes Firefox’s getFullPageScreenshotAs and an AShot scroll-and-stitch approach for browsers such as Chrome. Browser support varies, so follow the relevant Selenium and browser guidance.
• A Percy snapshot is clipped: BrowserStack’s Percy documentation identifies CSS overflow clipping as one possible cause and suggests finding the clipping element and resetting its overflow with Percy CSS. This advice applies to Percy snapshots, not as a guaranteed fix for BrowserStack Screenshots.

Choosing between the web tool and automation

Workflow	Use it when	Check first
BrowserStack Screenshots web tool	You want to enter a URL and compare its rendering across selected browsers and devices.	Browser and device selection, capture settings, and the Opera/Safari 5.1 full-page exception.
BrowserStack Screenshots API	You want to create screenshot jobs programmatically and retrieve their status and results.	Whether your Automate plan includes browsers; use BrowserStack’s current API docs for authentication and request fields.
Selenium screenshot in a test	You need a capture as part of code-driven browser automation.	Whether the chosen browser supports the full-page method you intend to use.
Percy snapshot	You are using Percy for visual testing and need to diagnose a clipped snapshot.	Whether CSS overflow is clipping the page content.

Use the Screenshots web tool when you need a quick URL-based comparison. Choose an API or Selenium workflow when captures must run as part of automation, and use Percy guidance only when the snapshot is from Percy. The research for this guide does not establish a head-to-head performance or price comparison among these workflows.

Or skip the browser setup

ScreenshotNeo captures a URL with one API request and returns an image or PDF. It can capture full pages and load lazy images. Cookie banners, newsletter popups, and chat widgets are removed before the shot; bot checks, blank pages, failed loads, timeouts, and cache hits are not billed. Its MCP server lets AI agents use screenshot tools, including from Claude, Cursor, and other MCP clients.

For a full-page capture, call the ScreenshotNeo API with your URL. See the API documentation for 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

ScreenshotNeo offers 1,000 screenshots per month free with no card; paid plans start at $5 for 3,000 screenshots. Sign up for free.

FAQ

Does BrowserStack Screenshots capture the whole page?

BrowserStack says it provides full-page screenshots except for Opera and Safari 5.1, which capture the visible area before scrolling.

Does the Safari limitation apply to every Safari version?

The FAQ names Safari 5.1 specifically. It does not say the same limitation applies to all Safari releases.

Can I automate BrowserStack Screenshots?

BrowserStack documents an API for creating screenshot jobs and retrieving status and results. Its documentation says the API is available on Automate plans that include browsers; confirm your plan and credentials.

Is the Screenshots API the same as Selenium?

No. The API creates BrowserStack screenshot jobs from a URL and browser or device configuration. Selenium captures are taken from a browser automation workflow, such as a test.