Typical viewing-distance differences across phone, desktop, TV, and in-vehicle displays

What it is

Visual-angle conversion needs an actual distance number to produce a result — this entry provides that number: phones sit at roughly 25-40cm (a handheld, arm-bent distance), desktop monitors at roughly 50-70cm (an extended-arm distance under typical seated desk posture), TVs are commonly referenced at "10 feet" (roughly 3m), and an in-vehicle center display, while its physical distance is usually under a metre and superficially close to desktop range, is used in a fundamentally different way. These figures are typical values, not constants — each device category has its own reason for the distance it has, plus its own extra usage constraints.

Why it happens

These typical distances are set by each device's usage posture and physical placement. A phone sits at arm-bent distance because that's the comfortable range for holding and reading a small handheld device. A desktop monitor's distance is set by desk depth and conventional seated posture. A TV's distance is set by common living-room furniture layout, typically placed across a room at a distance on the order of several metres. An in-vehicle center display's distance is set by fixed dashboard and seat geometry — superficially not much farther than a desktop — but the driver must glance at it briefly between driving-attention demands rather than fixating on it continuously the way one looks at a desktop monitor. That means even when the raw distance numbers are similar, the actual "information-extraction time budget" usable in the vehicle scenario is far smaller than in the desktop scenario, and size/contrast design needs to compensate for glance duration, not just distance.

Studying it

• Field/observational measurement of actual usage distance: using depth cameras or self-report to measure the real distribution of how far users actually hold phones or sit from monitors and TVs — the result is a distribution, not a single number, and it's this distribution that underlies each device category's actual size guidelines.
• Glance-duration research for in-vehicle scenarios: automotive HMI research specifically measures the duration and frequency of a driver's single glance at the center display; this data matters as much as distance data, since the usable information in an in-vehicle scenario is set by glance duration, not by raw viewing distance alone.
• Typical independent variables: device category, measured distance distribution, (for vehicles) glance duration.
• Typical dependent variables: actually reported/measured viewing distance, glance duration and frequency, the recommended minimum size derived at that distance.

Where it stops holding

• These are typical values, and real individual and postural variation exists and can be substantial (the same phone might be held 15cm away to check detail, or kept at arm's length while scrolling a feed; the same living room's TV viewing distance varies with furniture layout) — a design that satisfies only the "typical" distance can fail for users at the edge of that distribution, so these numbers should be treated as central estimates needing margin, not guaranteed values.
• Looking only at the distance number for in-vehicle scenarios understates the real constraint — glance duration and split attention are the real additional limit in that category, and applying visual-angle conversion using distance alone will systematically underestimate the size and contrast an in-vehicle display actually needs.
• These reference distances shift as product form factors change (foldables, larger phones, ultra-wide monitors all shift the typical usage distance for their category) — they are not permanent physical constants, and should be periodically re-validated against how current-generation devices are actually used rather than treated as fixed figures to rely on indefinitely.

Applying it

• When no product-specific measured data exists, use these reference distances as the default input to visual-angle conversion, but treat them as defaults to validate rather than final answers — measure actual usage distance for the specific product and context when feasible (e.g. a specific vehicle model's dashboard geometry, or actual holding distance from user research on a specific phone form factor).
• For glance-limited scenarios like in-vehicle displays, set size and contrast specs more generously than a pure distance-based conversion would suggest, to compensate for short glance duration, rather than assuming the driver can fixate continuously the way they would on a desktop screen.
• Verification: validate final size specs against the actually measured distance; for glance-limited scenarios, test legibility under a bounded glance-duration constraint (not unlimited viewing time), confirming the design still holds up under the real usage rhythm.

Related

• Same group: A1.16.1 Visual angle unifies physical size and viewing distance into one quantity · A1.16.2 Cross-device size specs must be converted on a visual-angle basis
• Nearby: A1.03.2 Font size only means something when specified jointly with viewing distance · A1.01.4 Viewing distance changes directly alter how much content the effective field of view covers
• Search terms: viewing distance · 10-foot UI · glance duration · arm's length viewing