ESP32-CAM Camera Init Failed and Brownout Fixes

You upload the CameraWebServer sketch, open the Serial Monitor, and instead of a stream URL you get Camera init failed with error 0x105, or the board prints Brownout detector was triggered and reboots. Both errors are common on the classic ESP32-CAM, and both usually come down to the same two things: the board is not getting clean, steady power, or the camera sensor is not talking to the chip. Work through the checks below in order and most boards start streaming without new hardware.

This guide covers the classic AI-Thinker style ESP32-CAM with the OV2640 camera. The power and PSRAM steps also apply to the ESP32-S3-CAM, but that board has a different pin map, so verify pins against your own board variant.

What does “Camera init failed” mean?

It means the ESP32 ran esp_camera_init() and the sensor did not answer. The driver first talks to the sensor over a small two-wire control bus (SCCB, like I2C) and asks it to identify itself. If nothing answers, setup stops and the sketch prints the error code, and no stream URL appears.

The usual reasons are a loose ribbon cable, the wrong camera model or board, or a supply that sags during the camera startup spike.

What is an ESP32-CAM brownout?

A brownout is a brief dip in supply voltage below the level the ESP32 needs to run. The chip has a built-in brownout detector that watches the 3.3V rail. When the rail sags too far, even for a moment, the detector resets the chip, and the Serial Monitor prints Brownout detector was triggered, often with rst:0xf (BROWNOUT_RST).

The ESP32-CAM is more prone to brownouts than a bare ESP32 board because the camera and Wi-Fi draw sharp current spikes at the same time. MakerGuides reports the board can draw up to about 500 mA with the camera and Wi-Fi active, and Projectech puts Wi-Fi transmit bursts at 160 to 260 mA with the camera and flash LED adding more on top. A laptop USB port, a thin cable, or a weak adapter cannot always deliver those spikes fast enough. The fix is a better supply, not a code change.

Which error are you seeing?

Match your Serial Monitor output to a row first. Starting in the wrong place is the most common way to waste an evening on this board.

What you see Most likely cause Check first
Camera init failed with error 0x105 on every boot Sensor not found: loose cable, wrong model, wrong pin map Ribbon cable seating, then camera model in the sketch
Camera init failed with error 0x105 sometimes Power sags during camera startup 5V 2A supply, short thick cable, capacitor across 5V and GND
Camera init failed with error 0x20001 Sensor not detected by the driver Ribbon cable, camera model, then power
Camera init failed with error 0x20004 or 0x103 Frame buffer could not be allocated, or the control bus timed out PSRAM enabled, lower resolution, one frame buffer
frame buffer malloc failed then Camera init failed with error 0xffffffff PSRAM not enabled or resolution too high PSRAM enabled, lower resolution, frame buffer count to 1
Brownout detector was triggered or rst:0xf (BROWNOUT_RST), then reboot loop Supply sagging under Wi-Fi or camera spikes 5V 2A supply, capacitor, short thick leads
Camera starts, board reboots when streaming starts or the flash LED turns on Wi-Fi or flash LED spike collapses the rail Capacitor across 5V and GND, separate 5V supply, test with flash off
Works on a wall adapter, fails on a laptop USB port USB port current limit or thin cable voltage drop Wall adapter, powered hub, shorter cable
Detected camera not supported with error 0x106 Newer drivers report a missing sensor this way Same steps as 0x105; replace the camera module if it persists

What do the error codes mean?

The camera driver returns a numeric code from esp_camera_init(). These are the codes builders actually see.

Error code Meaning First fix
0x105 ESP_ERR_NOT_FOUND: the camera probe found no sensor on the control bus. The sensor did not answer: no power, cable not seated, or wrong pins. Reseat the ribbon cable with power off, confirm the camera model in the sketch, check the supply
0x20001 Camera not detected by the esp32-camera driver. Same practical meaning as 0x105: the sensor did not answer the probe. Same as 0x105: cable, camera model, power
0x106 Newer drivers report a missing or unrecognised sensor as Detected camera not supported. Same steps as 0x105; try a known-good camera module
0x20004 / 0x103 Reported by some guides as a PSRAM allocation failure or a control bus timeout. Secondary sources disagree on the exact mapping for these codes. Enable PSRAM, lower the resolution, check the cable
0xffffffff Frame buffer memory could not be allocated, usually after a frame buffer malloc failed line. Enable PSRAM, lower the resolution, set frame buffer count to 1
rst:0xf Brownout reset: the brownout detector tripped and reset the chip. This is a reset reason, not a camera error. Power supply checklist below

Two notes on the codes. First, 0x105 is confirmed as ESP_ERR_NOT_FOUND by the driver log line itself, Camera probe failed with error 0x105(ESP_ERR_NOT_FOUND), which appears in Arduino Forum threads and in two of the guides below. Second, one guide maps 0x105 to a power fault while others map it to a probe fault. The log line supports the probe reading, and a weak supply can cause a probe fault too. See the unverified flags at the foot of this post.

