Terabyte to Block

TB

1 TB

blk

8,000,000,000,000 blk

Conversion History

ConversionReuseDelete
No conversion history to show.

Entries per page:

0–0 of 0


Quick Reference Table (Terabyte to Block)

Terabyte (TB)Block (blk)
0.54,000,000,000,000
18,000,000,000,000
216,000,000,000,000
432,000,000,000,000
864,000,000,000,000
16128,000,000,000,000
20160,000,000,000,000

About Terabyte (TB)

A terabyte (TB) equals 1,000,000,000,000 bytes (10¹² bytes) in the SI decimal system. It is the standard unit for consumer hard drives, high-capacity SSDs, and NAS (network-attached storage) devices. A typical desktop hard drive is 1–8 TB; enterprise SSDs can exceed 100 TB. The binary tebibyte (TiB = 2⁴⁰ bytes ≈ 1.0995 × 10¹² bytes) is about 9.95% larger than a decimal terabyte — the largest practically encountered gap in the SI/IEC ambiguity at consumer scale. Cloud storage plans commonly use 1–5 TB tiers.

A 2 TB external hard drive holds roughly 500,000 photos, 500 HD movies, or 400 hours of 4K video. A standard laptop SSD today ranges from 512 GB to 2 TB.

About Block (blk)

A block (also called a disk block or storage block) is a fixed-size unit of data used by filesystems and storage devices when reading or writing to disk. Block size is not fixed across systems — common sizes are 512 bytes (the historic disk sector size), 4,096 bytes (4 KiB, the modern standard for HDDs and SSDs), and larger sizes (64 KiB, 1 MiB) for enterprise storage arrays. Filesystems allocate space in whole blocks: a 1-byte file still consumes one full block on disk. Block size affects performance (larger blocks favor sequential reads) and space efficiency (smaller blocks waste less space on small files).

A 4,096-byte (4 KiB) block filesystem storing a 1-byte text file uses 4,096 bytes of disk space — 4,095 bytes are wasted. On a system with 1 million tiny files, this slack space becomes significant.


Terabyte – Frequently Asked Questions

1 terabyte (TB) = 1,000 gigabytes (GB) in the SI decimal system. In the binary IEC system, 1 tebibyte (TiB) = 1,024 gibibytes (GiB). Consumer hard drives and SSDs are labelled in decimal TB; operating systems may display available space in either GB or GiB depending on the OS and version, leading to a discrepancy of up to ~7% between the label and the OS display.

A 1 TB SSD holds approximately: 200,000 JPEG photos (at 5 MB each), 250 HD movies (at 4 GB each), 200+ modern AAA games (at 50 GB average), or enough for about 100 hours of 4K video footage from a modern camera. In practice, the OS and drive firmware overhead reduce usable capacity to roughly 900–930 GB as reported by the operating system.

A terabyte (TB) = 10¹² bytes = 1,000,000,000,000 bytes. A tebibyte (TiB) = 2⁴⁰ bytes = 1,099,511,627,776 bytes. The TiB is about 9.95% larger. This gap is why a 1 TB hard drive appears as 931 GiB (≈ 0.909 TiB) in Windows. The IEC formally defined TiB in 1998 to eliminate this naming ambiguity.

Timeline depends heavily on use case: continuous 4K video recording fills 1 TB in about 2–3 hours (at 1 GB/min). Typical laptop use (documents, photos, apps) might take 3–5 years to fill 1 TB. A game library of 20 modern AAA titles uses 500 GB–1 TB. Home security camera systems recording 24/7 at 1080p use about 1 TB every 10–15 days per camera.

For most individuals, 1 TB of cloud storage is generous: it holds 200,000+ photos, years of documents, and even video libraries. Google One offers 2 TB for €9.99/month; iCloud offers 2 TB for £6.99/month. Power users — especially photographers and videographers — may need 2–5 TB. Family sharing plans can make 2 TB cost-effective across multiple users.

Block – Frequently Asked Questions

Modern hard drives (2011+) and SSDs use 4,096-byte (4 KiB) physical sectors — known as "Advanced Format" or AF. Legacy drives used 512-byte sectors. Filesystems (NTFS, ext4, APFS) typically use 4 KiB logical block sizes to match physical sectors, which avoids the performance penalty of misaligned writes. Enterprise SSDs may use larger block sizes (16 KiB or more) for better parallelism.

Cloud block storage services (AWS EBS, Azure Managed Disks, GCP Persistent Disk) use I/O block sizes typically of 4 KiB or 16 KiB. Performance is measured in IOPS (I/O operations per second) and throughput (MB/s) — both depend on block size. A throughput-optimized workload (sequential video) benefits from large blocks; an IOPS-optimized workload (database random reads) uses small blocks.

Filesystems allocate disk space in whole blocks. On a system with 4 KiB blocks, every file — no matter how small — occupies at least 4,096 bytes. A directory of 10,000 small configuration files (each 100 bytes of content) uses 40 MB of disk space (10,000 × 4,096 bytes) rather than 1 MB (10,000 × 100 bytes). This is called "block slack" or "internal fragmentation".

Disk blocks (filesystem blocks) are typically 512 bytes to 4 KiB. Database blocks (database pages) are the unit of I/O for a database engine — typically 8 KiB (PostgreSQL, SQL Server), 16 KiB (MySQL InnoDB), or 32 KiB (Oracle, configurable). Database blocks usually align to multiples of disk blocks for efficiency. Reading one database page may involve reading 2–8 disk blocks.

RAID stripe size (or chunk size) is the amount of data written to each drive before moving to the next drive in the array — typically 64 KiB to 512 KiB. It should be set to match your workload: sequential large-file workloads benefit from larger stripe sizes; random small-block workloads benefit from stripe sizes closer to the filesystem block size. Mismatched stripe and block sizes cause write amplification and reduce RAID performance.

© 2026 TopConverters.com. All rights reserved.