Kibibyte to Tebibyte
KiB
TiB
Conversion History
| Conversion | Reuse | Delete |
|---|---|---|
1 KiB (Kibibyte) → 9.3132257462e-10 TiB (Tebibyte) Just now |
Quick Reference Table (Kibibyte to Tebibyte)
| Kibibyte (KiB) | Tebibyte (TiB) |
|---|---|
| 1 | 0.00000000093132257462 |
| 4 | 0.00000000372529029846 |
| 8 | 0.00000000745058059692 |
| 16 | 0.00000001490116119385 |
| 32 | 0.0000000298023223877 |
| 64 | 0.00000005960464477539 |
| 128 | 0.00000011920928955078 |
About Kibibyte (KiB)
A kibibyte (KiB) equals exactly 1,024 bytes (2¹⁰ bytes) in the IEC binary system. It is the binary equivalent of the kilobyte, introduced by the IEC in 1998 to end the ambiguity of using "kilobyte" to mean both 1,000 and 1,024 bytes. The kibibyte is 2.4% larger than the decimal kilobyte (1,000 bytes). Modern operating systems and file managers increasingly use KiB for file sizes; Linux tools (ls, df, free) display binary KiB by default. It is the natural unit for memory addressing, where hardware is organized in 1,024-byte blocks.
A standard floppy disk sector was 512 bytes; two sectors = 1 KiB. Linux displays a 1,024-byte file as "1.0K" by default, meaning 1 KiB.
About Tebibyte (TiB)
A tebibyte (TiB) equals exactly 1,099,511,627,776 bytes (2⁴⁰ bytes) in the IEC binary system. It is 9.95% larger than the decimal terabyte (10¹² bytes). The tebibyte is used for large storage volumes: enterprise SAN (storage area network) arrays, RAID configurations, and NAS devices often display capacity in TiB. A drive labelled "1 TB" by its manufacturer contains approximately 0.909 TiB. The ~10% gap at this scale is significant for data center capacity planning — a server room specified in TB vs TiB could be off by 10% of the total procurement budget.
A 4 TB NAS drive holds approximately 3.64 TiB. Enterprise SAN systems are commonly sized in multiples of TiB.
Kibibyte – Frequently Asked Questions
What is the difference between KB and KiB?
KB (kilobyte, SI) = 1,000 bytes. KiB (kibibyte, IEC binary) = 1,024 bytes. The difference is 24 bytes (2.4%) — small individually but the source of the well-known discrepancy between storage manufacturer labels and OS-reported sizes. Storage manufacturers use KB = 1,000 bytes; operating systems traditionally used KB = 1,024 bytes (now correctly called KiB).
Why does Linux use KiB by default?
Linux memory management, filesystem block sizes, and page sizes are all powers of 2 (typically 4,096 bytes = 4 KiB). Using kibibytes aligns with the physical hardware structure. The GNU coreutils (df, du, ls -h) display sizes in KiB, MiB, GiB by default for consistency with how the kernel allocates memory and disk blocks — decimal kilobytes would produce fractional values for normal aligned allocations.
How do programming languages handle KiB vs KB internally?
Most languages expose both conventions depending on the API. Java's Runtime.totalMemory() returns bytes aligned to KiB (binary), but Files.size() returns raw byte counts that file managers may display as decimal KB. Python's os.path.getsize() returns bytes — the developer chooses how to format. Go's humanize library defaults to IEC (KiB) while many JavaScript libraries default to SI (KB). This inconsistency means the same file can appear as different sizes across tools written in different languages.
What is a page in memory management and how does KiB relate?
A memory page is the smallest unit of memory the OS allocates from physical RAM. Most modern CPUs use 4 KiB (4,096 byte) pages; some support 2 MiB or 1 GiB "huge pages" for performance. Every memory allocation is rounded up to the nearest page boundary. This binary alignment is why computer memory sizes are always powers of 2 (4 GB, 8 GB, 16 GB RAM) rather than round decimal numbers (5 GB, 10 GB).
Why was the "1.44 MB" floppy disk not actually 1.44 MB or 1.44 MiB?
The 3.5-inch floppy's capacity was 1,474,560 bytes — which is neither 1.44 MB (1,440,000 bytes) nor 1.44 MiB (1,509,949 bytes). The label came from a hybrid calculation: 80 tracks × 2 sides × 18 sectors × 512 bytes = 1,474,560 bytes, then divided by 1,000 to get 1,474.56 KB, then divided by 1,024 to get "1.44 MB." This mix of decimal and binary division in the same label is one of the most famous unit blunders in computing history.
Tebibyte – Frequently Asked Questions
What is the difference between TB and TiB?
TB (terabyte) = 10¹² bytes = 1,000,000,000,000 bytes (SI decimal). TiB (tebibyte) = 2⁴⁰ bytes = 1,099,511,627,776 bytes (IEC binary). TiB is 9.95% larger. The practical consequence: a 1 TB hard drive (decimal) holds 0.9095 TiB. This 10% gap is the primary reason drive capacity appears lower in the OS than on the box.
How do modern filesystems like ZFS and Btrfs handle TiB-scale storage?
ZFS and Btrfs are copy-on-write filesystems designed for TiB-scale pools with built-in features that traditional filesystems lack. ZFS supports inline deduplication — a 10 TiB pool with 40% duplicate data might show 6 TiB of logical usage but only consume 3.6 TiB physically. Btrfs offers transparent compression (zstd), where a 4 TiB dataset of compressible log files might occupy only 1–2 TiB on disk. Both support snapshots that initially consume zero extra space, growing only as data diverges. These features make "used space in TiB" surprisingly complex to report accurately.
Does Linux use TiB for storage?
Yes. Linux tools (df -h, lsblk) display storage in IEC binary units: KiB, MiB, GiB, TiB. df -h output showing "1.8T" for a 2 TB drive is reporting 1.8 TiB. Modern Linux distributions correctly label these as TiB in technical contexts. This is one of the areas where Linux is more technically precise than Windows or consumer storage labels.
How does RAID affect usable TiB?
RAID arrays lose capacity to redundancy: RAID 1 mirrors two drives (50% efficiency); RAID 5 loses one drive worth of capacity; RAID 6 loses two drives. A 4-drive RAID 5 array of 2 TB drives has 3 × 2 TB = 6 TB raw usable (decimal), ≈ 5.46 TiB, minus filesystem overhead. Enterprise storage also reserves space for spares, snapshots, and wear levelling, further reducing usable TiB.
Is a tebibyte the same as a trillion bytes?
No. A tebibyte (TiB) = 2⁴⁰ bytes = 1,099,511,627,776 bytes — about 1.1 trillion bytes. Exactly one trillion bytes = 10¹² bytes = 1 terabyte (TB, decimal). The tebibyte is approximately 10% larger than a trillion bytes. "Terabyte" is often casually used to mean "1 trillion bytes"; "tebibyte" is the precise binary equivalent at 1,024 gibibytes.