Fiber Link Budget Calculator

Fiber profile:

Start from a common single-mode, multimode, or PON-style profile, then edit the numbers below.

Transmit power:

Enter optical launch power in dBm; conservative budgets use minimum Tx power.

dBm

Receiver sensitivity:

Enter the lowest acceptable receive level in dBm, usually a negative number.

dBm

Fiber distance: {{ formatRangeUnit(distance_km, 'km', 2) }}

Enter the full optical path length through the installed fiber route.

Fiber attenuation: {{ formatRangeUnit(fiber_loss_db_per_km, 'dB/km', 2) }}

Use measured OTDR/loss-test data when available; otherwise use a conservative design value.

dB/km

Mated connections:

Count each mated connector interface that contributes insertion loss.

joins

Loss per connection:

Enter the design or measured loss for each mated connection.

Splices:

Enter total splices in the optical path.

splices

Loss per splice:

Enter the design or measured loss for each splice.

Passive component loss: {{ formatRangeUnit(passive_loss_db, 'dB', 1) }}

Enter extra insertion loss from splitters, WDMs, couplers, attenuators, or modules.

Required reserve: {{ formatRangeUnit(required_margin_db, 'dB', 1) }}

Set the minimum remaining operating margin after modeled link loss.

Receiver overload level:

Optional max receive power in dBm; blank skips the too-hot receiver check.

dBm

Dispersion or equipment penalty:

Optional extra penalty added to link loss; default 0 keeps the baseline unchanged.

Test uncertainty allowance:

Optional allowance for measurement tolerance; leave at 0 unless you need an explicit test guard band.

Rounding:

Choose how many decimals to show in result tables and exports.

Metric	Value	Read	Copy
{{ row.label }}	{{ row.value }}	{{ row.read }}

Loss component	Basis	Loss	Share	Copy
{{ row.label }}	{{ row.basis }}	{{ row.loss }}	{{ row.share }}

Check	Status	Action	Reason	Copy
{{ row.check }}	{{ row.status }}	{{ row.action }}	{{ row.reason }}

Embed:

Customize

Include current inputs

Size

Advanced

Width

Height

Aspect ratio

Max height

Collapsible embed

Allow fullscreen

Referrer policy

Sandbox tokens

Fiber links can fail at both ends of the light range. Too little power at the receiver causes errors or loss of signal, while a very short or high-power path can overload a sensitive receiver. A link budget gives those risks a number before a route is built, extended, or handed over. It compares the optical power that leaves the transmitter with the attenuation from fiber, mated connections, splices, splitters, filters, couplers, fixed attenuators, and any extra allowance for equipment penalties or test uncertainty.

The arithmetic uses two related units. Optical power is usually expressed in dBm, which is an absolute power level referenced to 1 milliwatt. Loss and margin are expressed in dB, which is a relative change. That is why a transmitter at -3 dBm and a receiver sensitivity of -18 dBm create a 15 dB power budget. The dB budget is then spent by cable attenuation and every event in the path.

Optical power budget path from transmitter to receiver with fiber loss, connections, splices, passive loss, and reserve margin.

Distance is only one part of the answer. A long clean single-mode span can have less loss than a short path that crosses several patch panels and a splitter. Wavelength also matters because fiber attenuation changes with fiber type and operating wavelength. Common design estimates often put single-mode attenuation lower at 1550 nm than at 1310 nm, while multimode 850 nm links usually spend budget much faster per kilometer.

Power budget: The dB difference between transmitter output and receiver sensitivity.
Loss budget: The expected loss of the cable plant and passive devices in the optical path.
Reserve: Unused margin kept for aging, dirt, repairs, future patches, and measurement uncertainty.
Overload: A receiver condition where the incoming light is above the optic's maximum allowed input.

Design work uses the budget to choose an optic class, splitter plan, route length, and reserve margin before installation.
Turn-up work compares the design estimate with source-and-power-meter or optical loss test set measurements.
Troubleshooting work looks for the part of the route that is consuming more dB than expected, such as dirty connectors or an undocumented passive device.

