ProcirelAntenna Basics for IoT: Wavelength, Gain and Matching
The antenna is the least understood component in every wireless build — and the one with the biggest effect on range. A quarter-wavelength whip and a basic understanding of matching can double or triple link distance compared to a poorly placed chip antenna.
> At a glance: 9 minute guide · part of the IoT and ESP32 complete guide track · worked example, quick-reference table and field notes included.
## Wavelength and antenna size
Antennas resonate at fractions of the signal wavelength. At 2. 4 GHz, λ ≈ 12. 5 cm, so a quarter-wave element is 3. 1 cm. At 868 MHz it is 8. 2 cm. That is why PCB antennas struggle in tiny enclosures and why a cut-to-length wire often beats them — physics sets the minimum size.
## Gain, direction and polarization
Gain does not create power — it focuses it. A 2 dBi “omni” radiates a flattened donut. A 9 dBi panel trades coverage width for distance in one direction. Match polarization between ends (usually vertical) or eat a 20 dB-plus penalty as they cross.
## Matching and placement
The radio expects 50 Ω; the antenna must present it across the band. Keep antennas away from metal, batteries and hands — a hand over a 2. 4 GHz antenna can cost 10 dB. Feed with proper transmission line or controlled trace, and never coil excess coax into a loop.
| Band | Wavelength | Quarter-wave | Notes |
| — | — | — | — |
| 433 MHz | 69 cm | 17.3 cm | Long range, big antennas |
| 868 MHz | 34.6 cm | 8.6 cm | EU LoRa |
| 915 MHz | 32.8 cm | 8.2 cm | US LoRa/ISM |
| 2.4 GHz | 12.5 cm | 3.1 cm | WiFi/BT/LoRa 2.4 |
## How to apply this in your build
Work through the sequence below. Each step assumes the previous one passed. The numbers that need arithmetic are covered by the linked tools at the end of this guide.
1. Cut or select the antenna for your exact band
2. Mount it clear of metal and batteries
3. Keep polarization consistent across the link
4. Measure RSSI before and after every change
### Worked example
Moving a 2. 4 GHz module’s chip antenna 3 cm away from a LiPo pack improved RSSI by 8 dB — more range than upgrading to the “high power” module would have given. Cross-check with the Frequency & Wavelength and the result should agree to within rounding.
> Practical note from the bench. Range problems are antenna problems nine times out of ten — before touching firmware, re-seat and re-place the antenna and measure.
## Who this guide is for
First-time readers get a single focused topic instead of a textbook chapter, with every term defined where it first appears. Returning readers use it as a reference. The table, the worked example and the mistake list answer the questions that come up mid-build. If you teach, the structure (theory, application, example, failure modes) maps cleanly onto a lab session.
## Prerequisites and preparation
Before starting. Cut or select the antenna for your exact band and mount it clear of metal and batteries. Keep the [Frequency & Wavelength](/tools/frequency-wavelength) open, every number in the worked example is reproducible. Total time including the bench steps: about 7 to 9 minutes.
## Common mistakes to avoid
Each of these has cost real hardware on someone’s bench, usually ours:
– Coiling surplus antenna wire — it detunes exactly like an inductor
– Mixing polarization between node and gateway
– Judging antennas by dBi alone without direction patterns
## Key takeaways
– Wavelength and antenna size — the foundation of this guide; revisit it if any measurement here surprises you.
– Gain, direction and polarization — the foundation of this guide; revisit it if any measurement here surprises you.
– Matching and placement — the foundation of this guide; revisit it if any measurement here surprises you.
### Quick reference card
| Aspect | Where to find it in this guide |
| — | — |
| Core theory | Wavelength and antenna size |
| Application steps | How to apply this in your build |
| Worked numbers | Worked example |
| Failure modes | Common mistakes to avoid |
## How this fits the IoT and ESP32 complete guide track
This guide is one stop in a structured path. Start from the [IoT and ESP32 complete guide](/tutorial/iot-esp32-complete-guide) pillar page for the full map, or continue with [LoRaWAN basics](/tutorial/lorawan-tutorial-beginners) and [frequency and wavelength](/tutorial/frequency-wavelength). For the arithmetic, open the [Frequency & Wavelength](/tools/frequency-wavelength).
## Frequently asked questions
Do antenna “boosters” work?
Passive stickers and repeater chips do nothing. Real gains come from proper geometry, placement and matching.
SMA or u.FL?
SMA for external antennas and testing; u.FL for internal routing where a small connector matters.
Is there a calculator for this?
Yes, the [Frequency & Wavelength](/tools/frequency-wavelength) run the formulas from this guide instantly, client-side, no signup.
## Continue the learning path
– The complete iot, sensors & esp32 guide: [IoT, Sensors & ESP32 complete guide](/tutorial/iot-esp32-complete-guide)
– Read next: [lorawan for beginners: long-range iot without wifi](/tutorial/lorawan-tutorial-beginners)
– Also in this track: [biomedical sensors: how wearables measure the body](/tutorial/biomedical-sensor-guide)
– Continue with: [5g architecture explained: what actually changed](/tutorial/5g-architecture-explained)
– Calculate as you go: [battery life estimator](/tools/battery-life) · [LM317 regulator designer](/tools/lm317-regulator) · [wire gauge checker](/tools/wire-gauge-awg)
– Bookmark this page against the day a measurement surprises you. Most readers return to the table and the mistake list first, and that is the correct order.
## Measurement discipline
Keep a lab notebook entry for every build in this track. The measured values, the deviations from the guide and the reason for each. Six months from now, those notes are worth more than any tutorial. They describe your bench and your components rather than a general case.
When a result here disagrees with your expectation, write down both numbers before changing anything. The gap between predicted and measured is where the real engineering lives. It is usually a tolerance, a parasitic or an assumption that was never checked.
## Formulas and checks from this guide
Verification checklist for this track: watch RSSI before blaming code, measure supply current during radio bursts. Confirm MQTT topics against the broker log. Wireless bugs are usually power or signal problems wearing a software disguise.
Bookmark this page against your next build in the track. The checklist above is the same one used across 23 guides in this series.
## Hard-won notes
Measure current during transmit bursts. Sags under load are power problems, no firmware fixes those.
Location, then device, then measurement. Document the tree before flashing the first device.