How to capture a website screenshot with browser zoom set to 125 percent

To capture a website at 125% browser zoom, set the page zoom to 125% first, confirm the browser shows that value, then take a viewport or full-page screenshot. Page zoom changes how large page content appears; it is separate from operating-system display scaling and from device pixel ratio (DPR). Do not assume 125% zoom always produces an image that is exactly 1.25 times wider or taller. Capture methods can render differently, so inspect the saved file.

1. Choose what you need to capture

Decide the capture scope before choosing a tool:

Visible viewport: captures the portion currently on screen. Use this for a specific section or a quick review.
Full page: captures content beyond the current viewport, where the browser’s selected method supports it. Use this for a complete page review.
Area or element: useful when you need a selected region or a particular DOM node. Chrome DevTools documents area and node screenshot workflows.

If the requirement is specifically “125% zoom,” set browser page zoom rather than changing only text size or the operating system’s scaling. After capture, check that the page looks as intended and verify the output dimensions if they matter.

2. Set 125% page zoom in Chrome

Open the website in Chrome desktop.
Open the three-dot More menu and use the Zoom controls. You can also press Ctrl and + on Windows or Linux, or Command and + on Mac, until Chrome displays 125%.
Capture the page with the browser’s screenshot workflow or Chrome DevTools. In DevTools, choose the full-page, area, node, or mobile-view workflow that matches your goal.
Open the saved image and confirm its appearance and dimensions.

To make a zoom level the default, Chrome provides Settings > Appearance > Page zoom. This changes page zoom, which Chrome distinguishes from changing font size alone. See Chrome’s zoom guidance and Chrome DevTools screenshot workflows.

3. Set 125% page zoom and capture in Firefox

Open the page and use Firefox’s zoom controls to set page zoom to 125%. Confirm the displayed value.
Right-click an empty part of the page and choose Take Screenshot, or use Ctrl+Shift+S on Windows or Linux, or Command+Shift+S on Mac.
Choose Save visible for the viewport or Save full page for the whole page.
Save the image or copy it to the clipboard, then inspect the result.

Firefox DevTools also has an optional full-page screenshot button. Enable Take a screenshot of the entire page under DevTools Settings > Available Toolbox Buttons, then use the screenshot icon. In the Web Console, Firefox’s :screenshot helper supports --fullpage and a separate --dpr option. See Firefox screenshot instructions and Firefox DevTools screenshot documentation.

4. Understand page zoom, DPR, and image dimensions

Page zoom changes the apparent size of page content. DPR is a separate rendering parameter. Firefox documents a --dpr option for its screenshot helper; values above 1 create zoomed-in images and values below 1 create zoomed-out images. That does not make DPR interchangeable with the browser’s page-zoom control.

There is no universal guarantee that every browser-native, DevTools, or operating-system screenshot path turns 125% page zoom into a fixed output-pixel multiplier. If exact pixel dimensions matter, capture with the required browser and method, inspect the actual file, and adjust the capture setup to meet the output requirement. Do not substitute display scaling for page zoom without confirming that this meets the specification.

5. Automate the capture with Playwright

For repeatable captures, set the browser context’s zoom behavior through a page-level CSS zoom style before taking the screenshot. This is a practical page-rendering adjustment, but it is not guaranteed to match every browser’s native zoom control in every layout. If the requirement is strict, confirm the result in the target browser and compare the saved image.

import { chromium } from 'playwright';

const browser = await chromium.launch({ headless: true });
const page = await browser.newPage({ viewport: { width: 1440, height: 900 } });
await page.goto('https://example.com', { waitUntil: 'networkidle' });
await page.addStyleTag({ content: 'html { zoom: 1.25; }' });
await page.screenshot({ path: 'page-125.png', fullPage: true });
await browser.close();

Install Playwright in your project with npm install playwright. Replace the URL and viewport with your target. For a viewport screenshot, remove fullPage: true. Some websites respond to resizing or zoom with responsive layout changes; inspect the captured page for reflow, sticky elements, and content that loads only after scrolling.