How do I diagnose it step by step?

Do these in order. Each step rules out a whole category. Do not skip ahead to replacing the camera module until steps 1 to 5 pass.

  1. Read the exact error. Open the Serial Monitor at the baud rate your sketch uses (usually 115200) and copy the full line, including the hex code. 0x105 or 0x20001 means cable, model, or power; a malloc failure means PSRAM; a brownout line means power only.
  2. Fix the power first. Connect a regulated 5V 2A supply to the 5V pin with a short, thick USB cable. Do not use a laptop USB port or an adapter 3.3V output while diagnosing. If the error changes on the wall adapter, the supply was the problem.
  3. Reseat the ribbon cable with power off. Lift the black locking flap, pull the 24-pin ribbon cable out, push it back in straight and fully, then close the flap. Check the cable is not creased or nicked, then power on and read the error again.
  4. Confirm the board and camera model in the sketch. In the Arduino IDE, select AI Thinker ESP32-CAM, and check the sketch defines CAMERA_MODEL_AI_THINKER for a classic ESP32-CAM with an OV2640. A generic ESP32 Dev Module board can disable the PSRAM mapping the camera needs.
  5. Enable PSRAM. Set Tools, PSRAM to Enabled. Then lower the resolution one step (UXGA to SVGA), set the frame buffer count to 1, and test again. If a malloc error clears, memory was the limit.
  6. Remove GPIO0 from ground. If you jumpered GPIO0 to GND to flash the board, remove that jumper before running the sketch. Held low, GPIO0 keeps the board in flash mode and the camera never initialises.
  7. Test with Wi-Fi and the flash LED off. If the board resets when streaming starts or the flash turns on, the current spike is collapsing the rail. Add the capacitor and retest.
  8. Swap one part at a time. Try a different USB cable, then a different camera module, then a different board, changing one thing per test.

Why does power cause most ESP32-CAM failures?

Three facts stack against this board. First, the classic ESP32-CAM has no onboard USB-to-serial chip, so most builders power it through an adapter whose 3.3V output typically supplies only 50 to 100 mA, far below what the camera and Wi-Fi draw together. Second, the onboard AMS1117-3.3 regulator needs a 5V input with headroom to hold the rail steady during spikes. Third, the camera and Wi-Fi spike at the same moment during startup and streaming, so the worst load lands exactly when the driver probes the sensor.

  • Power the board through the 5V pin, not the 3.3V pin. The 3.3V pin bypasses the onboard regulator, and a weak 3.3V source sags under load.
  • Use a regulated 5V 2A supply. A 1A supply is the minimum several guides quote, and 2A leaves headroom for the spikes. A phone charger rated 5V 2A works; a laptop USB port often does not.
  • Use a short, thick USB cable. Long thin cables add resistance, and resistance turns a current spike into a voltage drop.
  • Add a bulk capacitor across 5V and GND. A 470uF to 1000uF electrolytic capacitor near the board supplies the millisecond spikes the regulator cannot track. Add a 0.1uF ceramic capacitor in parallel for high-frequency noise. Watch the polarity: the marked side goes to ground.
  • Keep the serial adapter at 3.3V logic. The adapter is fine for the TX and RX signal lines, and its logic jumper should stay at 3.3V, since ESP32 GPIO pins are not 5V tolerant.
  • Do not share the rail with hungry peripherals. Motors, servos, and LED strips draw their own spikes, so give them a separate regulated supply with a common ground.

For a battery-powered build, the battery path must still deliver a steady 5V under spike load. A small lithium cell alone cannot do that without a boost stage, so use a battery module with a regulated 5V USB output and test under streaming load, not just at idle.

Power-supply checklist

Check Pass looks like Fail looks like
Supply rating Regulated 5V adapter rated 2A Laptop USB port, unbranded 5V 500 mA charger
Power pin 5V pin fed from the adapter 3.3V pin fed from an adapter
USB cable Short, thick, data rated Long thin charging cable
Capacitor 470uF to 1000uF electrolytic across 5V and GND, close to the board No capacitor, or one far from the board
Breadboard Power wired direct to the board pins Power through a breadboard with loose jumpers
Flash and stream test Board stays up with the flash LED on and the stream running Board resets when the flash turns on or the stream starts
Battery test Battery module with regulated 5V output Bare cell wired direct

Is the ribbon cable the problem?

The 24-pin ribbon cable between the camera module and the board is the most fragile part of the build, and a bad seating produces exactly the 0x105 probe failure. Power the board off first, then lift the black locking flap, slide the cable out, and look at it: the gold fingers should be clean and straight, the cable should not be creased, and the blue stiffener should sit flat. Push the cable in straight and all the way, then close the flap. If it went in crooked, the sensor gets power on the wrong pins or no connection at all.

Two more checks. Clean the gold fingers with isopropyl alcohol and a cotton swab if the module sat unused in a damp room; oxidation on the contacts is a real failure mode. If reseating changes nothing, try a different camera module on the same board. If a known-good module works, the first module or its cable is faulty.

