Free tools Windows power users keep installed
One-click scans. No signup required.
The ESP32-P4 has no built-in Wi-Fi or Bluetooth radio. It can still run a capable standalone or wired application, using its high-performance RISC-V cores and extensive peripheral set. If your design needs wireless connectivity, add a supported external wireless SoC—such as an ESP32-C5 or ESP32-C6—or select a board that already includes one. The radio belongs to that companion chip, not to the P4 itself.
Does the ESP32-P4 have Wi-Fi or Bluetooth?
No. Espressif states in its ESP32-P4 getting-started guide that the P4 does not include built-in Wi-Fi or Bluetooth. This is a chip-level distinction: a development board built around the P4 may also carry a separate wireless chip, but that does not give the P4 an integrated radio.
As an Amazon Associate I earn from qualifying purchases.
That matters when planning a product or prototype. Do not assume that code or a board setup designed for an ESP32 with onboard wireless will work unchanged on a P4. Wireless needs an additional supported target and a compatible board-level connection and software path. Conversely, a project that needs computation, imaging, audio, USB, or other supported peripherals—but no wireless radio—can still make use of the P4.
In other words, the absence of a radio answers only one part of the connectivity question. It does not mean that the P4 is unable to communicate with peripherals, store data, or take part in a wired system. Its datasheet lists multiple interfaces for those jobs. Whether a particular connection is usable on your device depends on the board exposing the necessary pins and adding any required supporting hardware.
#1 Best Overall
- ESP32-P4-WIFI6 multimedia development board adopts ESP32-P4, with a 400MHz dual-core RISC-V processor and supports up to 32MB PSRAM, integrated ESP32-C6, supports Wi-Fi 6/BLE 5 wireless connections and other functions through SDIO
- 128 KB HP ROM, 16 KB LP ROM, 768 KB HP L2MEM, 32 KB LP S-R-A-M, 8 KB TCM, 32MB PSRAM in the chip's package, with onboard 32MB Nor Flash
- Powerful image and voice processing capability. Provides image and voice processing interfaces including JPEG Codec, Pixel Processing Accelerator, Image Signal Processor, H264 encoder. Supports AI speech interaction
- Rich human-machine interfaces, as MIPI-CSI, MIPI-DSI, USB 2.0 OTG, SDIO 3.0 TF card slot, microphone, speaker header, etc. Adtaping 2*20 GPIO headers with 27 x remaining programmable GPIOs. Built-in 40PIN GPIO expansion interface
- Security features: Secure Boot, Flash Encryption, cryptographic accelerators, and TRNG. Additionally, hardware access protection mechanisms help to enable Access Permission Management and Privilege Separation
What the P4 can do without wireless
The P4 is a high-performance microcontroller rather than a wireless-only device. Espressif’s ESP32-P4 Series Datasheet describes dual high-performance 32-bit RISC-V cores running up to 400 MHz, alongside a low-power core. These are specifications, not a guarantee of application speed: actual performance depends on the workload, software, memory, and board design. The cited P4 datasheet version is pre-release v0.7, so consult the current documentation when making a production design decision.
The datasheet lists substantial processing and interface capabilities. Depending on the application and board implementation, the P4 can run application logic and work with functions and interfaces such as:
- Imaging and display: camera and display interfaces, an image signal processor (ISP), JPEG codec, and H.264 encoding.
- Voice processing: voice activity detection (VAD) and audio interfaces.
- USB: USB 2.0 high-speed and full-speed OTG, as well as USB Serial/JTAG.
- Wired networking hardware: an Ethernet MAC.
- Storage and peripheral connections: an SD/MMC host controller, UART, SPI, I2C, I3C, I2S, and TWAI.
These capabilities can support designs in which the device processes data locally, communicates over a wired connection, or connects to sensors, storage, cameras, displays, and other peripherals. The absence of Wi-Fi does not prevent the P4 from doing those jobs; it only means that wireless networking and Bluetooth are not provided by the P4’s own integrated hardware.
For example, a design may use the P4 to process camera input, handle a display, or run voice-related functions while communicating with other equipment over USB or a wired network. These examples describe the kinds of work suggested by the datasheet interfaces, not a guarantee that every P4 board exposes every interface or that a specific application will meet a particular speed or quality target. Check the target board’s specifications and pin availability before settling on a design.
Ethernet MAC does not mean a complete Ethernet port
The P4’s Ethernet MAC is a wired-networking capability, but it is not by itself a finished Ethernet port. A working board design must provide the additional hardware required for its Ethernet connection. Check the board schematic and documentation if you need Ethernet; do not infer from the MAC specification alone that a particular P4 board has a usable port.
This is an important distinction when comparing a P4 design with one that has Wi-Fi built in. The P4’s MAC does not make it a wireless alternative, and it does not mean an Ethernet cable can be plugged directly into every P4 board. Networking needs must be evaluated at the board level: establish whether the board includes the necessary Ethernet circuitry, or whether a wired connection is actually available in the intended product.
How to add Wi-Fi to a P4 design
Espressif documents Wi-Fi expansion for the P4 using a separate Wi-Fi-capable ESP32 target. The stable Wi-Fi Expansion guide describes the esp_wifi_remote component: connect a supported target to the P4 in a predefined way, include the component, and use the Wi-Fi API and features through the expansion arrangement.
Recommended Free Tools
The guide also describes esp-extconn as an alternative supported-target approach. In that arrangement, the target’s firmware can be delivered by the hosted side, so the target can operate without flash. The guide links examples including MQTT over TLS and Wi-Fi iperf, which can help developers understand the documented software route. They are examples of the documented expansion path, not evidence that every board and wireless target supports every feature without configuration.
Rank #2
- ESP32-P4-Module Development Board. High-performance Development Board Based On ESP32-P4 and ESP32-C6, supports Wi-Fi 6 and Bluetooth 5 wireless connection.
- It features rich Human-Machine interfaces, including MIPI-CSI (with integrated Image Signal Processor), MIPI-DSI, SPI, I2S, I2C, LED PWM, MCPWM, RMT, ADC, UART, TWAI, etc. Additionally, it supports USB OTG 2.0 HS, onboard RJ45 Ethernet port with reserved PoE function header, and onboard 40PIN GPIO header which is compatible with some Raspberry Pi HATs, enabling a wider range of application adaptability.
- The ESP32-P4 adopts a 400MHz dual-core RISC-V processor and supports up to 32MB PSRAM, featuring USB 2.0, MIPI-CSI/DSI, H.264 encoder, and other peripherals, meeting the needs for low-cost, high-performance, and low-power multimedia development.
- It also integrates the Digital Signature Peripheral and a dedicated Key Management Unit, ensuring secure data and operations. Specifically designed for high-performance and high-security applications, the ESP32-P4-Module-DEV-KIT meets the requirements of Human-Machine interaction, efficient edge computing, and IO expansion.
- Security features: Secure Boot, Flash Encryption, cryptographic accelerators, and TRNG. Additionally, hardware access protection mechanisms help to enable Access Permission Management and Privilege Separation.
- Choose the wireless requirement. Establish whether the design needs Wi-Fi, Bluetooth, or both, and identify the protocols and features it actually needs.
- Choose a documented companion and board arrangement. Espressif’s getting-started guide names ESP32-C5 and ESP32-C6 as examples of external wireless SoCs. Confirm that the chosen P4 board, companion target, connection, and software path are supported together.
- Check the board schematic and current component instructions. Connector availability, routing, and board design affect whether the intended expansion works. Do not assume every third-party P4 board has the same connections or wireless configuration.
- Follow the applicable ESP-IDF expansion guide. Use the documented component and supported-target setup for the selected arrangement, rather than assuming the P4 has native Wi-Fi or using an unverified connection.
- Validate the required features in the finished design. Confirm that the specific target and software setup provide the protocols and functions your application needs. Compatibility is not established universally across boards, software versions, or radio features.
The key architectural point is that this approach adds a second target to the system. The P4 continues to run the application and use its own interfaces; the companion target supplies the radio capability. The precise division of work and supported features depend on the selected design and Espressif’s current component instructions.
For a developer, “use the same Wi-Fi API” does not mean that the radio has appeared inside the P4. Espressif’s guide says the P4 does not support Wi-Fi functionality natively and that expansion makes it possible to use the Wi-Fi API and features. The supported arrangement and software component are what bridge the application to the external target. Start from the guide’s supported targets and examples, then confirm that the exact P4 board and software release match the instructions.
What a companion chip contributes
A wireless companion’s capabilities should not be attributed to the P4. For example, Espressif’s ESP32-C6 Series Datasheet lists 2.4 GHz Wi-Fi 6, Bluetooth LE, Zigbee, and Thread for the C6. Those are C6 capabilities. The cited datasheet is version 1.5, dated 2026-03-31; actual use in a P4 system still depends on a compatible board and software configuration.
This distinction also helps when drawing up requirements. If a project calls specifically for Bluetooth, Zigbee, or Thread, verify that the selected companion and supported P4 expansion path provide the needed capability. The presence of a C6 datasheet feature alone does not establish that every board, connection, component version, or application exposes it in the way you need. Similarly, do not describe the P4 itself as having Wi-Fi 6 or Bluetooth LE simply because a C6 is attached to a board.
Espressif also names the ESP32-C5 as an example of an external wireless SoC in its P4 getting-started guide. The cited material does not establish a universal set of C5/P4 combinations or guarantee every wireless feature on every board. Treat a chip name as a starting point for checking a supported design, not as proof that any module can be wired to any P4 board and used without further setup.
Which design path should you choose?
| Design path | What it provides | What to verify |
|---|---|---|
| Use the P4 without wireless | P4 compute and its on-chip interfaces for a standalone, USB-connected, or other wired application. | Whether the board has the specific peripheral hardware your design needs. For Ethernet, verify board-level circuitry in addition to the P4’s MAC. |
| Add an external wireless target | A documented expansion path for Wi-Fi using a supported Wi-Fi-capable ESP32 target and the relevant software approach. | Supported target, board connections, component instructions, required protocols, and software versions. Bluetooth support must be confirmed for the specific target and design. |
| Select a P4 board with wireless hardware fitted | Wireless hardware may already be present on the board, potentially avoiding separate assembly. | Whether the board actually includes a separate wireless SoC, which chip it uses, and whether its configuration is supported for your project. Espressif’s board list does not imply that all P4 boards have the same wireless setup. |
There is no universal cost or performance comparison established for these paths. The useful comparison is project-specific: required protocols, the board’s integration and routing, supported ESP-IDF target and component, and whether a wired interface meets the application’s needs.
That means you should not choose solely by assuming that a P4-plus-companion design is cheaper, faster, or more capable than a board with wireless already fitted. The available documentation does not provide a general price, benchmark, or board-level test for that comparison. Compare actual product documentation and supported software arrangements for the boards under consideration, including whether their connectivity meets the application requirements.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWhat to check before choosing a P4 board
- Wireless hardware: Look for a separately identified radio or wireless SoC in the board’s product documentation. A P4 listing alone does not establish that Wi-Fi or Bluetooth is present.
- Expansion support: Match the board’s connections and companion target to Espressif’s documented expansion method. Check current instructions for the ESP-IDF version you intend to use.
- Wired alternatives: If the product only needs networking but not wireless, inspect whether the board provides the additional hardware needed to use its Ethernet MAC.
- Peripheral fit: Verify that the particular board exposes the USB, storage, camera, display, audio, or control interfaces your design requires. A chip datasheet lists silicon capabilities; board availability and routing determine what you can actually connect.
Espressif’s P4 getting-started page lists official development boards, but does not establish that every listed board shares one wireless configuration. Read the documentation for the exact board rather than generalizing from the P4 name. A development board is a way to prototype with the P4, not a guarantee that it includes wireless hardware or that its wireless arrangement matches another board’s.
Rank #3
- ESP32-P4-ETH development board based on ESP32-P4, MCU with RISC-V 32-bit dual-core and single-core processors, 128 KB HP ROM, 16 KB LP ROM, 768 KB HP L2MEM, 32 KB LP S-RAM, 8 KB TCM, 32MB PSRAM in the chip's package, onboard 32MB Nor Flash
- Rich human-machine interfaces such as MIPI-CSI, MIPI-DSI, USB 2.0 OTG, 100M RJ45 Ethernet port, SDIO 3.0 TF card slot, onboard microphone, speaker header, PoE module & power supply header, etc.
- Powerful image and voice processing capability. Provides image and voice processing interfaces including JPEG codecs, Pixel Processing Accelerator (PPA), Image Signal Processor (ISP) and H.264 video encoder
- Adapting 2*20 GPIO headers with 27 x remaining programmable GPIOs
- Security features: Secure Boot, Flash Encryption, cryptographic accelerators, and TRNG. Additionally, hardware access protection mechanisms help to enable Access Permission Management and Privilege Separation
Before committing, line up three things: the protocol requirement, the hardware connection between the P4 and companion, and the ESP-IDF instructions for that arrangement. These checks prevent a common planning mistake—buying a P4 board and a wireless module based only on their product names, then discovering that the proposed combination or software route is not documented. Where compatibility is unclear, resolve it against the current board schematic and Espressif component documentation rather than assuming interoperability.
Common assumptions to avoid
- “The P4 is an ESP32, so it must have Wi-Fi.” The P4 is an ESP32-family MCU, but Espressif explicitly says it has no built-in Wi-Fi or Bluetooth.
- “A board with a P4 automatically has a P4 radio.” If wireless is present on a board, it is provided by separate hardware; confirm the board’s components.
- “An Ethernet MAC means I can plug in a cable.” The MAC is not a complete port. Board-level Ethernet hardware is also necessary.
- “Any wireless companion will work with any P4 board.” The expansion guides describe supported targets and predefined arrangements, not universal compatibility across all boards and software versions.
- “The companion’s protocol list is the P4’s protocol list.” Wi-Fi, Bluetooth LE, Zigbee, and Thread capabilities cited for the C6 belong to that companion chip, not to the P4.
Frequently Asked Questions
Does the ESP32-P4 have Wi-Fi?
No. Espressif’s ESP-IDF getting-started guide says the ESP32-P4 does not include built-in Wi-Fi or Bluetooth. Wi-Fi can be added through a supported external wireless target and documented expansion path.
Can I add Wi-Fi to an ESP32-P4?
Yes. Espressif documents Wi-Fi expansion using a supported Wi-Fi-capable ESP32 target, including the esp_wifi_remote component, and describes esp-extconn as another supported-target approach. Confirm the companion, board connection, and ESP-IDF instructions for your exact setup.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Can I use Bluetooth with an ESP32-P4?
Not with the P4 chip alone, because it has no built-in Bluetooth radio. A separate wireless companion may provide Bluetooth capability, but verify the specific target, board, and software arrangement rather than assuming all expansion configurations support it.
Can an ESP32-P4 use Ethernet without Wi-Fi?
The P4 datasheet lists an Ethernet MAC, but that is not a complete Ethernet port. Check whether the board includes the additional Ethernet hardware required for a usable wired connection.
Does every ESP32-P4 development board include wireless?
No such guarantee is established by the P4 board list. Inspect the exact board documentation to see whether it includes a separate wireless SoC and whether that configuration suits your project.
The Bottom Line
The ESP32-P4 has no built-in Wi-Fi or Bluetooth, but it can still run applications using its compute, imaging, voice, USB, storage, and other interfaces. For wireless, use a supported external ESP32 target or a board with separate wireless hardware, and verify the exact board and software path. Treat Ethernet MAC as a chip capability—not proof that a complete Ethernet port is present.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
