Why Is My WebGL GPU Different?

A website can read a WebGL vendor and renderer that do not look like the graphics-card name shown by the operating system. First determine whether you are seeing the profile’s saved choice, the browser’s actual renderer string, or only a different label from one test page. Do not keep replacing the values until one checker turns green.

Understand what the page reads

Web pages can request UNMASKED_VENDOR_WEBGL and UNMASKED_RENDERER_WEBGL through the standard WEBGL_debug_renderer_info extension. These are browser-exposed strings about the graphics driver; they are not an inventory screen for the physical computer, and privacy settings may limit whether the extension is available.

MaskPilot’s Graphics information protection setting changes only the WebGL vendor and renderer presented by the profile. It does not replace the physical GPU, install a driver, or configure WebGPU. The setting is off by default because the default provides the best compatibility. When protection is enabled, leaving GPU vendor and GPU model blank keeps their actual values.

Check the current profile before editing

1. Open the affected website and one WebGL test page inside the same profile.
2. Record the reported vendor and renderer, the browser version, the profile name, and the test time. Do not include account credentials or proxy secrets in a screenshot.
3. Fully close the profile and wait until it becomes available again.
4. Edit that profile and find Graphics information protection in the fingerprint settings.
5. Confirm whether protection is enabled and whether GPU vendor or GPU model contains a saved value.

If you tested another profile, another browser, or the desktop operating-system panel, you did not measure the same browser environment. Repeat the comparison without changing settings first.

Choose the smallest safe correction

• If you never intended to present custom WebGL metadata, leave Graphics information protection off. This is the default and has the broadest compatibility.
• If protection must remain enabled but no custom vendor or model is required, leave both fields blank so the actual values continue.
• If a specific workflow requires custom values, treat the vendor and model as one reviewed pair. Do not copy an arbitrary model from a forum, set only half of the pair, or change the value on every launch.
• Do not alter canvas, screen, language, time zone, browser version, and WebGL together. One change at a time makes the result attributable.

Save the profile only after deciding which case applies. For the wider configuration boundary, see configure a stable browser fingerprint.

Relaunch and verify the result

Fingerprint settings are read when the browser process starts. Saving the form does not rewrite a profile that is already running:

1. Confirm that the original profile process has fully exited.
2. Launch the same profile again.
3. Reopen the same test page and compare the vendor and renderer with the recorded result.
4. Repeat the check once without editing anything. A stable result is more useful than repeatedly rotating values.
5. Test the actual work site separately; a diagnostic page and a business site may display or interpret the same strings differently.

If the old value remains, follow why profile settings did not apply before making another change.

If the site still reports a problem

A WebGL result alone does not prove why a site challenged or rejected a session. The site may also evaluate the browser version, screen, language, time zone, network exit, extensions, and account activity. Keep the WebGL result as one observation and isolate the next variable instead of guessing.

If WebGL cannot initialize at all, pages render incorrectly, or the browser falls back to software rendering, that is different from a vendor or renderer text mismatch. Restore the default WebGL setting, fully restart the profile, check the device’s graphics driver and remote-desktop environment, and record the exact visible error before contacting support.

MDN documents how WEBGL_debug_renderer_info exposes the unmasked vendor and renderer, while the Khronos extension specification explains the debugging purpose and privacy considerations of those strings.