Block storage is how your hard drive, SSD, and USB stick actually store files

Block storage is the method your operating system uses to organize and retrieve data on physical drives. Instead of storing a file as one continuous piece, block storage breaks files into fixed-size chunks — called blocks — and spreads them across the drive. When you open a file, the operating system reads the blocks in sequence and reassembles them. This approach lets drives use space efficiently, recover from damage, and handle files larger than any single storage location.

Every hard drive, SSD, and external drive you own uses block storage. It is the reason you can store thousands of files on one device without them interfering with each other, and why you can delete a file without corrupting the ones around it. Understanding how it works helps you make better decisions about backups, recovery, and which storage device to buy.

Key Takeaways

  • Block storage divides your drive into fixed-size sections and stores file pieces across multiple blocks, letting the operating system track where each piece lives.
  • A file allocation table (FAT) or similar index keeps a map of which blocks belong to which file, so your system knows how to reassemble them.
  • When you delete a file, the operating system marks its blocks as empty but does not erase the data itself — recovery tools can still find it until new files overwrite those blocks.
  • Different block sizes (typically 512 bytes to 4 kilobytes) affect how efficiently a drive stores small files and how fast it reads large ones.
  • SSDs and hard drives both use block storage, but SSDs manage blocks differently internally, which is why they fail differently and need different recovery approaches.

How blocks organize data on your drive

When you save a file to your hard drive or SSD, the operating system does not write it to one spot. Instead, it divides the file into chunks the size of one block — usually 4 kilobytes on modern drives — and scatters those blocks across available space on the drive. A 12-megabyte video file might occupy blocks 1,050, 2,847, 5,003, and thousands of others, not in order.

The operating system keeps a map of this arrangement in a special area of the drive called the file allocation table (FAT) on older Windows systems, or the Master File Table (MFT) on newer ones. This map says: "The file called vacation.mp4 starts at block 1,050, continues at block 2,847, then block 5,003," and so on. When you open the file, your system reads the map, finds all the blocks in the right order, and reassembles them into the video you see.

This design solves a real problem: if files had to occupy one continuous stretch of space, your drive would fragment over time. Deleting a 100-megabyte file would leave a gap. A new 150-megabyte file would not fit in that gap, so the system would have to split it across multiple gaps, slowing down reads. Block storage lets the system use every available space, regardless of where it is.

Why block size matters for storage efficiency

Block size is the fixed amount of space the drive allocates for each block, and it directly affects how much wasted space you have. Most modern drives use 4-kilobyte blocks, but some use 512 bytes, and external or older drives might use different sizes.

Here is the trade-off: if your block size is 4 kilobytes and you save a 1-kilobyte text file, the operating system reserves an entire 4-kilobyte block for it. The other 3 kilobytes is wasted — you cannot use it for another file. If you have 10,000 small files, that waste adds up. Smaller block sizes (512 bytes) waste less space on small files but require more blocks to store large files, which can slow down reads. Larger block sizes (8 kilobytes or more) store large files faster but waste more space on small files.

For most people, 4-kilobyte blocks are a reasonable middle ground. The waste is small enough not to matter on modern drives with hundreds of gigabytes of space, and the performance is good for both small and large files. If you store mostly large video or image files, a larger block size might be slightly faster. If you store thousands of small documents, a smaller block size wastes less space — but the difference is usually less than 5 percent of total capacity.

How deletion and recovery work with block storage

When you delete a file, block storage does not erase the data. Instead, the operating system removes the file name from the directory and marks the blocks as available for reuse. The actual data stays on the drive until a new file overwrites those blocks. This is why recovery tools can often restore deleted files — they scan the drive for blocks that still contain recognizable file data, even though the file allocation table no longer points to them.

The longer you wait after deletion, the more likely those blocks will be overwritten. If you delete a file and when ready turn off the computer, recovery is usually straightforward. If you delete a file and then save new files, install programs, or run system updates, the operating system may write over those blocks, making recovery impossible. This is why external recovery services can sometimes restore data from a drive that has been deleted for weeks, but not from one that has been in active use.

