A small display reaches a Raspberry Pi through DSI, HDMI, SPI, I²C, or USB, and matching the cable to that exact interface decides whether the screen works.
Raspberry Pi 5 and Raspberry Pi 4 need different ribbon cables for the same 7-inch panel, and a mechanically similar FFC in the wrong size can leave the screen dead or damage the board. Whether the panel is an official touchscreen or a generic module, knowing how to connect a small display to a Raspberry Pi starts with the port on the display, not the cable that looks close enough.
Three interface families cover nearly every panel sold today. The table below lines up each one with the cable it needs and the extra requirement that trips people up.
Which Display Interface Fits Your Raspberry Pi?
An official DSI touchscreen uses the board’s DSI connector plus a power lead on the GPIO header, while an HDMI display uses a normal HDMI cable and usually its own power supply. Panels wired to GPIO pins over SPI or I²C depend on the seller’s wiring diagram and driver, and an HDMI or DSI screen will not run through those pins.
| Interface | Cable Or Connector | What Else It Needs |
|---|---|---|
| DSI, Touch Display 2 (5-inch and 7-inch) | Supplied FFC: 22-way-to-15-way Standard–Mini on Raspberry Pi 5, 15-way-to-15-way on Pi 4 and earlier | Power lead on the specified GPIO pins |
| DSI, Touch Display 2 (10-inch) | 22-way-to-22-way Mini–Mini FFC | Raspberry Pi 5 or a Compute Module |
| HDMI | Standard or micro-HDMI cable and adapter | Separate power supply for most panels |
| SPI or I²C | Jumper wires to the display’s labeled pins | Bus enabled plus the vendor’s driver |
| USB | USB cable from panel to Pi | Driver support that varies by model |
Compatibility is worth checking before you buy. The 5-inch and 7-inch Touch Display 2 work with boards from the Raspberry Pi 1 Model B+ onward except the Zero series, while the 10-inch version runs only on Raspberry Pi 5 and Compute Modules. The original 7-inch Touch Display does not connect directly to a Raspberry Pi 400 or a Zero through the normal DSI connection.
Panels outside the official lineup vary widely in cable length and driver support, and this tested roundup of small Raspberry Pi displays sorts them by what plugs in where.
Connecting A Small Display To A Raspberry Pi: The Step Order That Works
A DSI panel goes on with the Pi powered down: ribbon cable seated in both connectors, contacts facing the matching contacts, power lead on the documented GPIO pins, then boot.
- Shut down the Raspberry Pi and pull its power cable.
- Match the FFC to the board: Raspberry Pi 5 and later take the supplied 22-way-to-15-way Standard–Mini cable for the 5-inch and 7-inch Touch Display 2, and Raspberry Pi 4 and earlier take the 15-way-to-15-way cable.
- Seat the ribbon cable in the display’s DSI connector and in the Pi’s DSI connector, then check the board-specific diagram for contact orientation.
- Connect the display’s power lead to the specified GPIO header pins — no other pins, no other voltage source.
- Mount the panel so no conductive hardware can short the board.
- Reconnect power and boot Raspberry Pi OS.
Raspberry Pi’s Touch Display 2 documentation lists the FFC part numbers and GPIO pin details for each board revision.
Overlays And The Mistakes That Cause A Blank Screen
A blank panel after a correct-looking install comes from one of five causes: the wrong FFC size, an upside-down cable, an unsupported board, a missing overlay line, or a weak power supply.
- Wrong cable. Raspberry Pi 5 and older boards use different FFC sizes, and a similar-looking but electrically wrong cable can block operation or damage hardware.
- Wrong connector. A camera connector does not carry display signals unless the board and overlay explicitly support that use.
- Upside-down FFC. Contacts must face the connector contacts, so check the board diagram rather than guessing.
- Unsupported board. The Zero series is excluded from the Touch Display 2 DSI connection, and the 10-inch model needs Raspberry Pi 5 or a Compute Module.
- Weak supply. The display’s GPIO power lead does not replace a suitable power supply for the Raspberry Pi itself.
Compute Modules and non-default connectors need an overlay line. Open /boot/firmware/config.txt, add the entry for your panel, and reboot:
- 5-inch:
dtoverlay=vc4-kms-dsi-ili9881-5inch - 7-inch:
dtoverlay=vc4-kms-dsi-ili9881-7inch - CAM/DISP 0 or DISP0 connector: add the suffix, for example
dtoverlay=vc4-kms-dsi-ili9881-7inch,dsi0
The original 7-inch Touch Display on DISP1/DSI1 uses dtoverlay=vc4-kms-dsi-7inch, and disable_touchscreen=1 switches off the touch layer while leaving the panel as a plain display.
So the short version: an HDMI panel takes a cable and its own power, an official DSI panel takes the correct FFC plus a GPIO power lead, and an SPI, I²C, or USB panel takes the maker’s wiring and driver. Buy the panel that matches the connector on your board and the whole job stays at one cable and one lead.
Common Questions
Can The Raspberry Pi Power A Panel Through GPIO?
The GPIO lead powers the display, not the entire setup. A Raspberry Pi still needs its own suitable power supply, and the display’s power wire belongs only on the pins named in the hardware documentation. Running a panel from other pins or a different voltage source can leave the screen dark or stress the board.
Do DSI Touchscreens Need Drivers Installed?
An overlay line is needed only for a Compute Module or a non-default DSI connector, and the documented overlay names differ across the 5-inch, 7-inch, and 10-inch versions.
Will A Raspberry Pi Zero Run A Touch Display 2?
Not through the standard DSI connection. The 5-inch and 7-inch Touch Display 2 support boards from the Raspberry Pi 1 Model B+ onward, but the Zero series is excluded, and the 10-inch version works only with Raspberry Pi 5 and Compute Modules. An HDMI panel suits a Zero build better.
Sources
- Raspberry Pi. “Touch Display 2” Supports the cable types, GPIO power connection, overlay names, and per-board compatibility.
- Raspberry Pi. “Displays” Explains DSI, HDMI, and GPIO-connected display interfaces and the common connection errors.