This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Reported browser resolution is 1536×722

more options

I am using firefox 85.0 and this issue still exist in 84.0

In browserleaks.com amiunique.org coveryourtracks.eff.org my browser reported my resolution as 1536x722 which the "722" height part was weird.

I am having 1920x1080 and 125% zoom level in windows 10 home 1909. some quick math: 1536 is normal because 1920/1.25=1536 but how come the 722 was?

I am worried by this issue. This problem probably will make me more unique in browser fingerprinting.

i have privacy.resistFingerprinting = True and some extensions, also i disabled "navigator" and "screen" api on "CanvasBlocker" extensions

I also searched this problem but didn't end up with a clear answer. Someone said its cause by firefox tool bar, someone said tor browser also has this problem. I totally don't know what's happening.

I need help!

I am using firefox 85.0 and this issue still exist in 84.0 In browserleaks.com amiunique.org coveryourtracks.eff.org my browser reported my resolution as 1536x722 which the "722" height part was weird. I am having 1920x1080 and 125% zoom level in windows 10 home 1909. some quick math: 1536 is normal because 1920/1.25=1536 but how come the 722 was? I am worried by this issue. This problem probably will make me more unique in browser fingerprinting. i have privacy.resistFingerprinting = True and some extensions, also i disabled "navigator" and "screen" api on "CanvasBlocker" extensions I also searched this problem but didn't end up with a clear answer. Someone said its cause by firefox tool bar, someone said tor browser also has this problem. I totally don't know what's happening. I need help!

Chosen solution

It seems that with resistFingerprinting, the screen.width/screen.height, the innerWidth/innerHeight, and the outerWidth/OuterHeight all match the actual innerWidth/innerHeight of the window, adjusted by the zoom level.

Perhaps the idea behind this is that every time you resize the window (assuming you don't always maximize your window), your screen resolution will look different. I don't know whether that is a logical way to disassociate your browser's current fingerprint from a previous one.

Read this answer in context 👍 0

All Replies (6)

more options

Hey Eric,

It would help if you provide steps to replicate so that we can see similar results. Not everyone is familiar with these site.

more options

This can be caused by zooming pages as this affect the screen dimensions reported by JavaScript, but also can be caused by having a higher DPI setting in Windows.

You may have accidentally zoomed webpage(s). Reset the page zoom on pages that cause problems.

  • View -> Zoom -> Reset (Ctrl+0/Command+0 (zero))
more options

Hello, I can reproduce the problem by changing "privacy.resistFingerprinting" from false (default) to true in about:config. It changed my screen resolution reported from 864 to 722.

more options

Normally the screen dimensions are rounded to the nearest 200x100 when you enable "Resist Fingerprinting". Note that you are moved to the UTC timezone and your user agent is changed and other features work differently.

You can check your resolution via this website.

more options

Suluhisho teule

It seems that with resistFingerprinting, the screen.width/screen.height, the innerWidth/innerHeight, and the outerWidth/OuterHeight all match the actual innerWidth/innerHeight of the window, adjusted by the zoom level.

Perhaps the idea behind this is that every time you resize the window (assuming you don't always maximize your window), your screen resolution will look different. I don't know whether that is a logical way to disassociate your browser's current fingerprint from a previous one.

more options

Thanks jscher2000.