Mbps converter
A 100 Mbps plan equals 12.5 MB/s, the unit your download bar shows. Enter one speed in megabits per second and see megabytes, kilobits and bits per second side by side, so a factor-of-eight slip never under-sizes a backup window. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Mbps
- 100
- Megabytes per second
- 12.5
- Kilobits
- 100,000
- Bits per second
- 100,000,000
A megabits-per-second converter turns an ISP plan speed, Ethernet throughput, or lab measurement quoted in Mbps into the three related figures people actually compare: megabytes per second for file-transfer time, kilobits per second for older telecom and SLA worksheets, and bits per second for the SI base unit. Enter a non-negative finite rate in megabits per second. The solver divides by eight to obtain megabytes per second, because one byte is eight bits, multiplies by one thousand for kilobits per second, and multiplies by one million for bits per second.
Why megabits per second is not megabytes per second
Megabits per second is the unit ISPs print on plan cards, the unit speed-test apps advertise, and the unit Ethernet marketing still uses for everything from Fast Ethernet at one hundred megabits per second to mixed dashboards that later convert ten-gigabit uplinks down into megabit figures. Megabytes per second is the unit people actually feel when a download progress bar moves, because operating systems, browsers, and storage tools report file size in bytes, not bits.
Kilobits remain common on older telecom worksheets, voice-circuit SLAs, and lab instruments that never moved off kilo prefixes. Confusing Mbps with MB/s by a factor of eight is the classic planning error that under-sizes a backup window or over-promises a transfer time. This converter hard-codes the SI decimal bit-rate definitions and the eight-bit byte; it never applies mebibyte or gibibit factors.
Zero megabits per second maps to zero in every output field.
Practical checks, SI versus binary, and related searches
Round-trip sanity checks are easy: convert eight megabits per second and confirm you receive exactly one megabyte per second, one thousand times eight kilobits per second, and eight million bits per second; convert one hundred megabits per second and confirm twelve point five megabytes per second; convert one megabit per second and confirm zero point one two five megabytes per second, one thousand kilobits per second, and one million bits per second. Stay inside the absolute range so the multiplications cannot overflow into a non-finite result the solver must reject.
This landing targets people searching for an Mbps converter, megabits per second to megabytes per second, Mbps to kbps, or Mbps to bits per second; it is not a general multi-unit data-rate hub, not a Gbps-to-Mbps primary form, and not a binary mebibit converter. Prefer this capability when the input is already in megabits per second and you need MB/s, kilobits, and bits per second in one call. Overhead, packet headers, and duplex versus simplex are out of scope—this tool converts advertised bit rates, not measured goodput.
What you can do with it
ISP plans and download-time estimates
Turn a plan quoted in Mbps into megabytes per second so you can estimate how long a backup, ISO, or video file will take, plus kbps and bps for mixed worksheets.
Network design and SLA dashboards
Engineers convert policer and link rates in Mbps into bits per second and kilobits per second for devices and tickets that still mix kilo and mega prefixes.
FAQ
How do I convert Mbps to megabytes per second?
Divide megabits per second by eight: MB/s = Mbps / 8, because one byte is eight bits. One hundred Mbps is twelve point five MB/s under SI decimal prefixes.
How many kilobits and bits per second is one Mbps?
One megabit per second is exactly one thousand kilobits per second and one million bits per second. The converter applies those SI decimal factors with no binary shortcuts.
Why is a negative Mbps rejected?
A data rate cannot be negative. Failed tasks are not charged.
Does this use mebibytes (MiB/s) instead of megabytes?
Binary mebibit and mebibyte prefixes are out of scope.
Is the Mbps converter free?
The browser tool is free and runs locally.
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/mbps-converter \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"mbps":100}'const res = await fetch("https://api.kit.forhosting.com/conv/mbps-converter", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"mbps": 100
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/conv/mbps-converter",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"mbps": 100
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/conv/mbps-converter", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"mbps":100}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"mbps":100}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/conv/mbps-converter", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"mbps": 100
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "conv.mbps_converter",
"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
Negative rates fail with invalid_input instead of inventing a signed delta.
Why megabits per second is not megabytes per second
The factor between them is exact and small: eight bits make one byte, so a link advertised as one hundred megabits per second delivers twelve point five megabytes per second of payload if you ignore protocol overhead. Bits per second is the SI coherent rate: one megabit per second is exactly one million bits per second under the decimal prefixes used for network bit rates, not a binary mebibit. Negative rates are rejected as invalid_input because a physical or commercial data rate cannot be negative.
How to call the API and what comes back
String numbers are accepted only when they match a strict finite numeric pattern without units, thousand separators, or currency symbols. Send a JSON body with one required finite number field named mbps. Aliases megabits_per_second, mbit_s, value, rate, and speed are accepted so SDK clients and form posts can use the name that fits the product. Failed validation—missing fields, non-finite numbers, bare plus or minus signs, non-numeric strings, negative rates, or values outside absolute limits—returns invalid_input and is never charged. Pricing is a flat $0.002 per successful request with unit item. Prefer sending a JSON number when you control the client.
Practical checks, SI versus binary, and related searches
Failed tasks that return invalid_input do not consume prepaid balance, which keeps exploratory scripts cheap when learners deliberately omit mbps or pass a negative number.
Integration use cases
Homework and unit-test fixtures
Students and developers convert classroom Mbps readings to MB/s, kbps, and bps and pin golden JSON so browser and API arithmetic never drift.