Is PSRAM enabled and the right board selected?

The ESP32-CAM needs its external PSRAM to buffer image frames. The classic board carries 4MB of PSRAM. If the Arduino IDE is not told the PSRAM exists, the driver fails to allocate memory, and you see a malloc failure or an init error at higher resolutions.

Check three settings. First, the board must be AI Thinker ESP32-CAM, not a generic ESP32 Dev Module, because the board selection carries the pin definitions and PSRAM mapping. Second, Tools, PSRAM must be set to Enabled. Third, the partition scheme must leave enough app space. If the error clears at a lower resolution or with one frame buffer, memory was the limit.

Is the wrong camera model selected?

The sketch must define the camera model that matches the hardware. For the classic ESP32-CAM with an OV2640, that is CAMERA_MODEL_AI_THINKER. Other boards use different definitions and pin maps, so a sketch written for one board fails on another with the same 0x105 probe error. Check the definition at the top of the sketch before changing anything else.

The sensor matters too. An OV2640 and an OV5640 are not interchangeable: the OV5640 needs its own initialisation settings, and OV2640 settings fail the probe on an OV5640 module. The ESP32-S3-CAM in the parts list below carries an OV5640, so use the S3 board definition and the S3 guide for that hardware. Verify the pin table for your board variant before wiring, because published pin tables disagree on some signals.

What are the common mistakes?

  • Powering the board from the 3.3V pin of a USB-to-serial adapter instead of the 5V pin.
  • Using a laptop USB port or a long thin charging cable.
  • Leaving the GPIO0 to GND jumper in place after flashing.
  • Selecting a generic ESP32 Dev Module board instead of AI Thinker ESP32-CAM.
  • Leaving PSRAM disabled, then running UXGA resolution with two frame buffers.
  • Reseating the ribbon cable with power on, or pushing it in crooked.
  • Setting the USB-to-serial adapter to 5V logic and feeding 5V into the RX pin.
  • Changing the sketch, the cable, and the power supply all at once.

When is the board or camera module dead?

If the power checklist passes, the cable is reseated, the board and camera model are correct, PSRAM is enabled, and a known-good camera module still fails with 0x105 or 0x20001, the board itself is the suspect. Check the connector for a lifted flap or bent pins, and look for a damaged AMS1117 regulator if the board browns out on a known-good 5V 2A supply. Before replacing anything, run the same module on a second board: a module that fails on two boards is a bad module, and a board that fails with two modules is a bad board.

Parts used in this guide

These parts are in stock at Quality RC Parts in Queensbury, NY, shipping within the USA. Prices verified live on 2026-11-21.

Related guides on this site: ESP32-CAM Getting Started, ESP32-CAM Flashing and First Camera Stream, ESP32-CAM Pinout, ESP32 Brownout Reset and Boot Loop: Causes and Fixes, ESP32-CAM S3-CAM Camera Projects Guide, ESP32-S3-CAM Guide.

Frequently asked questions

How do I fix the ESP32-CAM “Camera init failed” error?

Check the error code first. For 0x105 or 0x20001, reseat the ribbon cable with power off, confirm CAMERA_MODEL_AI_THINKER for a classic board, enable PSRAM, and power the board from a regulated 5V 2A supply. For a malloc failure, enable PSRAM and lower the resolution. (Source: Bluegrays; Robotics Engineering.)

What does “Brownout detector was triggered” mean?

It means the supply voltage dipped below what the ESP32 needs and the built-in detector reset the chip. The usual cause is a weak supply, a thin or long USB cable, or current spikes from Wi-Fi and the camera. Fix it with a regulated 5V 2A adapter, a short thick cable, and a 470uF to 1000uF capacitor across 5V and GND. (Source: MakerGuides; ESPBoards.)

What does error 0x105 mean on the ESP32-CAM?

It is ESP_ERR_NOT_FOUND: the camera probe found no sensor on the control bus. The sensor did not answer, usually because the ribbon cable is loose, the wrong camera model is selected, or the power sagged at startup. (Source: Robotics Engineering; Bluegrays; Arduino Forum.)

Can I power the ESP32-CAM from the 3.3V pin?

You can, but you should not. The 3.3V output of a typical USB-to-serial adapter supplies only about 50 to 100 mA, and the board draws far more with the camera and Wi-Fi running. Power the board through the 5V pin and let the onboard regulator step it down. (Source: MakerGuides; ElectricalFlux.)

What size capacitor fixes an ESP32-CAM brownout?

A 470uF or larger electrolytic capacitor across 5V and GND, close to the board, is what MakerGuides and Projectech recommend; ESPBoards gives a 470uF to 1000uF range. Add a 0.1uF ceramic capacitor in parallel for high-frequency noise. The capacitor fixes spikes, not a supply that is too weak overall. (Source: MakerGuides; ESPBoards; Projectech.)

Sources


Last updated: 2026-11-21