Rubric 1.0.0 · column 2 of 13
Screen resolution
screen.width by screen.height, in CSS pixels, before any device pixel ratio is applied.
Under rubric 1.0.0 this column is worth between 2.18 and 7.97 bits, and the likeliest outcome the table knows — 1920x1080 — costs 2.18. Those figures are assumptions printed before your run. The counted box beside them is not: it is how many of the devices these sites have read share your value.
How a browser produces a screen resolution
The panel reports a native pixel geometry to the operating system, the operating system applies a display scale, and the browser divides one by the other to give the page a CSS-pixel figure. That is why a 3024x1964 MacBook panel reads as 1512x982 and why the same physical monitor produces different values on two machines with different scaling settings. The rule reads the screen, not the window — resizing the browser changes nothing here, and a maximised window on a 4K display and a 400-pixel-wide one report the same value.
How rubric 1.0.0 prices a screen resolution
Nine sizes carry an explicit prior and everything else falls to 0.004. 1920x1080 is assumed at 0.22 and costs 2.18 bits. 1536x864 and 1366x768 sit at 0.07, 1440x900 and 2560x1440 at 0.05, 1280x720 and 3840x2160 at 0.03, and the two MacBook-shaped sizes 1512x982 and 1728x1117 at 0.02. Anything not on that list — an ultrawide, a rotated panel, a spoofed geometry, a second monitor set as primary — is a flat 7.97 bits with no gradient underneath it.
The spread between the cheapest and the dearest outcome is 5.78 bits, and that spread is the whole of what this column can ever do to a total. Where the four band edges sit →
Every outcome this rule can produce
This is the printed envelope, written out. The pen cannot land outside it, because these are
all the answers rule screen has.
| Outcome | Assumed p | −log₂p |
|---|---|---|
| 1920x1080 modal outcome — the printed line | 0.220 | 2.18 |
| 1536x864 | 0.070 | 3.84 |
| 1366x768 | 0.070 | 3.84 |
| 1440x900 | 0.050 | 4.32 |
| 2560x1440 | 0.050 | 4.32 |
| 1280x720 | 0.030 | 5.06 |
| 3840x2160 | 0.030 | 5.06 |
| 1512x982 | 0.020 | 5.64 |
| 1728x1117 | 0.020 | 5.64 |
| 3440x1440 any size not on the rule's list | 0.0040 | 7.97 |
What changing a screen resolution costs
Screen resolution is grouped with pixel ratio and colour depth, so whichever of the three carries the most surprisal counts in full and the other two are charged at 35%. Moving off the tail into 1920x1080 saves you 5.79 raw bits, but if the pixel ratio is the dominant member in your pass you keep only 35% of that saving. And a declared screen that does not divide sensibly by the declared pixel ratio is a geometry no real display produces.
The rubric's own reasoning, verbatim
A handful of resolutions cover most of the web; everything else is a long tail. 1920x1080 is treated as the single most common, common laptop sizes next, anything unlisted as tail.
What moves it
Resizing a window does not move it — this is the screen, not the viewport. A different monitor, a spoofed screen size, or a change in OS display scaling does.
Where this prior is weakest
Nine sizes get a real prior and everything else falls off a cliff to 0.004. There is no gradient. A 3440×1440 ultrawide and a 1600×1000 laptop are priced identically at 8 bits despite one being far commoner than the other, and this is where a measured table would help most.
Correlation
Grouped with Device pixel ratio and Color depth under "display". Whichever of them carries the most surprisal in a given pass takes full weight; the others take 35%. The chart draws the short stroke rather than describing it.
How the correlation discount works →
Challenge it
If you have a source that contradicts this assumption, the honest thing is to say so in
public against this specific prior. Open a challenge
against screen →
What people ask about a screen resolution
Answered from rubric 1.0.0 itself. Where an answer quotes a probability, that probability is a constant in the shipped scoring code and is printed in the table above.
- Does resizing my browser window change my score?
- No. The rule reads screen.width and screen.height, which describe the display, not the viewport. Window size, zoom state and whether the developer tools are docked are invisible to this column.
- Why does my 4K monitor report a smaller resolution?
- Because the value is in CSS pixels, after the operating system display scale has been applied. A 3840x2160 panel at 150% scaling reports 2560x1440, and both of those sizes are on the rule list with different priors.
- Is an unusual resolution worth more than a common one?
- Under this rubric, yes: anything not among the nine listed sizes is priced at 0.004 and costs 7.97 bits. That is the coarsest cliff in the table and it is drawn on the chart form as a single flat envelope ceiling rather than hidden.
Where to read next
- The prior for device pixel ratio — the other reading the display group discounts this one against.
- The prior for color depth — the other reading the display group discounts this one against.
- The complete prior table for all 13 columns — every rule, every outcome, and the rationale the rubric ships with each one.
- Assumed and counted: what a prior is, what the counted column beside it measures, and why the two are never added.
- Compare two passes for the delta on this column — change one setting and read what actually moved, instead of guessing from a total.
Where the pens move
Knowing which prior is weak is only useful if something can actually move the signal.
Engine level, not JS level. Donut Browser spoofs through CDP injection in its Wayfern Chromium fork, so the value a page reads is the value the engine reports — there is no patched accessor to catch.
It refuses to contradict itself. A profile whose proxy exit geography, time zone or language disagrees with its fingerprint does not launch. That is a pre-launch gate in the app, not advice in a manual.
Open, and quiet. AGPL-3.0, desktop app and sync server both in the repository, and no analytics SDK anywhere in the source. macOS, Windows, Linux.