Skip to calculator

Waypoint Utility Web

Video Delay Calculator

Broadcast engineering · Compare the one-way delay across two video contribution paths.

VERSION 0.9STATUS: BETA

Results · Path comparison

Path comparison

Difference in delay

Inputs · Transport, codec & endpoints

Checking address lookup… Distance and coordinate calculations run in your browser.

Calculation method

Total one-way delay = encode + transport + decode + display. Results update as inputs change. Seconds = milliseconds ÷ 1,000. Equivalent frames = milliseconds × 60 ÷ 1,000.

Fiber and microwave calculate propagation from geographic distance; other transports use editable planning presets. Diagrams are schematic. Open Sources & Assumptions below for equations, defaults, references and limitations.

Sources & Assumptions Equations, planning values, and limits

What the total includes

Total = encode + transport + decode + display. All values are one-way milliseconds. Seconds = ms ÷ 1,000. Frames = ms × 60 ÷ 1,000; fractional frames are equivalent delay at a fixed 60 fps.

Capture, production switching, audio alignment, packetization, retransmission, jitter buffers, network processing and queuing are not separate stages in this calculator. Include applicable delay in your measured stage values. Avoid counting the same buffer twice.

Generic codec planning defaults

Editable estimates; these are not equipment specifications.
CodecEncodeDecode
HEVC / H.265150 ms10 ms
AVC / H.264100 ms10 ms
JPEG XS8 ms8 ms

Display starts at 15 ms and is editable under Advanced. Actual delays depend on hardware, configuration, GOP, resolution, frame rate and operating mode. AWS explains the codec latency tradeoffs; the exact presets here are the packaged planning values.

Fiber and microwave

Fiber route = geographic distance × route factor. The default route factor is 1.25, editable under Advanced. Fiber delay = route km ÷ (0.65 × 299,792.458 km/s) × 1,000.

Microwave delay = geographic km ÷ (0.99 × 299,792.458 km/s) × 1,000. No fiber route factor is applied. The 65% and 99% propagation speeds are the agreed approximations. They are not universal medium specifications.

The NIST speed of light is 299,792,458 m/s. 1 mile = 1.609344 km. Coordinates use a spherical great-circle calculation with mean Earth radius 6,371.0088 km. This is geographic separation, not a surveyed cable route or a radio link survey.

Microwave calculations do not verify line of sight, terrain, Earth curvature, Fresnel clearance, weather, equipment delay or required relay hops. A long geographic path is a propagation estimate only.

Satellite and Internet

GEO: 300 ms. LEO / Starlink: 60 ms. These are editable one-way planning assumptions. GEO includes an Earth–satellite–Earth traversal. It is not a round trip back to the source. NASA places GEO altitude at approximately 35,786 km; a minimum vertical up-and-down traversal takes about 239 ms before other delay.

Starlink published latency is round-trip. Our 60 ms one-way preset is an independent planning assumption, not a conversion of that figure.

Internet: Local / Metro 15 ms; Regional 30 ms; Long Distance 60 ms. These are agreed planning tiers, not measured guarantees or distance-based models. Replace them with observed one-way delay where available. RFC 7679 explains one-way measurement and path asymmetry; half of ping round-trip time is only an approximation.

Locations, privacy, and value sources

Endpoints are linked by default; unlink to give Path B its own endpoints. Typed distances are used directly. Address lookup occurs only when you select Look up and sends that query to the configured Cloudflare Worker and Geoapify. Coordinates and CSV export require no external service. The app does not save your settings or put them in a share URL.

Check the returned address before selecting a result. Geocoding precision varies, and a city result is not a building location. Powered by Geoapify · © OpenStreetMap contributors.

Default identifies an agreed planning estimate. Calculated identifies a value derived from distance. User entered identifies an override. The difference is absolute and does not rank the paths. Exported numeric results keep more precision than the display.

Diagrams are schematic and not to scale. This is a planning tool; validate against actual equipment and network measurements.