If you are building a LoRa or LoRaWAN device, airtime is one of the most important values to understand. Airtime determines battery impact, network capacity, and duty-cycle compliance. This calculator gives you a practical estimate of packet time-on-air using the standard LoRa modem equations.
What is LoRa airtime?
LoRa airtime is the total time a radio packet occupies the channel, from preamble through payload. Longer airtime means:
- More energy consumed by the transmitter
- Higher collision probability in shared spectrum
- Lower capacity for nearby devices
- Greater risk of violating regional duty-cycle limits
How this calculator works
The calculator uses the common Semtech LoRa time-on-air model:
Tsym = 2^SF / BWTpreamble = (Npreamble + 4.25) × Tsym-
Npayload = 8 + max(ceil((8PL - 4SF + 28 + 16CRC - 20IH) / (4(SF - 2DE))) × (CR + 4), 0) Tpayload = Npayload × TsymToA = Tpreamble + Tpayload
Where PL is payload bytes, IH indicates implicit header mode, and DE is low data rate optimization.
Input guide
1) Payload size
Start with your real application payload, not just sensor bytes. Include framing, ports, counters, and any protocol overhead in your estimate.
2) Spreading factor (SF)
Higher SF improves link budget and range but increases airtime significantly. For many deployments, SF is the biggest lever on airtime.
3) Bandwidth (BW)
Wider bandwidth shortens symbol duration and reduces airtime. Typical LoRaWAN channels commonly use 125 kHz for uplinks in many regions.
4) Coding rate (CR)
More redundancy (e.g., 4/8) improves robustness at the cost of longer packet duration.
5) Header mode, CRC, and DE
- Explicit header is typical because it carries packet metadata.
- CRC enabled is common for better integrity checks.
- DE (low data rate optimization) should be enabled in slow symbol conditions (often SF11/12 at 125 kHz).
Quick interpretation of results
The calculator returns per-packet airtime and optional batch airtime for multiple packets. It also estimates:
- Minimum interval between transmissions for a selected duty cycle
- Maximum packets per hour/day on one channel under that duty-cycle cap
This helps with planning sensor reporting intervals and understanding whether a configuration is operationally safe.
Example scenarios
| Use Case | Settings | Impact |
|---|---|---|
| Battery sensor (rural) | SF11, BW125, CR4/5, 12-byte payload | Longer airtime but better range margin |
| Dense urban meter | SF7, BW125, CR4/5, 20-byte payload | Short airtime, better capacity |
| Robust industrial link | SF9, BW125, CR4/8, 32-byte payload | Higher reliability, moderate airtime increase |
Tips to reduce airtime
- Use the lowest spreading factor that still provides stable link quality.
- Keep payloads compact; pack fields efficiently and avoid unnecessary chatter.
- Avoid frequent retries by improving antenna placement and RF conditions.
- Batch non-urgent data where possible to reduce transmission count.
- Review ADR strategy in LoRaWAN networks to move nodes toward lower SF when feasible.
Final thoughts
A LoRa airtime calculator is a practical design tool, not just an academic one. Use it early when defining reporting cadence, power budget, and network scale. Small parameter changes can dramatically alter airtime, so test several realistic profiles before finalizing firmware defaults.