Free tools Windows power users keep installed
One-click scans. No signup required.
To capture a webpage that extends below the screen, use your browser’s full-page command rather than the normal screenshot shortcut. In Microsoft Edge press Ctrl+Shift+S and choose Capture full page; in Firefox open its Screenshot tool and select the full-page option; in Chrome desktop use DevTools → Device mode → More options → Capture a full size screenshot. On an iPhone, take a screenshot in Safari, tap the preview, choose Full Page, then save the result as an image or PDF.
A standard screenshot records only the visible viewport. A scrolling, full-page screenshot captures the page content below it without requiring you to stitch separate images manually. The exact control depends on the browser and device, and labels can change between releases. The instructions below reflect the documented workflows available on September 29, 2026.
Choose the right method
| Platform or browser | Documented path | DevTools required? | Output and handling |
|---|---|---|---|
| Microsoft Edge desktop | Ctrl+Shift+S → Capture full page | No | Capture, mark up, copy or save |
| Mozilla Firefox desktop | Open the Screenshot command → Full page | No | Download the full-page image |
| Google Chrome desktop | DevTools → Device mode → More options → Capture a full size screenshot | Yes | Saves a capture including content outside the viewport |
| iPhone Safari | Take screenshot → preview → Full Page | No | Save as an image or PDF |
These are workflow differences, not a guarantee that one browser works best on every site. If a named command is missing, update the browser or check its current menu: Microsoft notes that Edge’s Screenshot availability and behavior can vary by device, market and browser version.
Microsoft Edge: capture the entire page
Use the keyboard shortcut
- Open the webpage in Edge and wait for the content you need to appear.
- Press Ctrl+Shift+S (on macOS, open Edge’s Screenshot command from the browser menu instead of using this Windows shortcut).
- Choose Capture full page. Edge captures the material below the visible viewport in one operation.
- Use the annotation or drawing controls if you need to mark the capture.
- Copy the result or save it to a file when you are finished.
Edge’s full-page feature is the least technical desktop route because it does not require DevTools. If the shortcut does nothing, open the browser menu and look for Screenshot; the wording and placement can differ by release.
Recommended Free Tools
#1 Best Overall
Mozilla Firefox: use the built-in Screenshot tool
Save a full-page image
- Open the page in Firefox.
- Open Firefox’s page screenshot command. Depending on your release, this may be available from the page actions or browser tools menu; menu placement is not identical on every platform.
- Select the Full page option rather than the visible-area option.
- Preview the capture, then download it to your chosen location.
Firefox also documents a --fullpage option for its screenshot command-line workflow. That option is useful when you are automating Firefox, but the graphical Screenshot tool is simpler for a one-off capture. If you cannot find the command, search Firefox’s current help for “screenshots” because menu labels can move between releases.
Google Chrome desktop: capture through DevTools
Extension-free full-size capture
- Open the webpage in Chrome.
- Open DevTools with Ctrl+Shift+I on Windows/Linux or Command+Option+I on macOS.
- Turn on Device mode by selecting the phone/tablet icon in the DevTools toolbar, or press Ctrl+Shift+M (Windows/Linux) or Command+Shift+M (macOS).
- In the Device mode toolbar, open More options (the three-dot menu).
- Select Capture a full size screenshot.
Chrome’s documented command includes content outside the viewport. Device mode is a simulation tool, so check the emulated width and device scale before capturing if the layout matters. This method is more involved than Edge or Firefox, but it avoids installing an extension.
iPhone: capture a full webpage in Safari
Save as an image or PDF
- Open the webpage in Safari.
- Take a normal screenshot using the hardware-button combination for your iPhone model.
- Tap the screenshot preview when it appears.
- Tap Full Page at the top of the editor.
- Scroll the preview to inspect the complete page. Crop or annotate if necessary.
- Save the capture as an image or choose the PDF save option.
Apple’s example is an entire webpage in Safari. The Full Page tab appears in the screenshot editor; it is different from the initial screenshot, which contains only what was visible on screen.
Rank #2
Which workflow should you use?
- Use Edge when you want a direct shortcut and built-in markup.
- Use Firefox when you prefer its dedicated Screenshot tool and a simple download.
- Use Chrome when you are comfortable with DevTools and want an extension-free desktop method.
- Use iPhone Safari when the page is open on an iPhone and you need Apple’s image or PDF output.
Android and Safari on Mac are not covered by the official workflows cited here. Their controls depend on the operating-system and browser version, so consult the current platform documentation rather than assuming that an iPhone or Chrome desktop shortcut applies.
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 →When a full-page capture is not straightforward
Long or dynamically loaded pages
A full-page command asks the browser to render content beyond the viewport. Pages that load material only after interaction, use an infinite feed, or place content in a separate scrolling panel may not behave like a simple document. The documented browser instructions do not promise perfect results for those cases. Try waiting for the page to finish loading, and capture after expanding the sections you need.
Consent dialogs, popups and chat controls
A cookie banner, newsletter dialog or floating chat button can become part of the image. Dismiss those elements before capturing when the site allows it. If a dialog blocks the page, close it first; otherwise the browser may capture the obstruction repeatedly.
Very large pages
Long captures can produce large image files and may take longer to render. For documentation or sharing, a PDF can be easier to navigate; on iPhone, the Full Page editor provides a PDF option. For a web asset, choose the browser’s image download and verify that the file opens before deleting the original page.
Troubleshooting checklist
The shortcut or menu is missing
- Check that you are using a current desktop release; feature availability can vary by version.
- Open the browser’s main menu and search for Screenshot or Capture instead of relying on a remembered shortcut.
- In Chrome, use DevTools and Device mode; the full-size command is located in the three-dot More options menu.
The capture stops at the visible area
- Confirm that you selected Full page, Capture full page or Capture a full size screenshot, not a visible-area command.
- In Chrome, make sure Device mode is enabled before opening More options.
- On iPhone, reopen the screenshot preview and tap Full Page; the initial screenshot alone is not a scrolling capture.
Images or sections are absent
- Wait for the page to finish loading before starting the capture.
- Scroll through the page once if its design loads media only as it approaches the viewport, then capture again.
- Expand accordions or menus that must appear in the final image.
The result contains an unwanted overlay
Close consent prompts, newsletter forms and chat widgets before taking the capture. If the overlay returns, reload, dismiss it again, and capture immediately after the page settles.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Chrome’s output looks like a different layout
Device mode changes the simulated viewport. Set the width and device profile to match the layout you want, then run Capture a full size screenshot again.
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server for developers. One GET request returns a PNG, JPEG, WebP or PDF, so you can capture pages from a script, build pipeline or AI-agent workflow instead of opening a browser manually. Read the parameter reference in the ScreenshotNeo documentation.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
Python
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
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}`);
Replace the example URL with the page you need and store your access key securely rather than committing it to source control.
Options for difficult pages and production jobs
ScreenshotNeo exposes 63 options. You can request full-page capture with lazy images loaded, target one element by CSS selector, choose dark mode, use 12 device presets or any viewport, set retina scale, and resize the output. For PDFs, set paper size, margins, landscape orientation and page ranges. You can inject custom CSS or JavaScript, click an element before capture, hide selectors, and wait for a selector, a delay or network idle.
For request control, block ads, trackers, individual requests or resource types; send custom headers, cookies, a user agent or an Authorization header; and set timezone and geolocation. Transparent backgrounds, caching with a TTL you choose, signed links for public <img> tags, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, a usage API and an OpenAPI specification are also available. Parameter names used by other screenshot APIs work as well, which can reduce migration changes.
Best Value
Why the result can be cleaner and easier to budget
- Before capture, ScreenshotNeo accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups and chat widgets. 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 in
X-Page-Verdictand whether it was billed inX-Billed. - An MCP server provides
take_screenshot,get_page_infoandcapture_pdftools for Claude, Cursor and other MCP clients.
Plans
| Plan | Allowance | Price |
|---|---|---|
| Free | 1,000 shots/month | $0, no card |
| Starter | 3,000 shots | $5 |
| Growth | 15,000 shots | $15 |
| Pro | 60,000 shots | $39 |
| Scale | 250,000 shots | $99 |
| Business | 1,000,000 shots | $249 |
Yearly billing gives two months free, and every feature is included on every plan. Create a free ScreenshotNeo account to get 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 shots.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.FAQ
Does a scrolling screenshot include the browser toolbar?
The documented full-page commands capture webpage content, not the surrounding browser interface. If you need the address bar or toolbar as evidence, take a separate normal screenshot.
Can I turn a full-page capture into a searchable document?
Use the PDF output where the workflow offers it, such as iPhone Safari’s Full Page editor or an API capture configured for PDF. Image files preserve the visual page but do not automatically add selectable text.
Is a browser extension required?
No. Edge, Firefox, Chrome desktop and iPhone Safari each have documented built-in workflows. Chrome’s route requires DevTools, but it does not require an extension.
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.

