Blog
ESP32 Display: LCD, TFT, ILI9341
How to connect lcd to esp32, which TFT controller to trust, whether the I2C backpack is worth it — display questions show up in every third project. The answer is one chip on the panel; this FAQ covers the 16×2 LCD, the ILI9341 TFT, and the wiring between them.
How to Connect LCD to ESP32?
A 16×2 LCD with an I2C backpack needs four wires: VCC, GND, SDA, SCL. On a classic ESP32 the defaults are GPIO21 for SDA and GPIO22 for SCL; on ESP32-S3 or C3 boards they move, so check the pinout. The backpack is a PCF8574 that turns eight parallel lines into two.
How to Use LCD with ESP32?
Install the LiquidCrystal_I2C library, then lcd.init() and lcd.backlight() in setup. The line that trips everyone is the address: it defaults to 0x27, but 0x3F boards exist — scan the bus first. My DevKit V1 answered at 0x27; a friend’s identical-looking board at 0x3F.
How to Hook Up LCD Display to ESP32?
Same four wires, two habits that prevent half the support threads: power the backpack from 5V when the panel looks dim (many 1602s struggle on 3.3V), and keep the SDA/SCL jumpers short — 20 cm works, 50 cm glitches. A lit screen with blocks is the contrast pot’s fault.
How to Use ESP32 to Print on LCD?
lcd.setCursor(column, row) then lcd.print() — a 16×2 has columns 0-15 and rows 0-1, with no wrapping: text past column 15 is invisible. For a counter that never stacks garbage, write over the old value instead of clearing the screen. Example projects show the pattern.
How to Set Up ST7789 TFT LCD with ESP32-S3?
With TFT_eSPI the setup lives in one header file: pick the driver (ST7789 — not ILI9341, the two are not pin-compatible), set width and height, then assign TFT_CS, TFT_DC, TFT_RST, TFT_MOSI, TFT_SCLK to real pins. Which pins work on an ESP32-S3 depends on the board, and the library docs are vague here. Change User_Setup.h, recompile — the InitDisplay example either draws or shows rainbows for “wrong driver”.
How to Control LCD with ESP32 MicroPython?
MicroPython has no LiquidCrystal, so install lcd_api plus a driver class (pcf8574 or esp32_gpio_lcd) and drive it via machine.I2C(0, sda=Pin(21), scl=Pin(22), freq=400000). Then lcd.putstr("Hi") prints. Ported C++ mostly fails on argument ordering — a syntax error until you swap sda and scl, which I hit on a fresh install.
Can I connect an LCD without the I2C module?
Yes — raw parallel: RS, E, D4-D7, VCC, GND, and a 10k contrast pot. Ten wires instead of four, and the sketch switches to the plain LiquidCrystal library with pins in the constructor. If you are asking how to connect lcd to esp32 without i2c module, the answer is this parallel wiring.
LCD, TFT, or OLED — which display do I pick?
Three questions decide it. Only text and under $3: a 16×2 LCD. Graphics or color: an ILI9341 2.4-inch TFT over SPI — the most-documented SPI display in the hobby. Low power or sunlight: OLED. How to connect a esp32 to a display reduces to the controller chip, so buy the panel whose library you trust.
Can I use two displays at once?
On an ESP32-S3, yes: two I2C buses or two chip-select lines on one SPI bus, and each library supports multiple instances. The real limit is RAM, not wiring — a TFT framebuffer eats tens of kilobytes. So how to use multiple displays with esp32-s3 starts with counting bytes, not pins.
The screen shows blocks or nothing — where do I start?
Blocks mean contrast or power; nothing means wiring or address. Run the I2C scanner first — it answers the address question in one upload — then confirm SDA and SCL are not swapped. A display that worked yesterday and died overnight is almost always a loose jumper; the getting started FAQ covers the boot side.
Light Up Every Display Class — In Your Browser
All three display families from this FAQ run free in our simulator:
- SSD1306 OLED over I2C — boots to
OLED ready!then draws live:Frame: 42,Frame: 43… - 7-segment counter — plain GPIO driving digits:
ESP32 7-Segment Counter/Digit: 7 - TFT over hardware SPI — a textured raycaster on ILI9341 with live stats:
STAT frame=348 t_ms=29114 devfps=11.9
I2C for two wires, SPI for speed, GPIO for brute simplicity — run one of each and the protocol choice stops being a spec-sheet memory exercise.