Choosing an ESP32-DevKitC module — WROOM vs WROVER, E vs UE/IE
Question this page answers: “The ESP32-DevKitC family supports several Espressif modules — which one does my project need, and what does each choice cost?”
The board ships from the factory with an ESP32-WROOM-32E soldered (the V4 guide’s own overview). You only move away from it for two reasons — memory and antenna — and each move has a cost you can see in the pin table.
The two decisions
1. Do you need PSRAM? → WROOM (no PSRAM) vs WROVER (PSRAM inside).
2. Do you need an external antenna? → PCB antenna on-board (E) vs an antenna connector (UE / IE).
The four compatible modules
| Module | Antenna | PSRAM | Pin cost |
|---|---|---|---|
| ESP32-WROOM-32E | on-board PCB antenna | no | — |
| ESP32-WROOM-32UE | external antenna connector | no | — |
| ESP32-WROVER-E | on-board PCB antenna | yes | GPIO16 / GPIO17 used by internal storage — not available externally |
| ESP32-WROVER-IE | external antenna connector | yes | GPIO16 / GPIO17 used by internal storage — not available externally |
The GPIO16/17 cost is not a footnote: if your wiring plan uses those two pins, a WROVER module takes them off the table — that is a pin-availability question, and the occupancy is recorded on the module pages.
Why choose PSRAM — and why not by default
PSRAM gives your project megabytes of external RAM for framebuffers, audio buffers, big data structures. If you do not have such a need, the WROOM default is the simpler start: two more GPIOs available and the factory configuration.
Why choose an external antenna connector
The connector variant (UE / IE) matters when your enclosure or mounting position hurts the on-board PCB antenna — metal cases, long distance to the access point, or a directed antenna. It is a mechanical/radio decision, not a performance upgrade in open air; this site does not publish range measurements for either antenna (see below).
Storage variants and the ordering suffixes
Each module family comes in storage variants (for example the WROVER-E family’s N4R8, N8R8 and siblings). The suffix encodes the memory configuration; the authoritative decoding lives in each module’s datasheet ordering table — the same check the GPIO35/36/37 guide uses for the S3 family. The WROOM-32E/32UE datasheet is the official entry linked from the board guide.
Next step
Back on the ESP32-DevKitC board page, the compatible-module list and the header tables reflect these facts; pick the revision and module, then check the pins you plan to use.
What this page cannot tell you
- Antenna performance comparison. No RF measurements were made or reproduced here; “which antenna reaches further” depends on enclosure, orientation and environment, and belongs to your own test.
- A full variant × suffix ordering table. Reproducing Espressif’s ordering tables here would fork their data; the datasheet tables are linked instead.
- Which module is on your physical board, if you cannot read the shield. The board guide’s overview describes the factory configuration (WROOM-32E); an unknown board keeps the question open.
Sources
- ESP32-DevKitC V4 User Guide — factory module (WROOM-32E), component list, WROOM-32E/32UE datasheet link (commit
5c06bf18) - MCUID module data — antenna (PCB vs connector), PSRAM presence, WROVER-E/IE GPIO16/17 internal-storage occupancy, WROVER-E storage variants (N4R8/N8R8 family)