ESP32 dev board with USB-C cable for installing USB drivers

How to Install CP210x USB Drivers for ESP32 & ESP8266

Updated

Updated October 2026: added CH340 drivers, boards with built-in USB, and Linux and Mac checks.

If your computer doesn't detect your ESP32 or ESP8266 board when you plug it in, the usual cause is a missing USB-to-serial driver. Without it, your computer won't give the board a COM port (or serial port), and the Arduino IDE or PlatformIO in VS Code can't talk to it or upload your code.

Most classic ESP32 and ESP8266 dev boards use one of two USB-to-serial chips: the Silicon Labs CP210x (usually the CP2102) or the WCH CH340. This guide covers both.

Before you start: two quick checks

  • Use a data cable. Many USB cables, especially ones bundled with chargers and gadgets, only carry power. If the board lights up but nothing appears on your computer, try another cable before anything else. If you're not sure, our USB-C data cable is tested for programming.
  • Check which chip your board has. Look at the small chip next to the USB port. It will be marked CP2102 (or CP2104), CH340 (or CH343), or there may be no extra chip at all. You need the driver that matches that chip.

Boards with built-in USB don't need these drivers

The ESP32-S3 SuperMini, the ESP32-C3 SuperMini and other boards whose USB port connects straight to the ESP32 chip use the chip's own USB. Windows 10 and 11, macOS and Linux recognise them without any driver. If one of these boards won't show up, the cause is usually the cable, or a setting in your code (see the pin guide's PlatformIO settings for USB CDC). It is not a missing driver.

Step 1: Download the driver

CP210x (Silicon Labs)

All downloads are on the Silicon Labs CP210x VCP drivers page. Open the Downloads tab and choose:

  • Windows 10 and 11: CP210x Universal Windows Driver.
  • Mac: CP210x VCP Mac OSX Driver.
  • Linux: nothing to download. The cp210x driver is built into the Linux kernel.

CH340 (WCH)

Download drivers only from these manufacturer pages. Driver files from other sites can be out of date or unsafe.

Step 2: Install the driver

Windows

  1. Unzip the download to a folder.
  2. CP210x Universal driver: right-click silabser.inf and choose Install. (On Windows 11 you may need Show more options first.) The older CP210x VCP Windows package instead includes an installer: run CP210xVCPInstaller_x64.exe.
  3. CH340: run CH341SER.EXE and click Install.
  4. Unplug the board and plug it back in.

Mac

  1. Open the downloaded .dmg or .pkg and run the installer.
  2. If macOS blocks it, open System Settings > Privacy & Security (on older macOS, System Preferences > Security & Privacy) and click Allow next to the Silicon Labs or WCH message.
  3. Restart if the installer asks you to, then plug the board back in.

Recent versions of macOS often recognise CP2102 and CH340 boards without any extra driver. Check Step 3 first. If your board already shows up, you don't need to install anything.

Linux

The drivers are already there. You may need permission to use the serial port. Add yourself to the dialout group (on Arch-based systems it's uucp), then log out and back in:

sudo usermod -a -G dialout $USER

Step 3: Check the connection

  • Windows: open Device Manager and expand Ports (COM & LPT). You should see Silicon Labs CP210x USB to UART Bridge (COM3) or USB-SERIAL CH340 (COM4), or similar. If the board appears under Other devices with a yellow warning sign, the driver isn't installed yet.
  • Mac: in Terminal, run ls /dev/cu.*. Look for something like /dev/cu.SLAB_USBtoUART, /dev/cu.usbserial-0001 or /dev/cu.wchusbserial....
  • Linux: run ls /dev/ttyUSB*. You should see /dev/ttyUSB0.

A quick test: run the check, unplug the board, run it again. The port that disappears is your board.

Once you see the port, select it in the Arduino IDE under Tools > Port. In PlatformIO, the port is usually found automatically. You can set it with upload_port in platformio.ini if you have several boards plugged in.

Troubleshooting

  • Still no port, even with the driver installed. Swap the cable first. Then try a different USB port on your computer, ideally directly on the computer rather than through a hub.
  • Port appears, but uploads fail with "Failed to connect" or "Timed out waiting for packet header". Hold the BOOT (IO0) button, start the upload, and release it when you see Connecting... in the output.
  • Port is busy or access is denied. Another program is using it. Close any other Serial Monitor or second IDE window, and try again.
  • Wrong port chosen. Windows may give the board a new COM number when you use a different USB socket. Recheck Tools > Port.
  • Upload works but the Serial Monitor shows nonsense. Match the baud rate in the monitor to the one in your code, usually 115200. In PlatformIO, set monitor_speed = 115200.

Next steps

Further reading: Random Nerd Tutorials: Install ESP32 / ESP8266 USB Drivers.

Back to blog

Leave a comment