There is no single CSS fix for a white strip in a Chrome full-page screenshot: first check whether the band is present on the page, then compare Chrome’s built-in full-size screenshot with your usual capture. If it appears in both, inspect the layout and painted edges; if it appears only in a stitched capture, investigate that capture path before changing the page.
1. Make a reliable reference screenshot
- Open the page in Chrome and open DevTools.
- Enable the device toolbar if needed.
- In DevTools, open More options and choose Capture a full size screenshot.
Chrome documents this command as capturing the whole page, including content outside the current viewport. Use its result as a comparison with the screenshot that shows the strip. Chrome DevTools: Capture a screenshot.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
The 138 Best Chrome Extensions | $2.99 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
2. Find out whether the strip belongs to the page
Inspect the boundary in the browser
Scroll to the same section boundary in the rendered page. In DevTools’ Elements panel, inspect the adjoining elements and compare their backgrounds and computed box edges. Check whether the white area is genuinely visible between the elements or appears only in the saved image. This comparison helps locate the issue; the precise cause depends on the page and capture method.
Compare the two screenshots
Check whether the band appears in the DevTools full-size capture as well as your normal capture, and whether it aligns with a DOM boundary or a join between captured regions. If only the other capture has the strip, the evidence points toward differences in that capture path, but does not by itself establish that a particular extension or screenshot tool caused it.
#1 Best Overall
3. Check for real CSS spacing
When the band is visible in the page or both captures, inspect the layout around the boundary before changing CSS. Look at:
gapandrow-gapon grid, flex, or multi-column layouts;- margins and padding on the adjoining sections and their children;
- grid or flex track sizes and alignment, including distributed alignment that can add space;
- section heights and backgrounds, to see whether the white area is an intentional or exposed part of the layout.
The CSS gap property creates space between rows and columns. The visible separation can also be affected by margins, padding, and alignment, so reducing gap alone may not remove the band. See MDN: gap.
If inspection confirms an unintended gap, correct the specific spacing or sizing rule responsible. Avoid applying a blanket negative margin or overlap: it can conceal one seam while causing content to overlap elsewhere.
4. Check fractional edges before assuming a Chrome bug
A narrow, specific paint-rounding case is documented in Chromium’s source history: a fractional parent size combined with a border width floored during painting could leave a one-pixel gap between the parent border and a child’s background. This is a possible mechanism, not a general explanation for every white strip. Chromium change, “Snap Border, Outline, and Column-Rule Widths before Layout” (October 18, 2022).
If the seam is very thin, inspect the adjoining dimensions, borders, transforms, browser zoom, and device scaling for fractional CSS-pixel boundaries. Change only a geometry value that matches what you observe, then verify the result at the affected zoom or device scale. The cited Chromium change does not establish that your page has this condition or that a particular Chrome version is at fault.
5. Use Rendering diagnostics to observe, not repair
When the boundary is hard to explain, open DevTools’ Rendering panel and use the available overlays to examine browser behavior:
- Paint flashing highlights areas that repaint.
- Layout Shift Regions highlights layout shifts.
- Layer Borders displays layer and tile outlines.
- Scrolling Performance Issues highlights potentially problematic scrolling listeners.
These are diagnostic visualizations, not commands that remove screenshot seams. Chrome describes them in Discover issues with rendering performance.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors6. For automated captures, compare the capture parameters
If you capture through automation, Chrome DevTools Protocol’s Page.captureScreenshot method includes a captureBeyondViewport option and supports clipping to a region. Compare your automation settings with the DevTools full-size reference, especially if the strip aligns with a capture boundary. Those parameters provide a way to investigate the workflow; they do not prove that automation caused a given seam. See the DevTools Protocol Page documentation.
7. Fix only the cause you have confirmed
- If the gap is present in the rendered layout, adjust the responsible gap, margin, padding, alignment, or section sizing.
- If evidence points to fractional paint geometry, test a small geometry change on the actual page and verify it at the affected scale.
- If the strip appears only in one capture path, compare its settings and output against DevTools’ full-size screenshot before editing page CSS.
Without the page URL, DOM, CSS, Chrome version, and capture method, the exact cause cannot be identified from the symptom alone.
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server for developers. One GET request can return an image or PDF; its cleanup options remove cookie banners, newsletter popups, and chat widgets before capture. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers identify the page verdict and billing status. Its MCP server lets AI agents take screenshots, and the free plan includes 1,000 screenshots a month without a card; paid plans start at $5 for 3,000.
For request options and response details, see the ScreenshotNeo documentation. Example using cURL:
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpReplace the target URL with the page you want to capture. Sign up for 1,000 free screenshots a month, with no card required.
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.
