Convert storage numbers from bytes through petabytes with explicit binary (1024) or decimal (1000) bases — live grid, swap, and copy. Computation stays in your browser, matching the local-first trust model of APK Analyzer and APK String Extractor: nothing you type is uploaded. For typical APK / asset ranges you can also use Android File Size Converter (B–TB).
—
Engineers, Android developers, and content authors constantly translate between B, KB, MB, GB, TB, and PB when comparing CI artifacts, object-storage quotes, download estimates, and UI copy. This page does pure arithmetic in JavaScript — no server round-trip for your numbers — similar to how APK Analyzer inspects packages without uploading them.
One kibibyte is 1024 bytes; many UIs still label that as “KB”. Storage vendors often use 1 KB = 1000 B, 1 MB = 1000 KB, and so on. The mismatch is why a “1 TB” disk can look like ~0.91 TiB in an OS that uses 1024-based powers. Toggle the base here to match the document you are reconciling.
The grid includes PB for data-center and backup rough checks. JavaScript represents numbers as IEEE doubles; for everyday files and APKs you are safe. If you need integer-exact bookkeeping at extreme scale, use big-integers or your billing system’s API rather than any browser float utility.
No. Every conversion runs in your browser with JavaScript. Your numbers are not sent to DroidXP servers — the same local-first approach as APK Analyzer and APK String Extractor.
Use 1024 for most OS, memory, and many engineering workflows. Use 1000 when aligning with SI-style storage marketing, some cloud SKUs, or network-style kilo = 1000.
When the base is 1024, KB/MB/GB behave like KiB/MiB/GiB in practice (powers of 1024). Labels stay KB/MB for familiarity; the important part is which base you selected.
Manufacturers often advertise decimal terabytes (1012 bytes) while Explorer and macOS often display tebibyte-style counts (powers of 1024) — the same raw bytes can read as different “TB”.
JavaScript uses double-precision floats; results stay accurate for typical file and APK sizes. Extremely large petabyte-scale values may lose the last integer digits of precision — fine for estimates, not for cryptographic byte accounting.
Yes. The grid lists B through PB so you can sanity-check backups, clusters, or marketing sheet figures.
Providers may bill on binary vs decimal units, compress objects, round differently, or exclude metadata. Treat this tool as a quick converter, not as your vendor’s pricing engine.
Yes — convert MB to bytes for thresholds, or compare with the Android File Size Converter. Both stay local in the browser.
It sets decimal places on converted numbers; trailing zeros are trimmed for readability.
This page adds PB, richer explanatory copy, and TSV export aimed at general storage — the Android tool focuses on B–TB for typical app and asset planning.