Screenshot.rocks Screenshot Is Cut Off: Full-Page Capture Fixes
If a Screenshot.rocks screenshot shows only the visible tab, use your browser’s full-page capture. Here are the browser steps and fixes for missing or clipped content.
If your Screenshot.rocks screenshot is cut off at the bottom, it may be capturing only the visible browser tab. The Screenshot.rocks extension captures the visible tab; use your browser’s built-in full-page screenshot command to capture the whole document. In Chrome, open DevTools, press Ctrl+Shift+P (Mac: Command+Shift+P), search for Capture full size screenshot, and select it. Chrome saves a PNG to Downloads. Screenshot.rocks’ full-page screenshot guide documents the browser steps and common fixes.
A visible-area screenshot contains what fits in the current viewport. A full-page capture extends down the page. They are different capture modes, so changing the editor’s crop or frame cannot restore page content that was never captured. If you only need a section, capture that section; if the page is extremely tall, split it into multiple captures.
1. Capture the full page in Chrome
- Open the page you want to capture and wait for its initial content to finish loading.
- Open DevTools with F12 (Mac: Option+Command+I).
- Open the Command Menu with Ctrl+Shift+P (Mac: Command+Shift+P).
- Type
screenshotand choose Capture full size screenshot. Avoid the ordinary screenshot command if you need content below the viewport. - Find the resulting PNG in Downloads. Open it and check the top, middle, and bottom before using it.
- If the page uses lazy-loaded images, scroll slowly to the bottom and back to the top, then repeat the capture.
To capture one element rather than the document, select it in DevTools’ Elements panel, open the Command Menu, and choose Capture node screenshot. This is useful when the page contains a long feed or unrelated surrounding content.
2. Use the full-page command in other browsers
| Browser | Steps | Result and caveat |
|---|---|---|
| Firefox | Right-click an empty part of the page or press Ctrl+Shift+S (Mac: Command+Shift+S), then choose Save full page. | Save or copy the capture. In the Web Console, the command :screenshot page.png --fullpage also saves a full-page PNG to Downloads. See Mozilla’s Firefox documentation. |
| Microsoft Edge | Press Ctrl+Shift+S, or open the three-dot menu, choose Screenshot, then Capture full page. | Use the full-page choice rather than a visible-area capture. |
| Safari on Mac | Enable web developer features, open Web Inspector, find the <html> element in Elements, right-click it, and choose Capture Screenshot. |
The route requires developer features to be enabled. |
| Safari on iPhone | Take a screenshot, tap its preview, then choose Full Page. | The full-page result is a PDF. For an image, capture from a desktop browser using device mode. |
| Android | Take a screenshot and choose Capture more in the preview, then extend the capture. | Labels vary by phone; Samsung calls this Scroll capture. |
3. Fix common full-page screenshot problems
| Symptom | Likely cause | Fix |
|---|---|---|
| Only the first screen appears | The extension or operating-system screenshot captured the visible tab, not the full document. | Repeat using the browser’s full-page command. Screenshot.rocks’ extension can still open a viewport screenshot in its editor for cropping, framing, or background work, but it does not capture the rest of the page. |
| Images are blank or missing | The site loads images only when they approach the viewport. | Scroll slowly to the bottom and back to the top to trigger loading, wait for images to appear, then capture again. |
| A cookie banner or sticky header covers content | The overlay is part of the page while capturing. | Dismiss the banner first. If an unwanted element remains, select it in DevTools’ Elements panel and press Delete. The change lasts until reload. |
| Text looks blurry | The capture’s pixel density may be too low for the display or intended output size. | In Chrome DevTools, enable device mode, open its device options, add device pixel ratio if needed, and set DPR to 2 before capturing. This can improve sharpness but is not a guarantee for every display or browser. |
| The capture ends early or fails on a very tall page | A browser may hit a maximum single-image height or resource limit. | Capture separate sections, or capture only the specific part needed. Do not expect one image to contain an arbitrarily long page. |
| The bottom section is absent although full-page mode was selected | The content may be inside a nested scrolling area, or it may not have loaded before capture. | Scroll the inner panel itself and make sure the relevant content is visible and loaded. If the page still exceeds the browser limit, capture that region separately. |
4. Choose the right output for the job
- Whole-page PNG: use the browser’s full-page screenshot command for a document that fits within its capture limits.
- One section or element: capture the relevant node or take separate section captures. This keeps a very tall result manageable.
- Mobile full page: iPhone Safari’s Full Page mode produces a PDF. Use desktop browser device mode if you specifically need an image.
- Readable text: increase device pixel ratio when needed, then inspect the result at its intended display size.
5. Capture a page through an API instead
If you need repeatable captures in a script, build pipeline, or agent workflow, ScreenshotNeo is a website screenshot API and MCP server. It returns PNG, JPEG, WebP, or PDF from a single GET request. The request can be adjusted for full-page capture, viewport, device preset, and other capture settings; see the ScreenshotNeo API documentation for parameter names and options.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython
import requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const bytes = new Uint8Array(await res.arrayBuffer());
await (await import('node:fs/promises')).writeFile('shot.webp', bytes);Options for scripted captures
ScreenshotNeo supports full-page capture with lazy images loaded, element capture by CSS selector, dark mode, 12 device presets or a custom viewport, retina scale, PDF page settings, custom CSS and JavaScript, selector clicks and waits, hidden selectors, request and resource blocking, headers, cookies, user agent, Authorization, timezone, geolocation, transparent backgrounds, resizing, and configurable cache TTL. It also supports signed links for public image tags, asynchronous jobs with signed webhooks, bulk capture up to 100 URLs per call, a usage API, and an OpenAPI spec. Parameter names used by other screenshot APIs also work to make migration easier. The API returns X-Page-Verdict and X-Billed headers; bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed.
Or skip the browser setup
Make one GET request to capture a page as an image or PDF. Cookie banners, popups, and chat widgets are removed before the shot. Bot checks, blank pages, and failed loads are never billed. An MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the API docs for options, then sign up for 1,000 free screenshots a month, with no card required.
Performance, reliability, and cost
For a one-off capture, the browser’s built-in command avoids installing another extension. For repeated work, automate captures and use waits or selector-based capture when content appears after initial page load. Very tall pages may take longer, produce large files, or exceed a browser’s single-image limits; split them when needed. Before sharing a capture, verify that the page finished loading and that key images and lower sections are present.
ScreenshotNeo plans are Free: 1,000 shots/month with no card; Starter: $5 for 3,000; Growth: $15 for 15,000; Pro: $39 for 60,000; Scale: $99 for 250,000; and Business: $249 for 1,000,000. Yearly billing gives two months free, and every feature is on every plan. For API jobs, check the response’s billing and page-verdict headers to distinguish a clean capture from a bot check, blank page, timeout, failed load, or cache hit.
FAQ
Can I get a full-page capture without an extension?
Yes. Chrome, Firefox, Edge, and Safari include browser-level full-page capture options.
Why does iPhone Full Page save a PDF?
That is the output provided by Safari’s Full Page capture. Use desktop browser device mode when you need an image file.
Can I capture only one part of the page?
Yes. Use Chrome’s Capture node screenshot for a selected element, or capture the needed area as its own section.
Will a full-page screenshot include content in an iframe?
It captures the browser page, but a nested or independently scrolling region may need to be scrolled or captured separately. Check the resulting image before relying on it.
