How to Capture a Full-Page Screenshot with Screenshot.rocks
Screenshot.rocks captures the first screen online. For a full-page image, use your browser’s built-in capture, then edit the result if needed.
Short answer: Screenshot.rocks’ online website capture makes an image of the first screen, not the entire scrolling page. To capture a full page, use your browser’s built-in screenshot feature. You can then import the image into Screenshot.rocks’ editor to crop it, add a frame, or set a background. Screenshot.rocks’ capture tool and its editor serve different steps in that workflow.
Choose the right capture method
Use the browser capture command when you need the whole scrolling page, a page behind a login, a local or staging page, or a particular page state. Screenshot.rocks says its online capture is for public pages, cannot access content behind a login or localhost, and may not capture sites that block automated browsers. Its browser extension captures the visible portion of the current tab; it is not the full-page method.
| Need | Use | Output or limit |
|---|---|---|
| Entire scrolling page on desktop | Browser’s full-page screenshot command | Usually an image; browser height limits can apply |
| First screen of a public page in a framed mockup | Screenshot.rocks online capture | Desktop or mobile layout with frame/background export |
| Visible portion of the current tab | Screenshot.rocks browser extension | Opens the visible-area image in its editor |
| Full Safari page on iPhone or iPad | Safari screenshot, then Full Page | Saved to Files as PDF |
Screenshot.rocks lists its online capture dimensions as 1440 × 800 at 2× density for desktop (2880 × 1600 pixels) and 375 × 812 at 3× density for mobile (1125 × 2436 pixels). Those are that tool’s stated dimensions, not universal browser screenshot sizes.
Capture a full page in Chrome
- Open the page you want to capture.
- Open DevTools: press F12, or Command+Option+I on Mac.
- Open the Command Menu with Ctrl+Shift+P on Windows or Linux, or Command+Shift+P on Mac. See Chrome’s Command Menu documentation.
- Type
screenshot, then choose Capture full size screenshot. - Chrome saves the PNG to your Downloads folder.
If the command is missing, check that DevTools is open and use the DevTools Command Menu rather than the browser’s address bar. Chrome’s menu labels can vary across versions.
Capture a full page in Firefox
- Open the page.
- Right-click an empty area and choose Take Screenshot, or press Ctrl+Shift+S (Windows/Linux) or Command+Shift+S (Mac).
- Choose Save full page.
- Choose to download the image or copy it. The available controls are described in Mozilla’s screenshot help.
Capture a full page in Microsoft Edge
- Open the page to capture.
- Press Ctrl+Shift+S (Windows) or Command+Shift+S (Mac), or open the three-dot menu and choose Screenshot.
- Choose Capture full page.
- Save or copy the result.
If your version labels the command differently, look in the browser’s screenshot or web-capture menu.
Capture a full page in Safari on Mac
- In Safari Settings → Advanced, enable Show features for web developers. In some versions this is labeled Show Develop menu in menu bar.
- Open Web Inspector with Command+Option+I.
- In the Elements panel, find the top-level
<html>entry. - Right-click it and choose Capture Screenshot.
The option is in Web Inspector’s Elements panel. Selecting a nested element or the wrong panel can make it hard to find.
Capture a full page on a phone or tablet
iPhone and iPad
- Open the page in Safari and take a normal screenshot.
- Tap the screenshot preview before it disappears.
- Select Full Page.
- Save the result to Files.
Safari’s full-page capture on iPhone and iPad saves as a PDF, not an image. If you specifically need a PNG or JPEG, capture from a desktop browser. You can use desktop DevTools’ device mode to set a mobile viewport, though the result is still a desktop browser capture.
Android
- Take a normal screenshot while viewing the page.
- Tap Capture more or your phone’s scrolling-capture control.
- Extend the capture through the part of the page you need, then save it.
Names and availability vary by phone. Samsung calls its option Scroll capture. If your phone does not offer a scrolling capture, use a desktop browser’s full-page feature.
Get a complete and readable capture
- Make lazy-loaded content appear: Slowly scroll to the bottom and back to the top before capturing. Some pages load images only as they enter view.
- Remove overlays: Dismiss cookie banners and other overlays first. If a page element still blocks the content, you can select it in DevTools’ Elements panel and delete it. That change lasts only until reload.
- Improve sharpness: Capture quality depends on display resolution. In Chrome DevTools device mode, set the device pixel ratio to 2 for a sharper capture.
- Work around height limits: Browsers limit the height of a single image. If capture fails or cuts off, capture the page in sections or capture only the relevant part.
- Keep a very tall image readable: A full page can be many times taller than it is wide. Crop to the section readers need, or put the full image on a tall canvas such as 9:16.
- Check the page state: Wait for the page to finish loading and make sure it is showing the content, viewport, and state you want before starting the capture.
Use the Screenshot.rocks editor after capture
The editor is a post-capture step: make the browser-native full-page image first, then drop it into Screenshot.rocks if you want to crop it, add a frame, or set a background. The online capture is more appropriate when a first-screen browser mockup is all you need. Screenshot.rocks says its online capture is returned to your browser and is not stored on its server.
Or skip the browser setup
For a full-page capture from an API, ScreenshotNeo provides a single GET request. The call below requests a full-page WebP; see the ScreenshotNeo API documentation for authentication and 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 \
-d format=webp \
-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",
"format": "webp",
},
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',
format: 'webp',
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const fs = await import('node:fs/promises');
await fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer()));
Cookie banners, popups, and chat widgets are removed before the shot. Bot checks, blank pages, failed loads, and cache hits are never billed, and response headers report the page verdict and billing status. An MCP server lets AI agents use screenshot tools. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots. Learn about ScreenshotNeo, or sign up free for 1,000 screenshots a month, no card required.
Troubleshooting
| Problem | Likely cause | Fix |
|---|---|---|
| Images are missing | The page loads images only as they approach the viewport. | Scroll slowly to the bottom and back up, wait for images to load, then capture again. |
| A cookie banner or sticky header covers content | The overlay is still present at capture time. | Dismiss it first. For a temporary change, remove the obstructive element in DevTools’ Elements panel; reload restores it. |
| Text looks blurry | The display or capture pixel density is low. | Use Chrome DevTools device mode and set device pixel ratio to 2. |
| The result is cut off or capture fails | The page exceeds the browser’s maximum image height. | Capture sections or just the needed region. |
| The full page is too small to read | The page’s portrait aspect ratio shrinks it when fitted to a normal canvas. | Crop to the relevant section or use a tall canvas such as 9:16. |
| Safari has no Capture Screenshot command | Web developer features are not enabled, or the wrong Elements node is selected. | Enable developer features in Safari Advanced settings, open Web Inspector, and right-click the top-level <html> node. |
| Phone capture saves a PDF | That is the output of Safari’s Full Page screenshot on iPhone or iPad. | Use a desktop browser if you need an image file. |
Frequently asked questions
Does Screenshot.rocks capture an entire webpage?
Its online website capture makes a first-screen image. Use your browser’s full-page screenshot command for the entire scrolling page.
Can Screenshot.rocks capture a page behind a login or on localhost?
Its online capture cannot access logged-in content or localhost. Use the browser on the machine where you can open that page.
Why is my iPhone full-page screenshot a PDF?
Safari’s Full Page screenshot route on iPhone and iPad saves to Files as a PDF. Use a desktop browser capture when an image is required.
Can I add a frame to a browser full-page screenshot?
Yes. Capture the page in the browser first, then import that image into Screenshot.rocks’ editor for framing, a background, or cropping.


