Byte Converter

The Byte Converter translates digital storage values between every common unit from bits up to petabytes. Every developer, sysadmin, and IT professional hits this conversion daily: a disk shows 931 GB but the box advertised 1 TB, a log file is 487,923,456 bytes and you want to know how many megabytes that is, an API returns content-length in bytes and you need to decide if the payload is too big for your queue. Doing the math by hand is tedious, error-prone, and worst of all ambiguous — because the storage industry uses base-1000 and the operating system uses base-1024.

This tool handles both conventions side by side. Enter a value in any unit and see the equivalent in every other unit using decimal (SI, base-1000: KB, MB, GB, TB, PB) and binary (IEC, base-1024: KiB, MiB, GiB, TiB, PiB) at once. This is the only way to diagnose the classic tell-me-why-my-disk-is-smaller problem: a 1 TB drive contains exactly 1,000,000,000,000 bytes by vendor math, but your OS reports it as 931 GiB because it divides by 1024 at each level. Both numbers are correct; they just use different unit conventions. The converter explains the conversion, shows the exact bytes involved, and gives you copy-paste-ready values in every unit.

Two parallel systems of units exist for digital storage, and almost every confusion comes from mixing them.

The SI (decimal, base-1000) system follows International System of Units rules: kilo means 1,000, mega means 1,000,000, giga means 1,000,000,000, and so on. Storage manufacturers, network equipment vendors, and most marketing materials use SI. A 1 TB hard drive contains approximately 1,000,000,000,000 bytes.

The IEC (binary, base-1024) system was formalized in 1999 to end the ambiguity that crept in when computer scientists overloaded the SI prefixes to mean powers of 1024 instead of 1000. IEC uses kibi (1024), mebi (1024^2), gibi (1024^3), and tebi (1024^4), abbreviated KiB, MiB, GiB, TiB. Operating systems like Linux and macOS report file sizes in IEC units (though Windows still says GB while meaning GiB, perpetuating the confusion). RAM is always specified in binary units because hardware physics makes powers of two natural (a 16 GB stick is actually 16 GiB).

Network bandwidth conventionally uses decimal (bits per second: 1 Mbps = 1,000,000 bps, not 1,048,576), which matches SI. File transfer speeds are often reported in binary megabytes per second (MiB/s), so a theoretical 1 Gbps link hits about 119 MiB/s sustained because of the mismatch.

Byte vs bit also trips people up. A byte is 8 bits. ISPs advertise 1 Gbps (one gigabit per second); divide by 8 to get 125 MB/s. The converter handles bit units explicitly so you can switch between Gbps and MB/s without mental arithmetic.

Compared to using Google as a calculator (typing 487923456 bytes in GB), this tool shows you every unit at once plus the decimal-vs-binary comparison, saving follow-up queries when you realize you needed GiB not GB. For one-off quick conversions Google works fine; for anything more than a single value, the side-by-side view wins.

Compared to Linux numfmt or dd bs= options, this browser tool is faster for interactive exploration. numfmt is the right choice inside a shell pipeline or script — it handles both SI and IEC prefixes via --from=iec or --from=si and integrates with other CLI tools perfectly.

Compared to stock calculator apps that handle only basic unit conversion, this tool is specifically designed for the binary/decimal distinction that matters in computing. Consumer converters often silently use one convention, which is exactly the behavior that caused the original confusion.