Budgets are useful during design, procurement, and troubleshooting because they show which assumption is consuming the margin. Dirty connectors, field-terminated connectors, repair splices, and passive optical network splitters can change the result more than a small distance change. A budget also helps separate cable-plant questions from transceiver questions: if the cable loss is reasonable but the optic power budget is too small, different optics may be needed.

A paper budget is not a certification result. Installed fiber still needs the relevant inspection and loss testing, usually with a light source and power meter or an optical loss test set, and long outside-plant routes may also need OTDR traces for event location. Treat the calculated margin as a design estimate until measured loss, connector condition, route documentation, and the actual optic datasheet all agree.

How to Use This Tool:

Start with the optic datasheet values, model the installed path, then use the ledgers and charts to see whether loss, reserve, or overload needs attention.

Choose a Fiber profile. The single-mode, multimode, and PON presets load common first-pass values; choose Custom datasheet values when measured route loss or vendor optic data should control the calculation.
Enter Transmit power and Receiver sensitivity in dBm. For conservative planning, use the minimum guaranteed transmitter output and the required receiver sensitivity for the target rate.
Set Fiber distance from the real optical path, not map distance. Include slack loops, risers, patch-panel routing, and any route length that light actually travels.
Set Fiber attenuation in dB/km. If distance is greater than zero but attenuation is left at 0 dB/km, distance will not add loss, so enter a measured or conservative attenuation value unless you are intentionally modeling fixed loss only.
The warning Fiber attenuation is 0 dB/km, so distance does not add loss. means reach and loss charts are not useful until attenuation is corrected or deliberately left at zero.
Count Mated connections and Splices, then set the loss per event. Count the connections at equipment ports, patch panels, couplers, and reference points that belong to the design case.
Add Passive component loss for splitters, WDM filters, couplers, patch modules, and fixed attenuators that are not already represented by the connection or splice counts.
Set Required reserve. A route can be above receiver sensitivity and still fail the reserve target, so compare Reserve surplus with Operating margin above sensitivity.
Open Advanced when you need Receiver overload level, Dispersion or equipment penalty, Test uncertainty allowance, or a different Rounding display. Use Power Margin Ledger first, then inspect Loss Component Ledger, Margin Action Ledger, Optical Loss Stack, and Reach Margin Curve for the reason behind the status.
Enter Receiver overload level for short or high-power links; otherwise the overload row remains Not checked.

Interpreting Results:

Estimated receive level is the modeled optical power at the receiver after subtracting all entered loss from transmit power. Compare it with Receiver sensitivity to judge whether the receiver should get enough light before any reserve policy is applied.

Operating margin above sensitivity can be positive while Reserve surplus is negative. That means the model is bright enough to clear the receiver's minimum input, but it does not leave the guard band entered in Required reserve. Do not treat a positive operating margin alone as approval when the design requires reserve.

Below sensitivity means the estimated receive level is below the receiver minimum.
Below reserve means the route clears sensitivity but misses the reserve target.
Narrow reserve means the reserve target is met with less than 1 dB extra room.
Too much receive power means the optional overload level is entered and the estimated receive level is above it.

Max distance at reserve holds fixed losses constant and solves for the fiber route length where reserve would be exactly consumed. It is useful when distance is the design variable. If connector count, splitter loss, or optic power changes, recalculate instead of reusing the old distance.

Use Loss Component Ledger to find the largest contributor before changing optics. A splitter-heavy PON path may need a different splitter plan or optic class, while a connector-heavy route may need inspection, cleaning, retermination, or a measured value replacing a conservative estimate.

Technical Details:

Optical loss budgeting is additive in dB. Fiber attenuation increases with route length and attenuation coefficient, connection loss increases with the number of mated interfaces, and splice loss increases with the number of splices. Passive component loss, dispersion or equipment penalty, and test uncertainty allowance are added as fixed dB terms because each one reduces the remaining margin.

