How to Capture Image and Video Results in Google SERP Screenshots

To capture image or video results in a Google SERP screenshot, run the search, wait until the result module you need is visible, then take a screenshot of the displayed page. Use a normal device screenshot when the content fits on screen. In Chrome, use DevTools when you need a selected area or a full-page capture. Google’s layout varies by query and context, so verify the saved image rather than assuming a particular module will appear.

1. Choose what the screenshot needs to show

Decide whether you need the visible screen, a specific region, or the full results page. Keep the query and enough surrounding results in frame to make the image understandable. Image and video features can appear alongside other results, but their appearance depends on the search; filters and tools can also vary by result type, language, and sign-in context. Google’s policies for image and video boxes explain that these features are conditional.

Need	Capture method	Check
What is currently visible	Device screenshot control	Query and target module are legible
A specific region	Chrome DevTools area screenshot	Selection includes surrounding context
More than the viewport	Chrome DevTools full-page screenshot	Page content is complete and readable
Repeatable capture workflow	Chrome Headless or a screenshot API	Rendered result matches the intended query and context

2. Capture the visible viewport

1. Open Google Search and run the query you want to document.
2. Wait for the results to render. Confirm that the intended image or video feature is actually visible.
3. Use your computer or phone’s standard screenshot control. The exact shortcut depends on the device and operating system.
4. Open the saved image. Check that the query, target feature, and necessary surrounding context are visible and legible.

This is usually the quickest choice when the target fits on screen. If it does not fit, use an area or full-page capture rather than shrinking the browser until text is difficult to read.

3. Capture an area or the full page in Chrome

1. Open the results page in Chrome and open DevTools.
2. Focus DevTools, then open the Command Menu with Ctrl+Shift+P on Windows or Linux, or Command+Shift+P on macOS.
3. Type screenshot and select the capture command that fits your need. Chrome documents an area capture in its Command Menu guide; DevTools release notes also describe full-page screenshot support. Menu labels can change, so search the menu for “screenshot” if needed.
4. Save the image, open it, and inspect the query and target module at normal size. Make sure a full-page capture did not omit lower content or produce an image too small to read.

Chrome Headless also supports a command-line --screenshot option and window sizing for repeatable automation. Its documented sizing example sets the viewport; do not assume that this alone captures the full document. See the Chrome Headless documentation for the available command-line options.

4. Preserve the context of the capture

A screenshot records the rendered view at one point in time. Keep the original file unedited and record:

• The exact search query and capture date and time, including time zone.
• Browser, device, viewport or display dimensions, and whether the image is a viewport, area, or full-page capture.
• Relevant context such as location and sign-in state, if known.
• Any later crop or annotation, saved separately from the original.

These notes make the file easier to interpret later. A screenshot by itself does not establish what every other searcher saw.

5. Permissions and realistic presentation

Google’s Search screenshot guidelines say third-party content-owner approvals are the user’s responsibility. Google says permission from it is not needed for screenshots of Search pages or results in print for educational or instructional purposes; that statement should not be treated as a universal license for every medium, commercial use, jurisdiction, or image and video item shown. The guidelines also call for realistic presentation and say, “Don’t modify the interface.” Keep an unmodified original and check the applicable rights for your intended use.

6. Automate repeat captures

For a one-off record, a manual screenshot is usually simpler. For a repeatable workflow, Chrome Headless can capture browser output from a command line. A screenshot API can also accept a URL and return an image, which is useful when you want to avoid managing browser installation and capture code. Google results can vary between requests and sessions, so automation does not guarantee a fixed set of modules or identical results. Record the query and relevant capture context alongside each output.

7. Troubleshooting

Problem	Likely cause	Fix
No image or video module appears	The feature is conditional on the query, language, location, or current results.	Confirm the query and context. Do not assume every search has the same layout; capture the page that actually rendered.
The module is cut off	It extends beyond the visible viewport or the area selection.	Use a full-page capture or select a larger area, then inspect the saved image.
Text or thumbnails are too small	The capture includes too much content or the browser viewport was reduced.	Capture a focused area or use a larger viewport while keeping the query and context visible.
The Command Menu option is hard to find	DevTools labels can differ between versions.	Open the Command Menu and search for screenshot; choose the available area or full-page action.
Automated output differs between runs	Search results and visual modules are dynamic and context-sensitive.	Save capture time and context, wait for the page to render, and review every output before relying on it.
Headless output contains only the viewport	Viewport sizing is not the same as full-document capture.	Use a documented full-page workflow for the browser/tool you selected, then verify the resulting dimensions and content.

8. Performance, reliability, and cost

Device screenshots and DevTools captures have no separate screenshot-service charge, but require a person or a browser automation setup. Headless capture adds browser startup and page-rendering work; dynamic results can make repeat runs inconsistent. A screenshot API moves browser operation to a service and may charge according to its plan and billing rules. Compare the scope you need, repeatability, treatment of failed or blocked pages, and the cost of successful captures before choosing. No official source in the research provides a benchmark for capture speed or a guaranteed stable Google results layout.

9. Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server for developers. One GET request can return a PNG, JPEG, WebP, or PDF. For a Google results page, pass the search URL you want to capture. The capture reflects the URL and context the service can access; it does not guarantee a particular result layout. See the ScreenshotNeo documentation for options and API details.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://www.google.com/search?q=your+query -o shot.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={
        "access_key": "YOUR_API_KEY",
        "url": "https://www.google.com/search?q=your+query",
    },
    timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://www.google.com/search?q=your+query'
});
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);

Replace your+query with a URL-encoded search query and keep your API key private. The Python and Node.js examples check for an HTTP error before saving or writing the response. For exact output format, capture timing, selectors, viewport, or other settings, use the API documentation.

• Cookie banners, newsletter popups, and chat widgets are removed before the shot; each cleanup step can be turned off.
• Bot checks, blank pages, timeouts, failed loads, and cache hits are never billed. Response headers report the page verdict and billing status.
• An MCP server gives AI agents tools to take screenshots, inspect page information, and capture PDFs.
• 1,000 screenshots a month are free with no card; paid plans start at $5 for 3,000.

Sign up for 1,000 free screenshots a month, with no card required.

10. Frequently asked questions

Can I make Google show a video or image carousel for every query?

No. Google’s image and video features are conditional, so capture the result page that appears for the query and context you need to document.

Does a screenshot prove what another person saw?

No. It shows a rendered page at capture time. Keep the query, time, browser, viewport, and relevant location or sign-in context with the original.

Should I crop the image before sharing it?

If you need a crop or annotation, preserve the original separately and make clear that the shared copy was altered. Check Google’s presentation guidance and rights for third-party content before publication.

Is a full-page capture always better?

No. A viewport capture can make the target module larger and easier to read. Choose the smallest scope that includes the context readers need.