What free-space path loss means for a radio link
Free-space path loss, usually shortened to FSPL, is the first number many radio planners check when they sketch a wireless path. In the ideal free-space model, with no buildings, hills, trees, weather, or reflections to complicate the route, the transmitted energy still spreads out as it travels. As that energy spreads over a larger area, the receiving antenna captures a smaller share. This calculator estimates that geometric spreading loss in decibels from only two inputs: frequency and distance.
That makes the page useful for practical radio work, not just class notes. You can use it while planning a point-to-point Wi-Fi bridge, checking a telemetry hop, comparing bands for an ISM deployment, or deciding whether a microwave path is worth pursuing before you spend time on antenna gain and installation losses. FSPL is not the entire link, but it is the clean baseline that shows how much budget has already disappeared before the environment gets involved.
The answer is shown in dB, so it behaves like a loss term in a link budget. A larger FSPL number means more geometric spreading loss between transmitter and receiver. A smaller number means less of the signal has been lost to distance and frequency alone. If two designs are otherwise similar, the one with the lower path loss is usually easier to close.
How to use the free-space path loss calculator for a link budget
Enter the radio frequency in megahertz and the antenna separation in kilometers, then press the calculate button. The page returns free-space path loss in dB. Those units matter because the familiar 32.44 constant on this page assumes exactly megahertz and kilometers. If you switch to meters, miles, or gigahertz without adjusting the formula, the result will be wrong even though the physics is unchanged.
A practical way to use the tool is to start with the band and distance you expect in the field, then run a few comparison cases. For example, keep the distance fixed and compare 900 MHz, 2.4 GHz, and 5.8 GHz. Or keep the frequency fixed and test a short, typical, and worst-case distance. FSPL changes in a predictable way, so a few quick checks often reveal whether you need more antenna gain, a shorter path, or a lower operating frequency.
- Type the carrier frequency in MHz.
- Type the link distance in km.
- Press Calculate FSPL to update the result panel.
- Read the answer as a loss term in dB, then compare it with your transmitter power, antenna gains, and receiver sensitivity.
If you are building a link budget spreadsheet later, this calculator is a fast way to verify that the FSPL term is in the right ballpark before you commit to a larger design.
How to choose sensible FSPL inputs for distance and frequency
The frequency box should contain the actual RF frequency, not the channel number, service name, or marketing label. A 2.4 GHz Wi-Fi link should be entered as 2400 MHz if you want a quick estimate; a 915 MHz telemetry system should be entered as 915. The distance box should represent the full separation between transmitting and receiving antennas, not the cable run, the route along roads, or the radius of a service area on a map.
When you are not sure which distance to use, think about the path you are trying to guarantee. A best-case line-of-sight test range may be much shorter than the longest path you need in production. Engineers often run at least three cases: nominal distance, maximum expected distance, and a conservative stretch case. That habit makes the result more useful because it turns a single number into a decision range.
The free-space path loss formula used on this page
For distance in kilometers and frequency in megahertz, the standard free-space path loss equation used by this calculator is:
Here, d is distance in kilometers and f is frequency in megahertz. The logarithms are why FSPL changes in clean, memorable steps instead of linearly. If you double the distance, the loss increases by about 6.02 dB. If you double the frequency, the loss also increases by about 6.02 dB. Increase either one by a factor of ten and the loss rises by 20 dB.
Those scaling rules are what make the calculator useful when you are comparing bands or checking a route. A 1 km path at a low frequency can look comfortable, while a modest jump in distance or a jump into a higher band can add enough loss to change the rest of the design. The point of the calculation is not to produce a polished final answer; it is to show how quickly distance and frequency consume your budget.
In a full wireless design, you normally combine FSPL with transmitter power, antenna gain, cable loss, connector loss, polarization mismatch, fade margin, and receiver sensitivity. This calculator isolates the propagation term so you can see how much of the budget is already spent before those other pieces are added.
Worked example: 2.4 GHz over a 5 km radio path
Assume you want the free-space loss for a 2.4 GHz link over 5 km. Because the form expects megahertz, enter 2400 for frequency and 5 for distance. The calculation becomes 32.44 + 20 log10(5) + 20 log10(2400). That works out to 32.44 + 13.98 + 67.60, which gives approximately 114.02 dB.
That number is the propagation loss term only. On its own, 114.02 dB is neither good nor bad; it simply tells you how much signal strength disappears to spreading before gains and other losses are considered. If your transmitter has generous power, both antennas have gain, and the receiver is sensitive, the link may still be comfortable. If you are using low-power hardware with little antenna gain, the same path loss may be too high.
Now compare that with a 900 MHz link over the same 5 km. The loss drops to about 105.50 dB. That difference of roughly 8.52 dB is large enough to matter. It helps explain why lower bands can feel easier to close over the same distance, even before you think about diffraction, penetration, or regulatory power limits.
How to interpret the result in a link budget
The calculator returns only the free-space loss term, not received power. To estimate received power, place the FSPL number into a simple link budget. A common engineering shorthand is:
Here, received power equals transmit power plus transmit and receive antenna gain, minus the free-space path loss, minus any other losses such as feedline, connector, polarization, or implementation loss. Imagine a 2.4 GHz link over 5 km with 20 dBm transmit power, 8 dBi gain at each antenna, and 2 dB of miscellaneous loss. You would estimate received power as 20 + 8 + 8 - 114.02 - 2, or about -80.02 dBm.
If the receiver needs only -92 dBm for the data rate you care about, that rough budget leaves almost 12 dB of margin. That is a useful first-pass result. It suggests the link may work in free space, but you would still want extra margin for fading, alignment error, rain, foliage, interference, and real installation losses. In other words, FSPL gets you to the starting line; engineering margin gets you to a robust system.
Free-space path loss comparison scenarios for common bands
The table below shows how free-space path loss changes in a few common radio-link situations. They are not universal recommendations, but they show how quickly the loss rises as either variable increases.
| Scenario | Frequency | Distance | FSPL | Reading the number |
|---|---|---|---|---|
| VHF telemetry | 150 MHz | 2 km | 81.98 dB | Very modest free-space loss compared with higher bands, which is why low-frequency links can tolerate range more easily. |
| Sub-GHz / ISM | 900 MHz | 2 km | 97.55 dB | Still manageable for many practical systems, but already about 15.6 dB higher than the 150 MHz case at the same distance. |
| 2.4 GHz bridge | 2400 MHz | 5 km | 114.02 dB | A useful benchmark for outdoor Wi-Fi-style planning. Antenna gain and fade margin become important here. |
| 5.8 GHz microwave hop | 5800 MHz | 5 km | 121.69 dB | High-capacity bands can work well, but the free-space loss is much steeper and link budgets tighten quickly. |
A quick pattern appears: long distance and high frequency compound each other. If you have flexibility in only one design variable, even a modest reduction in path length or operating band can buy back several dB.
Free-space path loss assumptions and limits in the real world
This calculator intentionally uses the simplest widely accepted model: unobstructed propagation in free space. That means it ignores obstacles, terrain, buildings, foliage, Fresnel-zone blockage, antenna pattern detail, feeder losses, multipath fading, humidity, rain fade, earth curvature, and polarization mismatch. In the field, any of those can matter. The result is therefore best treated as a baseline rather than a guarantee.
That baseline is still valuable because it answers an important question early: if the link does not look feasible even in free space, it will not improve once reality is added. On the other hand, if the FSPL result looks comfortable, you have a reason to continue into a fuller design with gains, margins, and environmental effects included.
- Line of sight: the calculation assumes a clear, unobstructed path.
- Far-field conditions: FSPL is a propagation model, not a near-field coupling model.
- Unit discipline: MHz and km are required for the constant used here.
- No antenna terms: antenna gain is not part of the answer shown by this calculator.
- No fade margin: real deployments need extra dB beyond the mathematical minimum.
Practical FSPL checks before you trust the path-loss number
After calculating FSPL, ask three plain questions. First, does the number move in the right direction when you change inputs? It should rise when distance rises and also rise when frequency rises. Second, is the result in the range you would expect from similar systems? Third, when you insert the number into a larger link budget, is there still a healthy margin after all other losses are added?
Those checks catch the most common mistakes: entering gigahertz as if it were megahertz, confusing miles with kilometers, and mistaking path loss for received power. They also keep you from over-trusting a clean-looking result. Radio math is precise, but field conditions are rarely ideal.
Common FSPL questions for radio planning
Does a higher dB output mean a stronger link? No. In this calculator, the dB number is a loss term. Higher FSPL means more spreading loss and therefore a weaker received signal for the same transmitter and antenna setup.
Why does the answer jump so quickly? Because the equation is logarithmic. Ten times the distance adds 20 dB. Ten times the frequency adds another 20 dB. That scaling is why microwave links often need tighter engineering discipline than lower-frequency links.
Can I use the result for indoor or obstructed paths? Only as a lower bound on loss. Once walls, people, ground reflections, foliage, or weather appear, real attenuation may be much higher. The calculator remains useful as the clean starting point, but it is not a substitute for a site survey or a full propagation model.
Why preserve a simple FSPL tool when full simulators exist? Because fast intuition matters. A one-line estimate helps you reject impossible ideas, compare bands quickly, and understand which variable is doing the damage before you move into more detailed software.
Free-space path loss result
The value above is easier to use when you compare scenarios. Try keeping frequency fixed and doubling distance, then keeping distance fixed and doubling frequency. You should see the same pattern both times: each doubling adds about 6 dB of free-space loss.
Optional mini-game: Link Window Sprint
This arcade mini-game turns the same idea into a fast reflex challenge. Receivers drift across space at different ranges, and you choose the band that can still close the link before the target gets away. Lower frequency is forgiving at long distance; high frequency scores more, but only when the receiver is close enough for the path loss to stay manageable. The calculator above is the real math tool; the game below is simply a playful way to build intuition.
Best score is saved on this device. Quick lesson: doubling distance adds about 6 dB of free-space loss, and doubling frequency adds about 6 dB too.
