Does Running An E-Paper Display At 30 FPS Destroy It?

Although e-paper displays are famous for being low-power and lasting essentially forever if not damaged physically, the recent push to drive even cheaper e-paper displays at a framerate like 30 FPS for a decent monochrome gaming experience does raise a few questions. The first being what this does to the power usage of these displays, and the second whether this will wear out the display in short order. To investigate this, [Bo Made It] set up a few experiments.

Subject of this test was a Waveshare ESP32-S3-ePaper board, which had previously been demonstrated running a Game Boy emulator at 30 FPS. With this software running, the board consumed on average about 115 mA, which would run down the device’s 400 mAh battery in about 3.5 hours. From here key was to isolate the power consumption of the display itself, with the system minus the display updates consuming about 90 mA.

Running the frame calculations for the greyscale mode without rendering to the screen pushed that up to 107.6 mA, with even in the 30 FPS greyscale mode the display thus only consuming about 7.4 mA, which is vanishingly small. Clearly the low-power claims of e-paper remain intact even at higher framerates.

As for lifespan, one datasheet gives the typical lifespan as one million updates. This would translate to about 9.3 hours at 30 FPS, though that assumes a full display refresh. Since a smart driver only updates changed pixels, obviously this will be longer, but the question is how much longer, and what will degradation look like?

After running 2.16 million frames of a custom endurance test featuring repeating patterns, some ghosting was apparent, but repeated refreshing made this go away again. This means that so far no permanent damage has been detected within the no doubt conservative limit provided by e-paper manufacturers.

It should be noted that Waveshare itself also recommends against running such high-FPS applications on their device, meaning that this is definitely one big longevity experiment. If actual damage occurs, this means that obviously this won’t be covered under any warranty.

Check out our original coverage of this fast-e-paper hack.