The receiver check has two limits when both are known. The lower limit is receiver sensitivity, the minimum receive power needed for the target performance. The upper limit is the receiver overload level, the maximum receive power the optic can tolerate. The usable receive level sits between those limits after the modeled route loss is subtracted from transmit power.

Formula Core:

The governing calculation converts route assumptions into total modeled loss, estimated receive level, operating margin, and reserve surplus.

\begin{array}{lcl} L_{fiber} & = & D * A \\ L_{total} & = & L_{fiber} + (N_{conn} * L_{conn}) + (N_{splice} * L_{splice}) + L_{passive} + L_{penalty} \\ P_{rx} & = & P_{tx} - L_{total} \\ M_{op} & = & P_{rx} - P_{sens} \\ M_{reserve} & = & M_{op} - R \end{array}

Fiber link budget symbols and units
Symbol	Meaning	Unit
`Ptx`	Transmit power entered for the design case	dBm
`Psens`	Receiver sensitivity, or the minimum acceptable receive power	dBm
`D`	Full fiber route distance	km
`A`	Fiber attenuation coefficient	dB/km
`Ltotal`	Total modeled link loss after fiber, events, passive loss, and penalties	dB
`R`	Required reserve kept unused after clearing receiver sensitivity	dB

For the single-mode 1310 nm access preset, -3 dBm transmit power and -18 dBm receiver sensitivity produce a 15.00 dB transceiver power budget. An 8.00 km route at 0.35 dB/km, four 0.50 dB mated connections, and six 0.10 dB splices produce 5.40 dB modeled link loss. Estimated receive level is -8.40 dBm, operating margin is 9.60 dB, and a 3.00 dB reserve leaves 6.60 dB reserve surplus.

Reach Rule:

Maximum distance at reserve solves the same budget backward. Fixed losses are subtracted first, then the remaining dB allowance is divided by fiber attenuation.

D_{\max} = \frac{(P_{tx} - P_{sens}) - R - L_{fixed}}{A}

When attenuation is greater than zero, negative reach is clamped to 0 km for the maximum-distance display while Distance overrun still shows how far the entered route exceeds the reserve reach. When attenuation is 0 dB/km, distance cannot consume budget, so the distance fields are reported as not bounded by attenuation.

Fiber link budget status rules and boundaries
Status	Boundary	Meaning
`Below sensitivity`	`Operating margin above sensitivity < 0 dB`	The estimated receive level is below the receiver minimum.
`Too much receive power`	`Estimated receive level > Receiver overload level`, after clearing sensitivity	The receiver may need attenuation or a lower-power optic.
`Below reserve`	`Reserve surplus < 0 dB`, after clearing sensitivity and overload priority	The link may work but misses the entered reserve target.
`Narrow reserve`	`0 dB <= Reserve surplus < 1 dB`	The reserve target is met with little additional room.
`Reserve met`	`Reserve surplus >= 1 dB`, unless overload applies	The modeled route has at least the requested reserve plus one extra dB.

Rounding changes display precision only. Counts are rounded to non-negative whole numbers, loss inputs are constrained to non-negative values, and the calculations keep full numeric precision before formatting the ledgers, charts, and JSON output.

Accuracy Notes:

Use measured cable-plant loss when it is available. Planning values for connector loss, splice loss, fiber attenuation, splitter insertion loss, and equipment penalties can be conservative or optimistic depending on installation quality, connector cleanliness, reference method, and vendor data.

Clean and inspect connector end faces before treating excess loss as a distance or optic problem.
Document whether end connections, patch cords, splitters, and passive modules are included in the design case.
Use the same wavelength, fiber type, and test reference method when comparing calculated loss with field measurements.

Advanced Tips:

