Show HN: 1080p is 920px tall – 1k real browser viewports
zenpe
41 points
20 comments
September 14, 2026
Related Discussions
Found 5 related stories in 83.1ms across 6,607 title embeddings via pgvector HNSW
- Show HN: I built a hand-modeled 3D Windows 98 portfolio with Three.js Abstract2D · 13 pts · September 11, 2026 · 51% similar
- Why tiny JPEGs look different in Chrome gutechh · 283 pts · August 12, 2026 · 47% similar
- Ask HN: Good large format (>20 inches) touchscreen E-Paper display options? foota · 12 pts · August 25, 2026 · 46% similar
- Show HN: Manim (3Blue1Brown's animation engine) in the browser via WebGPU sinaatalay · 46 pts · July 29, 2026 · 46% similar
- Show HN: A techno machine in one HTML file, with verifiable renders ssx360 · 187 pts · August 24, 2026 · 46% similar
Discussion Highlights (11 comments)
orielhaim
yeah the 1920 by 920 finding matches what I keep hitting browser chrome quietly eats the height and layouts built for 1080 start clipping
unnah
Only showing the most common values means that sizes of non-maximized windows are lost in the noise. It would be nice to see a cumulative size distribution that would show the percentage of viewport widths smaller than x, for various values of x. Then a developer could easily see that if they make the content e.g. 900 pixels wide, what percent of users will have to scroll the viewport left/right.
bcjdjsndon
Web development is such a mess man, it's all one bit hack trying to make programs out of documents
thisismyopinion
Claude slop design. Untrustable.
MyFirstSass
This is slop that looks like it was made with a single prompt
matsemann
I've never found it that useful to see a list of numbers of sizes. I can't visualize them quickly, and in the end the exact pixels doesn't matter, it's the various ratios. I made this ~15 years ago. Took all the common phone resolutions at the time and scaled so that they all were similarly tall. Then it gave me a good grasp on what aspects my game needed to support. https://imgur.com/a/JT5JyyH
Aldipower
Interesting information, but useful? No. You need to layout this way _no-one_ is excluded.
Zobat
There's people here devaluing this because "AI probably built this page". To me this is a perfectly valid use of AI; "Hey I got this set of data points, give me a page with these 'extractions'". The page layout is the least interesting part of the page, it's the data points that should be of interest, then again this is where I think the page is lacking. "1k real browser viewports" (page says 751 data points) tells me it's a quite small sample size to draw the amount of conclusions they draw. Now this is me guessing but I think it might be people actually visiting their site. Probably in the quest for viewport size, this might be why a whopping 6 percent of visitors appear to be visiting with their browser in full screen mode, and almost as many from a device with an 800x600 resolution (I can hear the device owners friend asking "man, what resolution are you running that thing at? Go to this site and check!"). AI report on actual data, not a problem. Low quality data to actually run that report on, now there's your problem.
loloquwowndueo
lol if you think the menu and native toolbar eating 160px is bad, you didn’t live through the 90s/2000s hell of bonzi buddy, yahoo search bar, and others, I remember people peeking at the web through a 120px slit, hilarious
IsTom
Why'd 800x600 be this popular? Is this some specific device? Is this 90s? Seems suspicious to me.
nnevatie
Brought to you by Claude.