Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Nightwatch’s built-in screenshot commands do not document a full-document-height option. When Nightwatch runs on BrowserStack Automate, that remote setup does not add one. BrowserStack documents full-page web captures through Percy, using the fullPage option—but this is a Percy capture path, not a Nightwatch screenshot setting, and the documentation does not provide a Nightwatch-specific integration recipe. If you need the exact page state in an active Nightwatch test, use its regular screenshot command and treat the result as a current-page capture; if you need a full-page snapshot, verify that Percy’s supported client and your test setup work together.
What “full-height” means in this workflow
A full-height or full-page screenshot covers the document beyond the portion currently visible in the browser viewport. That is different from a viewport screenshot, which records only the visible browser area. It is also different from a screenshot of one element: Nightwatch’s element screenshot command captures the visible region within that element’s bounding rectangle, not the whole document.
There are two distinct paths to keep straight:
- Nightwatch screenshot commands: capture the current page, without a documented full-document-height parameter. See the Nightwatch screenshot API and saveScreenshot API.
- BrowserStack Percy with Automate: BrowserStack documents a full-page web snapshot option,
fullPage: true. This is a Percy feature. The Percy full-page screenshot documentation includes language examples, but does not specifically show a Nightwatch call.
Consequently, do not expect a Nightwatch test to become full-page merely because it runs remotely on BrowserStack. Choose the capture path based on whether you need the active test session’s state or a Percy snapshot, and verify the integration before relying on it in a suite.
Capture the current Nightwatch page
Use Nightwatch’s saveScreenshot() when a viewport capture from the current browser session is sufficient. This JavaScript test opens a page, saves a PNG, and ends the session:
#1 Best Overall
module.exports = {
'save a current-page screenshot': async function (browser) {
await browser.url('https://example.com');
await browser.saveScreenshot('./artifacts/page.png');
await browser.end();
}
};This example demonstrates the Nightwatch command, not a full-height capture. The file path is where the test runner writes the screenshot; make sure the directory exists or is created by your project’s test setup. Nightwatch also documents .screenshot() as a current-page screenshot command. For a targeted visual check, .element(selector).takeScreenshot() is limited to the visible part inside the element’s bounding rectangle. Neither API should be treated as a documented full-page mode.
Run Nightwatch remotely on BrowserStack Automate
BrowserStack’s Nightwatch integration documentation explains how to configure a Nightwatch suite to use Automate’s remote WebDriver service and credentials. Follow the configuration for your project and installed Nightwatch version in the BrowserStack Nightwatch integration guide. Keep credentials in environment variables or another secret-management mechanism rather than committing them to the test file.
Once the test is connected, the ordinary Nightwatch screenshot command remains a current-page capture. Remote execution changes where the browser runs; it does not document a new full-height screenshot parameter. BrowserStack’s debugging options describe Nightwatch-compatible debugging configuration and visual logs, which can help inspect a failing run, but they are not a full-page capture switch.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallUse Percy for a documented full-page web snapshot
BrowserStack’s documented full-page option belongs to Percy. Its screenshot documentation identifies fullPage as the option for capturing the full webpage. BrowserStack provides examples for Java, JavaScript, .NET, and Python, but does not specifically document how to call that option from Nightwatch or establish that every Percy client can attach to a Nightwatch Automate session.
Rank #2
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
For that reason, avoid copying a generic Percy example into a Nightwatch test and assuming it will capture the exact active session. Instead:
- Confirm which Percy client/library and Automate integration you intend to use, and follow that client’s supported setup.
- Verify in the relevant Percy documentation that the client can capture the browser/session arrangement used by your Nightwatch suite.
- Use Percy’s documented
fullPage: trueoption in the supported screenshot call. Do not substitute it for Nightwatch’ssaveScreenshot()and assume the Nightwatch API recognizes it. - Run a small test against a page with content below the fold. Inspect the resulting snapshot and confirm that it includes the document area you expected before enabling it across a larger suite.
The distinction matters operationally: Nightwatch’s documented commands save screenshots of the current page, while Percy’s full-page option produces a Percy snapshot. If your requirement is a screenshot artifact from the same live browser state in which assertions ran, establish that the chosen Percy integration preserves that relationship; the cited BrowserStack docs do not provide a Nightwatch-specific recipe to guarantee it.
Know the Percy full-page limits
BrowserStack documents different caps for desktop and mobile Percy web captures. These are Percy product limits, not general browser limits:
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →| Capture category | Documented maximum | Source and qualification |
|---|---|---|
| Desktop web page | 10,000 pixels or 10 tiles, whichever is lower | BrowserStack Percy full-page screenshot documentation, accessed 2026 |
| Mobile web page | 10 tiles | BrowserStack Percy full-page screenshot documentation, accessed 2026 |
A page can therefore extend beyond the captured portion even when the full-page option is enabled. Check the resulting snapshot against the documented cap if a very long page is involved; do not assume that full-page means unlimited height.
Rank #3
Prepare the page so the capture is representative
Full-page capture depends on the state of the page when the capture is taken. BrowserStack notes that dynamic content and lazy loading can affect Percy snapshots, and users need to handle popups and dynamic elements. Before capturing, make the page stable and ensure the content you want exists in the rendered document.
Wait for meaningful readiness
Navigation completing does not necessarily mean that every image, client-rendered section, or asynchronous widget has finished. Wait for a page-specific selector or another reliable readiness condition before snapshotting. Use the appropriate wait mechanism for the Nightwatch test and the chosen Percy client; do not add an arbitrary short pause and assume it covers every network or rendering delay.
Trigger lazy-loaded content
Some pages load images or sections only when they approach the viewport. If the snapshot omits lower-page content, scroll through the page before capture so those areas have an opportunity to load, then verify the result. Scrolling is a preparation step, not a guarantee: the site may use its own loading thresholds or asynchronous behavior.
Control moving content and overlays
Pause or disable animations, video, and carousels when the test allows it, so capture timing does not change the visual result. Close or dismiss cookie banners, dialogs, and other popups when they obscure the content being checked. Handle those elements deliberately in the test rather than assuming the screenshot product will remove them.
Investigate clipping
If a Percy snapshot still stops at the viewport, inspect the page for CSS overflow rules that clip the content. BrowserStack’s Percy troubleshooting guidance explains that overflow clipping can limit a snapshot and describes using Percy CSS to reset the specific rule. Apply an adjustment narrowly to the element responsible; a broad CSS override can change layout and make the snapshot less representative.
Rank #4
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
Do not confuse the other BrowserStack capture products
BrowserStack offers other screenshot-related products, but their documented behavior does not establish a full-page Nightwatch capture in the active Automate session.
- BrowserStack Screenshots API: this is a separate authenticated, URL-based screenshot service with browser and operating-system selection. The Screenshots API documentation does not establish that it captures the active Nightwatch session or supplies full-page behavior for that session.
- BrowserStack Screenshots product: its FAQ says captures are viewport-only for Opera and Safari 5.1. That qualification applies to the Screenshots product FAQ; it should not be generalized to Percy or Nightwatch. See BrowserStack’s screenshot FAQ.
- App Percy: this is a separate mobile-app facility, described as beta, with a scroll-and-stitch approach and a maximum of 10 screen lengths. Its documentation is Appium-oriented, not the Nightwatch web capture flow described here. See App Percy full-page documentation.
When comparing approaches, check four things: whether capture uses the active test session or a URL, whether it includes the document or only the viewport, the product’s height/tile cap, and how it handles lazy-loaded or changing content.
Or skip the browser setup
If you need a screenshot of a URL rather than a capture tied to Nightwatch’s active test session, ScreenshotNeo offers a one-request screenshot API. It accepts a URL and returns PNG, JPEG, WebP, or PDF output. This is a separate URL-based capture, so it is not a replacement for verifying state that exists only inside your running Nightwatch session.
For API details and supported parameters, see the ScreenshotNeo documentation. Example cURL request:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpThe same request in Python:
import requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={"access_key": "YOUR_API_KEY", "url": "https://example.com"},
timeout=90,
)
open("shot.webp", "wb").write(r.content)Or in Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);- Cookie and consent banners are accepted and removed before the shot; newsletter popups and chat widgets from more than 60 known platforms are removed. Each cleanup step can be turned off.
- Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed. Response headers report the page verdict and billing status.
- An MCP server provides
take_screenshot,get_page_info, andcapture_pdftools for AI agents and MCP clients. - The Free plan includes 1,000 shots per month with no card. Paid plans start at $5 for 3,000 shots.
Sign up for ScreenshotNeo’s free plan and get 1,000 screenshots a month with no card.
Troubleshoot a screenshot that shows only the viewport
| Symptom | Likely explanation | What to check |
|---|---|---|
| Nightwatch output stops at the visible browser area | The standard Nightwatch screenshot API documents current-page capture, not full-document height. | Use Percy’s documented full-page route if it fits the integration, or treat the Nightwatch file as a viewport screenshot. |
| Percy output ends before the bottom of a long page | The desktop or mobile Percy cap may have been reached. | Compare the output with the documented 10,000-pixel/10-tile desktop cap or 10-tile mobile cap. |
| Images or sections are missing below the fold | Content may be lazy-loaded and not yet rendered. | Scroll through the page before capture, wait for the content, then inspect the snapshot. |
| Snapshot is cropped despite using fullPage | A CSS overflow rule may clip the relevant content. | Identify the clipping element and follow Percy’s guidance for a targeted CSS adjustment. |
| Different runs show different visuals | Animations, video, carousels, popups, or asynchronous content may change between captures. | Stabilize the page, control overlays, and wait for the relevant page state before snapshotting. |
| Cannot determine whether Percy captures the Nightwatch session | The cited integration pages do not give a Nightwatch-specific Percy recipe. | Confirm support for the precise Percy client and Automate setup, then validate with a small test before depending on it. |
Frequently Asked Questions
Does enabling BrowserStack Automate make Nightwatch’s screenshot full-page?
No. Automate runs the browser remotely; Nightwatch’s documented screenshot commands remain current-page captures.
Recommended Free Tools
Can BrowserStack Screenshots API capture a page from my running Nightwatch session?
The documented Screenshots API is URL-based, and its documentation does not establish capture of an active Nightwatch session.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
