Description
About Display Information
Introduction
The DeviceHub Display Information tool is a free online display capability signal reader that focuses on what the web can say about color gamut, HDR-related media queries, multi-screen hints such as isExtended-style signals when available, and coarse refresh-related hints, without duplicating Screen Information’s geometry job, without replacing Screen Resolution’s layout trio, and without absorbing Display category visual laboratories like HDR Test, Refresh Rate Test, Color Test, or Dead Pixel Test. Colorists checking whether matchMedia thinks the page is in a wide gamut, support staff capturing HDR boolean rows, developers feature-detecting before shipping HDR canvases, IT verifying extended desktop detection hints, and educators teaching Screen versus Display vocabulary all land here for capability prose. DeviceHub’s rule: screen equals geometry; display equals gamut/HDR/isExtended/refresh hints. Cross-link Screen Information and Screen Resolution for sizes and viewports. Cross-link HDR Test for perceptual HDR drills, Refresh Rate Test for rAF Hz estimates, Color Test and Gamma Test for visual judgment, this page will not re-implement those UIs. Pair with Device Information for hub context and GPU Information when GL renderer strings matter more than panel HDR flags. Permissions stay none for media-query and non-permissioned hint reads; privileged Window Management screen details may be mentioned only as out-of-scope or limited honesty rather than required flows. OS HDR toggles off while the panel is HDR-capable yields false media results, document OS state. Wide-gamut false on inexpensive panels is expected. Schools should stop calling every monitor tool “screen test” interchangeably; DeviceHub IA separates them on purpose. Display capability questions clog geometry tickets when IA is unclear; Display Information exists so gamut, HDR media, multi-screen hints, and coarse refresh-related signals have a Hardware home that refuses to become another screen.width article. Color scientists checking matchMedia against OS HDR toggles, streaming PWAs deciding whether to fetch HDR canvases, IT validating extended desktop detection at a feature level, educators drilling Screen versus Display vocabulary, and support staff capturing boolean rows before opening visual Display tests all start here. DeviceHub’s hard split remains: screen equals geometry on Screen Information and Screen Resolution; display equals capability hints here; visual proof stays in Display category tools such as HDR Test, Refresh Rate Test, Color Test, Gamma Test, and Contrast Test. Cross-links are mandatory in copy so users do not think a false HDR media query means DeviceHub failed to flash HDR patterns, those patterns live on HDR Test. GPU Information remains the place for WebGL renderer strings, including SwiftShader caveats, when the pipeline, not the panel flag, is broken. Permissions stay none for default media-query reads; privileged multi-screen detail APIs are described as limited or out of default scope rather than silently prompted. Mixed SDR/HDR docks require moving the window and retesting. Schools should update worksheets that say screen test for every monitor topic. DeviceHub will not claim calibrator accuracy. Browser differences in color-gamut support are expected and useful.
What this tool does
Display Information evaluates CSS media features and related display capability surfaces, for example color-gamut comparisons, dynamic-range or HDR-related queries where supported, and multi-screen extended hints when readable without breaking the none-permission posture, and presents them with explicit “not a calibrator” labeling. It may note refresh-related hints only as secondary web signals and immediately point to Refresh Rate Test for honest rAF measurement limits. It does not draw gradients, does not flash Hz patterns, does not detect dead pixels, and does not measure contrast ratios, those remain Display category tools. Compared with Screen Information, there is little width/height teaching here beyond redirects. Permissions none. Users enabling HDR in Windows Display settings should retest afterward. Browser differences in media-query support are called out. GPU tone-mapping paths can disagree with panel marketing, GPU Information sits beside, not inside, this page. The tool evaluates display-oriented CSS media features and related hints, shows color gamut and HDR-related results when queryable, surfaces multi-screen extended hints when available without breaking none-permission posture, and mentions refresh only with immediate redirection to Refresh Rate Test for honest rAF estimates. It does not draw color sweep animations, does not count dead pixels, and does not measure contrast. Geometry seekers get redirected in the first screen of guidance. Permissions none. After Windows HDR toggles, users should reload or re-run evaluations. Safari versus Chromium gaps are labeled platform limits. Notes separate panel marketing HDR from browser media-query belief. GPU tone mapping issues stay cross-linked, not duplicated.
When to use it
Use Display Information when shipping color-managed web content, when tickets ask “does the browser think HDR is on,” when extended multi-monitor hints matter at a feature-detect level, and when IA needs a Hardware capability URL distinct from geometry. Prefer Screen Information/Screen Resolution for pixels and avail area. Prefer HDR Test when humans must see highlight roll-off. Prefer Refresh Rate Test when Hz smoothness is disputed. Prefer Color Test/Gamma/Contrast tools for visual panels. Prefer GPU Information for WebGL strings. Avoid calibrator claims. Avoid assuming color-gamut: p3 means factory-proof P3 coverage. Retest after moving the window across mixed SDR/HDR monitors. Use in QA matrices beside OS HDR screenshots. Use when implementing color-managed web previews, when verifying OS HDR is reflected in media queries, when extended desktop hints matter for window placement features, and when Hardware IA needs a capability slug. Prefer Screen Information for sizes and orientation. Prefer Screen Resolution for layout viewport narratives. Prefer HDR Test for perceptual checks. Prefer Refresh Rate Test for Hz smoothness disputes. Prefer Color and Gamma tools for visual grading aids. Prefer GPU Information for GL strings. Avoid factory calibration claims. Avoid treating p3 queries as spectrophotometer proof. Retest across monitors. Use in QA matrices with OS HDR screenshots attached beside DeviceHub rows.
How it works
CSS media queries such as (color-gamut: p3) and dynamic-range features let pages adapt without EDID parsers. Browsers answer based on their understanding of the current output path, often influenced by OS HDR mode and ICC profiles, not by DeviceHub opening a hardware meter. isExtended-style multi-screen hints, when present, indicate multiple screens from the browser’s point of view and still are not a full permissioned Screen Details inventory unless product flows explicitly add those (out of default none scope). Refresh hints on the open web are incomplete; requestAnimationFrame timing tools in Display category remain the practical estimate with documented compositor caveats. DeviceHub permissions stay none for this capability readout. Secure HTTPS. No upload of gamut flags on view. Fingerprinting via display capabilities exists, copy carefully. Screen versus Display split keeps geometry pages from bloating with HDR essays and keeps HDR essays from re-teaching screen.width. matchMedia queries against color-gamut and dynamic-range style features return boolean matches based on the browser’s view of the current output configuration. That view depends on OS HDR mode, ICC profiles, and engine support, not on DeviceHub controlling the panel. Multi-screen hints such as isExtended-like signals, when readable, indicate more than one screen from the browser’s perspective without necessarily enumerating EDID names. Full Screen Details / Window Management flows may require permissions DeviceHub does not demand on this default page, honesty copy says so. Refresh-related web signals are incomplete; Display category rAF tools document compositor and vsync caveats properly. DeviceHub permissions none. Secure HTTPS. No capability upload on view. Fingerprinting via display features is real, minimize public pastes. Maintaining Screen versus Display separation prevents geometry pages from absorbing HDR essays and prevents HDR essays from re-teaching availWidth.
Step-by-step instructions
- Enable the OS display mode you care about (HDR on or off), place the window on that monitor, and open Display Information over HTTPS.
- Record color gamut and HDR-related media results with browser and OS HDR state noted in the same sentence.
- Note multi-screen or extended hints only as browser feature signals, not as a complete monitor asset list.
- For width/height/avail/orientation, open Screen Information; for layout viewport storytelling, open Screen Resolution.
- For visual confirmation, continue to HDR Test, Refresh Rate Test, Color Test, or related Display tools, do not stop at booleans when perception matters.
- Paste capability rows labeled as media-query/browser hints, not calibrator certificates.
Common problems
HDR monitor with OS HDR disabled yields false. Geometry seekers using the wrong tool. Assuming p3 media query equals full P3 volume. Refresh hint disagreement with marketing 144 Hz, use Refresh Rate Test and still expect compositor limits. Mixed DPI/HDR docks confusing which display the tab uses, move the window. Safari versus Chrome media-query gaps. GPU Information SwiftShader sessions with odd HDR flags. Expecting dead pixel detection here. Calibrator users disappointed, send to hardware probes. isExtended false on single-monitor laptops mistaken for bugs. Remote desktop color virtualization lies about gamut. HDR panel with OS HDR off. Geometry users on wrong tool. p3 query overread as full gamut volume. Refresh hint versus 144 Hz marketing, use Refresh Rate Test. Mixed docks. Engine media-query gaps. SwiftShader sessions with odd flags, check GPU Information. Dead pixel expectations. Calibrator disappointment. isExtended false on single displays. Remote desktop virtualization lying about gamut. Assuming Display Information replaces Color Test. Expecting Hz analyzer precision.
Privacy explanation
Display capability flags contribute to fingerprinting. DeviceHub displays locally without ad upload on view. Permissions none for default hint reads. Prefer omitting unnecessary flags from public posts. Tab close ends evaluation. We do not force privileged multi-screen permission prompts for casual visits. Combine with screen geometry carefully. Classroom: Screen versus Display ethics and privacy. Capability flags fingerprint. DeviceHub shows locally, no ad upload on view. Permissions none for default reads. Omit unnecessary flags from public posts. Tab close ends evaluation. No forced privileged multi-screen prompts on casual visits. Combine with geometry carefully. Classroom: Screen versus Display privacy. Prefer visual tests only when needed so you do not always create extra fingerprintable interactions.