How to Take a Full-Page Screenshot of a Website in Brave
Capture an entire webpage in Brave with DevTools. Learn the steps, common fixes, and when a screenshot API is a better fit.
To capture a full webpage in Brave desktop, open the page, open DevTools, launch the DevTools Command Menu, and choose Capture full size screenshot. On Windows and Linux, use Ctrl+Shift+P in DevTools; on macOS, use Cmd+Shift+P. Brave should save a PNG of the full document, including content below the visible window.
This is a DevTools command, not the same as Brave’s ordinary screenshot control. Brave lists a screenshot tool among its features, but the available instructions do not establish that the regular tool captures the whole document. Brave’s feature overview and a Brave Community discussion of DevTools capture commands describe the distinction.
Steps: capture a full page in Brave
- Open the page in Brave desktop and wait for the parts you need to appear. If the site loads content as you scroll, scroll through the page first so more of it has a chance to load.
- Open Developer Tools. On Windows or Linux, press F12 or Ctrl+Shift+J. On macOS, open DevTools from Brave’s menu if your configured shortcut differs. Brave’s shortcut reference lists the Windows/Linux DevTools shortcut.
- With DevTools focused, open the Command Menu: Ctrl+Shift+P on Windows/Linux, or Cmd+Shift+P on macOS. The macOS combination is the platform equivalent; the community procedure specifically documents Windows.
- Type
Capture full size screenshot. If the exact phrase does not appear, search forscreenshotand inspect the available commands. - Select Capture full size screenshot. Wait for the capture to finish, then check Brave’s download shelf or Downloads folder for the PNG.
The command may be available in other Chromium-based desktop browsers too, but this guide focuses on Brave. Command wording and placement can change with browser versions, so use the Command Menu search if the label differs.
What “full page” means, and what it does not
A full-page capture extends beyond the current viewport to include the document below the fold. It is useful for preserving a long article, inspecting a page design, or sharing a visual record of a page in one image.
Do not assume Brave’s ordinary screenshot interface produces that same result. The standard control and DevTools command are separate workflows, and the sources available for this guide do not document all capture modes of the ordinary control.
| Goal | Use | Output |
|---|---|---|
| One image containing content below the fold | DevTools → Capture full size screenshot | Full-document PNG |
| Capture a visible region or use the browser’s normal screenshot interface | Brave screenshot tool, subject to the modes in your installed version | Image; confirm the selected mode before relying on full-page coverage |
| Save a printable or paginated version | Brave Print | Printer output or a PDF destination, depending on available system options |
To print, use Ctrl+P on Windows/Linux or Cmd+P on macOS, then select an available destination. A print/PDF document is paginated and is not a single full-page screenshot image. See Brave’s printing instructions.
Before you capture: make the page state predictable
- Wait for important content. Let images, fonts, and embedded content finish loading where possible.
- Scroll through lazy-loaded sections. Some sites load images or cards only as they approach the viewport. Scrolling down and back up can prompt those sections to load before capture.
- Set the desired page state. Dismiss dialogs or expand sections if you want their resulting state in the image. A screenshot records the page as it is presented at capture time.
- Check sticky elements. Fixed headers, chat buttons, or floating controls may appear in ways that differ from a manually scrolled view. Review the result rather than assuming it matches a stitched scroll capture.
- Keep the tab open until the file appears. Very long pages may take longer to render and encode.
Dynamic pages can change while they are being captured. Live feeds, animations, personalized content, and delayed requests may mean that a single image does not represent one perfectly synchronized moment. The exact behavior depends on the page.
Troubleshooting
| Symptom | Likely cause | What to try |
|---|---|---|
| The command menu does not open | Focus is in the webpage or another DevTools panel, or the shortcut is customized. | Click inside DevTools and try again. Open DevTools using Brave’s menu, then use the platform’s Command Menu shortcut. Brave notes that shortcuts can be customized in Settings → System → Shortcuts. |
| “Capture full size screenshot” is missing | The command label or availability differs in this Brave/Chromium version, or the menu has not been opened in DevTools. | Confirm DevTools is open, search screenshot, and inspect the listed capture commands. The Brave Community instructions are older, so command labels may have changed. |
| Only the visible screen was saved | A viewport or ordinary screenshot command was selected instead of the full-size command. | Repeat the process and select the command explicitly named Capture full size screenshot. |
| Images or sections are missing | The site may load content lazily or after a delay. | Scroll through the page, wait for sections to populate, return to the top, and capture again. |
| The image looks different from the page while scrolling | Sticky controls, animation, or changing page content may affect a full-document capture. | Pause where possible, close overlays, and capture again. For a critical record, inspect the saved file and consider preserving the page as a PDF as well. |
| The capture does not download or Brave seems stuck | The page may be unusually long or resource-heavy, or browser resources may be constrained. | Wait briefly, check Downloads, close unrelated heavy tabs, and try again. If it continues, reload the page and capture after it has settled. |
Performance, reliability, and output considerations
A full-page image can be much taller and larger than a viewport screenshot. Long pages with large images or complex layouts take more memory to render and encode, and the resulting file may be cumbersome to send or open. If you only need one section, capture that section instead of the entire document. If you need a readable record rather than a single image, printing to PDF may be easier to navigate.
For repeatable documentation, keep the page state consistent: use the same viewport and browser zoom, wait for the same content to load, and note any interactive state you changed. This reduces accidental visual differences between captures. DevTools capture is an interactive browser workflow; it is not a managed API for scheduled or bulk screenshots.
Or skip the browser setup
If you need screenshots from code, a server, or an agent workflow, ScreenshotNeo is a website screenshot API and MCP server. One GET request returns an image or PDF. The API accepts URL and capture options, including full-page capture with lazy images loaded. See the ScreenshotNeo documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpimport 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)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}`);
await Bun.write('shot.webp', res);These examples use the API’s basic call; configure full-page capture and output options as described in the docs. ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before capture, and each cleanup step can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed; response headers identify the page verdict and billing status. Its MCP server gives AI agents tools for screenshots, page information, and PDF capture. The free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots.
Sign up for 1,000 free screenshots a month, with no card required.
Frequently asked questions
Does the DevTools method need an extension?
No. It uses the DevTools command menu built into the browser workflow described above.
Can I capture a full page on Brave mobile?
The steps here are for Brave desktop and rely on desktop DevTools. The research for this guide does not establish an equivalent full-page workflow in Brave mobile.
Can I use the image as a PDF?
The DevTools command saves an image. Use Brave’s print workflow for a paginated document or a PDF destination.
Is Brave Leo’s full-page capture the same feature?
A community report mentioned full-page screenshot capability in a particular Leo version, but that is a version-dependent community report rather than universal official documentation. Check the feature in your installed version; the DevTools route is the procedure covered here.