22 thoughts on “Does Running An E-Paper Display At 30 FPS Destroy It?”

  1. Awesome, now if the cost of these displays could come down from the stratosphere. The types of usage I want require a large area and infrequent updates, although a good refresh rate would be important on occasion. (Think mostly static with occasional interactivity.)

    1. Yeah it is annoying… Is e-ink particularly challenging to manufacture? I have no idea about that process, I never thought about it till now

      1. Have you considered other similar technologies that are already used for large panels (e.g. bus schedules)? Electrochromic displays, cholesteric LCD… The second one isn’t that much cheaper actually

  2. Clearly the low-power claims of e-paper remain intact even at higher framerates.

    This is an interesting result. It definitely is not universal. The Dasung and Bigme 13.3″ e-ink monitors cannot be powered off a single usb-c connection that is providing the video signal. They both require a second external power supply. Even without front-light these displays use much more power than an equivalent sized tft lcd portable monitor (all of which can be powered off the single usb-c connection from the computer). Testing a Bigme 13.3″ e-ink, power draw, even idle (with no front light) was around 10W with any screen updates driving it quickly up to 14-17W. The manufacturers recommend, and include 30W power supplies for the displays e.g., displaying video at high frame rate with front light at max brightness.

    1. I’d suspect that a lot of that power draw is from the FPGA that handles the driving logic in those monitors rather than the e-ink panel itself. The curse of being a niche product…

      Also, obviously it wouldn’t improve power efficiency, but I’m not sure why they don’t just support usb-c PD rather than requiring two cables…

        1. In general, I agree. And providing only a single-cable usb pd option for power would be a foolish move. But for the people trying to run a second screen on a modern laptop or desktop, it’s rare these days to find a port on one that supports displayport alt mode but not PD.

          So why not provide both options? For relatively expensive monitors like these, the added bonus of being able to use a single cable seems like it’d easily outweigh the marginal cost increase.

  3. remember that eink displays don’t include a backlight. When comparing to other display technologies, subtract backlight power usage for a more fair comparison.
    how does power usage scale with screen size? I would expect that larger screens would draw much more power (on a full refresh at least)
    how consistent is this power draw? 7mA average sounds good but is it really mostly 0mA with sudden spikes?

    1. “…remember that eink displays don’t include a backlight. When comparing to other display technologies, subtract backlight power usage for a more fair comparison…”

      Why? These other displays that require a backlight are basically unusable without it, so it makes no sense to exclude the BL power consumption from the measurements.

      1. Because eink is not usable without light of some kind. You can use a backlit LCD by holding it in front of a light, many LCDs are reflective only, RLCD color LCDs exist, and transflective LCDs exist. The point is that if you’re trying to compare eink at high refresh rates to other technologies capable of high refresh rates, it’s easier to see differences if you take the light out of the equation.

  4. “As for lifespan, one datasheet gives the typical lifespan as one million updates. This would translate to about 9.3 hours at 30 FPS, though that assumes a full display refresh. Since a smart driver only updates changed pixels, obviously this will be longer…”

    Well, a smart driver can prevent the eink state toggling for full refresh (the “erasing” action), but if there are moving images (like in the cool GB demo), even the smart driver can’t prevent the required pixel update.

    Also, I don’t think the eink screen wearing is aggregated, as neighbor pixels can’t replace a damaged one. If a pixel burns out, it’s out. IMHO the lifespan is per-pixel.

    Just to make it clear – as a hobbyist I’m also interested in eink displays for my own toy-projects, and I would love to see a durable eink display option as much as you do.

    PS: I don’t remember seeing a worn-out eink still. Maybe the damaged pixel stops reacting and gets stuck in some dead state, I don’t really know. If someone can share photos of a damaged eink, please do so.

    1. I want to see a test that doesn’t do smart updates and just crudely refreshes the whole screen at 30fps for a few hours, see what happens..

      1. The answer to this one is actually known, and it lies in what you mean by “crudely”. The reason that e-ink displays do that black-white-black-white clearing-the-screen dance every few refreshes is so that the little electrically charged microballs that are in the fluid cell “pixels” keep floating freely around.

        Older controllers would just re-write the whole screen with every frame, with the negative effect of double-driving pixels that were already black, and thus had the little black microballs already at the surface. Do this often enough, and they can bleed charge which makes for ghosting, or they can get stuck entirely, which gives you a permanently black pixel.

        If you keep re-driving a pixel in the same state, you are asking for trouble.
        https://docs.pervasivedisplays.com/knowledge/Technology/updating-the-display.html

        If you can refresh individual pixels then there is no extra wear. This is Wen-ting Zhang’s trick: https://hackaday.com/2026/06/13/behold-a-60-hz-refresh-rate-e-ink-monitor/ and it looks like a lower-end version of this has now gone mainstream.

        It sure looks like the driver chips on these newer screens don’t re-drive all the pixels. So I’d expect a pretty long life.

        Thanks for attending my e-ink Ted Talk. No relation to the upcoming Supercon badge. :)

    2. I’ve a product on my wall I’ve made with an old 800×480 panel since 2011. It’s refreshing every 30s (completely, with full black then white dance). So if I compute correctly, that’s around 16.46 million refreshes. And it’s definitively marked, it’s never going back pristine, whatever the number of black/white cycles I’m attempting on it. It’s not really painful, it’s still readable, but I can see the previous text below the current one, and the various fixed pattern in my UI. I didn’t write when it became “marked” (it was progressive), that would have been useful for a real MTBF computation.

  5. Sample size of 1: I was also interested in this. Earlier this year, I had a brand new “control” eink display + driver board running known waveforms. An associate stress tested another identical display + driver board for ~24 hours, sending all sorts of waveforms to it, not all correct, and using global refreshes (not damaged rectangle refresh). At the end of it there were noticeable black specks from e-ink particles which had adhered to the front and would not come off. The overall effect was lower contrast, like dirty newsprint. It was still usable. Extrapolating this, I assume overworked eink displays will get foggier as time goes on. I suspect being gentle with waveforms + refreshing only damaged rectangles will give much better longevity.

    1. Dunno how those e-ink particles or their drivers work but maybe something like the old degausser tools can help “force” refresh/free stuck pixels?

      External capacitive charging (alternating?)?

    2. Many eink controllers have temperature sensors because they need to use a stronger field / longer time when it’s cold, and the working fluid is more viscous, than when it’s warm.

      You also might try doing a bunch of full-screen refresh cycles with the panel held a bit warmer than usual. If they’re just badly wedged against the front, you might stand a chance.

      Or just run tons and tons of full refresh cycles and hope for the best?

      If you’ve driven it so hard that you’ve discharged the microballs, you’re probably out of luck.

  6. I made the comment the video is somewhat based around. In a comment I left under this video the author accepts that more long term testing is needed as we agree that the datasheet is likely conservative because its figures need to be guaranteed. Still that it outlasts the datasheet easily is nice to know. Sample of 1, but still. It will be nice to know how far this tech can be pushed.

Leave a Reply

Please be kind and respectful to help make the comments section excellent. (Comment Policy)

This site uses Akismet to reduce spam. Learn how your comment data is processed.