Human Readable Bytes Converter

How to use

1. 1Choose a direction: Bytes to human to format a byte count, or Human to bytes to parse a size string.
2. 2Pick the unit base: SI (1000) for kB, MB, GB as disk makers and most CLIs use, or IEC (1024) for KiB, MiB, GiB as RAM and du use.
3. 3Set the decimal places for the formatted output, then type a value or click a sample.
4. 4Read the result: the human readable size with the exact byte count, or the exact byte integer with the base that was applied.
5. 5Switch Mode to Batch to convert many lines at once, one value per line, then copy the whole output column.
6. 6Use the copy buttons to grab the formatted size or the plain byte count, and Clear to start over.

About this tool

Human Readable Bytes Converter does the two byte-size jobs that a plain unit converter skips. The first is formatting: you read a raw byte count out of a log line, an API response, a Content-Length header, ls -l, df, or an S3 object listing, and you want the single clearest way to say it. Paste 1536000 and the tool returns 1.5 MB in the decimal (SI) system or 1.46 MiB in the binary (IEC) system, choosing the largest unit where the value is at least 1 and rounding only the displayed number while keeping the exact byte count beside it. The second job is the reverse: you have a human size like 2.5 GiB or 1.5 MB and you need the exact integer to drop into a config value, a storage quota, an environment variable, or a request body. Type the size and the tool returns the precise byte count, computed with arbitrary-precision integers so a multi-gigabyte value is exact rather than a floating-point approximation. Both directions handle the kilobyte ambiguity head on. A kilobyte is 1000 bytes in SI and a kibibyte is 1024 bytes in IEC, and the gap is why a drive sold as 1 TB shows up in some tools as about 931 GiB. A unit base toggle switches every result between 1000 and 1024 per step, and on parsing, a suffix written explicitly as KiB, MiB, or GiB always means 1024, while a suffix written as kB, MB, or GB follows the toggle, which lets you model both the SI reading and the Windows or JEDEC reading where KB is treated as 1024. The parser is deliberately forgiving: it accepts 1.5MB, 1,5 GB with a decimal comma, 1024k, 2 gigabytes spelled out, grouped numbers with commas or underscores, and bare integers with no unit. Single mode shows the headline result plus a full table of the same value in every unit from bytes to exabytes. Batch mode runs the whole conversion on many lines at once, which is the real devops case: paste a column of byte counts pulled from a script or a list of sizes from a ticket and convert all of them in one shot, with any unreadable line flagged in place rather than silently dropped. Copy buttons return either the formatted size or the plain byte integer, ready to paste. One honest scope note: this works on byte counts and size units only; it is not a disk-usage or directory-scanning tool, and it does not read files. Everything is computed locally in your browser with plain arithmetic, so the numbers you paste are never uploaded, logged, or sent anywhere.

Free to use. Works in your browser. No signup, no login.