Product added to cart
ESP32-WROVER-B ESP32 Wi-Fi Bluetooth Development Board
$5.9500
In stock
SKU
COM-03-042
Volume discounts:
- +25 5 % $5.6800
- +50 7 % $5.5500
- +100 9 % $5.4200
- +300 11 % $5.2800
- +500 13 % $5.1500
Product Variations:
Add an Accessory:
Ships in 2-3 business days, then:
Free delivery in 12-15 days by Tracked Economic Shipping on orders over $100.
Free delivery in 7-10 days by Express Shipping on orders over $300.
More shipping info
Shop with confidence Learn More
ESP-WROOM-32 ESP32 Wi-Fi Bluetooth Development Board Previous
ESP32-WROVER-B Review: 16 MB Flash and 8 MB PSRAM
The ESP32-WROVER-B ESP32 Wi-Fi Bluetooth Development Board is a wireless development product for embedded developers and makers who need expanded memory for demanding firmware. With 16 MB Flash, 8 MB PSRAM, and a dual-core Xtensa processor, it provides the storage and memory buffers required for complex local tasks. Carrier-board details such as the USB interface, onboard regulation, and specific pin breakouts are not documented, however. Verify these before committing to a final hardware design, especially against standard ESP32 development boards with integrated USB programmers.
Specifications of ESP32-WROVER-B ESP32 Wi-Fi Bluetooth Development Board
- Processor: Dual-core 32bit Tensilica LX6 microprocessors
- Processor frequency: 80 to 240 MHz
- Wi-Fi: 11 b/g/n
- Wi-Fi frequency: 2.4 GHz
- Wi-Fi mode support: access point and client mode
- Bluetooth: Bluetooth Classic (BR/EDR) and Bluetooth Low Energy (BLE)
- Memory: 16 MB Internal Flash
- Memory: 8MB PSRAM
- Security Features: Secure Boot
- Security Features: Flash Encryption
- Security Features: WPA3
- Security Features: WPA2
- Operating Voltage: 3V to 3.6V
- Operating temperature: -40 to 85℃
- Low-Power Modes: Yes, including Deep Sleep mode
- GPIO: GPIO0 - GPIO39
- UART: Serial communication interface
- SPI: Serial communication interface
- I2C: Serial communication interface
- I2S: Serial communication interface
- Other External Interfaces: JTAG Debugging Support
- ADC: 16 channel 12-bit Analog signal input
- SD/SDIO/MMC Host: External storage support
- TWAI (CAN 2.0): Controller Area Network support
- Touch Sensor Inputs: Touch Sensor Inputs
- Temperature Sensor: Temperature Sensor
- Programming environments: Arduino IDE
- Programming environments: PlatformIO
- Programming environments: Espressif IDF (IoT Development Framework)
- Programming languages: C
- Programming languages: C++
ESP32-WROVER-B Specifications Explained
Although the top specification lists 16 MB Internal Flash, the physical architecture uses 16 MB external SPI flash integrated directly into the module package rather than on the ESP32 silicon die. The distinction between flash memory and pseudo-static RAM (PSRAM) matters for system architecture. The 16 MB flash stores non-volatile assets, including compiled application binaries, OTA partitions, and embedded file systems such as SPIFFS or LittleFS. The 8 MB PSRAM expands volatile working memory beyond the internal ~520 KB SRAM limit.
| Specification | Listed Value | Why It Matters |
|---|---|---|
| Working Memory | 8MB PSRAM | Allows large memory buffers necessary for camera frame buffers (such as OV2640 captures), high-resolution display buffers, audio streaming pipelines, and heavier web applications that quickly exhaust internal SRAM. |
| Non-Volatile Storage | 16 MB Internal Flash | Provides ample partition space for dual OTA firmware images, core dumps, and local web assets without running into storage boundaries common on 4 MB modules. |
| Wireless Radio | 2.4 GHz 802.11 b/g/n & Bluetooth Classic / BLE | Operates strictly on 2.4 GHz network bands in access point and client modes. Bluetooth support matches standard Bluetooth 4.2 capabilities; it does not support 5 GHz Wi-Fi or Bluetooth 5 high-throughput modes. |
| Peripherals (I2C, SPI, I2S, UART) | Dynamic software assignment | ESP32 features an internal GPIO matrix, allowing communication buses to be assigned to various physical pins, provided memory and strapping restrictions are respected. |
| Controller Area Network | TWAI (CAN 2.0) | Integrates the two-wire automotive interface protocol controller on-chip, but requires an external CAN transceiver to connect to a physical differential bus. |
| Security Features | Secure Boot & Flash Encryption | Hardware cryptographic engines support signature verification and encrypted storage, but both mechanisms require intentional eFuse burning and configuration during firmware generation. |
For standard embedded tasks that do not require massive frame buffers or extensive audio caching, the standard ESP32 development board with CP2102 includes a built-in USB-to-serial converter and standard 4 MB flash memory. It simplifies initial benchtop prototyping across the wider catalog of ESP32 Wi-Fi and Bluetooth development boards.
ESP32-WROVER-B GPIO, Power, and Compatibility
Understand pin multiplexing before laying out a circuit or wiring external modules. Although the silicon supports GPIO0 through GPIO39, several pins are permanently assigned to onboard components. GPIO6 through GPIO11 connect directly to the integrated SPI flash and must never be used. GPIO16 and GPIO17 are connected internally to the 8 MB PSRAM chip; using either pin for external circuitry will crash the memory controller or cause firmware execution faults.
Pin assignments must also account for input-only lines and bootstrapping requirements. GPIO34, GPIO35, GPIO36, and GPIO39 lack internal pull-up or pull-down resistors and cannot output signals. GPIO0, GPIO2, GPIO5, GPIO12, and GPIO15 are strapping pins that dictate boot states. Pulling these lines high or low with external circuits during power-up can unintentionally force the chip into flashing or test modes. For detailed breakout planning, consult our reference on ESP32 GPIO and pinout planning.
Analog inputs also require careful hardware planning. Two 12-bit ADC units are present, but ADC2 cannot be sampled while Wi-Fi is actively transmitting or receiving because the radio subsystem shares its internal circuitry. Route continuous analog sensor monitoring to ADC1 channels, or offload it to a dedicated external analog-to-digital converter. For prototype connections, use quality jumper-wire connections to maintain clean 3.3 V logic levels without exceeding electrical limits.
The core module operating voltage is strictly 3.0 V to 3.6 V, with 3.3 V logic levels. Connecting 5 V directly to the power rails or any GPIO will cause permanent damage. Because complete carrier-board regulation is undocumented for this product, supply power strictly through a verified regulated 3.3 V source unless you have tested the onboard regulator circuitry. For portable operation with managed charging, the ESP32 board with LiPo charging interface integrates dedicated battery management hardware alongside a 19-pin breakout.
ESP32-WROVER-B Development Board Setup
Getting this board running starts with confirming the physical hardware before attempting software uploads. The board may be supplied as either an assembled carrier or a bare module. First inspect the unit to determine whether it includes an onboard USB-to-UART bridge and physical pushbuttons, or requires an external programming fixture.
Follow this initial verification sequence to validate the board and its memory:
- Identify hardware connections: Check whether the board features a physical USB port or exposed serial header pins (TXD, RXD, 3V3, GND, EN, and GPIO0). If the carrier board features a dedicated Micro USB port, connect using a reliable Micro USB programming cable. If the board lacks an onboard bridge, connect through an external USB-to-serial programming module or seat the hardware into an ESP32 programming fixture.
- Configure development software: Install your preferred environment following instructions for installing ESP32 support in Arduino IDE or PlatformIO. Select an ESP32 Wrover Module target rather than a generic WROOM board.
- Enable PSRAM: In the development environment board options, explicitly set PSRAM to "Enabled" and verify Flash Size is configured for 16 MB. Standard ESP32 board definitions leave PSRAM disabled by default.
- Upload minimal test sketch: Compile and flash a simple sketch that reports heap memory and scans available Wi-Fi networks. Check serial-console output using functions such as
ESP.getPsramSize()andESP.getFreePsram()to confirm that roughly 8 MB of external memory is recognized by the operating system. - Validate power stability: Run a Wi-Fi scan loop while monitoring supply voltage on an oscilloscope or multimeter to verify that the rail remains between 3.0 V and 3.6 V during transmission bursts.
Common initial upload failures trace back to bootloader timing. If the carrier board lacks an automated reset circuit, GPIO0 must be tied to ground while toggling the EN (Reset) pin to pull the processor into download mode. For a guaranteed plug-and-play prototyping experience with a pre-configured CP2102 interface, consider the breadboard-compatible ESP32 board instead. More comprehensive setup steps are available in our guide to ESP32 development board setup.
ESP32-WROVER-B Limitations and Buying Mistakes
The main uncertainty with this product is carrier-board variability. While the module itself is built to Espressif WROVER-B standards, the underlying PCB revision, regulator model, presence of automatic flashing transistors, and pin header layouts are not standardized in the listing. Buyers expecting an out-of-the-box experience with documented schematics should be prepared to probe power traces and test serial lines manually.
Memory verification is another common issue. The WROVER-B module family was manufactured in 4 MB, 8 MB, and 16 MB flash versions, all sharing the same physical footprint and 8 MB PSRAM. While this product is specified with 16 MB Internal Flash, check the laser marking on the metal shield, such as the N16R8 ordering designation, or use the esptool flash-id readout to confirm exact capacity before partitioning your code.
Other operational constraints include:
- Not Recommended for New Designs (NRND): Espressif officially designates the ESP32-WROVER-B module as NRND. It remains fully functional for maintenance and prototypes, but should not be selected for long-term commercial production.
- Reserved memory lines: Avoid wiring anything to GPIO6–GPIO11 (flash) and GPIO16–GPIO17 (PSRAM). For safety margins on strapping pins, review our guide covering ESP32 strapping pins and safe GPIO choices.
- Power drops during transmission: Current draw can spike upward of 500 mA during RF calibration. Weak supplies or long USB cables will cause cyclical brownout resets (Brownout detector was triggered).
- RF Enclosures: The module uses a fixed onboard PCB trace antenna. Installation inside an aluminum, steel, or grounded enclosure will severely attenuate RF signals.
For projects requiring modern processor architecture with native USB support and long-term production availability, evaluate the newer ESP32-S3 development board instead.
ESP32-WROVER-B vs ESP-WROOM-32 and ESP32 Alternatives
Choosing between ESP32 modules comes down to memory demands, peripheral needs, and antenna requirements. Standard modules handle typical telemetry and relay control. Media buffering requires specialized hardware.
| Model | Flash | PSRAM | USB Bridge | Antenna Style | Primary Use Case |
|---|---|---|---|---|---|
| ESP32-WROVER-B | 16 MB | 8 MB | Not specified | Onboard PCB | Memory-heavy prototypes, camera buffering, and audio processing |
| ESP-WROOM-32 Dev Board | 4 MB | None | CP2102 | Onboard PCB | General IoT projects, sensor monitoring, and standard Arduino builds |
| ESP32-WROVER-IB Module | 16 MB | 8 MB | None (Bare module) | IPEX Connector | External antenna installations requiring high memory inside metal enclosures |
| ESP32-S3 WROOM-1 Dev Board | 8 MB | 2 MB | Dual USB-C (Native/Bridge) | Onboard PCB | Modern Xtensa LX7 builds, vector instructions, and USB OTG applications |
| ESP32-C3 with Dual USB | 400 KB SRAM | None | CH340 / Native USB-C | Onboard PCB | RISC-V architecture, Bluetooth 5 Mesh, and low-cost compact sensors |
Use the external-antenna ESP32-WROVER option when your project must reside inside an RF-shielded case. For everyday projects where 520 KB SRAM is sufficient, the standard ESP32 WROOM development board provides predictable USB flashing and wide pinouts. If you need modern peripheral sets or direct USB host features, the compact ESP32-C3 board with Bluetooth Mesh or an S3 variant offers a direct migration path. You can browse and compare ESP32 development board options to find the best match for your mechanical footprint.
ESP32-WROVER-B FAQ
Does this ESP32-WROVER-B product have 16 MB flash and 8 MB PSRAM?
Yes. The listing specifies 16 MB Internal Flash and 8 MB PSRAM, matching the N16R8 configuration. Because the WROVER-B line was produced in several memory variants, verify the laser-etched shield markings or run an esptool memory query upon arrival.
Is the 16 MB memory all RAM?
No. The 16 MB is external SPI flash storage for program code, partitions, and file systems. Volatile working memory consists of internal SRAM alongside the separate 8 MB PSRAM chip, which handles dynamic buffers and arrays.
Is this a complete USB development board?
The product is titled as a development board, but specific USB-UART bridge chips, driver requirements, onboard regulators, and dimensions are not documented. Inspect the delivered item before connecting power to determine whether external serial hardware is required.
Can I power the ESP32-WROVER-B with 5 V?
No. The module operating voltage is strictly 3.0 V to 3.6 V. You may only connect a 5 V supply if the carrier board contains an onboard linear or switching regulator with a dedicated 5 V or VIN power input pin.
Can I use GPIO16 and GPIO17 for peripherals?
No. GPIO16 and GPIO17 are connected internally to the 8 MB PSRAM. Using these pins for external buses, displays, or sensors will cause bus conflicts and crash the memory system.
Can I use ADC2 while Wi-Fi is active?
No. ADC2 channels are shared with the Wi-Fi subsystem and will return erroneous values or fail to read while the radio is active. Route all analog sensors to ADC1 channels when running Wi-Fi, or connect an external I2C ADC.
Does TWAI/CAN support mean I can wire directly to a CAN bus?
No. The TWAI peripheral is only a software-configurable protocol controller. A physical CAN network requires an external 3.3 V CAN transceiver, such as an SN65HVD230, and a 120-ohm terminating resistor.
Does this board support Bluetooth 5 or 5 GHz Wi-Fi?
No. The Wi-Fi radio operates solely on 2.4 GHz 802.11 b/g/n, and the Bluetooth controller supports Bluetooth 4.2 Classic and BLE modes. It does not support 5 GHz networks or Bluetooth 5 long-range modes.
Can I use an external antenna?
No. The standard WROVER-B includes an onboard meandering PCB antenna. If your application requires an external antenna through an IPEX connector, choose the dedicated ESP32-WROVER-IB Module instead.
Is ESP32-WROVER-B suitable for a new commercial product?
No. ESP32-WROVER-B is officially designated as Not Recommended for New Designs (NRND). It remains useful for prototyping, hobby builds, and replacement components, but new commercial designs should use active modules such as the ESP32-WROVER-E or ESP32-S3 series.
Purchase Decision Summary
- Ideal for: Experienced developers who need 8 MB PSRAM and 16 MB flash for audio buffers, camera frame storage, complex local web servers, or maintaining existing WROVER-B hardware.
- Maybe for: Makers comfortable identifying serial pinouts, verifying regulator circuits, and manually configuring board parameters in Arduino IDE or ESP-IDF.
- Consider another option if: You need guaranteed plug-and-play USB setup, standard GPIO16/GPIO17 availability, battery charging, an IPEX antenna connector, or an active lifecycle status for a new commercial product. For simpler needs, a standard ESP32 development board with CP2102 or other ESP32 boards will streamline development.
Buying Checklist
- Confirm whether your firmware actually requires 8 MB PSRAM or whether standard SRAM is sufficient.
- Verify that your project does not depend on GPIO16, GPIO17, or flash pins GPIO6–GPIO11.
- Ensure your analog inputs can be handled entirely on ADC1 if Wi-Fi is enabled.
- Check that you have a stable, regulated 3.3 V power source capable of delivering at least 500 mA peaks.
- Have an external USB-to-serial adapter available in case the delivered carrier board lacks an onboard bridge.
- If using breadboard prototyping, confirm the pin pitch and row spacing once received.
- Source an external CAN transceiver if you plan to use the TWAI interface.
- Review our ESP32 first-project guidance to confirm tooling and development environment requirements.
| MCU/SoC | ESP32-D0WD |
|---|---|
| Product Family | ESP32 |
| Architecture | Tensilica Xtensa LX6 |
| CPU Cores | Dual-core |
| Clock Speed (MHz) | 240 MHz |
| Flash | 16MB |
| SRAM | 8MB PSRAM |
| External Memory | SD/SDIO/MMC Host |
| GPIO Pins | GPIO0 - GPIO39 |
| SPI interface Pins | 3 |
| I2C interface Pins | 2 |
| UART interface Pins | 3 |
| CAN Bus Support | TWAI (CAN 2.0) |
| Ethernet Support | Yes |
| ADC Channels | 16 channel 12-bit |
| DAC Channels | 2 |
| PWM Channels | 16 |
| Timers Count | 4 |
| Operating Voltage (V) | 3.3V |
| GPIO Voltage (V) | 3.3V |
| GPIO Current (mA) | 12 mA |
| Wireless | Bluetooth, Wi-Fi |
| Form Factor | Compact form factor |
| IDE Support | Arduino IDE, ESP-IDF |
| Antenna Type | Internal Antenna |
| Bluetooth Ver. | 4.2 |
| Operating Temp (°C) | -40 to 85℃ |
| Wireless Protocol | 802.11 b/g/n, 2.4 GHz, Access point and client mode support |
| Encryption | Secure Boot, Flash Encryption, WPA3 and WPA2 security modes |
Write Your Own Review




Please complete your information below to login.
Sign In
Create New Account