ESP32 PCB Antenna Layout: Reference Design & Keepout

Identify the hardware route first

Keep the complete manufacturer part number, including its suffix. A related name can conceal an antenna option or a package difference. Use the current official document for that part and record its revision in the project. A web tutorial showing a similar board can explain a concept, but should not replace the manufacturer's integration requirements.

Espressif maintains device-family hardware design guidance, including layout and schematic sections. Start with the official ESP32 hardware design guidelines, then select the documentation for the actual family and module. This page intentionally does not impose one clearance dimension on every ESP32 product.

Preserve the antenna's documented environment

An integrated antenna interacts with the module and the host board around it. Show the module position relative to the host edge, all host copper layers, components and the enclosure. A clearance that looks empty on the top layer can still contain copper or a battery on another level. Review the complete three-dimensional installation.

If the reference allows or recommends an antenna region outside the host-board edge, show how the mechanical design supports that position. If the antenna remains over the host outline, apply the exact documented clearance arrangement. Do not substitute a smaller empty rectangle solely because the module can physically fit there.

The product enclosure can add screws, metal labels, conductive coatings, displays and cables near the antenna. Include these in the review before freezing the housing. A board tested on the bench may behave differently after assembly even though its copper artwork has not changed.

Use a reference-conformance worksheet

The worksheet records the exact device, document revision, antenna route and whether the relevant mechanical checks have been completed. It returns the unresolved checks as a review list. It does not calculate an official keepout or certify a layout against Espressif requirements. Keep the actual reference drawing with the downloaded brief.

For a useful example, imagine that the electrical team has selected an integrated-antenna module, but the mechanical team has not yet fixed the battery position. The correct status is a documented open installation item. A completed PCB routing check does not close that issue, and moving the battery later should trigger another antenna integration review.

Separate RF layout from ordinary signal routing

The route between a radio and an antenna is not just another short net. Follow the exact reference network and identify its intended impedance, matching topology and component footprints. A footprint substitution may change the mounted RF behavior even if the nominal component value remains the same.

For a module with a complete integrated antenna path, avoid adding unapproved structures around the antenna region. For a bare-chip implementation, preserve the reference's essential layout relationships while reviewing any changes to stackup, components or ground. A reference design is tied to its conditions; it is not a guarantee for a visually similar drawing.

Use RF PCB design to define the feed cross-section and references. The PCB impedance tool can support an initial geometry review, but it does not validate the antenna or replace the chip-specific reference.

Keep power and digital behavior in the test plan

An antenna problem can be confused with supply instability, firmware state or interference from another circuit. Record the supply, radio configuration and active subsystems during testing. A comparison made with a display disabled and a quiet processor does not necessarily describe normal product operation.

Review placement and return paths for switching regulators, clocks and high-activity digital interfaces. Their relevance depends on the frequency content and coupling path, so avoid treating a fixed separation distance as universal protection. If performance changes with a subsystem state, use a controlled diagnostic comparison before modifying the antenna.

For a battery-powered product, include representative battery and charging configurations. A USB cable used for debugging can alter the mechanical and RF environment as well as the power state. Record whether it is attached and where it is routed; otherwise a bench result may be difficult to reproduce after the cable is removed.

Compare prototypes in controlled stages

Begin with a board-level baseline in a documented setup. Add the enclosure, battery and other structures in a controlled sequence when practical. If a change is observed, repeat the comparison to confirm it and identify which variable changed. Avoid simultaneously changing the antenna, matching values and housing when the purpose is to isolate one cause.

Return-loss or impedance measurements require an appropriate access method and reference plane. Over-the-air performance requires its own measurement conditions. A connection-status indicator or one successful data transfer is useful functional evidence, but does not characterize efficiency, pattern or performance across all required channels.

Save the module part, board revision, fitted components, firmware and setup with the result. Where tuning is performed, record the before and after populations rather than editing the only copy of the BOM. The production assembly must identify which configuration was actually approved.

Make keepout requirements inspectable

A manufacturing package should show the host-board clearance on the relevant layers and identify prohibited components or metal structures. Explain which dimensions are controlled and which drawing is authoritative. The assembler should not have to infer an antenna keepout from a marketing image of the module.

Consider what can change during assembly: cable dressing, adhesive location, module orientation, shield placement or enclosure hardware. Define an inspection point before these features become hidden. A simple annotated assembly drawing is often more useful than a long paragraph stating that RF performance is important.

If a substitute module is proposed, compare its exact antenna and integration requirements before accepting it. Pin compatibility alone does not establish RF or mechanical equivalence. Record the qualification work needed for a substitution rather than allowing purchasing to treat all similarly named modules as interchangeable.

A practical release example

Suppose the approved prototype places an integrated-antenna module at the host-board edge, with a defined plastic enclosure and a fixed battery location. The production drawing should preserve those relationships and identify the approved module suffix. If a later housing revision introduces a metal mounting bracket near the antenna, retain the original measurement record and open a new integration review for the revised product.

This approach makes the reason for the restriction visible. The issue is not whether a bracket violates an arbitrary generic distance; it is whether the changed installation still meets the product's documented RF requirements. Engineering can then choose the right model or measurement to answer that question.

Prepare an ESP32 assembly enquiry

Include fabrication files, the stackup, exact module or chip part number, BOM, placement data and assembly drawing. Add the referenced antenna integration document, enclosure information and a list of tests requested from the assembly supplier. Identify customer-owned RF validation separately from ordinary assembly inspection.

For products that move to a cabled antenna, continue with ESP32 external antenna integration. For the broader product context, review IoT PCB manufacturing and PCB Manufacturing. You can request a build review without completing the worksheet.

Common layout questions

Can one keepout dimension be used for every ESP32 module?

No. Apply the exact device or module documentation and its stated placement conditions. Record the reference revision so a later reviewer can see which requirements were used. This guide does not replace a module-specific integration drawing.

Does a prequalified module remove all product testing?

No blanket conclusion should be drawn. The installed product, antenna configuration and intended market need review against the applicable requirements and the module's conditions. Resolve that scope with the responsible compliance team rather than treating the module label as approval of every enclosure.

Can I tune only by checking signal strength on a phone?

That can reveal a gross functional change, but the reading depends on the environment, orientation and radio behavior. Use controlled RF and product-level tests for acceptance claims. Keep casual connectivity observations separate from calibrated measurement evidence.