ESP32 Development Boards, Modules and IoT Accessories

ESP32 hardware for embedded, wireless and connected projects

Explore ESP32-family microcontroller modules, development boards, display controllers, camera boards, LoRa nodes, networking and industrial I/O hardware, as well as programming tools and project accessories. This is a broad engineering collection, not a single interchangeable ESP32 board. Selected products also include ESP8266, RP2040/RP2350, SAMD21, nRF52, MG24 and other non-ESP32 choices, plus antennas, bare PCBs, cameras, power boards and finished kits. A listing headline often describes several selectable products: the chosen variant determines the actual chip, physical assembly, radio band, accessory and pack quantity.

Start with the silicon family, not the headline

Classic ESP32 boards and WROOM-32/WROVER modules are common choices for 2.4 GHz Wi-Fi and Bluetooth projects; a WROOM module is not the same delivered item as a USB-equipped DevKit board. ESP32-S2, S3, C3, C5, C6, H2 and P4 are different platforms with different processors, peripherals, memory configurations and wireless capabilities. Do not infer that every ESP32-name item has identical Bluetooth support, 5 GHz Wi-Fi, USB, camera input, Ethernet or Arduino-core support. In particular, an ESP32-P4 Ethernet board and an ESP32-H2 SuperMini should not be treated as drop-in equivalents to a classic ESP32 Wi-Fi board. Check the exact chip and board revision against the intended firmware framework, SDK, pin map and required radio protocol.

Module codes such as N4, N8, N16, R2 and R8 identify selectable flash/PSRAM configurations on specific listings. Compare the full selected module code, not a generic “ESP32-S3” label. External-antenna versions such as WROOM-32U or WROOM-1U require the appropriate antenna connection, whereas onboard-antenna versions have different mechanical and RF clearances. Bare SMD/QFN chips, solder-down RF modules, assembled development boards and complete enclosures require different PCB, power, programming and assembly work. Some XIAO multiproduct listings offer ESP32-C3/C5/C6/S3 alongside RP2040, RP2350, nRF52840, MG24, SAMD21, RA4M1 and antenna-only variants: selecting one never supplies the others.

Board format, USB and expansion fit

• DevKit-style ESP32: listings distinguish 30-pin, narrow or wide 38-pin, Type-C or Micro-USB, CH340/CH340C or CP2102 USB-to-serial, soldered versus unsoldered headers, one-piece versus multi-piece lots, and board-only versus board-and-expansion sets. USB connector style and pin count alone do not prove a shield fits; compare board width, header spacing, pin mapping, regulator and accessible GPIO.
• SuperMini and XIAO-size boards: C3, C6, H2, S2 and S3 small boards, plus soldered and unsoldered variants, appear here. Expansion-board-only and antenna-only options can sit beside the actual microcontroller. Check exposed pads, boot/USB behavior, flash size and supply method before selecting a footprint for a permanent design.
• Breakout, power and prototyping boards: 30/38/44-pin GPIO expanders, 1-to-2 breakout boards, separate power boards, QFP/TQFP/SOP test PCBs and general USB-C breakout boards are accessories, not programmable ESP32 devices. A “Power Board,” “Expansion Board,” “Empty PCB” or “Only Shell” option is not a functioning controller. Some accessory sets combine the controller and carrier; only a specifically selected set should be expected to include both.
• Programming and debug tools: ESP-Prog JTAG adapters, USB-to-TTL serial modules, ESP-01/ESP-12 programmers, WROOM/WROVER test fixtures and empty fixture PCBs target particular module footprints and boot circuits. A programming socket is not itself an ESP32 module. Confirm electrical voltage, interface pinout, target footprint and whether cables or target hardware are in the selected package.

Displays, touch and user interfaces

Integrated ESP32 smart-display listings include 2.8-inch resistive-touch ILI9341 boards, 4-inch TFT options, larger LVGL-oriented screens and compact OLED-equipped LoRa or SuperMini designs. “With touch,” “No touch,” “1 display,” “1 display 1 case,” “5 display,” and “10 display 10 case” represent different deliveries. Check panel driver, native resolution, touch technology and controller, board variant, backlight power, memory headroom, connector orientation and case fit. A display assembly with an ESP32 onboard differs from a plain SPI/I²C screen that still needs a host. UI frameworks such as LVGL depend on the chosen display driver, memory allocation and firmware configuration; a headline mentioning Arduino or LVGL is not a guarantee that an unmodified sketch works on every variant.

ESP32-CAM and vision hardware

Camera listings mix complete ESP32-CAM and ESP32-S3 camera boards, camera-only OV2640/OV3660/OV5640/OV7670 modules, FPC ribbon extensions, programmer baseboards, antennas and enclosures. Options such as “ESP32-CAM-MB,” “Only Downloader Board,” “CAM Without Camera,” “Single Module,” “Module-OV5640” and “Camera Adapter” should be read literally. OV2640 2 MP, OV3660 3 MP and OV5640 5 MP are different sensors; a 24-pin FPC matching mechanically may still have an incompatible pinout, voltage, MIPI CSI versus DVP signaling, clock, firmware driver or lens arrangement. Raspberry Pi OV5647 camera modules mentioned in mixed listings are not automatically interchangeable with ESP32-CAM modules. Select the actual board-camera pair and confirm supported interface, flex length, field of view, IR filter or illumination requirements and included programming method before building an imaging system.

