Fresnel Zone Calculator
The formula
What the fresnel clearance tells you
The bulge of radio energy around the visual line of a microwave path, and whether your trees and rooftops are inside it.
Calculation: r₁ = 17.32 × √(d1·d2 ÷ ((d1+d2)·f)); clearance % = actual ÷ r₁. Enter your inputs and every substitution is shown below the result.
Reading the result
Visual line-of-sight is necessary but not sufficient: 60 % of zone one clear is what the link budget assumed.
Rules of thumb: 60 % = full budget; 40 % = survivable with margin; below that the link trains to a lower MODCAP or not at all.
Limitations and best practice
Reed and grass “clearance” grows with humidity; design to winter photos, verify in August.
This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Frequently asked questions
Does the zone differ off-midpoint?
Can antennas below the obstacle work?
Source & methodology
Fresnel zone geometry r = √(λ·d1·d2/(d1+d2)); ITU-R P.526 diffraction model.
Fresnel Zone: what this tool answers
You are here because you need a specific number, and you want to see how it was produced before you rely on it. Searchers land on a Fresnel Zone page for three reasons — to plan, to compare options, and to check that somebody else’s arithmetic is honest. This tool serves all three, and everything after the calculator explains the model instead of hiding it.
People rarely disagree about arithmetic; they disagree about assumptions that were never written down. Printing the substitution and the sensitivity ranking removes that category of disagreement for Fresnel Zone.
Systems math in Technology & Computing has a peculiar property: it feels precise until an assumption breaks silently. Fresnel Zone is exact arithmetic over r₁ = 17.32 × √(d1·d2 ÷ ((d1+d2)·f)); clearance % = actual ÷ r₁ — but only as truthful as the model. A wrong assumption about Leg 1 distance (km) will not throw an error; it will just quietly produce the wrong 8.97 m.
Nothing below is stock text pasted around a number: the worked example computes first Fresnel zone radius = 8.97 m from this tool’s own defaults, and the sensitivity section ranks the inputs that move the result — Frequency first, at ≈5.4 % of the headline for a ten-percent error either way in that input — which is the thread the rest of this guide pulls on.
Inside the Fresnel Zone calculation: formula and every input
The engine implements a single stated model: r₁ = 17.32 × √(d1·d2 ÷ ((d1+d2)·f)); clearance % = actual ÷ r₁. There is no hidden coefficient and no login-gated precision — the formula printed is the formula executed, which is also what makes the result citable.
Leg 1 distance (km) (example value 2) is a plain measured quantity — the unit shown in the label is the unit the formula expects. Measure twice and use the unit the label asks for — length terms often scale the result geometrically.
Leg 2 distance (km) (example value 6) is a measured number in the unit named by the label; the formula does not convert for you. Keep every length field in the same unit; the formula assumes a consistency it cannot check for you.
Frequency (GHz) (example value 6) is a measured number in the unit named by the label; the formula does not convert for you. The example value is there to demonstrate the mechanics, not to describe your situation — overwrite it.
Actual clearance at midpoint (m) (example value 4) is a quantity rather than a category — precision here is cheap and worth having. This input feeds the formula directly; a defensible figure here is worth more than false precision anywhere else.
A fully worked Fresnel Zone example
Rather than describe the calculation, here it is end to end — every substitution in order, starting from the inputs above. Starting figures: Leg 1 distance (km), Leg 2 distance (km), Frequency (GHz), Actual clearance at midpoint (m). The endpoint of that chain is 8.97 m of first Fresnel zone radius, sitting in the “Compromised — a few dB of diffraction loss” band.
- r₁ = 17.32 × √(2.1×6.0 ÷ (8.1×5.8))
- = 8.97 m at the midpoint
- Clearance 4.4 m ÷ 8.97 m = 48.7 %
- 2.4 dB of edge diffraction expected
Clearance of zone 1 — 48.7%. If your inputs change, this is usually the first companion figure to move.
Estimated diffraction loss — 2.4 dB. If your inputs change, this is usually the first companion figure to move.
Total path length — 8.10 km. If your inputs change, this is usually the first companion figure to move.
Required clearance for 60 % — 5.38 m. Compare it against the main result of 8.97 m before drawing conclusions.
Keep this worked example open while you enter your own figures: matching the shape of the substitution is the fastest way to spot a unit or convention mistake.
The Fresnel Zone corridor: your result across a realistic band
Read this table as the practical error bar on the headline figure. It answers the question people actually have after seeing a single number: how wrong could this be if the main input is off by ten or twenty percent?
| Frequency setting | First Fresnel zone radius |
|---|---|
| 80 % of the example value | 10.03 m |
| 90 % of the example value | 9.45 m |
| example inputs | 8.97 m |
| 110 % of the example value | 8.55 m |
| 120 % of the example value | 8.19 m |
The corridor runs from 8.19 m to 10.03 m across that band — which is the range worth planning inside rather than the single 8.97 m point estimate. Reproduce it in the form above by editing Frequency alone; the substitution steps will follow your figures exactly.
Where Fresnel Zone is fragile — and where it is not
This list was computed for this specific engine just now: each numeric input was nudged ±10 % while every other field held its example value, and the first Fresnel zone radius was recalculated from scratch. It is the fastest honest answer to “what matters most in Fresnel Zone?” — and it is specific to these defaults, because sensitivity moves with the starting point.
- Frequency: ten percent up gives 8.55 m, ten percent down gives 9.45 m — ≈5.4 % of the first Fresnel zone radius either way
- Leg 1 distance: ten percent up gives 9.29 m, ten percent down gives 8.62 m — ≈3.9 % of the first Fresnel zone radius either way
- Leg 2 distance: ten percent up gives 9.08 m, ten percent down gives 8.84 m — ≈1.4 % of the first Fresnel zone radius either way
Frequency is the dominant lever here: ten percent either way moves the result by about 5.4 %, from 8.55 m to 9.45 m. Measure that input from a document rather than from memory, and treat Leg 1 distance as the second priority (≈3.9 % per ten percent). The rest of the inputs earn only a rounding-error of attention, and that asymmetry is the practical payoff of measuring rather than asserting.
Interpreting the Fresnel Zone verdict
A number on its own is trivia; a number against a range is intelligence. On the example inputs the band reads “Compromised — a few dB of diffraction loss”; your own figures place you on a different rung of the same ladder. How much of that band is luck? On Frequency alone ten percent either way covers 8.55 m to 9.45 m. The practical reading rules: ask what would have to change to move you one band. If the answer is “a small, plausible input difference”, the band itself is not the finding — the uncertainty is.
Placing this figure in context: calculators of this kind differ less in arithmetic than in what they choose to ignore. This one keeps Leg 1 distance (km) explicit so that the omissions are visible rather than hidden in a preset.
Common mistakes with Fresnel Zone (and the fix)
Reed and grass “clearance” grows with humidity; design to winter photos, verify in August. This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Reading Fresnel Zone as a promise rather than a conditional. Every number here is of the form “if these inputs, then this result”; when an input moves, the honest response is to recompute rather than to defend the old figure.
Attention is also misallocated between fields. Having measured this engine, we can say where it belongs: Frequency first, everything else second.
The subtlest error is answering the wrong question precisely. Confirm that first Fresnel zone radius is actually the quantity your decision needs — the arithmetic is flawless either way, which is what makes the mistake invisible.
A quick check for any Fresnel Zone figure
- Re-run the calculation with a ±10 % stress on the two most sensitive inputs.
- State, in one sentence, which convention each rate, unit or period in the form is using.
- Re-verify Frequency against a source document — ten percent of error there moves the headline by ≈5.4 %.
- Verify each input against its original source document, not memory.
- Check that every field the formula needs actually arrived from a document, not from recollection.
- Repeat the ±10 % test on the inputs that matter and see whether the decision — not just the number — still holds.
Five steps from raw inputs to a figure you can defend
Using a calculator well sounds trivial, but the difference between a decision-grade figure and a throwaway one lives entirely in the routine. The routine for Fresnel Zone takes a minute to learn and applies to every input above.
Step 1 — start from evidence. The inputs behind Fresnel Zone are leg 1 distance (km), leg 2 distance (km), frequency (ghz), actual clearance at midpoint (m). Write them down with their source next to each one; if you cannot name where a figure came from, that is the input most likely to be wrong. When in doubt, prefer the boring input: the interesting one is usually the one you misread.
Step 2 — compute the version you would not be embarrassed by. If a stranger audited your inputs, which set would you hand over? Enter that set, read the result, and treat everything else as upside. A figure nobody can reproduce is a figure nobody will act on twice.
Step 3 — change one input at a time. Nudge a single field by ten percent, watch the headline and its companions move, then undo it. Two or three fields will dominate — the sensitivity table above already ranks them for this engine. The inputs are the part of the work that nobody else can do for you.
Step 4 — ask what would have to be true. Take the result you want and work backwards through the inputs until you find the assumption that produces it; then decide honestly whether that assumption is defensible. When in doubt, prefer the boring input: the interesting one is usually the one you misread.
Step 5 — record the context, not just the number. Note today’s date and the inputs alongside the 8.97 m output. Six months from now the context is what turns this figure into a trend. Estimates improve most when the worst case is written down in ink.
The real-world conversations Fresnel Zone settles
Technology & Computing arguments end at arithmetic or they do not end. Fresnel Zone is the arithmetic: 8.97 m on the example inputs, reproducible by anyone who types the same numbers. Comparisons are cheap: run the identical calculation for the alternative and look at the gap.
Used properly this is a five-minute filter that saves weeks. Compute Fresnel Zone, reject what fails, and only then bring in the expensive analysis for the survivors. Half of a good calculation is knowing which input you would hate to be wrong about.
Nothing here is stored or transmitted, so the habit of checking is free: open the page, re-enter current figures, compare with the number you saved last time. Write the figure down before moving on; memory flatters whichever number you saw last.
Quick answers: what searchers ask about Fresnel Zone
What affects Fresnel Zone the most?
Fresnel Zone is driven above all by Frequency. Perturbing only that field by ten percent either way produced 8.55 m against the 8.97 m baseline — a ≈5.4 % response, while Leg 1 distance manages ≈3.9 %.
Which matters more: leg 1 distance or frequency?
For Fresnel Zone, Frequency wins the head-to-head (≈5.4 % against ≈3.9 % per ten-percent change). Knowing which input dominates is the difference between careful work and merely slow work.
What is a typical Fresnel Zone?
On the worked example above Fresnel Zone comes out at 8.97 m. Treat that as one point on a distribution rather than a norm: the bands, the companion outputs and the sensitivity ranking tell you how wide the plausible range really is.
How do I calculate Fresnel Zone by hand?
Three steps: write the formula (r₁ = 17.32 × √(d1·d2 ÷ ((d1+d2)·f)); clearance % = actual ÷ r₁), insert your values, and simplify. The worked example section shows exactly that chain for the default inputs; replicating it once on paper teaches you more about Fresnel Zone than any number of calculator runs.
What happens to Fresnel Zone if frequency changes by 10 %?
The engine was re-run with that field moved by ten percent while everything else stayed fixed: the first Fresnel zone radius goes across 8.55 m to 9.45 m, a swing of roughly 5.4 % around the 8.97 m baseline. That ratio is the practical definition of how much this input matters.
Is the Fresnel Zone result of 8.97 m good or bad?
The tool answers “what”, not “whether”: 8.97 m carries the verdict “Compromised — a few dB of diffraction loss” for the default case, which is a starting interpretation rather than a verdict on your situation. Re-run with your own figures and compare the bands.
Is Fresnel Zone accurate?
The arithmetic is exact: r₁ = 17.32 × √(d1·d2 ÷ ((d1+d2)·f)); clearance % = actual ÷ r₁ is evaluated with full floating-point precision and every substitution is printed in the worked example. What limits accuracy is input quality and the model’s assumptions, so treat the 8.97 m result as the correct answer to the question you typed — and check the assumptions section before acting on it.
How do I calculate Fresnel Zone manually?
Write down the inputs, then follow the printed steps in order — r₁ = 17.32 × √(d1·d2 ÷ ((d1+d2)·f)); clearance % = actual ÷ r₁. A spreadsheet replicates it with two or three cells. The manual route is worth doing once to build intuition; after that the calculator saves time and eliminates transcription slips.
Does the zone differ off-midpoint?
Yes — it is an ellipsoid, bulging largest near the middle thirds; check the worst obstruction leg, not just center.
Can antennas below the obstacle work?
Sometimes — diffraction loss falls fast with clearance; a 1 dB loss path is cheaper than a 12 m pole.
Does this Fresnel Zone tool store my numbers?
No. The entire calculation runs in your browser session; nothing entered above is transmitted or saved, which is the correct behaviour for sensitive Technology & Computing figures and the reason you can re-run this page as often as you like.
The vocabulary of Fresnel Zone
- Clearance of zone 1
- 48.7% for the Fresnel Zone worked case; it sits next to the main result because it carries context the headline leaves out.
- Estimated diffraction loss
- 2.4 dB on the example inputs — a companion figure printed beside the headline of Fresnel Zone so that no result is read in isolation.
- Total path length
- 8.10 km in the default Fresnel Zone calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- First Fresnel zone radius
- The primary output of this tool: 8.97 m for the default inputs, computed exactly from r₁ = 17.32 × √(d1·d2 ÷ ((d1+d2)·f)); clearance % = actual ÷ r₁.
- Worked example
- The calculation written out in full so that nothing on this page has to be taken on trust.
- Verdict band
- The interpretation attached to a result (“Compromised — a few dB of diffraction loss” on these inputs), which turns a bare number into a position on a scale.
- Sensitivity (±10 %)
- How far the Fresnel Zone moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
Method, sources and what this tool cannot tell you
Everything above runs on one stated formula, applied without hidden coefficients: r₁ = 17.32 × √(d1·d2 ÷ ((d1+d2)·f)); clearance % = actual ÷ r₁. Source of record: Fresnel zone geometry r = √(λ·d1·d2/(d1+d2)); ITU-R P.526 diffraction model. Specialist software layers extra coefficients on top of the same algebra; none are hidden here, and that transparency is what makes a disagreement traceable to a specific input instead of a black box.
This page is an estimation aid, not professional advice. The design rule is simple: two people entering identical figures must get identical answers. The design constraint was set by usefulness rather than by comfort: an estimate you can interrogate beats an answer you have to trust.
What to do with your Fresnel Zone next
Save the number together with its inputs and today’s date; a Fresnel Zone figure without context is unusable the moment an input changes.
This page was written for people who need one trustworthy number before their next decision, and the promise is that nothing above required trust. Bookmark the tool, re-run it whenever an input moves by more than a few percent, and keep the date with the number.