How to Check Screen Resolution

Screen resolution is the pixel count of your display—width by height—before UI scaling multiplies logical units. Knowing the native resolution helps when capturing screenshots for docs, choosing wallpaper, and debugging responsive layouts. Each operating system exposes it in Display settings; developers also check window.devicePixelRatio in the browser. /tool/screen-resolution reports what the browser sees, including scale factor effects. Fractional scaling on Windows 125% or 150% changes effective CSS pixels—developers should log both screen.width and devicePixelRatio when reproducing layout bugs. External GPU docks can limit max resolution on older USB-C cables; if 4K looks unavailable, try the monitor’s HDMI port directly before blaming the laptop panel. Game engines and creative apps show internal render resolution separate from desktop Display settings—check both when diagnosing blur. Screen sharing in meetings downscales your output; presenters should share slides full-screen rather than a tiny window scaled on a 4K panel. VMware and Parallels guests report the scaled window size—full-screen the VM before measuring for guest OS apps. Ultrawide monitors list custom resolutions; use the monitor OSD to confirm you are on the panel native timing, not an interpolated stretch mode that softens text. Color-managed workflows need resolution and scaling documented together—designers proof at 100% scaling even if daily work uses 125%. KVM switches sometimes cap at 1080p; read the switch spec before filing a laptop warranty claim. Accessibility zoom magnifies logical pixels without changing reported screen width—note zoom level in bug repro steps alongside resolution. Dual GPU laptops switch outputs when unplugged; reconnect the external monitor and re-read Settings after graphics handoff completes. Print the Display settings screenshot into IT tickets when remote helpdesk asks for proof of scaling issues. QA matrices should list OS, scaling, and browser version together because layout bugs often require that triple to reproduce.

Windows Display settings

Settings → System → Display. Scroll to Display resolution and read values like 1920 × 1080 or 2560 × 1440. Scale (125%, 150%) is separate—it affects text size, not the underlying panel pixels. Advanced display lists refresh rate; higher Hz helps motion, not layout width.

macOS

System Settings → Displays. Default resolution matches the panel’s native pixels on Retina screens; macOS may label it as “looks like” 1440 × 900 while backing store is higher. Hold Option and click Scaled to see more modes. Screenshot utilities capture at device pixels when configured.

Linux desktop environments

GNOME Settings → Displays shows resolution per monitor. KDE System Settings → Display and Monitor mirrors that. xrandr --query in a terminal lists connected outputs and modes for X11 sessions.

Multiple monitors

Each display has its own resolution. Extend desktop versus mirror mode changes whether both share one framebuffer. Move windows to the monitor you are measuring before reading size in an app.

Browser tool

Open /tool/screen-resolution to read viewport size, screen size, and pixel ratio as reported to JavaScript. Compare to OS settings when CSS breakpoints misbehave—HiDPI can make 1920 logical with 3840 physical pixels.

Remote desktop caveat

RDP and VNC often report the session size, not the physical monitor at the remote site. Test locally when calibrating design mockups.

Designers and QA workflows

Capture resolution in bug reports when layout breaks “only on 1366×768” laptops. Responsive breakpoints should be tested at native resolution plus common scaled modes. Emulator devtools approximate phones but not Windows scaling quirks—real hardware still matters.

Projectors and conference rooms

Mirrored laptop-to-projector setups may downscale to 1280×720 for cable compatibility. Presenters who expect 4K canvas should verify what the room EDID negotiates before demo day.

Final checks

Screenshot tools on Retina Macs may save at 2× pixel dimensions—note that in bug tickets so engineers do not chase a non-bug. Web designers should test at both 100% and 125% Windows scaling because font rendering shifts subtly. Document your test machine resolution in QA templates next to browser version.

FAQ

Is 4K always 3840×2160? Consumer 4K UHD is; some cinema 4K widths differ—check your panel spec. Why does my screenshot look huge? Retina or fractional scaling captures more pixels; export at intended display size for docs.

Can I change resolution safely? Stay at recommended/native when possible; odd modes can blur on LCD panels. Does the FileToolsHub tool see ultrawide correctly? It reports browser screen API values available in your session.