Some ESP32-S3 Ethernet/camera pages offer a main board only, separate PoE board, OV2640 or OV5640 combinations, W5500 Ethernet variants and a named kit. The kit and the individual daughterboards are not equivalent. A PoE-capable board must be matched to its specified PoE hardware and isolation design; RJ45 presence alone does not imply PoE power input. Camera resolution, Ethernet throughput, available GPIO and power consumption belong to the exact assembled combination, not every choice on the product page.

Wi-Fi, Ethernet, LoRa and antennas

Classic Wi-Fi modules, ESP32-C5 dual-band/Wi-Fi 6 development kits, ESP32-C6 boards, ESP32-P4 Ethernet boards, WT32-ETH01, ENC28J60 SPI Ethernet modules, ESP32-S3 RJ45 boards and LoRa-equipped ESP32 nodes address different network requirements. Verify the particular board's radio, Ethernet PHY/controller, antenna topology and software support. An ENC28J60 board is an Ethernet peripheral, not an ESP32; an ESP32-P4 board's communications depend on its actual companion hardware. Some listings have soldered versus unsoldered Ethernet modules and PoE versus non-PoE variants.

Heltec WiFi LoRa 32/Stick, LILYGO T-Beam, T3S3 and T-Deck, RAK3112 modules and Meshtastic-oriented nodes are offered in different revisions with SX1262 or SX127x radios, 433/470–510, 868 or 915/923 MHz options, optional GNSS, OLED, case or solar accessories. A 433 MHz radio choice is not a firmware setting that transforms it into a 915 MHz unit. Select the band permitted in your deployment region and match antenna center frequency, impedance, SMA mating gender or U.FL/I-PEX connector, feed cable and output power. Antenna-only, U.FL-pigtail-only and “Only Shell” variants include no powered LoRa node. Advertised range, antenna gain or protocol compliance depends on the complete installation, firmware, region and legal limits; no universal long-range figure is promised here.

Meshtastic firmware or LoRaWAN in a title does not make every board preconfigured for both protocols, and LoRa is not Wi-Fi. Check exact radio chipset, supported board target, firmware build, display/GPS pin map and whether the selected option actually includes a battery, antenna or enclosure. Battery charging circuitry on a board is not proof that a cell ships with it; use a suitable cell and verified polarity/charge specifications for the model.

Industrial control, RS485 and switching hardware

ESP32-S3 RS485/CAN controllers, Modbus relay boards and Ethernet or Wi-Fi I/O modules appear alongside ordinary relay peripherals. Choices include 4- or 8-channel RS485 relay models, 8-channel opto-isolated input/relay boards, 16-input/16-output MOSFET controllers, DIN-case versus bare-board options and 12 V versus 24 V supply variants. A generic “5 V 2-channel relay module” is a peripheral that still needs a compatible controller. Check actual input type (NPN, dry-contact or voltage), output type and current rating, logic voltage, supply and terminal arrangement for the selected product. RS485 is a physical bus and Modbus RTU is a protocol; Wi-Fi, CAN, TTL serial and RS485 ports cannot be interchanged by software alone. Do not infer safety isolation, mains suitability or certification from “opto isolated” in a title. Follow the specific equipment documentation and applicable electrical safety practice for load wiring.

Learning kits, audio devices and complete projects

ESP32 learning kits from Keyestudio, Freenove, ACEBOTT and other suppliers vary by Basic, Complete, Ultimate, Beginner, Starter and Advanced choices, flash size, included boards, sensor modules and pack count. Some options supply only wooden chassis pieces rather than the electronics. ESP32-CAM robot cars, voice assistant boards, M5Stack ATOM Voice/Base/ASR selections and integrated display projects are assembled subsystems or project kits, not bare MCUs. Confirm included controller, camera, motor hardware, microphone, display, battery case and learning materials from the exact selected listing; a generic kit headline cannot establish a bill of materials.

Related DFPlayer MP3 modules, DS3231 real-time clocks, photoresistor comparator boards, ADC button modules, USB-C test boards and fast-charge trigger modules are peripherals that may be used with an ESP32 but are not ESP32 processors. USB PD/QC/AFC trigger boards require a compatible charger and voltage choice; never assume their output is safe for a 3.3 V GPIO. A 3–5 V ADC-button or comparator output needs electrical level verification before interfacing to an ESP32 input.

Engineering checks before ordering

1. Identify exactly what ships: read the selected Color, Model Number, Bundle, Package and quantity together. “1 SET,” “board only,” “camera plus adapter,” “without GPS,” “unwelded” and “antenna” change the functional product.
2. Confirm the target: ESP32, S2, S3, C3, C5, C6, H2 and P4 have distinct software, radio and pin capabilities. A mixed XIAO or ESP8266 listing may offer a non-ESP32 part.
3. Match electrical levels: many ESP32 GPIOs operate at 3.3 V logic; a board's 5 V USB input or expansion power rail does not make every signal pin 5 V tolerant. Verify regulator capacity, peripheral current, grounding, boot strapping and safe I/O limits in the selected board's documentation.
4. Match physical interfaces: compare header spacing and pinout, FPC pin count and protocol, Ethernet/PoE hardware, USB connector function, antenna mating connector and radio band. Similar-looking connectors can have incompatible assignments.
5. Match firmware and region: check current SDK or Arduino board definitions, display and camera drivers, Modbus mapping, radio firmware target and local RF regulations for the precise hardware revision.

Use this collection as an engineering shortlist. The model code and selected variant are the source of truth for included hardware; verify critical limits and interfaces at the individual product level before production or safety-sensitive deployment.