Raspberry Pi camera not detected: ribbon cable, port and software test

Power off, reseat the ribbon cable in both ends with the contacts facing the right way, and run the camera test again.

What the message means

The ribbon cable is delicate and has a front and a back. A half-inserted cable or the wrong port gives no camera.

Fix it in this order

Shut the Pi down and remove power before you touch the cable.
Lift the connector latch, push the cable in fully with the contacts facing the correct way, and close the latch.
Check that the cable is the right type for your Pi and camera, since connector sizes differ.
Use the camera port, not the display port, and the right port number on boards with two.
Run the camera test tool of your operating system version and read its message.
Update the operating system if the camera is new.

Why it happens

The camera connects through a flat ribbon cable with exposed contacts on one side. The contacts must meet the pins inside the connector, so a cable that is half inserted, reversed or in the wrong port makes no connection and the system reports no camera.

The cable and latch are delicate, so work with the power off and do not bend the cable sharply. Newer boards can have different camera connectors, so check which port and cable your Pi and camera need.

If you see this, do this

You see	Do this
No camera listed	Cable, port or cable type.
Listed but no picture	Check software and cover on the lens.

ESP32-CAM upload, Raspberry Pi GPIO levels.

Last reviewed: November 2026. These are the usual causes and the order that finds them fastest. Test on your own board; clones and cables differ.

Why this happens

The camera ribbon cable carries the image data on fine conductors, and the connector has contacts that must line up with them exactly. The cable has bare contacts on one face only. It must be pushed in fully, with the contacts facing the correct way, and the latch closed to hold it. A cable that is a few millimetres short of full depth looks seated but makes no contact on some of the lines, so the camera does not answer.

Different boards use different connectors. Pi 5 and the Pi Zero models use a smaller connector than the standard Pi boards, and need a matching cable. Pi 5 has two camera ports, and the software addresses them by number. A cable that fits physically but is the wrong kind can also fail.

How to confirm the cause

Power off the Pi. Reseat both ends of the cable and check the latches are closed.
Check the orientation against the diagram for your board and camera. Which way the contacts face can differ between the camera end and the Pi end.
Run the camera list command for your system, such as rpicam-hello –list-cameras on current releases, or libcamera-hello –list-cameras on older ones. An empty list means no camera was found.
Search the system log for camera messages with dmesg and grep. Messages about the sensor driver show whether the sensor was found.
Check the configuration file for camera detection, which is normally switched on by default on current releases.

Worked example

The commands below list cameras and search the log. On a current release the configuration file is in the firmware folder under /boot, and on older ones it is directly in /boot. A line enabling camera detection is normally already present.

# list cameras seen by the system
rpicam-hello --list-cameras
# older releases
libcamera-hello --list-cameras

# look for sensor messages
dmesg | grep -i -E "camera|imx|ov5647"

# in config.txt, camera detection should be on
camera_auto_detect=1

Common mistakes

Plugging the cable in with the power on.
Inserting it the wrong way round or not fully.
Using the display connector instead of the camera connector.
Forcing the latch or bending the cable sharply.
Using an old command that does not exist in the newer software.

If this did not fix it

A damaged cable. Try another one if you have it.
An outdated system image that does not support your camera. Update it.
A supply that is too weak, which makes the camera fail to start under load.