PPD

Also known as: Pixels per degree

On this page 7

PPD, short for pixels per degree, is the number of display pixels that fall within one degree of the user’s visual angle in a headset or other near-eye display. In XR displays & optics, PPD is the most meaningful measure of perceived sharpness, because it combines panel resolution with the field of view that the lenses spread those pixels across.

Resolution figures alone can mislead: two headsets with identical panels look very different if one has a wider field of view. PPD answers the question a user actually cares about, namely how much detail the eye receives, and it relates directly to the limits of human vision.

How pixels per degree is calculated

Pixels per degree is calculated, in its simplest form, by dividing horizontal pixels per eye by the horizontal field of view in degrees. A panel with 2000 horizontal pixels per eye spread across 100 degrees gives an average of 20 PPD.

That average hides an important detail. XR lenses do not distribute pixels evenly: most designs concentrate more pixels per degree in the center of the lens and fewer toward the edges, partly because of lens distortion and its software correction. Manufacturers therefore often quote peak or center PPD, which is higher than the simple average and better reflects what the user sees when looking straight ahead.

MeasureHow it is obtainedWhat it tells the user
Average PPDHorizontal pixels divided by horizontal FOVRough overall comparison
Center PPDMeasured or modeled at the optical centerSharpness when looking straight ahead
Edge PPDMeasured toward the peripheryClarity when eyes look sideways
Effective PPDAccounts for blur, subpixels and renderingReal detail delivered to the eye
Ways PPD is reported

Effective PPD can be lower than the nominal figure. Lens blur, a PenTile subpixel layout that shares subpixels between pixels, or rendering below native resolution all reduce the detail actually delivered, even when the panel has many pixels.

PPD and the limits of human vision

PPD matters because it can be compared directly with visual acuity. A person with standard 20/20 vision resolves detail of about one arcminute, which corresponds to roughly 60 pixels per degree. A display reaching that value is often described as retinal resolution, since individual pixels can no longer be distinguished.

PPD rangeTypical device classPerceived result
About 10 to 15Early consumer VR headsetsVisible screen-door effect, hard-to-read text
About 20 to 25Current mainstream standalone headsetsUsable text at larger sizes, mild softness
About 30 to 40High-end micro-OLED headsetsComfortable reading, fine detail visible
About 60 or moreSpecialized professional headsetsClose to the limit of 20/20 vision
Typical PPD levels and their perceptual effect

Human acuity is high only in the fovea, the central two degrees or so of vision, and falls steeply toward the periphery. That is why foveated rendering and some experimental dual-display designs concentrate high PPD only where the user is looking.

PPD compared with other display metrics

PPD is often confused with resolution per eye and pixels per inch (PPI), but each answers a different question. Understanding the difference prevents misleading comparisons between headsets and between headsets and monitors.

MetricWhat it measuresLimitation for XR comparison
Resolution per eyeTotal pixels on each eye’s panelIgnores how widely pixels are spread
PPIPixel density on the physical panelIgnores lens magnification
Field of viewAngular size of the visible imageSays nothing about sharpness
PPDPixels per degree of viewAverage figure hides center-to-edge variation
PPD and related display metrics

PPD also makes headsets comparable with monitors. A 27-inch 4K monitor viewed from about 60 centimeters delivers well over 60 PPD at the center of the screen, which explains why reading text on a virtual monitor in a headset still feels less crisp than on a good physical display.

The trade-off between PPD and field of view

With a fixed panel, PPD and field of view pull in opposite directions. Widening the field of view spreads the same pixels over more degrees and lowers PPD; narrowing it raises PPD but reduces immersion. Headset designers choose a balance according to the intended use.

  • Gaming and immersion favor a wider field of view, accepting moderate PPD.
  • Productivity and text work favor higher PPD, accepting a narrower view.
  • Simulation and training often demand both, which leads to expensive high-resolution panels.
  • Optical design such as pancake lenses improves edge clarity, raising usable PPD across the view.

Raising PPD has a performance cost. Doubling PPD in both directions with the same field of view requires about four times as many pixels, so the GPU must render far more. This is a key reason why eye-tracked foveated rendering accompanies most high-PPD headsets.

Common mistakes when interpreting PPD

PPD is a valuable metric, but a single figure rarely tells the whole story. Several frequent mistakes lead to wrong conclusions when headsets are compared on specification sheets.

MistakeWhy it misleadsBetter approach
Comparing center PPD with average PPDCenter values are always higherCompare like with like
Ignoring field of viewHigh PPD may come from a narrow viewCheck both figures together
Ignoring rendering resolutionApps may render below panel resolutionCheck default render settings
Ignoring lens qualityBlur lowers effective detailEvaluate edge-to-edge clarity
Ignoring subpixel layoutShared subpixels reduce real sharpnessPrefer RGB stripe figures when known
Pitfalls in reading PPD figures

In simple terms

PPD tells you how sharp a headset’s picture looks to your eye. Imagine holding your thumb at arm’s length: it covers about two degrees of your view. PPD counts how many tiny dots of the screen fit into each of those degrees.

More dots per degree means a clearer, smoother picture and easier reading. Around 60 per degree matches what a person with normal eyesight can see, and most current headsets are well below that, which is why text can still look slightly soft.

A practical example

An architecture firm wants staff to review building plans and read dimension labels inside a headset instead of on large monitors. Its current headset delivers roughly 20 PPD at the center, and small labels have to be enlarged before anyone can read them.

The firm tests a newer model with micro-OLED panels at about 34 PPD in the center and a slightly narrower field of view. Labels at normal size become legible at a comfortable virtual distance, while the narrower view makes no difference for desk-based plan review. The higher PPD demands more GPU power, so the firm enables foveated rendering. The outcome is that design reviews move into the headset without any change to drawing standards or label sizes.