ESP32 Display Guide: SPI, 8080, RGB or MIPI DSI, and Which Panel Fits

An ESP32 display connects over one of four buses, and the chip decides which ones you have: every ESP32 has SPI, the ESP32, S2, S3 and P4 add an 8080-style parallel bus (I80), the S3 and P4 add a parallel RGB interface, and only the ESP32-P4 has MIPI DSI. Screens up to about 320 × 240 work well on SPI. From 480 × 480 to 800 × 480 you move to RGB with a frame buffer in PSRAM, which is where the ESP32-S3 runs short of bandwidth. Above that, the ESP32-P4 with MIPI DSI is the realistic option.

Request a quote TFT LCD catalogue

ESP32 chips and the display interfaces each one supportsMatrix of ESP32 chips against display buses. ESP32 and ESP32-S2 support SPI and I80. ESP32-S3 supports SPI, I80 and RGB. ESP32-P4 supports SPI, I80, RGB and MIPI DSI. ESP32-C2 and C3 support SPI only. ESP32-C5, C6 and H2 support SPI and can emulate I80 through the Parlio peripheral. Below, bars show where each bus fits in the worked examples: SPI at 40 MHz gives at most 43 fps at 240 by 240 and 33 fps at 320 by 240; a 16-bit I80 bus at 20 MHz gives up to 130 fps at 480 by 320 before overheads; RGB on an ESP32-S3 with octal PSRAM runs 480 by 480 at 60 Hz and 800 by 480 near 40 Hz; MIPI DSI on the ESP32-P4 with 2 lanes carries 720 by 1280 or 800 by 1280 at 60 Hz.ESP32 chips, display buses, and where each bus fitsSPI / QSPII80 (8080)RGBMIPI DSIESP32, ESP32-S2ESP32-S3ESP32-P4ESP32-C2, C3ESP32-C5, C6, H2via ParlioWhere each bus fits in the worked examples (16-bit colour)SPI at 40 MHz240 × 240: 43 fps max; 320 × 240: 33 fpsI80, 16-bit at 20 MHz480 × 320: up to 130 fps before overheadsRGB on ESP32-S3, octal PSRAM480 × 480 at 60 Hz; 800 × 480 near 40 HzMIPI DSI on ESP32-P4, 2 lanes720 × 1280 or 800 × 1280 at 60 Hz
Figure: which display buses each ESP32 chip has, and where each bus fits in this guide’s worked examples.

Which display interfaces each ESP32 supports

Espressif’s LCD development guide lists the interfaces per chip. I80 is the Intel 8080 parallel bus, also called the MCU interface on display datasheets.

ChipSPI / QSPII80 (8080)RGBMIPI DSI
ESP32, ESP32-S2YesYesNoNo
ESP32-S3YesYesYesNo
ESP32-P4YesYesYesYes
ESP32-C3, C2YesNoNoNo
ESP32-C5, C6, H2YesThrough the Parlio peripheralNoNo

There is a second split that matters as much as the bus. SPI and I80 panels keep the image in their own display RAM, so the ESP32 only sends what changed. Most RGB panels have no RAM of their own, so the ESP32 must hold a full frame and stream it continuously.

How to connect a display to an ESP32

  1. Read the panel datasheet for the driver IC and the interface modes it allows. Many drivers select SPI, 8080 or RGB with IM pins, and the module FPC decides which of those are wired out.
  2. Count pins. SPI needs about six GPIOs (clock, data, chip select, data/command, reset, backlight). An 8-bit I80 bus needs about twelve. A 16-bit RGB565 bus needs 16 data lines plus clock, DE, HSYNC and VSYNC. MIPI DSI uses the dedicated D-PHY pins of the ESP32-P4.
  3. Check whether an RGB panel needs initialization commands first. Many do, over a 3-wire SPI port; our catalogue lists those as SPI + RGB.
  4. Use the esp_lcd driver for the controller, then a graphics library such as LVGL on top.
  5. Budget the backlight separately. The S35001D backlight, for example, is annotated 19.2 V at 40 mA, which calls for a boost LED driver, not a GPIO.

SPI: the default for small ESP32 screens

The SPI clock sets the frame rate ceiling: frames per second ≤ clock ÷ (width × height × bits per pixel). At 40 MHz and 16-bit colour that is about 43 fps for 240 × 240, 33 fps for 320 × 240 and 16 fps for 480 × 320. Partial updates help, because the panel keeps everything you did not redraw. Check the driver datasheet for its own SPI clock limit before raising the clock.

SPI references in our catalogue include the 1.54-inch STFT154D (240 × 240), the 1.77-inch S177MEHS-04 (128 × 160) and the 1.3-inch round S130MH2ZG-03 (240 × 240, SPI, RGB or MCU interface). The full list is on the SPI display modules page.

When SPI is too slow: 8080 parallel (I80)