6. Save a screenshot through ScreenshotNeo

ScreenshotNeo is a website screenshot API and MCP server for developers. It accepts a URL in one GET request and returns a PNG, JPEG, WebP, or PDF. Its capture options include viewport dimensions and device presets, full-page capture, and other rendering controls. For browser page zoom specifically, use the browser workflows above; the API example below captures a URL and saves its response as an image.

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}`);
const bytes = new Uint8Array(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', bytes));

See the ScreenshotNeo API documentation for authentication and request options. ScreenshotNeo can remove known consent banners, newsletter popups, and chat widgets before capture, and exposes page-verdict and billing headers so you can distinguish clean captures from bot checks, blank pages, failed loads, and cache hits.

Or skip the browser setup

Make one API request to capture a URL. Cookie banners, popups, and chat widgets are removed before the shot. Bot checks, blank pages, and failed loads are never billed. An MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

7. Troubleshooting

Symptom	Likely cause	What to do
The screenshot does not look like 125% zoom.	Zoom was not set on the page, or the capture route rendered it differently.	Confirm the browser’s page zoom display reads 125% before capture. Reopen the saved image and inspect it; do not infer zoom from output dimensions alone.
The text is larger, but the image dimensions did not grow by 25%.	Page zoom affects page layout and rendering, while screenshot pixel dimensions depend on viewport, DPR, and capture method.	Set the required viewport and inspect the actual output. Treat page zoom and DPR as separate settings.
The full-page option is missing.	The selected browser tool may not expose full-page capture in that location.	Use Firefox’s Save full page, enable its DevTools full-page screenshot button, or use the supported Chrome DevTools screenshot workflow.
Parts of the page are blank or missing.	Content may load lazily or only after scrolling, or the page may still be loading.	Wait for the page to finish loading, scroll through the content before capture when necessary, and capture again. Check the page in the browser before diagnosing the screenshot file.
The layout changes or content is clipped.	At 125%, the effective page space is smaller and responsive breakpoints or fixed elements may alter the layout.	Check the viewport size and page layout at the requested zoom. Choose viewport versus full-page capture deliberately, and inspect sticky headers, menus, and overlays.
The screenshot looks zoomed when DPR was changed.	DPR is separate from page zoom and affects rendering scale.	Set page zoom to 125% using browser controls. Adjust DPR only when you have a separate pixel-density requirement.

8. Performance, reliability, and cost

Browser-native screenshots are the simplest option for one-off manual captures and do not require an API request. DevTools adds useful capture scopes but requires opening developer tools. Automated browser capture is useful for repeatable jobs, but page load time, lazy content, and the page’s response to zoom can affect the result; wait for the content you need and validate representative outputs.

For API capture, request only the scope and output format you need, and use caching when repeated captures of the same page are acceptable. ScreenshotNeo provides a cache TTL option, async jobs with signed webhooks, and bulk capture for up to 100 URLs per call. Plans are Free: 1,000 shots/month; Starter: $5 for 3,000; Growth: $15 for 15,000; Pro: $39 for 60,000; Scale: $99 for 250,000; Business: $249 for 1,000,000. Yearly billing gives two months free, and every feature is on every plan. Only clean shots are billed; bot checks/CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing.

9. FAQ

Can I screenshot at 125% without changing my operating-system scaling?

Yes. Set the browser’s page zoom to 125%. Operating-system display scaling is a different control.

Does 125% browser zoom mean the screenshot is 1.25 times larger?

Not necessarily. Output dimensions depend on the browser screenshot path, viewport, and pixel density. Inspect the saved image.

Can I save only the visible part of the page?

Yes. Use the browser’s visible or viewport screenshot option. Firefox labels this choice Save visible.

Can a full-page screenshot include content below the fold?

Yes, when the capture method supports full-page screenshots. Lazy-loaded content may need to be loaded before capture.