Data Storage Unit Converter (TB vs TiB, GB vs GiB, Decimal vs Binary)

Convert accurately between manufacturer decimal SI units (KB, MB, GB, TB, PB) and operating system binary IEC 80000-13 units (KiB, MiB, GiB, TiB, PiB).

Input Parameters

Try Example:

Calculation Results

Input Value Summary: 4 TB (Standar Desimal SI 10^n)
Exact Capacity in Bytes: 4,000,000,000,000 Bytes
Formatted Total Bytes: 4,000,000,000,000 B
Decimal Kilobytes (SI 10³): 4,000,000,000 KB
Decimal Megabytes (SI 10⁶): 4,000,000 MB
Decimal Gigabytes (SI 10⁹): 4,000 GB
Decimal Terabytes (SI 10¹²): 4 TB
Decimal Petabytes (SI 10¹⁵): 0.004 PB
Binary Kibibytes (IEC 2¹⁰): 3,906,250,000 KiB
Binary Mebibytes (IEC 2²⁰): 3,814,697.27 MiB
Binary Gibibytes (IEC 2³⁰): 3,725.29 GiB
Binary Tebibytes (IEC 2⁴⁰): 3.64 TiB
Binary Pebibytes (IEC 2⁵⁰): 0.0036 PiB
Manufacturer Label vs OS Display Comparison: 4 TB Desimal = ~3.64 TiB Biner (Tampilan OS)
Representation Discrepancy (SI vs IEC): 9.05%
Drive Capacity Technical Analysis (EN): A "4 TB" drive contains exactly 4,000,000,000,000 raw bytes. Storage drive manufacturers utilize decimal SI standards (1 TB = 10^12 bytes = 1,000,000,000,000 bytes). Conversely, operating systems like Windows compute storage in binary powers of 2 (1 TiB = 1024^4 = 1,099,511,627,776 bytes) while continuing to label it as "TB", reporting the drive as ~3.64 TiB. The resulting 9.05% difference stems entirely from mathematical definitions, not defective hardware or reserved hidden blocks.

Want to compare 2 design options side-by-side (e.g., Scenario A vs Scenario B)?

⚡ Enterprise Network Infrastructure Standard

Managed L2+/L3 Gigabit Switch (802.1Q VLAN & RSTP) + Cat6/FO Uplink

RFC 1918 / RFC 4632 Compliant Addressing

Isolate management, server, user, and IoT/CCTV traffic into dedicated 802.1Q VLANs.

Manufacturer Drive Capacity vs Operating System Usable

Drive Label (SI)	Raw Bytes	OS Usable (IEC)	Nominal Divergence
500 GB	500,000,000,000 B	465.66 GiB	6.87%
1 TB	1,000,000,000,000 B	0.91 TiB	9.05%
2 TB	2,000,000,000,000 B	1.82 TiB	9.05%
4 TB	4,000,000,000,000 B	3.64 TiB	9.05%
8 TB	8,000,000,000,000 B	7.28 TiB	9.05%
12 TB	12,000,000,000,000 B	10.91 TiB	9.05%
16 TB	16,000,000,000,000 B	14.55 TiB	9.05%
20 TB	20,000,000,000,000 B	18.19 TiB	9.05%

Share to WhatsApp

How to Use This Tool

Enter the numeric storage capacity value you wish to convert into the primary input field.
Select the source storage unit from either decimal SI manufacturer units (B, KB, MB, GB, TB, PB) or binary IEC operating system units (KiB, MiB, GiB, TiB, PiB).
Inspect the exact conversions across all SI and IEC tiers, the percentage divergence between representations, and the reference table of commercial drive capacities.

Worked Example: Standard 4 TB Drive (Displays ~3.64 TiB on Windows)

Worked example: A 4 TB (Decimal SI) capacity equals exactly 4,000,000,000,000 Bytes (4,000 GB), which converts to 3.64 TiB (3,725.29 GiB) in binary IEC units—a 9.05% display difference.

Example Input

Storage Capacity Magnitude: 4
Initial Capacity Unit: TB (Terabyte — 10^12 Decimal SI)

Calculated Output

Input Value Summary: 4 TB (Standar Desimal SI 10^n)
Exact Capacity in Bytes: 4,000,000,000,000 Bytes
Formatted Total Bytes: 4,000,000,000,000 B
Decimal Kilobytes (SI 10³): 4,000,000,000 KB
Decimal Megabytes (SI 10⁶): 4,000,000 MB
Decimal Gigabytes (SI 10⁹): 4,000 GB
Decimal Terabytes (SI 10¹²): 4 TB
Decimal Petabytes (SI 10¹⁵): 0.004 PB
Binary Kibibytes (IEC 2¹⁰): 3,906,250,000 KiB
Binary Mebibytes (IEC 2²⁰): 3,814,697.27 MiB
Binary Gibibytes (IEC 2³⁰): 3,725.29 GiB
Binary Tebibytes (IEC 2⁴⁰): 3.64 TiB
Binary Pebibytes (IEC 2⁵⁰): 0.0036 PiB
Manufacturer Label vs OS Display Comparison: 4 TB Desimal = ~3.64 TiB Biner (Tampilan OS)
Representation Discrepancy (SI vs IEC): 9.05%
Drive Capacity Technical Analysis (EN): A "4 TB" drive contains exactly 4,000,000,000,000 raw bytes. Storage drive manufacturers utilize decimal SI standards (1 TB = 10^12 bytes = 1,000,000,000,000 bytes). Conversely, operating systems like Windows compute storage in binary powers of 2 (1 TiB = 1024^4 = 1,099,511,627,776 bytes) while continuing to label it as "TB", reporting the drive as ~3.64 TiB. The resulting 9.05% difference stems entirely from mathematical definitions, not defective hardware or reserved hidden blocks.

