Small displays for DIY projects: a big comparison table of OLED, LCD, TFT and e-paper
Contents 11
A comparison of small displays that are easy to buy on AliExpress and wire to an Arduino, ESP32, STM32 or Raspberry Pi Pico. In this article:
- a big comparison table: colour, resolution, how many lines of text fit, whether it can show a picture;
- size, supply, current, brightness and backlight;
- how to connect it: protocol, number of wires, how much memory it takes in the firmware, libraries and microcontrollers;
- operating temperature and other conditions;
- the pitfalls people trip over most often;
- which display to put in a battery-powered fob (alarm, tag finder, car status);
- how to choose a display for your task, and what we ended up with.
The numbers in the tables come from the controller datasheets and from descriptions of specific modules (sources at the end). The [calc.] mark is our own calculation from the resolution: lines of text for a 6×8-dot font (5×7 plus spacing) are height ÷ 8, characters per line are width ÷ 6; with a large 16-dot font, height ÷ 16; the frame buffer is width × height × bits per dot ÷ 8. "Not found" means we found no reliable figure, not that there is none.
In short
| Task | What to pick |
|---|---|
| a few numbers and words, few pins, any microcontroller | a 0.96″ 128×64 OLED over I2C, 4 wires |
| text only, a 5 V microcontroller, readable from a distance | a 16×2 or 20×4 character LCD with an I2C adapter |
| digits only (clock, temperature, counter) | a TM1637, 4 digits, 4 wires |
| colour graphics, menus, icons | an ST7789 or ILI9341 TFT over SPI, best with an ESP32 or RP2040 |
| battery-powered, the picture must stay with the power off | e-paper; but a full refresh takes 2–3 s, and below freezing it is out of spec |
| bright sunlight | e-paper (it reflects light instead of emitting it) |
| battery-powered fob, state always visible | a segment LCD (better: a microcontroller that drives the LCD itself), a Sharp Memory LCD or e-paper (daytime only), see the fob |
What is on the screen
| Display | Controller | Colour | Dots | Lines × chars 6×8 [calc.] | Lines 16 dots [calc.] | Picture |
|---|---|---|---|---|---|---|
| OLED 0.91″ | SSD1306 | one colour | 128×32 | 4 × 21 | 2 | yes |
| OLED 0.96″ | SSD1306 / SSD1315 | one colour; "two-colour" means a yellow strip on top, blue below | 128×64 | 8 × 21 | 4 | yes |
| OLED 1.3″ | SH1106 | one colour | 128×64 | 8 × 21 | 4 | yes |
| OLED 1.5″ | SSD1327 | 16 shades of grey | 128×128 | 16 × 21 | 8 | yes |
| OLED 1.5″ | SSD1351 | up to 262k colours | 128×128 | 16 × 21 | 8 | yes |
| LCD 16×2, 20×4 | HD44780 | one colour, backlight | 5×8 character cells | exactly 2 × 16, 4 × 20 | — | no: only 8 custom 5×8 characters |
| Nokia 5110 | PCD8544 | one colour, backlight | 84×48 | 6 × 14 | 3 | yes |
| LCD 12864 | ST7920 | one colour, backlight | 128×64 | 8 × 21; built-in text mode 4 × 16 | 4 | yes |
| TFT 0.96″ | ST7735 | up to 262k | 80×160 | 20 × 13 (portrait) | 10 | yes |
| TFT 1.14″ | ST7789 | up to 262k | 135×240 | 16 × 40 (landscape) | 8 | yes |
| TFT 1.3″ | ST7789 | up to 262k | 240×240 | 30 × 40 | 15 | yes |
| TFT 1.8″ | ST7735S | up to 262k | 128×160 | 20 × 21 (portrait) | 10 | yes |
| TFT 2.4–3.2″ | ILI9341 | up to 262k | 320×240 | 30 × 53 (landscape) | 15 | yes |
| TFT 3.5″ | ILI9488 | up to 262k | 480×320 | 40 × 80 (landscape) | 20 | yes |
| TFT 1.28″ round | GC9A01 | up to 262k | 240×240, round visible area | less than 30 × 40: the corners are cut off | less than 15 | yes |
| e-paper 1.54″ | depends on the module | black and white; some add red | 200×200 | 25 × 33 | 12 | yes |
| e-paper 2.13″ | SSD1680 (V4) | black and white; some add red | 250×122 | 15 × 41 (landscape) | 7 | yes |
| e-paper 2.9″ | depends on the module | black and white; some add red | 296×128 | 16 × 49 (landscape) | 8 | yes |
| 4 digits | TM1637 | LEDs | 4 seven-segment digits | — | — | no: digits and some letters |
| matrix / digits | MAX7219 | LEDs | 8×8 or 8 digits | — | — | the matrix, yes: 8×8 dots |
Size, supply, current and brightness
| Display | Module size | Supply | Current or power | Brightness and backlight |
|---|---|---|---|---|
| OLED 0.91″ | 38×12 mm | modules with a regulator: 3.3–5 V | dark screen ≈ 2 mA, half the dots ≈ 13 mA, all dots ≈ 25 mA | no backlight, each dot emits light; 256 contrast steps |
| OLED 0.96″ | not found | modules with a regulator: 3–5 V; some older ones 3.3 V only | ≈ 20 mA on average; all dots 28.5 mA (one module); depends on how much is lit | the same |
| OLED 1.3″ SH1106 | not found | logic 1.65–3.5 V | not found | the same |
| OLED 1.5″ SSD1327 | not found | logic 1.65–3.5 V | not found | contrast |
| OLED 1.5″ SSD1351 | not found | logic 2.4–3.5 V | not found | contrast |
| LCD 16×2 | not found | 2.7–5.5 V | logic 1.2–3 mA; backlight 20–25 mA (white, blue) or ≈ 100 mA (yellow-green) | backlight switched separately; contrast by a trimmer |
| LCD 20×4 | 98×60×13.5 mm | 2.7–5.5 V | backlight 25–60 mA (blue), up to 240 mA (yellow-green) | the same |
| Nokia 5110 | ≈ 43.6×43.1 mm | 3.3 V | logic ≈ 0.4 mA, backlight 1–10 mA | separate backlight |
| LCD 12864 ST7920 | 93×70×13 mm | 4.5–5.5 V (3.3 V versions exist) | logic 3–5 mA, backlight ≈ 60 mA | separate backlight |
| TFT 0.96″ ST7735 | 24×30 mm | 3.3 V; some versions take 5 V through an onboard regulator | backlight ≈ 25 mA | separate backlight, brightness by PWM through a transistor |
| TFT 1.3″ ST7789 | 27.95×39.16 mm | 3.3 V only | not found | separate backlight |
| TFT 1.8″ ST7735S | 34.5×58 mm | 3.3–5 V, logic 3.3 V | backlight 38.2 mA; whole module ≈ 0.2 W | separate backlight |
| TFT 2.8″ ILI9341 | 50×86 mm | 3.3–5 V, logic 3.3 V | ≈ 0.31 W | separate backlight |
| TFT 3.5″ ILI9488 | 56.34×98 mm | 3.3–5 V, logic 3.3 V | ≈ 0.62 W | separate backlight |
| TFT 1.28″ GC9A01 | not found | 2.5–3.3 V | ≈ 14 mA with the backlight | separate backlight |
| e-paper 1.54″ | 48×33 mm | not found | only while refreshing: ≈ 26 mW; almost zero in between, the picture stays on its own | emits no light, so no backlight |
| e-paper 2.9″ | 89.5×38 mm | 3.3 / 5 V | the same | the same |
| TM1637 | not found | 4.5–5.5 V (modules claim 3.3–5 V) | depends on how many segments are lit | 8 brightness steps |
| MAX7219 | not found | 4.0–5.5 V | 150 µA in shutdown; in operation it depends on the segments | 16 brightness steps |
How to connect it and what it costs the firmware
| Display | Protocol and speed | Wires, supply included | Frame buffer in RAM [calc.] | Libraries | Microcontroller |
|---|---|---|---|---|---|
| OLED 0.91″ | I2C up to 400 kHz | 4 | 512 B | Adafruit SSD1306, U8g2 | any |
| OLED 0.96″ | I2C up to 400 kHz or SPI up to 10 MHz | I2C 4, SPI 6–7 | 1 KB; also works without a buffer | Adafruit SSD1306, U8g2, SSD1306Ascii | any; on an ATmega328 (2 KB RAM) the buffer takes half the memory |
| OLED 1.3″ SH1106 | I2C up to 400 kHz or SPI | I2C 4 | 1 KB | U8g2, Adafruit SH110X | any |
| OLED 1.5″ SSD1327 | I2C or SPI | I2C 4 | 8 KB (4 bits per dot) | U8g2, Adafruit SSD1327 | ATmega328 only page by page, without a full buffer |
| OLED 1.5″ SSD1351 | SPI only, up to 20 MHz | 6–7 | 32 KB (16 bits per dot) | Adafruit SSD1351 (writes straight into the display) | full buffer: ESP32, RP2040, larger STM32s; without one, even an ATmega328 |
| LCD 16×2, 20×4 | parallel, 4-bit; or I2C through a PCF8574 (100 kHz only) | parallel 8, over I2C 4 | not needed | LiquidCrystal, LiquidCrystal_I2C, hd44780 | any |
| Nokia 5110 | SPI up to 4 Mbit/s | 8 pins on the module | 504 B | Adafruit PCD8544, U8g2 | any |
| LCD 12864 ST7920 | serial (write only) or parallel | serial: 3 signals + supply | 1 KB | U8g2 | any; ATmega328 page by page |
| TFT ST7735 / ST7789 | SPI; write up to ≈ 15 MHz per the ST7735 datasheet | 7–8 (the 1.3″ sometimes has no CS) | 25–113 KB (16 bits per dot); also works without a buffer | TFT_eSPI, Adafruit, LVGL | full buffer: ESP32, RP2040; without one, smaller chips too |
| TFT 1.8″ ST7735S | SPI | 7–8 | 40 KB | Adafruit ST7735, TFT_eSPI | the same |
| TFT ILI9341 | SPI; 10 MHz per the datasheet, the TFT_eSPI library 27–40 MHz | 7–8; XPT2046 touch adds 4–5 | 150 KB | TFT_eSPI, Adafruit, LVGL | full buffer: ESP32, RP2040 (264 KB RAM), larger STM32s |
| TFT ILI9488 | SPI, 3 bytes per dot; TFT_eSPI 27 MHz | 7–8 | 300 KB at 16 bits per dot in memory (3 bytes per dot go to the display) | TFT_eSPI | ESP32 with PSRAM, or without a full buffer |
| TFT GC9A01 | SPI | 7–8 | 113 KB | TFT_eSPI, Adafruit GC9A01A | ESP32, RP2040 |
| e-paper | SPI (SSD1680 up to 20 MHz) | 7–8 | 3.7–4.9 KB (1 bit); with red, twice as much | GxEPD2, Adafruit EPD | ATmega328 page by page (GxEPD2) |
| TM1637 | its own two-wire protocol, NOT I2C; up to 500 kHz | 4 | ≈ 4 B | TM1637Display, TM1637TinyDisplay | supply 4.5–5.5 V; we did not check the input threshold at 3.3 V |
| MAX7219 | serial, up to 10 MHz | 5 | 8 B per matrix | LedControl, MD_MAX72XX, MD_Parola | any; ⚠ a "1" at the input needs at least 3.5 V: out of spec for 3.3 V chips |
How long a frame takes to draw [calc., no overhead]: a 128×64 OLED over 400 kHz I2C ≈ 23 ms; a 240×240 TFT over 40 MHz SPI ≈ 23 ms; an ILI9341 at 40 MHz ≈ 31 ms; an ILI9488 at 27 MHz ≈ 136 ms, about 7 frames per second. E-paper: a full refresh takes 2–3 s, a partial one 0.3–0.6 s.
Operating conditions
| Display | Operating temperature | What else matters |
|---|---|---|
| OLED (SSD1306, SH1106 etc.) | controller −40…+85 °C | dots that stay lit for long dim for good (burn-in) |
| LCD HD44780 (STN) | standard 0…+50 °C, some −20…+70 °C | slower in the cold; without the backlight it is unreadable in the dark |
| Nokia 5110 | controller −25…+70 °C | pinout and backlight polarity differ between boards |
| TFT 1.8″ ST7735S | −30…+80 °C | |
| TFT 1.3″ ST7789 | −20…+70 °C | |
| TFT 2.8″, 3.5″ | −20…+60 °C | |
| e-paper | 0…+50 °C | a full refresh after about 5 partial ones; refresh at least once a day; viewing angle >170° |
Pitfalls
- The OLED address is 0x3C or 0x3D. Boards often print it in 8-bit form: 0x78 or 0x7A. If the display stays silent, scan the I2C bus.
- An SH1106 is not an SSD1306. The SH1106 has memory for 132 columns, so an SSD1306 library shifts the picture by 2 dots and leaves a strip of garbage at the edge. You need a driver made for the SH1106. 1.3″ displays mostly use the SH1106, but some use the SSD1306.
- PCF8574 and PCF8574A. I2C adapters for character LCDs are sold with either chip, and their addresses differ: 0x20–0x27 and 0x38–0x3F. An example using address 0x27 silently does nothing on a board with a PCF8574A.
- Five volts. An HD44780 LCD running on 5 V accepts signals from a 3.3 V microcontroller, but when read it drives 5 V onto that microcontroller's pin. The MAX7219 needs at least 3.5 V for a "1": from an ESP32 or RP2040 that is out of spec, although it often works.
- OLED burn-in. The longer a dot stays lit, the dimmer it gets compared with its neighbours, and it does not recover. Lower contrast, switching the screen off when idle and shifting the picture help.
- E-paper. Partial refreshes leave "ghosts" behind, so a full refresh is needed. Below freezing it is out of spec.
A display for a battery-powered key fob
This section is about fobs that run on a battery: a 433 MHz alarm fob, a handheld finder for a tag (the 433 MHz tag article), and a fob that shows the state of a car. A fob display works in one of two modes:
- "glance at it any time": the state is always on the screen, no button needed. What matters here is how much the display draws while it simply shows a picture;
- "a notification comes, you switch it on": the screen is off, the fob only beeps or blinks an LED, and after you press a button it shows the details for a few seconds. What matters here is how much the display draws when it is off, and whether you can read it at night.
| Looks like | Display | Draw while showing | Off / sleep | Sunlight and night | Cold | Wiring | Price |
|---|---|---|---|---|---|---|---|
| segment LCD (TN / STN) with an HT1621 controller: digits and a few icons only | controller ≈ 150 µA (300 max) on the internal oscillator at 3 V; with a 32 kHz crystal ≈ 60 µA | 0.1 µA (5 max), but the screen is blank then | easy to read in sunlight, since it reflects light; at night only with a backlight | controller −25…+75 °C; the glass depends on the liquid crystal, see operating conditions | 3 signals (CS, WR, DATA) + supply | ≈ $1.4–3.5 in AliExpress search results (November 2026) | |
| Sharp Memory LCD (e.g. LS013B7DH03 1.28″ 128×128 or LS013B7DH05 1.3″ 168×144; the photo shows an Adafruit board), graphics | LS013B7DH03 with a static picture: 12 µW (50 max, Sharp datasheet); Adafruit 1.3″ board updated once a second: ≈ 12 µW ≈ 4 µA at 3.3 V | the picture stays only while powered; the VCOM signal must be toggled once a second | good in sunlight, since it reflects light; no backlight, so unreadable at night | −20…+70 °C (LS013B7DH03) | write-only SPI, 3 signals + 3 V supply | Adafruit board $24.95; AliExpress prices not checked | |
| 1.54″ e-paper, 200×200, SSD1681 | only while refreshing: 4.5–26 mW; full refresh 2 s, partial 0.3 s | zero: the picture stays even without power | good in sunlight; unreadable at night | standard 0…+50 °C; cold-rated panels −20…+50 °C exist (GDEM0154D67WT) | SPI, 7–8 wires | Waveshare module $9.99 | |
| 128×64 chip-on-glass (COG) graphic LCD, ST7567 / ST7567S | ST7567S controller with its own voltage booster ≈ 150 µA (300 max) at 3 V; the backlight is separate | display off ≈ 95 µA; power-down mode ≈ 3 µA (Sitronix datasheet) | "black on light" modules read fine in daylight; at night only with the backlight | controller −30…+85 °C; glass: not found | SPI or I2C | not checked | |
| 0.96″ OLED, 128×64, SSD1306 | ≈ 20 mA on average (see the current table) | 10 µA max per the SSD1306 datasheet; more on a module with a voltage converter | emits its own light: readable at night with no backlight, worse in bright sun | controller −40…+85 °C | I2C (4 wires) or SPI | ≈ $2.4–6.2 |
Photos: segment module from an AliExpress listing (a 2.4″ 6-digit module with an HT1621; top without the backlight, bottom with it); Memory LCD from Adafruit; e-paper from Waveshare; OLED (SPI module) from Waveshare; 128×64 COG from Winstar.
A microcontroller with a built-in LCD driver. Segment glass can be driven without an HT1621: some low-power microcontrollers drive such glass themselves. For example, TI's MSP430FR4133 has a 4 × 36 or 8 × 32 segment driver and draws under 1 µA in standby with the real-time clock and the LCD running, at −40…+85 °C (TI). A separate HT1621 draws at least sixty times as much. The board gets more complex, though: the glass is soldered to the microcontroller's pins, and the number of segments is limited by how many pins it has.
What to choose
"Glance at it any time":
- a segment LCD, if digits and icons are enough (armed or not, alarm, zone number, battery). It is the cheapest and the easiest to read in the sun. But with a separate HT1621, a CR2032 coin cell (235 mAh, Energizer) would run the controller alone for about 2 months [calc.: 235 / 0.15 mA ≈ 1570 h]. That is the display's own draw, without the microcontroller and the radio. To make the display negligible, use a microcontroller with its own LCD driver;
- a Sharp Memory LCD, if you need graphics: a direction arrow, a scale, a few lines of text. It draws a few microamps, but the microcontroller has to wake up every second to toggle VCOM (or the signal comes from a separate oscillator). It is unreadable at night with no backlight;
- e-paper also works for "glance at it any time", but only by day: at night it can't be read without a backlight. The last state stays on the screen even with the power off, so between refreshes the display draws nothing. Drawbacks: a refresh takes 0.3–2 s, and standard panels are out of spec below freezing, so for a car fob in winter pick a cold-rated panel.
"A notification comes, you switch it on":
- OLED: it comes on instantly and is readable at night. 5 s on at 20 mA is ≈ 0.03 mAh [calc.], so even 10 looks a day is ≈ 0.3 mAh per day. But a CR2032 coin cell copes badly with tens of milliamps, so an OLED is better paired with AAA cells or a Li-ion battery.
⚠ The receiver, not the display, decides the fob's battery life. To show an alarm or a new event, the fob has to listen to the air. A 433 MHz receiver that listens non-stop draws ≈ 15–16 mA (the tag article), at least a hundred times more than any display in the table except the OLED. So the receiver in a fob listens in short windows (Wake-On-Radio on the CC1101), and the average current depends on how often it wakes up. [ВПИСАТИ: measure the receiver's average current with Wake-On-Radio]
For our three fobs
| Fob | What to show | What we pick and why |
|---|---|---|
| tag finder (433 MHz) | signal strength, direction, battery | while searching, the receiver listens non-stop and draws ≈ 15–16 mA, so the finder runs from a battery pack or a power bank anyway (see the tag article). Next to that, the display current doesn't matter: an OLED (readable at night in a forest) or a Memory LCD (readable in the sun) |
| alarm fob (433 MHz) | armed or not, alarm, which zone, battery | for an always-visible state, a segment LCD; if you need text, a Memory LCD. The fob only learns about an alarm by listening to the air: the receiver listens in short windows (Wake-On-Radio), and it is the receiver, not the display, that decides how long the battery lasts. The alarm is signalled by sound and an LED, with the details on the screen |
| car status fob (GSM and 433 MHz) | doors, alarm, car battery voltage, temperature, last event | a GSM module draws bursts of up to 2 A while transmitting (SIM800L, SIMCom), so GSM inside the fob itself needs a Li-ion battery. The 433 MHz receiver listens in short windows, as in the alarm fob. Display: e-paper (cold-rated) or a Memory LCD |
[ВПИСАТИ: which display went into the fob, what it actually draws, how readable it is in the cold and in the sun]
Prices
We could only check prices reliably for the most popular 0.96″ OLED: on AliExpress from ≈ $1–2 (often a new-buyer price), the usual price ≈ $2.4–6.2 without shipping (2026). We did not check prices for the other displays, so we do not give them.
Our own build
We wired a 0.96″ SSD1315 OLED with four buttons to the dishwasher board we are turning into a water heater (part 5). What we checked ourselves:
- the SSD1306 initialisation worked unchanged, and the display answered at address 0x3C;
- I2C and the buttons work even through a 1 kΩ resistor in every wire, with no bus errors;
- the module's buttons switch to ground;
- the module has one colour: a dot is either lit or dark.
Sources
- SSD1306, SSD1315, SH1106, SSD1327, SSD1351: OLED controller datasheets
- Adafruit: OLED power, a 0.96″ module datasheet, Seeed: SSD1315
- Winstar 0.91″, DFRobot 0.91″
- HD44780U, PCF8574 / PCF8574A (NXP), BC1602A, HJ1602A, Waveshare LCD2004, Handsontec I2C 2004
- PCD8544, Nokia 5110 current measurements
- ST7920, Handsontec 12864
- ST7735, ST7789V, 1.8″ ST7735S, 0.96″ 80×160, 1.3″ ST7789
- ILI9341, 2.8″ ILI9341, 3.5″ ILI9488, XPT2046, TFT_eSPI: settings
- GC9A01
- SSD1680, e-paper 2.13″ V4, e-paper 1.54″, e-paper 2.9″
- TM1637, MAX7219
- HT1621, MSP430FR4133, Sharp LS013B7DH03, Adafruit Sharp Memory 1.3″, GDEY0154D67, GDEM0154D67WT, ST7567S (Sitronix), Waveshare 0.96″ OLED, Winstar WO12864U1, Energizer CR2032, SIM800L: battery-powered fob
- LVGL: requirements, screen burn-in, SH1106 vs SSD1306
Article changelog
- 2026-11-18 — section "A display for a battery-powered key fob": a table with photos, how to choose, our three fobs.
- 2026-11-16 — first draft: four comparison tables, pitfalls, our experience.