An I80 bus moves 8 or 16 bits per write strobe. Assuming a 20 MHz write clock, an 8-bit bus carries 160 Mbit/s and a 16-bit bus 320 Mbit/s, enough for 65 or 130 fps at 480 × 320 in 16-bit colour before overheads. The panel still keeps its own frame, so the ESP32 needs no full frame buffer. The cost is GPIO count, and the driver IC sets the real write cycle limit. Use I80 when SPI is too slow and the chip has no RGB port.

RGB on the ESP32-S3: where PSRAM sets the limit

An RGB frame in 16-bit colour takes 768,000 bytes at 800 × 480 and 460,800 bytes at 480 × 480. The ESP32-S3 has 512 KB of internal SRAM, so the frame buffer goes in PSRAM, and PSRAM bandwidth caps the pixel clock. Espressif’s FAQ gives these limits from its own testing:

PSRAM on the ESP32-S3Highest pixel clock reported
Quad, 80 MHzAbout 11 MHz
Octal, 80 MHzAbout 22 MHz
Octal, 120 MHz (experimental)About 30 MHz

Worked example: frame rate an ESP32-S3 can reach on RGB. Assume octal PSRAM at 80 MHz, so a 22 MHz pixel clock. Take a 480 × 480 panel with a total frame of 552 × 512 including blanking: 22,000,000 ÷ (552 × 512) ≈ 78 Hz, so 60 Hz fits. Take an 800 × 480 panel with a total frame of 1056 × 525: 60 Hz would need 33.3 MHz, and at 22 MHz the panel runs at about 40 Hz. These totals are assumptions; use the porch values in your panel datasheet. Wi-Fi and flash writes compete for the same PSRAM bandwidth and can make the image drift; Espressif’s bounce buffer mode is one of the fixes it lists.

RGB references that suit an ESP32-S3 include the 4-inch square S400MHZS-03F1 (480 × 480, RGB + SPI, capacitive touch), the 4.3-inch S430MI2NI (480 × 272) and the 5-inch S500MIWI-04 (800 × 480). For 480 × 480 wall panels see square TFT LCD displays.

MIPI DSI on the ESP32-P4

The ESP32-P4 drives MIPI DSI with up to 2 data lanes at 1.5 Gbit/s each, 3 Gbit/s in total. A 720 × 1280 panel in 24-bit colour at 60 Hz needs about 1.33 Gbit/s of active video, and 800 × 1280 about 1.47 Gbit/s, so both fit with room for blanking. The catch is lane count. Some panels are designed for 4 lanes, so confirm that the panel runs on 2 lanes at your bit rate. MIPI references include the 3.97-inch STFT397D (480 × 800), the 4-inch S400MB1ZS-01F2 (720 × 720) and the 10.1-inch STFT1010D (800 × 1280), all with capacitive touch. Lanes and modes are explained in MIPI DSI interface.

Adding a touchscreen to an ESP32 display

Capacitive touch controllers talk I2C and raise an interrupt pin when a finger lands, so touch costs four GPIOs: SDA, SCL, INT and reset. Our 7-inch standalone touch panel S700GG-42 uses a GT911, and the 3.5-inch S35001D uses an FT5446. Bring-up details for the first are in the GT911 touch controller guide.

Choosing an ESP32 display for a product

Development boards such as the ESP32-2432S028R, sold as the Cheap Yellow Display, are a quick way to prove a UI. A product needs more: a module with a controlled drawing revision, an FPC length and connector that fit your board, a backlight current your supply can deliver, and a temperature range that fits the enclosure. Lock the panel before you tune the UI, because a different driver IC means a different init sequence.

An ESP32-S3 is the wrong host for full-screen video or for 1024 × 600 at 60 Hz. Use an ESP32-P4 or an application processor instead; compare the options in Raspberry Pi display interfaces.

FAQ

How do I connect a display to an ESP32?

Check which interface the panel offers and which ones your ESP32 has, wire the bus plus reset and backlight, then use the esp_lcd driver for the panel controller. SPI needs about six GPIOs, while RGB panels need about twenty and often an extra 3-wire SPI port for initialization.

What is the best display for an ESP32?

For an ESP32 or ESP32-C3, an SPI panel up to 320 × 240. For an ESP32-S3 with octal PSRAM, an RGB panel around 480 × 480 to 800 × 480. For an ESP32-P4, a MIPI DSI panel that runs on 2 lanes.

Can an ESP32 drive an 800 × 480 display?

Yes, an ESP32-S3 can over RGB with the frame buffer in PSRAM, but with octal PSRAM at 80 MHz expect a pixel clock near 22 MHz, about 40 Hz on an 800 × 480 panel with a 1056 × 525 total frame. An ESP32-P4 has more headroom.

Does the ESP32 support MIPI DSI?

Only the ESP32-P4, with up to 2 data lanes at 1.5 Gbit/s each. Other ESP32 chips use SPI, I80 or RGB panels.

Building a product around an ESP32 display? Send the ESP32 variant, PSRAM type, target resolution and frame rate, touch requirement and enclosure size. We will suggest a catalogue reference with an interface that fits and confirm the init sequence and FPC. See custom TFT displays and the TFT LCD module catalogue, or send an ESP32 display enquiry.

Scroll to Top
Get a QuoteWhatsApp