Use minimum guaranteed Transmit power and the required Receiver sensitivity for design approval; typical optic values can make the margin look better than the deployed link.
Keep Dispersion or equipment penalty separate from Passive component loss when the vendor penalty is not a physical splitter, coupler, or patch module.
Use Test uncertainty allowance when comparing a calculated budget with field measurements from a source and power meter or optical loss test set.
Read Optical Loss Stack before changing optics; the largest dB block often points to the practical fix faster than the headline margin.
Use Reach Margin Curve only for distance tradeoffs. If connector count, splitter loss, splice plan, wavelength, or optic class changes, recalculate the whole budget.

Worked Examples:

Access span with comfortable reserve

The Single-mode 1310 nm access span preset models -3 dBm transmit power, -18 dBm receiver sensitivity, 8.00 km of fiber at 0.35 dB/km, four mated connections, and six splices. Power Margin Ledger reports 5.40 dB modeled link loss, -8.40 dBm estimated receive level, 9.60 dB operating margin, and 6.60 dB reserve surplus. The status is Reserve met, so the next check is whether the event counts and attenuation match the actual route.

Route clears sensitivity but misses reserve

Change the same access span to 35.00 km while leaving attenuation, connections, splices, and 3.00 dB required reserve unchanged. Modeled loss rises to 14.85 dB, estimated receive level falls to -17.85 dBm, and Operating margin above sensitivity is still positive at 0.15 dB. Reserve shortfall is -2.85 dB, so the result is Below reserve rather than acceptable for a design that needs a guard band.

Short path with overload risk

A high-power short route can fail in the opposite direction. With 3 dBm transmit power, 0.10 km at 0.22 dB/km, two 0.20 dB connections, and an entered -3 dBm receiver overload level, estimated receive level is about 2.58 dBm. Margin Action Ledger reports Too hot for Receiver overload and recommends at least 5.58 dB of added attenuation.

Distance looks unlimited after a zero attenuation entry

If Fiber attenuation is set to 0 dB/km while Fiber distance is nonzero, fiber length does not add loss. Max distance at reserve can read Unlimited by attenuation input and Distance headroom can read Not bounded. Enter the measured attenuation or a conservative design value before using reach as a planning result.

FAQ:

Should I use typical or worst-case optic values?

Use conservative values for design approval. Minimum guaranteed Transmit power and required Receiver sensitivity leave less room for surprise than typical lab values.

Why does reserve fail when operating margin is positive?

Operating margin above sensitivity only checks the receiver minimum. Reserve surplus subtracts Required reserve, so it can be negative even when the receiver is modeled above sensitivity.

What should I do when the largest loss contributor is passive loss?

Review splitters, WDM filters, couplers, and fixed attenuators before changing fiber distance. Loss Component Ledger shows passive loss separately so a splitter-heavy route is not mistaken for a cable-length problem.

Why does the overload check say an attenuator is needed?

The overload check runs only when Receiver overload level is entered. If estimated receive power is above that level, Recommended attenuator shows the minimum added attenuation needed to bring the model back to the receiver limit.

Does a passing budget replace field testing?

No. The budget estimates viability from entered assumptions. Acceptance should use the actual optic specifications and field measurements such as source/power-meter, optical loss test set, or OTDR results where appropriate.

Glossary:

dBm: Absolute optical power referenced to 1 milliwatt.
dB: A relative gain, loss, or margin value used for optical budget arithmetic.
Mated connection: The optical interface created when two connectors are joined through an adapter or port.
Insertion loss: The optical loss introduced by a cable plant, connection, splice, splitter, filter, or other passive path element.
Receiver sensitivity: The minimum receive power needed for the optic to meet its intended performance.
Receiver overload level: The maximum receive power allowed before the receiver may distort or saturate.

References:

Calculating Fiber Optic Loss Budgets, The Fiber Optic Association, 2004-2018.
Guidelines On What Loss To Expect When Testing Fiber Optic Cables, The Fiber Optic Association.
Cisco ONS 15454 Engineering Planning Guide, Optical Power Budget, Cisco.
Fiber Optics Loss Budget Calculation, Fluke Networks.