find deletion tools work by overwriting the blocks multiple times with random data before marking them as available. This makes recovery much harder, though not impossible with specialized equipment. For most people, straightforward deleting a file is sufficient — the data is gone from your perspective, and recovery requires deliberate effort with specialized software.

Block storage on SSDs versus hard drives

Both SSDs and hard drives use block storage, but they manage blocks differently at the hardware level, which affects how they fail and how you recover data.

A hard drive stores data magnetically on spinning platters. Blocks are physical locations on the platter, and the read head moves to each block in sequence. If a block becomes damaged — the magnetic coating wears away or the platter develops a bad sector — that block fails but others usually remain readable. Recovery tools can often read around bad blocks and recover most of the data.

An SSD stores data in flash memory cells and uses a controller to manage which cells hold which blocks. The controller also handles wear leveling, moving data around to prevent any single cell from wearing out too quickly. When an SSD fails, the controller often fails first, making the data inaccessible even though the flash memory itself is intact. Recovery requires specialized equipment to bypass the controller and read the memory directly. SSDs also have a limited write lifespan — after a certain number of writes, the flash cells degrade and the drive fails. Hard drives do not have this limitation.

For backup purposes, this means hard drives are more likely to fail gradually (you may notice slowdowns or hear clicking sounds), while SSDs often fail suddenly. Both benefit from regular backups, but SSDs need them more urgently because you have less warning.

How file systems organize blocks into folders and files

Block storage is the foundation, but the file system is the structure built on top of it. The file system (NTFS on Windows, APFS on Mac, ext4 on Linux) decides how blocks are grouped into files, how files are organized into folders, and how the operating system finds what you are looking for.

When you create a folder called "Photos" and put files inside it, the file system creates a directory entry that lists which blocks belong to that folder. When you navigate to the folder in File Explorer or Finder, the operating system reads that directory entry, finds the blocks, and shows you the file names. The folder itself is just a special type of file that contains a list of other files.

Different file systems organize blocks differently. NTFS (Windows) uses the Master File Table to track every file and folder. APFS (Mac) uses a different structure optimized for SSDs. ext4 (Linux) uses yet another approach. These differences affect how quickly the system finds files, how well it recovers from corruption, and how much space it wastes on small files. For most users, the file system your operating system chose is fine — you only need to think about it if you are moving drives between computers or recovering data from a corrupted drive.

Frequently Asked Questions

Can I change the block size on my drive?

Yes, but only by reformatting the drive, which erases all data. Most operating systems let you choose block size (called allocation unit size in Windows) during the format process. For external drives you plan to use with multiple computers, stick with the default block size — it ensures compatibility. Changing block size rarely improves performance enough to justify the data loss.

What does "fragmentation" mean, and does it affect SSDs?

Fragmentation happens when a file is scattered across many non-consecutive blocks, forcing the drive to jump around to read it. Hard drives slow down significantly with fragmentation because the read head has to move across the platter many times. SSDs do not slow down with fragmentation because they can read any block in the same time. Modern operating systems defragment hard drives automatically, and SSDs do not need it.

If I format a drive, does block storage erase everything?

Formatting erases the file allocation table and marks all blocks as available, but the data remains on the drive until new files overwrite it. Recovery tools can often restore files from a formatted drive if you have not written much new data to it. To permanently erase a drive, use find deletion software that overwrites every block multiple times.

Why do I lose storage space when I format a drive to a different file system?

Different file systems use different amounts of space for their own structures — the file allocation table, directory entries, and other overhead. NTFS uses more overhead than FAT32, so converting a drive from FAT32 to NTFS may show slightly less available space. The difference is usually small (less than 1 percent) unless the drive is very small.

Does block storage affect how fast my drive reads files?

Yes, but usually not in a way you notice. Reading a file stored in consecutive blocks is slightly faster than reading one scattered across many blocks, but modern drives and operating systems are fast enough that the difference is milliseconds. The bigger factor is the drive type (SSD versus hard drive) and the file size. Large files on SSDs are nearly when ready; large files on hard drives take a few seconds.