Blog
ESP32 Install: Boards, IDEs, Libraries
Installing the ESP32 board package and libraries in the Arduino IDE and VS Code — the setup questions that stop people before the first blink.
How to Install ESP32?
Install the board package and the IDE knows the chip. In Arduino IDE: File → Preferences, paste https://dl.espressif.com/dl/package_esp32_index.json into “Additional Boards Manager URLs,” then Tools → Board → Boards Manager, search “esp32,” and install “esp32 by Espressif Systems.” One package covers the WROOM-32D, S3, and C3. On my Windows machine the first install took about four minutes; later ones are faster because the compiler stays cached. Restart the IDE afterwards — the board list refreshes on restart, and skipping that is why people think the install failed. The Arduino IDE FAQ has the same walkthrough with the gotchas called out.
How to Add ESP32 to Arduino?
“Add” and “install” are the same operation: you add a board by installing its package from Boards Manager. Paste the Espressif JSON URL into Additional Boards Manager URLs, then install, then restart — that restart resolves half the “still not there” reports.
How to Install ESP32 in Arduino?
It means the same thing as “add”: the Espressif board package defines every ESP32 variant. After it lands, verify via Tools → Board → ESP32 Arduino → ESP32 Dev Module. Submenu missing? Reinstall and restart before anything else.
How to Install ESP32 in Arduino 2.0?
Arduino IDE 2.x keeps the same Additional Boards Manager URLs field under File → Preferences. 2.x shows per-package progress and installs packages side by side. Old packages shadow new ones, so uninstall the old ESP32 entry before upgrading from 1.8.x. Mostly works fine once you know that.
How to Install ESP32 Libraries?
Sketch → Include Library → Manage Libraries, search, install — libraries install per IDE, not per board. The ESP32 core ships built-ins (WiFi, BLE, esp32-hal), so “library not found” errors are usually a missing include path, not a missing install. Third-party libraries appear as soon as the board package is present.
How to Get VSCode Working with ESP32?
Two routes. PlatformIO extension: install it, create a project, pick “Espressif ESP32 Dev Module” as the board, and the toolchain downloads on the first build — this is the route I use daily; libraries are per-project. Or the Arduino extension plus the board package you already installed. The first build pulls ~500 MB of toolchain, which looks like a hang on slow connections; it is not, wait it out. The PlatformIO FAQ covers project layout.
Why does the install fail at “Downloading packages”?
Usually the network, not the files — proxies and VPNs break the download mid-way, and the IDE retries from scratch. Fixes: clear the staging folder and retry; switch to a wired connection; unset the proxy; or install manually. The manual path differs by IDE version and the official docs are vague about it, so most people retry the network route.
Do I need both VS Code and the Arduino IDE?
No. Pick one. Arduino IDE is the gentler path; PlatformIO is the engineering path with better debugging and per-project libraries. The code is the same C++ either way.
What about installing MicroPython instead?
Different install, same hardware: erase the flash with esptool, then write the MicroPython firmware binary to address 0x1000. The Arduino board package is irrelevant from that point — MicroPython does not use the Arduino toolchain at all. Good if you prefer Python, with weaker sensor-library coverage as the trade-off. Depends on your project, honestly.
The install worked — what now?
Blink. Upload the Blink sketch, watch the serial monitor, then wire an LED to GPIO2. That loop — install, flash, print — is most of what “install” means in practice, and the flashing FAQ is the recovery path when it stops working later.
Install Nothing, Start in 30 Seconds
Every install path in this FAQ — core downloads, board manager indexes, toolchains — exists to get code onto silicon. The simulator starts at the same endpoint:
- 243 examples, zero setup: click one, it compiles with arduino-cli and runs on an emulated ESP32. Start with blink if you are new; end with DOOM if you are not.
Learn the board and the libraries first; install the toolchain when you actually need to flash. Inverted order, fewer dead ends.