Core Concept & Engineering Notes

The discrepancy between the storage capacity printed on a hard drive or NVMe SSD retail box and the usable volume reported by an operating system is one of the most frequent sources of confusion in storage engineering. This divergence stems from two distinct measurement conventions: the International System of Units (SI) based on decimal powers of 10, and the International Electrotechnical Commission (IEC 80000-13) standard based on binary powers of 2. Storage hardware manufacturers define kilobyte (KB), megabyte (MB), gigabyte (GB), terabyte (TB), and petabyte (PB) using decimal multiples of 1,000 (10^3). Under the SI decimal standard, 1 Gigabyte equals exactly 1,000,000,000 bytes (10^9 bytes), and 1 Terabyte equals 1,000,000,000,000 bytes (10^12 bytes). Conversely, operating system memory allocators, RAID controllers, and filesystems such as ZFS, ext4, and Windows NTFS address data blocks in binary multiples of 1,024 (2^10). To resolve this ambiguity, the IEC standardized explicit binary prefixes containing the 'bi' syllable: kibibyte (KiB = 1,024 bytes), mebibyte (MiB = 1,024^2 bytes), gibibyte (GiB = 1,024^3 bytes), tebibyte (TiB = 1,024^4 bytes), and pebibyte (PiB = 1,024^5 bytes). When a 4 TB decimal drive (4 × 10^12 bytes) is divided by 1,024^4 (1,099,511,627,776 bytes per TiB), the operating system reports 3.638 TiB—a 9.05% mathematical representation difference with zero missing physical bytes. In enterprise storage architecture, this compound gap widens with every order of magnitude: 4.86% at the MB/MiB tier, 7.37% at the GB/GiB tier, 9.95% at the TB/TiB tier (a 9.05% reduction when converting TB to TiB), and 12.59% at the PB/PiB tier. Confusing SI decimal capacity with IEC binary allocation when sizing Proxmox ZFS vdevs, Ceph OSD clusters, or NVR surveillance retention pools frequently causes unexpected capacity shortfalls of hundreds of gigabytes in production environments, especially before accounting for filesystem metadata, ZFS slop space reservations, and RAID parity overhead across multi-disk storage pools.

How It Was Calculated (Formulas & Steps)

Mathematical Formulas

SI Decimal Standards (Powers of 10^3): 1 KB = 10^3 B, 1 MB = 10^6 B, 1 GB = 10^9 B, 1 TB = 10^12 B (1,000,000,000,000 Bytes)
IEC Binary Standards (Powers of 2^10): 1 KiB = 2^10 B (1,024), 1 MiB = 2^20 B (1,048,576), 1 GiB = 2^30 B, 1 TiB = 2^40 B (1,099,511,627,776 Bytes)
Hard Drive Discrepancy Formula: TiB = (Raw Decimal Bytes) / (1024^4). Example: 4,000,000,000,000 / 1,099,511,627,776 = 3.63798 TiB (~9.05% difference)

Step-by-Step Calculation

Kapasitas Input = 4 TB (Desimal SI 1000^n) = 4,000,000,000,000 Byte.
Konversi Desimal SI: 4,000 GB = 4 TB.
Konversi Biner IEC 80000-13: 3,725.29 GiB = 3.638 TiB (Selisih representasi: 9.05%).

Frequently Asked Questions (FAQ)

Why does Windows File Explorer display a 1 TB drive as 931 GB?

Windows calculates disk volume using binary Gibibytes (1,000,000,000,000 ÷ 1024^3 = 931.32 GiB), but labels the value as 'GB' instead of the IEC 'GiB' symbol.

Does the percentage gap between decimal and binary units grow larger at the Petabyte (PB) scale?

Yes. Each tier compounds by a factor of 1000/1024: KB vs KiB differs by 2.34%, MB vs MiB by 4.63%, GB vs GiB by 6.87%, TB vs TiB by 9.05%, and PB vs PiB reaches 11.18%.

Which unit system do Linux commands 'df -h' and 'lsblk' use?

In GNU coreutils, 'df -h' divides by powers of 1024 (binary IEC units), whereas 'df -H' (or '--si') divides by powers of 1000 (decimal SI units).

How do storage byte units compare to network bandwidth units (Mbps)?

Networking standards always measure transmission rates in decimal bits per second (1 Mbps = 1,000,000 bits/s = 125,000 Bytes/s), whereas storage measures Bytes (1 Byte = 8 bits).

View All General Tools →

Network Data Transfer, Backup Window & Sync Time Calculator

Calculate file transfer duration, offsite backup windows, and effective throughput (Mbps, MB/s, MiB/s) accounting for TCP/IP protocol overhead.

SLA Uptime, Allowed Downtime & SRE Error Budget Calculator

Calculate maximum allowed daily, monthly, and yearly downtime from SLA targets (99.9%–99.999%) or audit achieved SLA from observed incident duration.

Proxmox ZFS & Hardware RAID Capacity Calculator

Calculate net usable Proxmox VE ZFS capacity, padding loss, slop space, 80% safe ceiling, ARC RAM, and zpool create CLI script.

IT Equipment Power Consumption (Watt, kWh), PUE & Electricity Cost Calculator

Calculate daily, monthly, and annual kWh energy usage, data center PUE overhead, monthly electricity bills, 220V MCB amperage, and BTU/hr heat load.

IT Project UAT Checklist & Handover BAST Generator

Generate formal User Acceptance Testing (UAT) checklists and project commissioning handover (BAST) documentation for enterprise IT deployments.

Complete General Directory →

References & Notes

Last updated: 2026-11-07Technically Verified · Industry Standard

Note: Results above are mathematical estimates based on standard formulas. Always verify against official vendor documentation and site conditions before production deployment.