Why Browser Screen Resolution Looks Wrong

The screen resolution reported to a website does not have to equal the physical pixel count printed in a display’s specifications. Webpages commonly see a size in CSS pixels and may also read the device pixel ratio, available screen area, and browser viewport. These values serve different purposes and are not interchangeable.

In MaskPilot, Screen resolution is saved in the profile together with scale, available area, and color depth, then loaded when the browser process starts. When a website reports an unexpected value, first identify which field is being compared.

Four commonly confused measurements

• Screen width and height: the size exposed through the browser screen interface in CSS pixels, which may differ from the panel’s total physical pixels.
• Device pixel ratio: the relationship between a CSS pixel and device pixels. Operating-system scaling, display density, and page zoom can affect the observed result.
• Available screen area: the space available to windows after taskbars, menu bars, or other reserved system areas are removed, so it can be smaller than the full screen.
• Browser window or viewport: depends on whether the window is maximized and whether sidebars or developer tools are open, and is normally smaller than the screen.

A website reporting a window width below the screen width does not by itself indicate a bad fingerprint setting. It may simply be reading the current page viewport.

When Use system display reads the system values

When you edit a profile and select Use system display, MaskPilot reads the screen size, device pixel ratio, available area, and color depth from the display that currently contains the MaskPilot client window when the profile is saved, then stores that set of values in the profile.

It does not continuously follow display changes on every launch. To sample another monitor, first move the MaskPilot client window to that display, then edit and save the profile. Moving the already running profile browser does not update the saved values. Replacing a display or changing operating-system scaling also requires another save followed by a full profile relaunch.

After selecting a fixed preset, the profile continues using the saved resolution and scale until they are changed again. A fixed preset is easier to reproduce when stable results matter across repeated launches.

Why a page looks too large or too small

Common causes include:

1. The device pixel ratio does not form the expected combination with the screen size.
2. The website has a separate saved page-zoom level.
3. The browser window is not maximized, causing the website to use a narrower responsive layout.
4. System scaling changed after the profile was last saved.
5. The profile was synchronized from another device and still has the previously saved fixed display configuration.
6. The website is showing a viewport, available area, or estimated value instead of the full screen size.

Visual size also depends on website CSS, fonts, and browser zoom. Do not repeatedly replace the display fingerprint merely because a page looks larger.

Recommended troubleshooting order

1. Fully close the target profile and confirm that no browser process remains.
2. Edit the profile and find Screen resolution under fingerprint settings.
3. To match a particular display, move the MaskPilot client window to that display before selecting Use system display and saving. For a stable result, select an appropriate preset.
4. Relaunch the same profile and reset page zoom to 100% before testing.
5. Record the screen size, device pixel ratio, available area, and window size reported by the website instead of keeping only one “resolution” value.
6. Compare a maximized window with a normal window to determine whether the difference comes only from the viewport.
7. For a profile used across devices, confirm where and when its display settings were last saved.

Fingerprint settings are read only when the process starts. See why profile settings did not apply for the complete lifecycle check.

Use system display or a fixed preset?

Use system display fits a profile that should match the current device. Place the MaskPilot client window on the target display before saving, and save again after changing devices, displays, or scaling.

A fixed preset fits a workflow that requires the same screen values across repeated launches. Select a reasonable, internally consistent size and scale instead of cycling through extreme combinations merely to match a single detection page.

The screen is only one part of the browser environment. Check language, time zone, and location independently. See configure a stable browser fingerprint, why a website shows the wrong language, and why a website shows the wrong location.

Before contacting support

Record the resolution and scale shown by MaskPilot, the operating system’s current screen size and scaling, each field reported by the website, whether the window was maximized, the page zoom, and the retest time after a full relaunch. Redact website accounts, notifications, and unrelated windows from screenshots.

MDN documents Screen.width as a value in CSS pixels and notes that the available width can be smaller because of system interface elements. MDN’s devicePixelRatio documentation explains that the value represents the ratio of device pixels to CSS pixels and can also be affected by page zoom.