The one line that changes

One token, five answers

LB_TFT_24 is not a resolution and it is not a chip name. It is a row in a table, and the row holds five things the driver needs before it can put a single pixel anywhere: which controller is behind the glass, how many pixels there are, how fast the bus may run, which way round the backlight is wired, and how far into the controller's memory the visible pixels start.

Change the constant and all five change. Nothing else in the sketch does.

Why the offsets exist at all

A display controller has a fixed amount of pixel memory, and the glass in front of it is sometimes smaller. An ST7735 has room for 132 × 162 pixels; the 0.96 inch panel shows 80 × 160 of them, starting 24 columns in.

Get that wrong and the picture is not missing, it is shifted — text runs off one edge with a band of junk down the other. It is one of the most common symptoms people post about these panels, and it is not a fault. It is a driver that was never told where the window is.

What the table is, and how much to trust it

The constants come from a file called panels.yaml in the display library, which is the single source of truth for both the Arduino side and the MicroPython side — both are generated from it, and the library's own tests fail if the two ever disagree.

It is worth being honest about how solid each column is. The driver chips and resolutions are firm: they match the product listing's own comparison table for all six panels. The SPI clocks are conservative choices rather than measurements — the old per-panel Arduino sketches ran at 40 MHz and the MicroPython ones at 20, and the library took the lower figure until somebody checks. The colour order and inversion flags have not been measured on a kit panel at all, which the file says in a warning at the top of itself.

That last one matters less than it sounds, because a colour fault announces itself immediately and takes one call to fix. There is an article on reading the symptom.

MicroPython says the same thing

from lb_display import LBDisplay
from lb_panels import TFT_24          # the only line that changes

d = LBDisplay(TFT_24)
d.begin()

Same table, same six names without the LB_ prefix, and the pins are picked at runtime from the chip the script is running on rather than at compile time. One script runs on a classic ESP32 and an ESP32-S3 unmodified.