Bandwidth and Transfer Time Calculator

Estimate transfer time, calculate required bandwidth, size concurrent-user capacity and convert sustained rates into data volume.

BW

Traffic and link parameters

Choose a mode and edit efficiency, utilization and latency assumptions.

Rates use decimal SI units by default. File sizes can use decimal or IEC binary units.
jobs
%
%
ms
RTT

Core calculation

Payload rate = physical rate × payload efficiency × allowed utilization. Transfer time = file bits ÷ payload rate + setup delay.

Bits vs bytes. Link rates are in bits per second; file sizes are converted to bits (×8) before timing.

Efficiency. Payload efficiency covers protocol/headers so not every physical bit carries user data.

Utilization. Allowed utilization caps how hard the link may run in planning (headroom for bursts and peaks).

Setup delay. Setup round trips × RTT add connection/handshake time on top of pure transfer time.

NET

Bandwidth planning result

Payload performance after configured efficiency and utilization.

Estimated completion time—
—
Per-transfer payload rate
Aggregate payload rate
Serialization time
Setup delay
Total transferred data
Combined payload factor
Unavailable / overhead share
Concurrent jobs
Payload share of physical link
About & applicability

Free planning calculator for network and systems engineers. Runs entirely in the browser: estimate transfer time, required link rate, concurrent-user capacity and sustained data volume with explicit bit/byte units, efficiency and utilization assumptions. Application category: engineering utility / capacity planning. No account required.

Use for backup windows, WAN/Internet transfers, VPN tunnels and concurrent-user sizing. Results are planning aids — not a substitute for traffic measurements, QoS design or enterprise standards.

Type · Engineering calculator Runs · Client-side Locales · EN / 中文 / ES Canonical · /tools/bandwidth-calculator/
How it’s calculated · methods & formulas
serialization time = data_bits ÷ (link_rate × efficiency × utilization)
setup delay = RTT × setup_round_trips
transfer time = serialization time + setup delay
required rate = data_bits ÷ time ÷ efficiency ÷ utilization
max users ≈ available_payload_rate ÷ (per_user_rate × burst_factor)

Network rates use bits per second; file sizes use bytes (decimal SI or IEC binary). Efficiency is the payload fraction after protocol overhead; utilization caps how much of the physical link the workload may consume. Concurrent jobs are assumed to share available payload rate equally unless your scheduler differs.

Bits and bytes

Link speed is expressed in bits per second, while file size is normally expressed in bytes. One byte equals eight bits. Keep MB (megabytes) distinct from Mb (megabits).

Efficiency and utilization

Protocol efficiency represents the payload fraction. Utilization limits the share of physical link capacity allowed for the workload so the result stays inside an engineered headroom target.

Concurrent transfers

The transfer-time mode assumes concurrent jobs share the available payload rate equally. Real scheduling, congestion control and hashing can differ.

Latency and setup

Setup delay is modeled as RTT multiplied by setup round trips, then added to serialization time. Large transfers may also be limited by TCP window growth beyond this simple model.

Data volume

Sustained rate × duration converts into transferred volume after the same efficiency assumption, useful for backup-window and link-fill estimates.

Results do not fully model TCP windowing, loss recovery, QoS or shared-link contention. Compare planning numbers with measured goodput and use related capacity tools when you need growth or uplink oversubscription analysis.

FAQ

Frequently asked questions

Why does 100 Mbps not transfer 100 MB every second?

100 Mbps equals 12.5 MB/s before protocol and utilization losses.

Should file size use GB or GiB?

Use GB for decimal storage values and GiB when the source reports IEC binary units.

What efficiency should be used?

Use measured application throughput when available; otherwise start with a preset and retain margin.

Does RTT matter for large transfers?

The tool adds setup delay, while real TCP can also be limited by window growth and recovery.

How is maximum user count calculated?

Available payload bandwidth is divided by engineered per-user bitrate after the burst factor.

Can this replace a traffic-engineering model?

No. Queueing, QoS, retransmissions, traffic distribution and peak-hour behavior still need validation.

Recent calculations

PROJECT RECORDS

Official references · standards & units

Bit and byte units must stay explicit so transfer-time math does not confuse megabits with megabytes. Sustained application goodput is usually lower than the nominal port rate after protocol overhead, delay, loss and window limits. Presets are planning aids, not a substitute for measured path throughput.

Reviewed: 2026-11-05. Official sources:

Part of the switching and bandwidth calculators hub.

ENGINEERING WORKFLOW

Continue the engineering workflow

Current workflowEnterprise LAN & IP Planning Workflow

Plan addressing, VLAN capacity, packet size, uplinks, optics, access policy and DNS behavior as one LAN design sequence.

Step 5 of 12

Related tools

Also used inData Center Network Fabric Planning Workflow

Related pages

Bandwidth and transfer-time method