Why 0.23 Inches and 640x400 Still Fit Near-Eye Wearables
A near-eye display is not judged by its diagonal; it is judged by what the optics can do with it. A 0.23-inch panel with 640x400 pixels is a sensible starting point for a wearable because the image is magnified by a lens anyway, and a small emissive source keeps the optical path short and the enclosure light. What decides whether the choice works is not the panel alone but the combination of pixel density at the eye, the luminance the optics can deliver after their losses, and how the mechanical stack tolerates being worn for hours. Get those three right and a small panel is an advantage rather than a compromise.
Key takeaways
- Magnification moves the pixel density question from the panel to the eye, so the number that matters is angular resolution after the optics, not diagonal size.
- An emissive panel removes the backlight from the optical stack, which shortens the path and removes a source of stray light.
- Luminance measured at the panel is only the input to an optical budget; every lens surface and combiner takes a share before light reaches the eye.
- Comfort and thermal behaviour are part of the specification, because a wearable runs warm against the head and cannot rely on a fan.
- Verify the mechanical envelope, the connector height and the flex stiffness before committing, since those constrain the whole enclosure.
Teams new to near-eye products often start with the largest panel they can afford, on the assumption that more display is more quality. In practice the opposite is usually true: magnifying a large image requires a larger optical path, which means more mass in front of the face and more glass to tolerate being dropped.
The reason small emissive panels dominate this category is that the optics do the work. Once a lens system sets the apparent image size, the panel only has to supply enough pixels to fill the field of view without visible structure, and enough luminance to survive the optical losses.
That reframes the selection problem. Instead of asking whether a panel is big enough, ask what angular resolution the eye will see, what the optic transmits, and what the mechanical stack can support. The sections below take those in turn.
The geometry that makes small panels viable
A display placed a few centimetres from the eye is magnified by whatever sits between it and the pupil. If the lens provides a large magnification, a physically small source fills a wide field of view, and the panel's diagonal stops being the interesting number. What becomes interesting is the angular size of one pixel, because that is what the eye resolves [1].
Angular resolution is set jointly by the pixel count and the field of view the optics deliver. Push the field of view wider while holding the pixel count constant and each pixel covers more angle, which is why a 640x400 panel maps naturally to a moderate field of view and looks coarse when asked for a very wide one. The same arithmetic explains why the same panel can look sharp in a camera viewfinder and soft in a virtual screen four metres away.
There is also a mechanical consequence. A short optical path permits a compact housing, and compactness is what makes a wearable wearable. The display contributes very little to the size of the device compared with the lenses and the electronics, provided the panel is small enough to sit inside the optical axis without pushing the lenses forward. Using a DisplayModule 0.23" Micro OLED display in that role keeps the display side of the stack modest and leaves the apparent image size to the optics, which is the right division of labour for a worn device.
What the near-eye constraint actually demands
| Constraint | Why it matters close to the eye | What to verify before committing |
|---|---|---|
| Angular resolution | The eye resolves structure in angle, not in millimetres on a panel | Field of view the optics deliver, and whether pixel structure is visible at the edges as well as the centre |
| Luminance after optics | Every surface between panel and eye costs light, and the eye sees only what survives | An optical budget with measured transmission, not a nominal figure from a lens drawing |
| Contrast in real scenes | Emissive displays avoid the grey floor of a backlit panel, which matters for dark backgrounds | How the panel behaves at low grey levels, and whether the optics introduce veiling glare from bright areas |
| Thermal behaviour | The device is worn against the head and cannot shed heat by convection alone | Worst-case power draw in the intended use pattern, and where that heat reaches the skin |
| Mechanical envelope | Panel thickness, connector height and flex stiffness set the minimum thickness of the temple | Clearance around the panel, bend radius of the flex, and how the assembly survives a drop |
Resolution is a system property, not a panel number
It is tempting to treat pixel count as the headline specification and everything else as detail. Near the eye the ordering is closer to the reverse. A panel with a modest pixel count and a well matched optical path will read as clean, while a higher count behind a poorly corrected lens can look worse because the extra detail is smeared rather than resolved.
Field of view and pixel pitch move together
Widening the field of view spreads the available pixels over a larger angle, so each pixel subtends more. If the intended content includes text or fine UI elements, that spreading is felt immediately as reduced legibility. The practical approach is to fix the field of view first from the use case, then check whether the resulting angular pitch is acceptable for the content, and only then choose the panel.
The same reasoning applies to the vertical axis. A near-eye device that shows a wide but shallow image may be perfectly suited to notifications and navigation prompts, and quite unsuited to immersive video.
Do not specify the panel in isolation
Because the optical chain and the panel are chosen together, the useful exercise is to write a one-page system budget: field of view, angular pitch, luminance at the eye, contrast at low grey levels, mass, and thermal rise. Every candidate panel is then scored against that page rather than against a datasheet in the abstract [2].
Teams that do this early tend to make fewer late changes, because the budget makes the trade-offs explicit. A decision to widen the field of view, for example, forces a visible reduction in angular resolution rather than letting it be discovered during the first user trial.
The cheapest moment to test a near-eye concept is before any tooling exists. Print a mechanical mock of the temple with the correct panel footprint and connector height, wear it for an hour, and check whether the optical path you intend actually fits the shape of a face. Most late redesigns in this category come from a stack that looked fine on a drawing and felt wrong on a head.
Sources
Frequently asked questions
Is 640x400 enough resolution for a wearable display?
It depends on the field of view and the content. Spread across a moderate field of view it is comfortable for text, icons and navigation prompts. If the same pixel count is stretched over a wide immersive field of view, pixel structure becomes visible and fine text suffers. Fix the field of view from the use case first, then judge the pixel count against it.
Why do near-eye products use small emissive panels instead of larger LCDs?
Because the optics magnify the image, so the panel does not have to be large. An emissive panel also removes the backlight from the stack, which shortens the optical path and reduces stray light. The result is a lighter, thinner assembly, which matters a great deal for something worn on the head.
What is the most common specification mistake in a wearable display design?
Treating panel luminance as if it were luminance at the eye. Lens surfaces, coatings and any combiner all remove light, and the losses add up quickly. Build the optical budget from measured transmission and design for it, rather than discovering the shortfall during a sunlight readability test.
How should thermal behaviour be evaluated for a worn display?
Run the device in its worst-case use pattern for an extended period and measure both the temperature of the outer surface and how it feels at the points that touch skin. A fan is not available, so the design has to limit sustained power or spread heat over a larger area. Decide this early, because it constrains the electronics as much as the display.
Ready to talk strategy with a senior partner?
Discreet, no-obligation discovery call. We listen first.