fileformer
search⌘KtranslateENexpand_moreupload_fileConvert
Converters8 file families · 44 direct conversions
What changes in a conversionarrow_forward
home/calculators/screen-size

How big is a 27-inch screen, really? And how sharp?

Screens are sold by their diagonal, which hides the width, height and sharpness. Enter a size and resolution to get pixel density, the real dimensions, and the distance at which you stop seeing individual pixels.

diagonal27″ · 69 cm
resolution
×
common screens
Phone6.1″ · 2556×1179Tablet11″ · 2388×1668Laptop14″ · 2560×1600Office monitor24″ · 1920×1080Monitor27″ · 2560×14404K monitor32″ · 3840×2160Ultrawide34″ · 3440×1440TV65″ · 3840×2160
cminches
pixel density109 ppiwidth59.8 cmheight33.6 cmpixel size0.233 mm
2560 × 144059.8 cm33.6 cm
A4 sheet
Area 2010 cm². Typical desktop density. Text looks fine, but individual pixels show up close.
~/sharp-enough

Sharpness depends on how far away you sit.

An eye with normal vision separates details about one arcminute apart. Beyond a certain distance, pixels blur together and extra resolution is wasted. The line shows where that happens for the screen above, and where each kind of screen is normally used.

pixels visiblelooks smooth
phonelaptopdesk monitorTV sofa
10 cm25 cm50 cm1 m2 m4 m
At 109 ppi, pixels blend together beyond about 80 cm. A monitor is usually used at about 70 cm, so at that distance you may notice the pixels.
~/diagonals-mislead

Same diagonal, different amount of screen.

A wider shape spreads the diagonal sideways, so a 27-inch ultrawide has less area than a 27-inch 16:9, and a 4:3 has the most. These are drawn to scale at your diagonal.

16:9reference59.8 cm × 33.6 cmMost monitors and TVs. The default for video.
16:10+5% area58.2 cm × 36.3 cmCommon on laptops; a little taller, handy for documents.
4:3+12% area54.9 cm × 41.1 cmTablets and older monitors. The most area for a given diagonal.
21:9-16% area63.2 cm × 26.7 cmUltrawide. Great for timelines and games, but less area than the number suggests.
~/measure-this-screen

A web page can’t know how big your screen is. A bank card can.

Browsers report pixels, never millimetres: CSS fixes 1 inch at 96 CSS pixels whatever the real size. Every payment card is the same ISO/IEC 7810 ID-1 size, 85.60 × 53.98 mm. Hold one against the screen and resize the outline until it matches. From that one measurement this page works out your real pixel density, your screen’s diagonal, and how long a CSS “inch” really is here.

85.60 × 53.98 mm
−+
Outline is 323.5 CSS px wide. At the nominal 96 px per inch a card would be 323.5 px; yours differs by 0.0%. Browser zoom changes CSS pixel size, so leave zoom at 100%.
CSS pixels per mmoutline width ÷ 85.60 mm3.779
CSS pixels per real inchnominal is 9696.0
devicePixelRatiodevice pixels per CSS pixel1
physical pixel densityCSS px per inch × dpr96 ppi
screen in CSS pixelsscreen.width × screen.height800 × 600
screen diagonaldiagonal pixels ÷ CSS px per inch10.4″ · 26.5 cm
one CSS “inch” here96 CSS px measured2.5 cm
inputLoad 10.5″ · 800 × 600 into the calculator
CSS 1in96 pxFixed by CSS 2.1 in 2011 and CSS Values 4. Physical units (cm, mm, in, pt) are all defined from px, so none of them is truly physical on screen.
reference pixel0.0213°The visual angle of one pixel at 96 dpi viewed from 28 in (71 cm). Browsers and operating systems scale so a CSS px looks roughly this size.
printexactOn paper the mapping is real: 1in prints as 25.4 mm, so 96 px is one printed inch. The approximation only applies to screens.
~/pixels-per-degree

Pixels per inch is the wrong unit. Your eye counts pixels per degree.

How sharp a screen looks depends on how many pixels fit in one degree of your view, which mixes density with distance. An eye that resolves details one arcminute apart (20/20) needs 60 pixels per degree before pixels disappear; sharper eyes need more. Set your eyesight and distance; the figures use the screen from the calculator above.

20/1020/1620/2020/2520/40
this screen at 70 cm52 ppdBelow what 20/20 eyes resolve: pixels can be seen.
needed for 20/2060 ppd1 arcmin per pixel. the clinical standard.
pixels vanish beyond80 cmFor this screen and eyesight. Closer than this, pixel structure is resolvable.
resolution needed here2935 × 1651At 27″ and 70 cm, 125 ppi. You have 109 ppi (87%).
Common screens at their usual distancebar shows ppd; needed 60 for 20/20
Phone6.1″ · 2556×1179461 ppi111 ppdat 35 cm
Tablet11″ · 2388×1668265 ppi73 ppdat 40 cm
Laptop14″ · 2560×1600216 ppi81 ppdat 55 cm
Office monitor24″ · 1920×108092 ppi41 ppdat 65 cm
Monitor27″ · 2560×1440109 ppi52 ppdat 70 cm
4K monitor32″ · 3840×2160138 ppi71 ppdat 75 cm
Ultrawide34″ · 3440×1440110 ppi57 ppdat 75 cm
TV65″ · 3840×216068 ppi116 ppdat 2.50 m
Find your own acuity on this screenEach panel alternates single device pixels, then pairs, then triples. Step back until the left panel turns a flat grey, measure the distance from your eyes, and enter it. The calibration above supplies the pixel size, so calibrate first.
1 px2 px3 px
your resolving angle-
Snellen equivalent-
One device pixel here is 0.265 mm, based on the calibration above.

