E-paper is meant for shelf labels, weather stations and e-readers, which redraw a few times an hour at most. Nobody designs it for 30 frames per second. That made it a good target for the maker behind the YouTube channel Bo Made It. In a video uploaded on October 27, 2026, the creator measured the power draw of a Waveshare ESP32-S3-ePaper board running the InkBoy Game Boy emulator with a custom display driver at 30 fps. They then ran the display at 30 fps for around 20 hours to see whether the continuous updates would cause lasting damage. Hackaday covered the results on October 28.
In short, the panel survived with some temporary ghosting, and the display turned out to use only a small part of the power budget. Neither result means high-frame-rate e-paper is safe, and the hardware vendor and the software author both say so.
The hardware and the software
The board is Waveshare's ESP32-S3 1.54inch e-Paper AIoT Development Board. Waveshare's product page describes a 200 x 200 black/white e-paper display driven by an ESP32-S3 with Wi-Fi and Bluetooth LE. It also lists AI voice interaction and temperature/humidity monitoring as supported uses. When PinoutFeed read the page on October 29, 2026, the board was listed at $15.99 to $22.99 (US dollars), depending on version options.
InkBoy is the software side, published by GitHub user kuslota and linked from the video description. The README says InkBoy runs Game Boy games on the Waveshare ESP32-S3-ePaper-1.54 V2, a board with a 200x200 e-paper screen, speaker and microSD slot, at about 30 fps. InkBoy offers two display modes, fast dithered black-and-white or four-shade grayscale. It also has an SD-card ROM browser, speaker audio, automatic resume and tunable display presets. The build needs ESP-IDF v6.1. The README also says only the custom ESP32-C3 InkBoy controller is currently supported, so this is not a generic gamepad project.
Where the current goes
According to Hackaday's write-up of the video, the measurements break down as follows:
- Full emulator running at 30 fps with display updates: about 115 mA on average.
- Emulator running with no display updates: about 90 mA.
- Emulator computing greyscale frames but not rendering them to the panel: 107.6 mA.
- The e-paper display itself at 30 fps greyscale: about 7.4 mA, the difference between the last figure and the 115 mA total.
The display is not the main load. By our arithmetic from Hackaday's numbers, computing the greyscale frames costs about 17.6 mA above the no-display baseline, more than twice what the panel adds by actually redrawing. Most of the current is drawn by the rest of the system, chiefly the ESP32-S3 running the emulator. That fits how e-paper works: the panel draws power to change its state and very little to hold an image. Even at 30 fps, driving the panel costs less than preparing the frames for it.
Hackaday puts the battery life at about 3.5 hours on the device's 400 mAh battery at the 115 mA average. That works for a short play session, but the battery-life case for e-paper mostly disappears once the processor is emulating a console at full speed.
The endurance question
The more interesting question is wear. Hackaday says one datasheet gives a typical lifespan of about one million updates. At 30 fps, one million full refreshes would take about 9.3 hours. The endurance run went well past that. The creator ran the display at 30 fps for around 20 hours, and Hackaday reports 2.16 million frames of a custom endurance test with repeating patterns. That is more than twice the cited update count.
Hackaday reports that some ghosting was apparent afterwards but went away with repeated refreshing, and no permanent damage was detected. Hackaday notes its 9.3-hour figure assumes a full display refresh, and that a driver updating only changed pixels would last longer, so some caution is needed. InkBoy's README says it uses custom waveforms, and a datasheet's update rating and a stream of fast custom-waveform frames are not necessarily the same measure of wear. The sources do not settle how the two compare. They establish only that this panel, under this test, came through about 20 hours without lasting damage being detected.
That is one board tested once. It shows that one panel survived one long run. It does not establish a safe operating mode, and it says nothing about panel-to-panel variation or whether damage builds up over months of play instead of one 20-hour session.
The warnings, from both ends
Neither the vendor nor the software author endorses this use. Hackaday notes that Waveshare recommends against running such high-FPS applications on its device, and that damage caused this way would not be covered under any warranty. The InkBoy README gives its own warning: custom waveforms and high refresh rates may cause permanent image retention or panel damage, and long-term panel life has not been validated.
The test is useful because it puts numbers on a risk that is usually only stated in general terms. Makers can now weigh measured results from one long run against the datasheet's conservative rating. But the official guidance has not changed, and this test does not change it.
What It Means for Makers
InkBoy and this test matter most to people interested in e-paper as a display technology, people who build handheld emulators, and anyone who wants to see how far a cheap ESP32-S3 board can be pushed. The power breakdown has a practical lesson beyond Game Boy emulation. On this board, at this frame rate, the rest of the system, mostly the emulator workload, uses far more power than the panel. If you are designing a battery-powered e-paper gadget with frequent updates, optimizing the firmware will probably save more than reducing refreshes.
The hardware costs little. Waveshare listed the ESP32-S3 1.54inch e-Paper AIoT Development Board at $15.99 to $22.99 (US dollars) as of October 29, 2026, depending on version options. InkBoy targets the V2 revision of the 1.54-inch board, builds with ESP-IDF v6.1 and currently supports only the creator's custom ESP32-C3 controller. Check those requirements before ordering parts.
Treat the 30 fps mode as an experiment. The creator's run suggests the panel tolerates more than a conservative lifespan rating implies, and that ghosting from heavy use can be refreshed away. Waveshare's position, as Hackaday reports it, is that such high-FPS use is not recommended, and the InkBoy author says long-term panel life is unvalidated. Anyone running it should assume they may lose the panel and that the warranty will not cover it.
