Data Transfer Rate Converter

Transfer rate:

Keep the unit attached to the number; Mbps and MB/s differ by a factor of eight.

Rate basis:

Use line rate for link or port specifications; use payload throughput for measured useful traffic.

Convert to:

Choose the notation needed by the next command, report, or capacity plan.

Overhead assumption:

Choose a common planning profile or Custom to enter a measured reserve.

Protocol overhead:

Zero is neutral. Editing this field changes the profile to Custom unless it exactly matches a preset.

Reference payload:

Changing the unit preserves the same byte quantity.

Delivery window:

Use the actual copy, maintenance, backup, or migration window.

Capacity labels:

Use SI for decimal vendor/network labels or IEC for binary storage labels.

Active hours per day:

Use 24 for continuous delivery or the permitted daily maintenance window.

hours/day

Planning month:

Choose 1 to 31 days to match the planning calendar.

days

Unit	Line rate	Payload rate	Copy
{{ row.label }}	{{ row.line }}	{{ row.payload }}

Measure	Value	Planning meaning	Copy
{{ row.label }}	{{ row.value }}	{{ row.note }}

Decision	Current reading	Next check	Copy
{{ row.label }}	{{ row.reading }}	{{ row.action }}

A transfer rate describes how much data crosses a boundary in a unit of time. Network links are commonly labeled in bits per second, while file-copy tools often report bytes per second. Because one byte contains eight bits, 100 MB/s and 100 Mbps describe rates that differ by a factor of eight.

Prefixes create a second source of disagreement. SI units scale by 1000, so 1 Gbps is 1,000,000,000 bits per second. Binary prefixes scale by 1024, so 1 Gibps is 1,073,741,824 bits per second. Capitalization also matters: Mb means megabits and MB means megabytes.

Transfer-rate terms used for capacity planning
Quantity	What it describes	Typical use
Line rate	Total bit rate on a link or interface	Port and circuit specifications
Payload throughput	Useful data rate after an overhead reserve	Measured copies, backups, and downloads
Transfer time	Payload size divided by useful throughput	Maintenance-window and migration planning
Capacity tier	First common Ethernet tier at or above a modeled line rate	Early link-sizing comparisons

Advertised link speed is not a promise of application throughput. Protocol headers, encryption, retransmissions, congestion, storage speed, CPU limits, latency, and parallelism can all reduce the useful rate. An overhead percentage is therefore a planning assumption that should be replaced with a measured reserve when reliable observations exist.

A delivery window changes conversion into a capacity question. The required rate must be high enough to move the full payload before the window closes, and repeated jobs also need enough active hours and days to support the expected daily or monthly volume.

How to Use This Tool:

Keep the unit and rate basis attached to the measurement, then model the payload and time window that matter.

Enter the Transfer rate and choose its unit. Confirm whether the number is a Line rate or Payload throughput.
Choose the output unit and an Overhead assumption. Select Custom when a measured protocol reserve is available; the accepted range is 0% to 40%.
Enter a positive Reference payload with an explicit decimal or IEC size unit.
Set the positive Delivery window. Adjust active hours per day and month days only when daily or monthly capacity is part of the plan.
Read Window plan for the estimated completion time, required rate, pass or miss result, and first common link tier.

Interpreting Results:

Payload ETA is the main completion estimate because it uses the useful-data rate. A nonnegative window slack means the modeled payload finishes on time; negative slack is the estimated overrun.

Required line rate includes the selected overhead reserve. Compare it with a link tier, not with payload throughput from an application graph.
First fit tier is the smallest built-in Ethernet tier at or above the current line rate. The buffered tier applies 20% headroom.
Window met is only as reliable as the payload size, rate basis, and overhead assumption. Verify those three values before scheduling work.

Technical Details:

Every rate is normalized to bits per second. Bit-rate units multiply by their decimal or binary prefix factor; byte-rate units multiply by the same prefix factor and by eight. Payload sizes are normalized to bytes and time windows to seconds before the transfer equations are applied.

Formula Core:

Let R be the entered rate in bits per second, o the overhead percentage, e the payload-efficiency ratio, B the payload bytes, and t the window seconds.

\begin{array}{lcl} e & = & 1 - \frac{o}{100} \\ R_{payload} & = & R_{line} \times e \\ T_{payload} & = & \frac{8 B}{R_{payload}} \\ R_{required line} & = & \frac{8 B}{t e} \end{array}

When the entered rate is a line rate, it is multiplied by e to get payload throughput. When the entered rate is payload throughput, it is divided by e to recover the modeled line rate. A window passes when t − T_payload is greater than or equal to zero.

Capacity per active day equals payload bits per second divided by eight, multiplied by active hours and 3600 seconds. Monthly capacity multiplies that daily value by the selected 1 to 31 days. These figures assume the modeled payload rate can be sustained throughout every active hour.

Unit and Rule Core:

Transfer-rate unit and planning rules
Rule	Exact treatment
SI prefixes	kilo through tera use powers of 1000.
IEC prefixes	kibi through tebi use powers of 1024.
Bits and bytes	1 byte equals 8 bits.
Overhead	Accepted from 0% through 40%, inclusive.
Tier fit	The first tier whose rated bits per second is greater than or equal to the modeled line rate.
Buffered tier	Tier fit after multiplying the modeled line rate by 1.2.

Common overhead presets are 0% for raw storage or application throughput, 3% for Ethernet TCP payload, 6% for encrypted file copy, and 12% for a VPN or tunneled WAN. They are planning defaults rather than measurements of a particular transfer.

Accuracy Notes:

The result is deterministic for the entered values, but real throughput can vary during a transfer. Use an observed sustained payload rate and a conservative overhead reserve for maintenance or migration decisions. The calculation runs in the browser and does not measure the network.

Worked Examples:

100 GB over a 1 Gbps link

A 1 Gbps line rate with 3% overhead provides 970 Mbps of modeled payload throughput. A decimal 100 GB payload contains 800 gigabits, so its payload ETA is about 825 seconds, or 13 minutes 45 seconds. A 15-minute window passes with about 75 seconds of modeled slack.

References:

Metric (SI) Prefixes, National Institute of Standards and Technology.
Prefixes for Binary Multiples, National Institute of Standards and Technology.
How to limit bandwidth in cURL, Simplified Guide.