Data transfer rate converter
100 Mbps is 12.5 MB/s: convert bandwidth between bits, kilobits, megabits and gigabits per second and bytes or megabytes per second, so an ISP plan, speed test or CDN dashboard is read without the eightfold bit-byte mix-up. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Value
- 100
- Source unit
- Mbps
- Target unit
- MB/s
- Result
- 12.5
- To
- MBps
- From label
- megabits per second
- To label
- megabytes per second
A data transfer rate converter turns a bandwidth or throughput figure written in one unit into another without hunting prefix tables or mixing up bits and bytes.
Supported units and how the conversion is computed
The converter accepts six data-rate families under stable canonical codes: bps for bits per second, kbps for kilobits per second, Mbps for megabits per second, Gbps for gigabits per second, Bps for bytes per second, and MBps for megabytes per second. Bit versus byte spelling matters: Mbps (lowercase b) is megabits, while MBps or MB/s (uppercase B) is megabytes—confusing them is the classic eightfold error on ISP plans and file-transfer UIs.
Factors follow the SI decimal telecom convention used in networking: one kilobit per second is one thousand bits per second, one megabit per second is one million bits per second, one gigabit per second is one billion bits per second, one byte per second is eight bits per second, and one megabyte per second is eight million bits per second.
Because the intermediate is always bits per second, converting A to B and B to A is consistent up to the published rounding of twelve decimal places, and there is no pairwise matrix that can drift out of sync. Binary kibibit or mebibyte-per-second prefixes are intentionally out of scope so ISP, CDN, and lab users get predictable results under one clear SI rate convention.
Where data rates need converting
Use the free in-browser data transfer rate converter when you need a quick megabits-to-megabytes, gigabits-to-bits, or kilobits-to-bytes-per-second check while reading an ISP plan, a CDN dashboard, a network datasheet, a speed-test report, or a homework problem. Open the page, enter the number and units, and copy the result without installing a spreadsheet, a unit library, or a desktop calculator pack. Source inputs follow the same retention rules as other KIT parse items, and results are safe to cache because the algorithm is fully deterministic.
Authors shipping mobile apps or chatbots can map the result and formula fields directly into cards that show both the number and the conversion path engineers, support teams, and students expect on paper.
What you can do with it
ISP plans and speed-test reports
Convert advertised Mbps (megabits) to MB/s (megabytes) so customers and support agents compare download expectations without the classic factor-of-eight mistake.
CDN and capacity planning
Normalize Gbps, Mbps, and bytes-per-second figures across dashboards, SLAs, and billing exports when vendors mix bit-based and byte-based labels.
FAQ
Which data-rate units does this converter support?
Bits per second (bps), kilobits per second (kbps), megabits per second (Mbps), gigabits per second (Gbps), bytes per second (Bps or B/s), and megabytes per second (MBps or MB/s).
What is the difference between Mbps and MBps?
Mbps is megabits per second; MBps (or MB/s) is megabytes per second. One byte is eight bits, so 8 Mbps equals 1 MB/s under SI decimal prefixes. Mixing them is the usual factor-of-eight error on consumer plans.
How do I convert 100 Mbps to megabytes per second?
The response result field is 12.5, plus a bps intermediate and a readable formula.
What happens if I send an unknown unit?
The message names the field and lists supported units. Validation failures are not charged.
Is the data transfer rate converter free?
The browser tool runs free on your device.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/conv/data-rate \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"value":100,"from":"Mbps","to":"MBps"}'const res = await fetch("https://api.kit.forhosting.com/conv/data-rate", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"value": 100,
"from": "Mbps",
"to": "MBps"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/data-rate",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"value": 100,
"from": "Mbps",
"to": "MBps"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/data-rate", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"value":100,"from":"Mbps","to":"MBps"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"value":100,"from":"Mbps","to":"MBps"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/data-rate", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"value": 100,
"from": "Mbps",
"to": "MBps"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.data_rate",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
The browser tool runs free on your device; the prepaid API charges $0.002 per successful item when pipelines need the same contract from servers and automation.
Supported units and how the conversion is computed
Friendly aliases such as bits per second, kilobits, megabits, gigabits, B/s, MB/s, byte per second, and megabytes per second are normalized so forms and APIs can pass either short codes or full names. Every request multiplies the input value by the exact bits-per-second factor for the source, then divides by the bits-per-second factor for the target.
Request shape, response fields, and unknown-unit errors
The error message names the bad field and lists the supported set so clients can correct forms without guessing. Negative values are allowed when you need signed rate deltas in engineering pipelines; zero converts cleanly to zero in every target unit. Send a JSON body with three required fields: value as a finite number, from as the source unit string, and to as the target unit string. Aliases amount, quantity, and rate are accepted for value; unit_from and source for from; unit_to and target for to. On success the response echoes the canonical from and to codes, human-readable from_label and to_label strings, the converted result, the intermediate bps quantity, the dimensionless factor from source to target, a short formula line suitable for UI display, the method tag data_rate_si_bps, and the fixed list of units_supported. Missing value, non-finite numbers such as NaN or Infinity, missing unit fields, and any token that does not map to a supported unit fail with invalid_input and are not charged after the engine rejects the request. Identical inputs always yield identical JSON because the path is pure arithmetic with no randomness, no remote lookup, and no dependence on the wall clock, which makes the endpoint safe to pin in continuous-integration goldens and SDK contract tests. Gigabit-scale results and bytes-per-second results share the same code path, so extreme magnitude pairs remain well-defined as long as IEEE double precision can represent the intermediate bits-per-second product.
Browser use, API pricing, and everyday workflows
Switch to the prepaid API when a bandwidth-billing app, monitoring agent, storage-sync planner, video-stream capacity tool, or network homework checker must convert rates at scale under a stable KIT contract at $0.002 per successful item; validation failures that raise invalid_input do not consume balance after rejection. Pair this endpoint with general unit converters when a product pipeline needs several measure families, or call it alone when search traffic is specifically for data-rate conversion—bits, kilobits, megabits, gigabits, bytes per second, and megabytes per second—rather than a general unit switchboard.
Integration use cases
Network homework and lab pipelines
Turn kilobits, bits, and megabytes per second into a single prepaid API contract with clear invalid_input on unknown units for checkers and notebooks.