Display scaling for 2560 × 1440 at 27″, viewed from 70 cm

A CSS reference pixel at this distance is 0.260 mm. Ideal scale: 112%.
100%closest2560 × 1440 workspaceUI at 90% of referenceclose to the intended size
125%closest2048 × 1152 workspaceUI at 112% of referenceclose to the intended size
150%closest1707 × 960 workspaceUI at 134% of referencelarge, less on screen
175%closest1463 × 823 workspaceUI at 157% of referencelarge, less on screen
200%closest1280 × 720 workspaceUI at 179% of referencelarge, less on screen
~/what-the-monitor-tells-the-computer

128 bytes describe your monitor to the computer.

Every monitor holds an EDID block that the computer reads over the cable: who made it, its physical size, colour primaries and native timing. This builds a valid EDID 1.4 base block for the screen in the calculator, with the native mode timed by VESA CVT reduced blanking. Click a region to decode it, or download the .bin and open it in edid-decode.

60 Hz75 Hz120 Hz144 Hz
downloadedid.bin
00:00FFFFFFFFFFFF0018CD012701000000
10:28240104A53C227806EE91A3544C9926
20:0F505400000001010101010101010101
30:010101010101565E00A0A0A029503020
40:350056502100001A000000FD00303C58
50:5919000A202020202020000000100000
60:000000000000000000000000000000FC
70:0046494C45464F524D455220323700F2
Native timing (DTD)bytes 54-71
pixel clock241.50 MHz (24150 × 10 kHz)
active2560 × 1440
blanking160 px · 41 lines
h front porch / sync48 / 32 px
v front porch / sync3 / 5 lines
image size598 × 336 mm
syncdigital separate, H+ V− (0x1A)
HeaderManufacturerProduct codeSerialWeek and yearVersionVideo inputPhysical sizeGammaFeaturesColour primariesEstablished timingsStandard timingsNative timing (DTD)Range limitsDummy descriptorMonitor nameExtensionsChecksum
pixel clock241.50 MHz
total frame2720 × 1481
line rate88.79 kHz
blanking overhead9.3%
size, whole cm60 × 34
checksum0xF2 · ok
check_circleValid EDID 1.4 base block. The native 2560 × 1440 at 60 Hz mode fits the detailed timing descriptor.
~/reference

What the number on the box measures.

The quoted diagonal means different things for different products, and no two layers of the stack store size the same way.

wherewhat the size meansexample
CRT monitor or TVDiagonal of the glass tube. The visible picture was about an inch smaller, so spec sheets added a “viewable” figure.17″ tube ≈ 16″ viewable
LCD and OLED monitorDiagonal of the active area. Marketing rounds it.23.8″ panel sold as 24″
TV (US)Sold as a size “class”; the viewable diagonal can be slightly smaller.65″ class ≈ 64.5″ viewable
PhoneDiagonal of the full rectangle, before rounded corners and cut-outs are removed.6.1″ rectangle, less actual area
LaptopActive panel diagonal, often rounded to the nearest inch in the product name.14.2″ panel in a “14-inch” laptop
EDID bytes 21-22Maximum image size in whole centimetres.this screen: 60 × 34 cm
EDID detailed timingImage size in millimetres, 12 bits per axis.598 × 336 mm
CSS1in is always 96 px; real size depends on the device and scaling.1in here ≈ 2.5 cm

Display identification standards

EDID 1.01994Introduced with VESA DDC so monitors could identify themselves over the VGA cable.
EDID 1.11996Reused unused fields for more descriptors.
EDID 1.21997Added monitor name and range-limit descriptors.
EDID 1.32000Made descriptors and preferred timing mandatory; long the most common version.
EDID 1.42006Added digital interface and colour depth fields, and redefined the size bytes so they may give an aspect ratio instead.
CTA-861from 2002Extension blocks for HDMI audio, video modes and HDR metadata.
DisplayID 1.x2009Variable-length successor with timings beyond EDID’s 12-bit and 655 MHz limits.
DisplayID 2.02017Designed for high resolutions, HDR and tiled displays.

Timeline

1984The Macintosh ships a 72 ppi screen, so one point equals one pixel.
1987IBM’s VGA brings 640 × 480 with square pixels to PCs.
1994VESA publishes DDC and EDID 1.0.
1996CSS1 defines px as relative to the viewing device.
2003VESA CVT 1.0 adds reduced-blanking timings for flat panels.
2006EDID 1.4 is published.
June 2010Apple launches the iPhone 4’s 326 ppi “Retina” display, claiming pixels vanish at 10-12 inches.
2011CSS 2.1 becomes a Recommendation, fixing 1in = 96px and defining the reference pixel.
2012The Retina MacBook Pro brings 220 ppi and 2× scaling to laptops.
2013CVT 1.2 adds reduced blanking version 2; consumer 4K monitors appear.
2017DisplayID 2.0 is published.
2020s4K at 27″ (163 ppi) and 5K at 27″ (218 ppi) become common desk screens.