E-paper & Non-LED Displays

Refresh behaviour, power profile, appropriate use cases, and limitations. When non-LED displays are the correct engineering choice.

Problem class: E-paper and other non-LED display technologies—when they are the correct engineering choice and how integration must account for refresh behaviour and power. Systems involved: Display device (e-paper or non-LED), integration layer, update logic. Why non-trivial: Refresh is slower than LED/LCD; update constraints affect content design; power profile differs. If done incorrectly: Wrong technology for use case (e.g. e-paper for fast-changing queue numbers) leads to poor usability; misuse of refresh or power assumptions shortens lifespan or causes visible artefacts. We do not describe products; we describe capability and rationale. For product selection, see CommercialDisplaySolutions.

How E-paper Differs from LED and LCD

E-paper (electrophoretic and similar technologies) is reflective: it uses ambient light rather than a backlight. Once an image is written, it is held without power until the next update. LED and LCD are emissive or transmissive: they require continuous power to display an image. This fundamental difference drives refresh behaviour, power usage, and use cases.

E-paper typically has a slower refresh rate than LED or LCD. A full refresh may take one or more seconds; partial refreshes may be faster but can leave ghosting or artefacts. LED and LCD can update at video frame rates. So e-paper is unsuitable for fast-changing content (e.g. video, real-time animations) but well-suited for content that changes infrequently (e.g. room labels, wayfinding, static instructions). We specify display type based on content and environment requirements.

Refresh Constraints and Update Behaviour

E-paper refresh constraints affect how we design content and update logic. We cannot assume instant updates; we must design for refresh cycles. That may mean batching updates, avoiding unnecessary full refreshes, and accepting a short delay between data change and on-screen update. For many operational use cases—room status, signage that changes a few times per day—this is acceptable. For others—queue numbers that change every few seconds—e-paper may not be the right choice.

Update behaviour also affects power and longevity. E-paper consumes power mainly during refresh; between refreshes, power draw is minimal. So update frequency directly affects battery life in battery-powered deployments. We design update logic to match the display technology: only refresh when content actually changes, and use partial refresh where supported to reduce wear and power.

Power Usage and Longevity

E-paper is well-suited to low-power and battery-powered deployments. LED and LCD require continuous power; e-paper does not. In environments where power is constrained (e.g. solar, battery, or limited mains), e-paper can extend runtime or reduce infrastructure cost. Longevity is also a factor: e-paper has no backlight to age, and refresh cycles can be minimised to reduce wear. For long-lived, low-maintenance deployments, e-paper is often the correct engineering choice.

When Non-LED Displays Are the Correct Engineering Choice

Non-LED displays (e-paper and others) are the correct engineering choice when: content changes infrequently; power is constrained; longevity and low maintenance are priorities; or the environment (e.g. high ambient light, need for readability without glare) favours reflective technology. They are not the right choice when: content changes rapidly; video or animation is required; or instant update is critical. We help stakeholders understand these trade-offs and specify accordingly. We do not describe specific products or vendors.

Consequences of Misuse

Using e-paper or non-LED where fast refresh is required (e.g. queue numbers updating every few seconds) results in stale or unreadable content. Ignoring refresh constraints in update logic can cause ghosting, excessive power use, or shortened display life. Specifying display type and update behaviour to match the use case avoids these consequences.

Why this matters in real deployments

Choosing the wrong display technology for the use case leads to poor UX, high power costs, or a short lifespan. Understanding refresh behaviour, power profile, and limitations ensures the right engineering choice.