Take full control
of your viewport.

When you navigate to a page where the URL’s protocol (http / https), domain (including subdomains), or port number changes, Chrome doesn’t allow the extension to regain the temporary access it was granted except through the proper route (clicking the extension icon again), so the control panel window is closed. If you were recording, everything up to that point is saved, just as if you had clicked the “Finish” button. To continue, just click the extension icon again.

For navigations or reloads where none of these change, the control panel automatically recovers, and you can keep resizing, capturing, and recording. However, if the page navigates or reloads during a scroll recording, the scroll can’t be resumed from where it left off, so the recording ends and is saved at that point.

On some pages — such as Chrome’s internal pages starting with chrome:// (Settings, the extensions page, etc.) and the Chrome Web Store — Chrome’s security restrictions don’t allow extensions to access the page. Viewport resizing, capturing, and other features don’t work on these pages.

Please use the extension on regular websites.

So you can see the content exactly as it should appear at the specified viewport size, and resize, capture, and record it accurately.

On Windows Chrome, the scrollbar takes up about 15–17px of the page width. Left as is, the content would be displayed narrower than the specified viewport size — which is the width CSS media queries use, and also the size of the saved images and videos. And hiding the scrollbar only at the moment of capturing or recording would make the layout reflow right then, so what you saved would differ from what you were looking at.

That’s why the page-wide scrollbar is hidden only while the extension window is open. You can still scroll with the mouse wheel or keyboard as usual, and the scrollbar comes back when you close the window. On systems where the scrollbar doesn’t take up width, such as macOS, nothing is changed.

This happens when Windows’ Settings → Display → Scale is set to a fractional value such as 125%, 175%, or 225%. At these settings, 1px on the page is drawn with 1.25, 1.75, or 2.25 screen pixels, so converting the whole number of screen pixels back to page units can leave a fraction.

(For example, at 175%, a viewport 3361 screen pixels wide is 3361 ÷ 1.75 = 1920.57px in page units. “Current Viewport” shows this actual value as is.)

When resizing with a preset, the extension tells Chrome’s API a window size that includes the browser UI (tabs, address bar, etc.). With a fractional display scale, making the viewport exactly the specified size can require a fractional window size such as 1234.57px. However, Chrome’s API only accepts whole numbers for window sizes, so in those cases the viewport is resized to the closest size that’s possible.

Captures and recordings are saved at the on-screen pixel size when “Save at Retina resolution” is on, and at the viewport size rounded to whole pixels when it’s off (recordings may additionally be rounded to even numbers).

It doesn’t happen when Scale is set to a whole multiple such as 100% or 200%, or on macOS.

Google Chrome 154.0.8037.58 / macOS Golden Gate 27.0
Google Chrome 154.0.8037.58 / Windows 11

You can’t resize beyond your display’s usable area (the work area). This appears to be because the operating system itself does not allow a browser window to be larger than the visible area of the display, and it can’t be worked around by an extension. If the specified size exceeds the screen, it is automatically adjusted to the largest size that fits.

By default, the aspect ratio of the specified size is preserved when it is adjusted to fit (you can turn this off in the settings).

Chrome’s screenshot API for extensions can only be called up to twice per second. Full page capture scrolls and captures step by step within this limit, so the longer the page, the longer it takes.

Full page capture covers the page as long as it was when the capture started. Content that loads during the capture and makes the page longer isn’t included. To capture further, scroll down the page first to load more content, then start the capture.

The saved image size depends on the “Save at Retina resolution” setting, as described below. The same applies to the width of full page captures.

When it’s on, the image is saved at the on-screen pixel size. On a Retina display on macOS or at a 200% display scale, that’s exactly twice the viewport. But on Windows with a fractional display scale such as 125% or 175%, the viewport multiplied by the scale is rounded to whole pixels when it isn’t a whole number, so the result isn’t always an exact multiple (for example, 1200×630 at 175% becomes 2100×1103).

When it’s off, the image is scaled down to the viewport size. Normally that’s exactly the specified size, but on Windows with a fractional display scale, the viewport can have a fractional size like 1920.57px. In that case, it’s saved at that size rounded to the nearest whole number.

When you record on a Retina display, the page itself is captured sharply, but the cursor is drawn by the browser’s native functionality, and its resolution can’t be controlled by the extension. Please consider this a known limitation for now.

The saved size of a recording is determined in two steps.

First, the viewport size is rounded to whole pixels. Normally it stays exactly as specified, but on Windows with a fractional display scale such as 125% or 175%, the viewport can have a fractional size like 1920.57px (see “Why does ‘Current Viewport’ show a decimal size on Windows?”). In that case it’s rounded to the nearest whole number.

Next, the browser’s video capture and encoding pipeline requires both dimensions to be even, so if the rounded result is odd, it’s automatically rounded down to the next even number, 1px smaller. For example, a 1080×1295 viewport is saved as 1080×1294. This is a browser-level constraint that occurs regardless of how the extension is implemented.

Permanently hiding the cursor with CSS would hide it not only in the recording but also on your own screen while you work, so we don’t use that approach.

Instead, you can show or hide the cursor whenever you like during recording with the Option + H (Mac) / Alt + H (Windows) shortcut.

The control panel is designed to close automatically when you switch away from the target tab, and this applies during recording as well. Your recording isn’t lost, though: it’s treated the same as pressing the “Finish” button, and everything up to that point is saved automatically. To keep recording, click the extension icon again on the target tab and start a new recording.

The captured video size isn’t expected to change mid-recording, so if the window’s size changes from what it was at the start, the recording automatically finishes and is saved at that point (simply moving the window won’t stop the recording). Please avoid resizing the window while recording.

No. When recording with audio, what’s captured is the audio output played by the target tab itself — a different mechanism from accessing a physical microphone — so no OS or browser microphone permission dialog appears. You’ll also continue to hear the target tab’s audio through your speakers as usual while recording.

At very large resolutions (around 4200px or more in our testing), both hardware and software encoding may fail, and MP4 recording can’t start. When this happens, an error message is shown — recording never silently continues in a broken state. In that case, try a lower resolution or use the WebM format instead.

The maximum recording time is 60 minutes, but recorded data is held in your computer’s memory during recording and saved all at once when you finish. Depending on your computer’s available memory and free storage space, recording may end before reaching 60 minutes, or saving may fail.

For longer recordings, close other apps and tabs to free up memory, and make sure you have plenty of free storage space.