Mbps to MB per Second Converter

Convert megabits per second into megabytes per second, with overhead and file-time checks for downloads, uploads and local transfers.

Speed Conversion Inputs

MB/s Result

12.500 MB/s

Pure conversion before overhead.

Recent Checks

    Share this Mbps to MB/s conversion

    The Eight-To-One Rule

    Mbps means megabits per second. MB/s means megabytes per second. A byte contains 8 bits, so the clean conversion is Mbps divided by 8. A 100 Mbps connection is therefore 12.5 MB/s before overhead. That explains why a browser, game client, backup app or file-copy window may show a number that looks much lower than the broadband speed on the bill.

    This converter is useful when checking download estimates, upload windows, server transfer limits and local network copies. It also helps when someone quotes a speed without making the capital B clear. A capital B normally means bytes. A lower-case b normally means bits. The distinction is small in text but large in the result.

    Formula Method

    MB per second = Mbps / 8 effective MB per second = MB per second x (1 - overhead percent / 100) seconds for decimal GB file = file GB x 1000 / effective MB per second seconds for binary GiB file = file GiB x 1024 / effective MB per second

    The pure conversion is exact for decimal megabits and decimal megabytes. The file-time estimate is only a planning figure because a real transfer may pause, verify chunks, decompress, encrypt, retry or wait for storage. The overhead field lets you test a more cautious speed without changing the headline Mbps value.

    Where The MB/s Number Appears

    Download Windows

    Many download managers report MB/s. Compare that value with Mbps by multiplying by 8.

    Backup Software

    Backup clients may show MB/s after compression, encryption and server limits, not just the connection.

    Local Copies

    Wired local transfers can show MB/s, but disk speed, small files and drive cache affect the result.

    Mbps To MB/s Conversion Table

    MbpsMB per secondEveryday reading
    1 Mbps0.125 MB/sVery slow for large files.
    5 Mbps0.625 MB/sSmall downloads and low-rate uploads.
    10 Mbps1.250 MB/sUseful mental anchor.
    25 Mbps3.125 MB/sModest file movement.
    50 Mbps6.250 MB/sCommon broadband-style comparison.
    100 Mbps12.500 MB/sDefault example.
    150 Mbps18.750 MB/sFast enough for many large downloads.
    500 Mbps62.500 MB/sStorage speed starts to matter.
    1000 Mbps125.000 MB/sGigabit theoretical byte rate.
    2500 Mbps312.500 MB/sMulti-gigabit path, check disks and adapters.

    Related Speed And Size Checks

    CheckFormulaReason to use it
    MB/s to MbpsMB/s x 8Convert a file-window speed to a network label.
    Mbps to GB/hourMbps x 0.45Estimate hourly movement.
    Mbps to GB/dayMbps x 10.8Estimate always-on daily data.
    MB/s to MB/minMB/s x 60Match backup logs that use minute averages.
    GB file to secondsGB x 1000 / MB/sPlan a download or upload time.
    GiB file to secondsGiB x 1024 / MB/sMatch binary file sizes.
    Effective speedraw MB/s x practical percentageAllow for overhead and pauses.
    Minute amountMB/s x 60 / 1000Read a short transfer as decimal GB.
    Hour amountMB/s x 3600 / 1000Plan a one-hour batch.
    Required Mbpstarget MB/s x 8Find the line speed needed for a target file rate.

    Why Real Downloads Are Lower

    A speed-test result and a file download can differ for good reasons. The file server may be busy. Wi-Fi may share airtime with other devices. A VPN may reduce throughput. The receiving disk may slow down. Security software may inspect files. A browser may show an average after a slow start. The converter shows the unit relationship, then lets you lower the effective value with an overhead setting.

    For support conversations, keep both numbers. Say, for example, “100 Mbps is 12.5 MB/s before overhead, but this download is averaging 8 MB/s.” That phrasing makes it easier to separate a unit mix-up from a real performance issue. For important transfers, time a known file and use the measured average rather than the advertised connection speed.

    Reading Browser And App Speeds

    Different applications label speeds in different ways. A browser may show MB/s, a games launcher may show MB/s or Mbps, a router may show bits per second, and a cloud client may average the whole job. Before comparing two readings, check the letter case, the averaging period and whether the number is upload or download. If a download begins at 60 MB/s and settles at 20 MB/s, use the settled value for a time estimate. If the app pauses to unpack or verify files, that time is outside the pure transfer conversion.

    For large software downloads, write down the average speed after the first few minutes rather than the opening burst. For uploads, check that the service is not rate-limiting the account. A clean unit conversion can still leave a poor forecast if the chosen speed is a short peak, a cached burst or a server-side limit rather than the sustained transfer rate.

    FAQs

    How do I convert Mbps to MB/s?

    Divide Mbps by 8. For example, 100 Mbps divided by 8 is 12.5 MB/s. This works because one byte contains 8 bits.

    Why is my download not 100 MB/s on a 100 Mbps connection?

    Because Mbps and MB/s are different units. A 100 Mbps connection is 12.5 MB/s before overhead, not 100 MB/s. Real downloads may then be lower because of servers, Wi-Fi, storage and other traffic.

    What does the capital B mean?

    A capital B normally means bytes. A lower-case b normally means bits. MB/s is megabytes per second, while Mbps is megabits per second. The capital letter changes the result by a factor of 8.

    Should I use overhead for a pure conversion?

    No. Leave overhead at zero for the exact unit conversion. Add overhead only when estimating a practical transfer speed after likely losses.

    Can this estimate download time?

    Yes. Enter a file size and the calculator estimates time using the effective MB/s. The estimate can still differ from a real download if the server, route or storage speed changes.

    Is GB or GiB better for the file-size check?

    Use decimal GB for provider and storage-label values. Use binary GiB when the file size comes from software that clearly uses 1024-based units. The converter keeps the choice visible.

    Sources

    • Bureau International des Poids et Mesures. (2019). The International System of Units, 9th ed. BIPM. https://www.bipm.org/en/publications/si-brochure
    • National Institute of Standards and Technology. (2008). Guide for the Use of the International System of Units, Special Publication 811. NIST. https://www.nist.gov/pml/special-publication-811
    • International Electrotechnical Commission. (n.d.). Prefixes for binary multiples. IEC. https://www.iec.ch/
    Scroll to Top