F12 opens Chrome DevTools; it does not take a screenshot by itself. After DevTools opens, switch to Device Mode and choose the capture command that matches your goal: Capture screenshot for the visible viewport, Capture a full size screenshot for the entire page, or Command Menu → Capture area screenshot for a hand-selected region.
Open DevTools with F12 (or the correct shortcut)
Open the page you want to capture in Google Chrome. Then use the shortcut for your operating system:
- Windows or Linux: press F12 or Ctrl+Shift+I.
- macOS: press Command+Option+I.
These shortcuts open the last-used DevTools panel. They are not screenshot commands. If a laptop uses the function-key row for hardware controls, you may need Fn+F12, or use the Chrome menu → More tools → Developer tools path instead.
Capture the visible viewport
Use this when you need exactly what is currently visible in the browser’s emulated viewport.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minute- Open DevTools using the shortcut above.
- Turn on Device Mode by clicking the phone-and-tablet icon in the DevTools toolbar, or press Ctrl+Shift+M on Windows/Linux (the menu route is preferable if that shortcut is unavailable).
- Set the desired device preset, orientation, zoom, and dimensions.
- Open More options in the Device Mode toolbar.
- Select Capture screenshot.
Chrome saves an image of the viewport shown in Device Mode. Content below the fold is not included. Before capturing, scroll or resize the emulated viewport to the state you actually want, dismiss transient menus, and wait for visible fonts and images to finish loading.
When a viewport shot is the right choice
- Documenting a responsive breakpoint at a specific width.
- Recording a bug exactly as it appears on screen.
- Creating a hero image or social preview with a fixed crop.
- Comparing desktop and mobile layouts at controlled viewport sizes.
Capture the entire page
For a page-length image, use Device Mode’s full-size command:
- Open Device Mode and configure the viewport or device preset.
- Open More options.
- Select Capture a full size screenshot.
Chrome captures content beyond the currently visible viewport. The result is a single image rather than a series of manually stitched viewport shots. Check the output after saving: pages with sticky headers, animated sections, lazy-loaded media, infinite scrolling, or stateful widgets can render differently when Chrome lays out the full page.
Improve full-page results
- Wait for the page’s visible network activity and animations to settle.
- Scroll through important sections first if the site loads images only after they approach the viewport.
- Pause carousels, videos, and other animations when a stable frame matters.
- Use a consistent viewport width; changing it can trigger a different responsive layout.
- Inspect the saved image for repeated sticky elements, missing lazy images, and unexpected blank regions.
There is no universal guarantee that every site’s dynamic content, lazy-loading behavior, or sticky positioning will appear identically in every full-size capture. If the result is wrong, try the page-specific fixes in the troubleshooting section below.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Select and capture an arbitrary area
Use area capture when you need a rectangle that does not correspond to the whole viewport or an individual element.
- Open DevTools and keep it docked to the browser window. Area capture does not work when DevTools is undocked.
- Open the DevTools Command Menu. In most Chrome installations, press Ctrl+Shift+P on Windows/Linux or Command+Shift+P on macOS.
- Type
screenshot. - Select Capture area screenshot.
- Drag over the page region you want, then release. Chrome saves the selected area.
Area selection is useful for a chart, form, error message, or component that is smaller than the viewport. Because the selection is made on the rendered page, first set the zoom and responsive dimensions that should appear in the final image.
Include a simulated device frame
To show the phone or tablet shell around the emulated page, use Device Mode’s device-specific settings:
- Choose a device preset rather than a generic responsive viewport.
- Open the device options and enable Show device frame.
- Capture with Capture screenshot or Capture a full size screenshot.
The frame represents Chrome’s simulated device view. It is different from capturing the physical browser window, operating-system chrome, or a real handset’s bezel.
Which DevTools command should you use?
| Need | Command | Result |
|---|---|---|
| Current visible content | Capture screenshot | The current Device Mode viewport. |
| Whole document | Capture a full size screenshot | Page content extending beyond the viewport. |
| Custom rectangle | Command Menu → screenshot → Capture area screenshot |
The region selected by dragging; DevTools must remain docked. |
| Device presentation | Enable Show device frame, then capture | The emulated page with its simulated device frame. |
Before you capture: a reliable checklist
- Confirm you are on the intended URL and account state.
- Choose the viewport width, height, orientation, and device preset.
- Set browser zoom and Device Mode scale consistently between comparisons.
- Wait for fonts, images, and critical data to finish loading.
- Dismiss cookie notices, chat bubbles, menus, and development overlays if they should not appear.
- Disable or pause animation when a repeatable frame is more important than motion.
- For sensitive pages, remove personal data and verify that tokens or passwords are not visible.
- Open the saved file and inspect the complete image rather than assuming the capture succeeded.
Troubleshooting common failures
F12 opens nothing
Your keyboard, operating system, or browser policy may intercept the function key. Try Ctrl+Shift+I on Windows/Linux, Command+Option+I on macOS, or Chrome menu → More tools → Developer tools. Managed computers can disable DevTools entirely.
The screenshot command is missing
Enable Device Mode first and open its More options menu. For an area image, use the Command Menu and search for screenshot. The labels are different commands, so searching for “full page” may not show the viewport command.
Area capture does not start
Dock DevTools back into the browser window. Chrome’s area capture does not work while DevTools is undocked. Then reopen the Command Menu and select Capture area screenshot.
The full-page image is incomplete
Check for lazy-loaded images, infinite scroll, delayed API data, and content hidden until interaction. Scroll through the page to trigger loading, wait for requests to finish, stop animations, and capture again. Infinite pages may have no stable “full size” boundary; save a viewport or selected area instead.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →A sticky header or widget is repeated
Fixed and sticky elements can be laid out differently during a full-size capture. Hide the element temporarily with DevTools’ element inspection, disable the site’s overlay, or use area capture for the section you need. Keep an untouched original capture if you are documenting the real user experience.
The mobile layout is wrong
Confirm Device Mode is enabled and that the selected preset or custom width matches the breakpoint you intend to test. Rotate the emulated device if orientation matters, then recapture.
The image looks blurry
Increase the emulated viewport or device scale only when the target image needs more pixels. A larger screenshot can also create a very tall file that is awkward to share. Use the smallest dimensions that meet the publication or testing requirement.
Performance, format and repeatability
DevTools captures the rendered page locally, so capture time depends on page load, scripts, fonts, image decoding, and the size of a full-page render. Full-size images can be substantially taller and larger than viewport shots. For repeatable visual checks, record the URL, viewport dimensions, device preset, orientation, zoom, login state, and capture time. Keep the same browser version and page data when comparing revisions.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Use viewport captures for fast regression checks, full-size captures for documentation, and area captures for focused bug reports. If a page changes between attempts, first determine whether the difference comes from responsive layout, asynchronous data, animation, consent overlays, or a capture setting rather than from the code under test.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
For automated screenshots, ScreenshotNeo returns a PNG, JPEG, WebP, or PDF from one GET request. It accepts cookie and consent banners, then removes more than 60 known consent platforms, newsletter popups, and chat widgets before the capture; each cleanup step can be turned off. Only clean shots are billed: bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers identify the page verdict and billing status.
Use the API documentation at https://screenshotneo.com/docs/ for the complete parameter list. This basic cURL request captures a page:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpThe equivalent Python request is:
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)In 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}`);ScreenshotNeo also supports full-page capture with lazy images loaded, CSS-selector element capture, dark mode, 12 device presets plus custom viewports, retina scale, PDF paper and page-range controls, custom CSS and JavaScript, pre-capture clicks, hidden selectors, selector or network-idle waits, ad/tracker/request blocking, headers, cookies, user agents, Authorization, timezone and geolocation, transparent backgrounds, resizing, configurable-TTL caching, signed image links, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, usage data, an OpenAPI specification, and parameter names used by other screenshot APIs.
Recommended Free Tools
An MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. The Free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account to get started.
Frequently Asked Questions
Does F12 take a screenshot in Chrome?
No. F12 opens the last-used DevTools panel on Windows and Linux. You must then choose a capture command in Device Mode or the Command Menu.
Can I capture only one element?
DevTools’ documented area workflow captures a rectangle you drag. For selector-based element capture in an automated workflow, ScreenshotNeo supports CSS-selector capture.
Why is my area screenshot unavailable when DevTools is detached?
Chrome’s Capture area screenshot command requires DevTools to be docked to the browser window.
Can DevTools capture a PDF instead of an image?
The documented DevTools commands here create screenshots. ScreenshotNeo’s capture_pdf MCP tool and API workflow support PDF output.
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.
