ESP32 KiCad Symbols, Footprints & 3D Models: Every Variant, One Guide

Nobody designs "an ESP32 board". You design an ESP32-WROOM-32 board, or an ESP32-S3 board, or an ESP32-C3 board, and those are different parts with different pinouts, different USB stories, and different footprints. Espressif's family tree now spans multiple CPU architectures and dozens of modules, and third parties like Ai-Thinker add their own module lines on top. The result is that most ESP32 footprint problems are not drawing errors at all. They are variant errors: a symbol for one module paired with a footprint for its cousin, or a schematic drawn against the chip when the board uses the module.

So before hunting for files, pin down the exact part. "ESP32" alone is ambiguous between the classic dual-core chip, every module that carries it, and several newer families that share nothing with it but the brand. The files below are organized the way the decision actually happens: first chip versus module, then which module.

A bare ESP32 chip like the ESP32-D0WDQ6 is a QFN part that needs an external flash chip, a 40MHz crystal, RF matching components, an antenna, and a layout done carefully enough that the radio performs and passes certification. Espressif publishes hardware design guidelines for exactly this work, and companies that ship at volume do it to save cents per unit. For everyone else it is a tax: every one of those support pieces is a chance to build a board that boots but will not stay on Wi-Fi.

A module like the ESP32-WROOM-32 or ESP32-S3-WROOM-1 is that same chip with the flash, crystal, RF path, and PCB antenna already integrated, shielded, and certified. You place one castellated component, follow the antenna rules, and the radio work is done. That is why the practical advice is blunt: use a module unless you have a specific volume or size reason not to, and if you are reading a guide to find your first ESP32 footprint, you want the module.

ESP32-WROOM-32: the classic. Dual-core ESP32 inside, 2.4GHz Wi-Fi plus Bluetooth, 38 castellated pins plus a thermal pad, and no native USB, so your board needs a USB-UART bridge like a CP2102N or CH340 for programming. Verified symbol, footprint, and 3D model: protoflow.ai/library/parts/C82899.

ESP32-S3: the current flagship for new designs that want lots of GPIO, optional PSRAM, and native USB (D- on GPIO19, D+ on GPIO20), which removes the bridge chip entirely. Files for the S3: protoflow.ai/library/parts/C2913192, and the same page pattern covers the S3-WROOM-1 modules as they are published.

ESP32-C3: the small one. Single-core RISC-V, BLE 5 plus Wi-Fi, native USB serial/JTAG, and a price that made it the default for simple connected sensors. Files: protoflow.ai/library/parts/C2838500.

ESP32-S (Ai-Thinker): a third-party module built around the classic ESP32, widely used in older designs and clones of them. If you are maintaining or remixing one of those boards, matching the exact module matters more than upgrading it. Files: protoflow.ai/library/parts/C277944.

ESP32-D0WDQ6: the bare classic chip, for the minority who genuinely need it. The files carry the full QFN pad geometry including the thermal pad. Files: protoflow.ai/library/parts/C129733.

Every one of those bundles came from the ProtoFlow component pipeline that real engineers use to import parts into real designs, converted to native KiCad format, so the symbol pin map, the footprint pads, and the 3D body agree with each other. Each page shows a rendered preview of the symbol and land pattern before you download anything.

The downloads are plain KiCad files: a .kicad_sym symbol library, a .kicad_mod footprint, and a 3D model. In KiCad, add the symbol file under Preferences, then Manage Symbol Libraries, add the footprint under Manage Footprint Libraries, and point the footprint's 3D model path at the downloaded model if you want the board viewer to show it. From there the part behaves like anything from the official libraries.

What about the official libraries themselves? They do include some Espressif modules and they are well reviewed, so if your exact variant is there, using it is completely reasonable. The two habits that save respins either way: check that the library part matches your exact module suffix, and compare the footprint against the land pattern drawing in the datasheet. Thirty seconds with the datasheet is cheaper than a board spin, whatever the source of the footprint.

If your variant is not covered anywhere, that is the case AI part generation actually solves now: ProtoFlow's generator reads the datasheet and produces the symbol, footprint, and 3D model for you, free to start, and you review the result against the same land pattern drawing you would have used to draw it by hand.

A correct footprint is necessary and not sufficient, because the ESP32's radio cares about the copper around it. The antenna end of the module must hang over the board edge or sit over a keepout with no copper, no ground pour, and no traces on any layer under the antenna area, and the module generally wants to be at the edge of the board, not buried in the middle of a ground plane. Espressif's hardware design guidelines draw the recommended keepout, and following it is the difference between the range the datasheet promises and a board that only works next to the router.

Power is the other classic miss. An ESP32 idles modestly but pulls sharp current spikes during Wi-Fi transmit, so give the 3V3 pin real bulk capacitance nearby plus a small ceramic right at the pin, and feed it from a regulator sized for roughly half an amp of headroom, which is exactly why so many ESP32 boards pair the module with an AMS1117-3.3. Get the antenna keepout and the power right and the rest of the layout is ordinary digital work.