HardDiskIndexFAQ

How much storage do you really need in 2026? SSD, games, photos, NAS

By Harry Saarinen ·

In this guide: 20 sections
  1. How much storage you need, by profile: modest on the computer, five times the data around it
  2. Sizing a purchase in ten steps
  3. Measure before you buy: three numbers, and where every system hides them
  4. One formula turns data into drives
  5. Laptop storage: Windows asks for 64GB, and 512GB is the least that lasts
  6. 1TB or 2TB for gaming: a big new PC game asks for about 100GB
  7. PS5 and Xbox storage: usable space is 5 to 29 percent below the number on the box
  8. Phone and photo storage: shots times format, and RAW multiplies the answer by ten
  9. Video storage is sized by bitrate, and “an hour of 4K” runs from 7GB to 1.8TB
  10. Music hardly registers; a Plex or Jellyfin film library is sized by the disc it came from
  11. Local AI models run from 1GB to 404GB each, and collections only grow
  12. Backups are the multiplier: 3-2-1 means three copies before versions
  13. Usable space starts below the label: the units, then the filesystem
  14. How much NAS storage you get: RAID returns half to four-fifths of the raw capacity
  15. How full is too full for an SSD, a NAS pool or a hard drive
  16. CCTV and NVR storage is cameras times bitrate times days
  17. A homelab is sized by its virtual disks, its snapshots and the copies of both
  18. A small office should measure its shares before trusting “per employee” figures
  19. How many drives, and which sizes: rebuild hours, bays and cost per usable terabyte
  20. Plan three years ahead, buy eighteen months at a time

A 1 TB SSD holds a working system and about six big new games, 2 TB suits a gaming or creative PC, and each terabyte you cannot afford to lose needs about five terabytes of drives to be kept properly. That last figure is the one this guide works out in full. Four terabytes of photos and documents on a six-drive home server with two drives’ worth of parity, a month of old versions and a fifth of the space left free, plus the two backup copies that the 3-2-1 rule asks for, comes to between 19 and 21 TB of drive labels, and the formula shows each step so that you can change it. Games, apps and anything else that downloads again need capacity but no copies.

The familiar tier lists - 256GB for light use, 512GB to 1TB for most people, 2TB for gamers - size the computer well, and this guide adds everything around it. 2026 raised the floors (the whole iPhone 17 line starts at 256GB) and made storage expensive on both media at once, so buying the largest drive “to be safe” costs more than it did a year ago. Why prices rose is the 2026 storage price hike, when to buy is buy storage now or wait, and how each size has moved is on Trends. Sources are named with their dates; listing prices live on the pages, where they refresh every few hours.

How much storage you need, by profile: modest on the computer, five times the data around it

“Computer drive” is the SSD inside the machine you sit at. “Data” is what you keep. “Copies” is what keeping it properly adds, and it is zero for anything you could download again.

Who Computer drive Data and library Copies on top Why, in one line
Light Windows laptop: web, office, cloud files 512 GB; 256 GB only if it is a thin client small, mostly in a cloud account a cloud backup or one external drive at twice the laptop’s drive (Apple’s Time Machine rule) Microsoft’s own figures leave about 140 GB of a 256 GB Copilot+ machine before a program is installed (laptops)
Student, five-year laptop 1 TB coursework is small; media and games are not one external drive at twice the laptop’s drive (Apple’s Time Machine rule) the drive is soldered on every current MacBook and on some thin Windows laptops, so check before counting on an upgrade (laptops)
PC gamer 2 TB NVMe a second, cheaper drive for the backlog (games are played from the SSD) none for games; saves sync to the cloud 1 TB holds about six big new releases, 2 TB about fourteen (gaming)
Console owner what came in the box a 2 TB or 4 TB M.2 drive on a PS5 none a PS5 shows 667 GB of 825; a Series S 364 GB of 512 (consoles)
Phone 256 GB; 512 GB if it shoots 4K60 or ProRes or keeps its library offline in a cloud account, optimized on the phone the cloud copy plus one local copy Apple keeps “space-saving versions” on the device and the originals in iCloud (phones)
Photographer 2 TB SSD for the catalog and current work 1 to 1.5 TB a year for a working professional NAS with parity plus two backups, about five times a 48 MP ProRAW is about 75 MB, a 61 MP RAW 64 to 135 MB (photos)
Video creator 2 to 4 TB fast SSD for projects in progress hours of footage times bitrate archive on a parity array, then backed up 4K ProRes 422 is 265 GB an hour; XAVC S is 45 (video)
Media server small boot drive 9 to 33 TB for 500 films, by format parity is enough if the discs are kept a UHD Blu-ray holds up to 66 or 100 GB (films)
Local AI 1 to 2 TB NVMe for models in use up to 404 GB a model none for public models a model is read whole at every start, so the ones in use belong on NVMe (local AI)
Camera recorder small bitrate x 0.45 x 24 x days x cameras mirror for footage that matters; export clips a recorder writes all day, so the drive’s workload rating limits it as much as capacity (recorders)
Homelab 1 to 2 TB NVMe for virtual machines a pool sized to the guests and their snapshots backups of the guests, not of the ISOs snapshots grow until deleted (homelab)
Small office, 25 people 512 GB to 1 TB per seat the measured shares, times three years of growth versions, an on-site and an off-site copy a “per employee” figure is a guess until the shares are measured (small office)

Three rules hold in every row. The computer’s own drive is sized by what you work on now, and the library by what you keep forever. Replaceable data needs capacity; irreplaceable data needs capacity times copies: a game library needs no backup at all, while ten years of family photos may be a tenth of its size and need five times their size in drives. Plan for the three years you can see, and buy only what the next twelve to eighteen months need wherever the rest can be added later, because at 2026 prices a terabyte bought for year three sits idle until then. Buy the whole plan on day one only where nothing can be added later: a laptop with a soldered drive, a full chassis, a RAIDZ group at its final width. The riskiest profile is irreplaceable data on a single drive, the only one that can lose everything at once.

Which medium holds which part follows HDD or SSD: flash for anything a person waits on (the system, this month’s games, active projects, virtual machine disks), hard drives for terabytes nobody waits on (libraries, archives, backups, camera recordings). A client SSD’s powered-off retention is specified at one year at 30 °C by the JEDEC standard, so an SSD in a drawer is not a backup plan.

Sizing a purchase in ten steps

  1. Measure first: used space split into replaceable and irreplaceable, its growth over the last year, and the largest working set, with the tools in measure before you buy.
  2. Run the formula once per copy, with the versions, layout and free-space factors that apply, and convert to drive labels with 0.9095.
  3. Choose the layout from the bay count and the drive size together, from the RAID table, then check the rebuild hours in how many drives, and which sizes.
  4. Open the section for the medium: NVMe SSDs for the system, games and active projects; 3.5-inch hard drives for libraries, backups and recorders; every drive together across both.
  5. Pick a capacity point, not a range: 8 TB, 12 TB and 16 TB drives side by side, or 2 TB and 4 TB NVMe. Trends names the cheapest size per terabyte for each drive type, and how each size has moved.
  6. Convert the price per terabyte into a price per usable terabyte with the multiplier for your layout, and compare capacities on that.
  7. For an array, keep shingled drives out: hard drives listed as SMR hidden, CMR vs SMR, and NAS-rated drives for their error-recovery behavior.
  8. For a recorder, check the workload rating against the streams on surveillance-rated drives.
  9. Start from the default view: it lists working drives at prices you can pay, and buy=now narrows it to fixed-price listings alone.
  10. If buying used, follow buying used drives on eBay, and for SAS pulls from the SAS listings, confirm the controller with drive interfaces.

Measure before you buy: three numbers, and where every system hides them

Every operating system shows what you use in under a minute. On Windows, Settings, System, Storage shows used space by category, and Microsoft’s Free up drive space page documents the cleanup tools; WizTree gives a per-folder view. Windows’ “931 GB” on a 1 TB drive is really 931 GiB (the units). On a Mac, System Settings, General, Storage shows the categories, in decimal units since 2009, so a Mac and a PC show different numbers for the same files. On Linux, df -h gives each filesystem in binary units, du -sh ~/* totals each folder, and ncdu walks the tree; on ZFS, zfs list -o space splits live data from snapshots. On a phone, Settings shows the per-app breakdown and the cloud accounts show the rest: Google counts “up to 15 GB” per account across Gmail, Drive and Photos, according to Google Photos Help, and iCloud’s free tier is 5 GB. A family’s library often lives in four phones and two clouds at once, and the total is the sum, not the largest.

Whatever the system, write down three numbers:

1. used now           split into irreplaceable (photos, documents, projects,
                      mail archives) and replaceable (games, apps, downloads,
                      ripped media you still own on disc)
2. growth per year    the irreplaceable part's size a year ago, from an old
                      backup, a photo library sorted by year, or folders by year
3. working set       the biggest thing that must be on fast storage at once:
                      the games you play this month, the project you are editing

The first number sizes the library, the second sizes it for the years you are buying for, and the third sizes the computer’s own drive. Growth is the easiest to measure from the past: the nature photographer Chrissy Donadi did it in an April 2024 article, reading growth of 1.3, 1.1 and 1.3 TB in 2020, 2021 and 2022 off a 5 TB library sorted by year, and bought a 12 TB drive for a five-year horizon. Measure the split between replaceable and irreplaceable first, because it decides how many copies each terabyte needs: a 2 TB disk that is three-quarters games is a 500 GB backup problem.

One formula turns data into drives

Every sizing in this guide is the same multiplication, applied once per copy and then added up:

labels for one copy  =  data  x  versions  /  redundancy efficiency
                              /  (1 - free space kept)  /  0.9095

total labels         =  the sum over every copy, then  x  growth
Factor What it means Typical value Where
data what the operating system reports, in binary units measured measuring
versions old versions and snapshots kept beside the live copy 1.1 for a month at 10% monthly change; open-ended for Time Machine versions
redundancy efficiency the share of raw capacity that holds data 1 for a single drive, 0.5 for a mirror, about 0.67 for six-drive double parity RAID
free space kept what the filesystem or the medium needs empty 0.2 for ZFS and SSDs that take steady writes, 0.15 for a games SSD, near zero for a camera recorder free space
0.9095 a decimal terabyte on the label, expressed in the binary units the system reports fixed units
growth compound growth over the years bought for measured; 1.95 for 25% a year over three growth

Worked for the home case in the first paragraph: 4 TB of irreplaceable data as the operating system reports it, a month of versions at 10% monthly change, a six-drive RAIDZ2 pool kept under 80% full, and two further copies on single drives, one of them off-site:

primary, six-drive RAIDZ2      4 x 1.1 / 0.667 / 0.80 / 0.9095  =  9.1 TB of labels
                               (six drives of about 1.5 TB each)
backup 1, one drive            4 x 1.1 / 0.9095                  =  4.8 TB
                               with 20% kept free                =  6.0 TB
backup 2, one drive off-site   the same                          =  4.8 to 6.0 TB
                                                                   ---------------
total                          9.1 + 4.8 + 4.8 to 9.1 + 6.0 + 6.0 = 18.7 to 21.2 TB
ratio to the data              18.7 / 4 to 21.2 / 4               =  4.7 to 5.3

About five terabytes of drive labels for each terabyte you cannot lose, when every copy is on your own drives. Nobody buys six 1.5 TB drives, so the real purchase rounds up, and the rounding is where growth lives: a RAIDZ2 group widened later keeps its old parity ratio (RAIDZ expansion), so six 4 TB drives bought at once give the pool room for more than four years at 25% a year. The ratio falls when part of the job goes elsewhere: a laptop with a cloud backup needs only one external drive, which Apple’s Time Machine guidance (July 6, 2026) sizes “with at least twice the storage capacity of your Mac”.

The formula has one trap: redundancy, versions and copies multiply only the data they protect. 4 TB of photos at about five times plus 8 TB of ripped films still on their discs at about twice (parity, free space and units alone) needs about 37 TB; a single multiplier across both would ask for 60.

Laptop storage: Windows asks for 64GB, and 512GB is the least that lasts

Microsoft’s Windows 11 specifications page asks for a “64 GB or larger storage device”, a device size that has to hold the system, the space Windows reserves for updates (about 7 GB when Microsoft introduced reserved storage in 2019) and the room to install them. Microsoft’s other documents add what a working Copilot+ laptop carries beside it:

Windows 11 floor: system, reserved storage   64 GB   Microsoft, Windows 11
and room for updates (a device size)                 specifications
Recall snapshots, default on a 256 GB device 25 GB   Microsoft Learn, Dec 10, 2025
hibernation file, 40% of 16 GB of RAM       6.4 GB   Microsoft Learn, Jul 14, 2025
                                            ------
Microsoft's figures, added                   95 GB
a 256 GB SSD as Windows shows it            256 x 10^9 / 2^30   = 238 GB
left for programs, games and files          238 - 95            = 143 GB

The 40% hibernation figure is the system power states documentation default; Microsoft’s hibernation troubleshooting article (February 12, 2026) puts the file at about the size of installed memory instead, which leaves about 133 GB. Recall is the line that scales with the drive: Microsoft’s Recall support page asks for “at least 50 GB of storage space free” to switch it on, and the Recall management page (December 10, 2025) allocates 25 GB of snapshots by default on a 256 GB drive, 75 GB on 512 GB and 150 GB on 1 TB or more. On a 256 GB Copilot+ laptop with Recall switched on, Microsoft’s own figures leave about 140 GB for everything else: room for an office suite and some years of documents, or for one big game and little else. macOS Tahoe 26 wants about 50 GB free to install, according to OSXDaily (June 13, 2025), and Ubuntu Desktop 26.04 LTS asks for 25 GB in Canonical’s release notes.

The computer’s own drive in 2026: 512 GB is the least for a Windows machine meant to last, 1 TB the comfortable size for anyone who installs games or creative software, and a 256 GB machine is a thin client whose files live elsewhere. Every current MacBook and some thin Windows laptops solder the drive to the board, so the number chosen at checkout is the number for the machine’s whole life. Machines with an M.2 slot can grow later from the NVMe listings; drive interfaces covers which slot takes which drive.

1TB or 2TB for gaming: a big new PC game asks for about 100GB

A PCWorld buying guide (April 15, 2026) says “Plenty of modern PC games take up between 20GB to 30GB each”. Big new releases ask for far more. The storage requirements of 32 large and popular PC titles were read from Steam and the publishers’ support pages on October 2, 2026; the table shows 19 of them:

Title Released Storage asked for Source
God of War Ragnarök Sep 2024 190 GB Steam
ARK: Survival Ascended Oct 2023 180 GB Steam
Call of Duty: Black Ops 7 Nov 2025 161 GB on an SSD “at launch”, every tier; Activision’s support page says 116 GB Steam; Activision, Mar 11, 2026
S.T.A.L.K.E.R. 2 Nov 2024 160 GB Steam
Baldur’s Gate 3 Aug 2023 150 GB “on an SSD” Larian
The Last of Us Part II Remastered Apr 2025 150 GB Steam
Marvel’s Spider-Man 2 Jan 2025 140 GB Steam
Black Myth: Wukong Aug 2024 130 GB Steam
The Elder Scrolls IV: Oblivion Remastered Apr 2025 125 GB Steam
Assassin’s Creed Shadows Mar 2025 115 GB Steam
Grand Theft Auto V Enhanced Mar 2025 105 GB Steam
Borderlands 4 Sep 2025 100 GB Steam
DOOM: The Dark Ages May 2025 100 GB Steam
Kingdom Come: Deliverance II Feb 2025 100 GB Steam
Battlefield 6 Oct 2025 55 GB minimum, 80 GB recommended, SSD required Steam
Monster Hunter Wilds Feb 2025 75 GB, plus a 70 GB texture pack Steam
Clair Obscur: Expedition 33 Apr 2025 55 GB Steam
Silent Hill f Sep 2025 50 GB Steam
Elden Ring Nightreign May 2025 30 GB Steam

Across all 32 the median requirement is 102.5 GB and the mean about 108 GB, and the 15 released in 2025 have a median of exactly 100 GB. A big new PC game needs about 100 GB, three to five times the figure that buying guide gives for a typical one, and the listing is a floor: Monster Hunter Wilds launched asking 140 GB before Capcom split off a texture pack that adds more than 70 GB as free DLC. Take a 150 GB system footprint (laptops) and 15% kept free (free space) off what Windows shows, and divide by 100 GB a game:

drive    as Windows shows it    minus 150 GB and 15% free    games at 100 GB
1 TB          931 GB                   642 GB                    6
2 TB        1,863 GB                 1,433 GB                   14
4 TB        3,725 GB                 3,016 GB                   30

A 1 TB SSD holds about six big new releases, 2 TB about fourteen and 4 TB about thirty. Valve’s Steam Hardware and Software Survey for September 2026 shows 53.30% of machines with more than 1 TB of total storage. Most of these titles now require an SSD, and Black Ops 7, Battlefield 6, Baldur’s Gate 3 and Monster Hunter Wilds say so in the listing, so a hard drive holds the backlog only as storage: a game is copied back to the SSD before it is played. Only save files and mods need a backup. For a gaming PC, buy a 2 TB NVMe drive for the games you play and a cheaper, larger drive for the backlog, and spend nothing on backing up what the store will give you again. The size step is on 2 TB NVMe drives and the step above on 4 TB NVMe drives.

PS5 and Xbox storage: usable space is 5 to 29 percent below the number on the box

Every console reserves part of its drive for the system software:

Console On the box Usable for games Held back Source
PlayStation 5 (launch model) 825 GB 667 GB 19% PlayStation Universe, Nov 6, 2024
PlayStation 5 Pro 2 TB 1.89 TB 5.5% PlayStation Universe, Nov 6, 2024
Xbox Series X 1 TB 802 GB 20% IGN’s hands-on, reported by Windows Central, Sep 28, 2020
Xbox Series S 512 GB 364 GB 29% GameSpot, Nov 4, 2020
Nintendo Switch 2 256 GB not published - Nintendo
Steam Deck OLED 512 GB or 1 TB not published - Valve

At 100 GB a game a launch PS5 holds six large games and a Series S three. Expansion is where the console owner’s real decision sits. Sony’s M.2 installation page accepts PCIe Gen4 x4 M.2 NVMe drives from “250 GB - 8 TB”, recommends “5,500MB/s or faster”, and limits the drive and its heatsink to 25 mm wide and 11.25 mm thick; Nintendo’s Switch 2 takes only microSD Express cards. Console makers charge well for capacity: Game Developer reported on June 22, 2026 that Valve’s Steam Machine would sell at $1,049 with 512 GB and $1,349 with 2 TB, $200 for each added terabyte, so compare the 2 TB NVMe listings before choosing the larger model. For a PS5, a 2 TB M.2 drive more than doubles a launch console and 4 TB makes storage a non-question for most libraries, as long as it is NVMe (an M.2 SATA drive in the same shape will not work) and its heatsink fits Sony’s 11.25 mm limit.

Phone and photo storage: shots times format, and RAW multiplies the answer by ten

A photo library is shots times size, and size depends almost entirely on the format. Apple’s ProRAW support page (April 19, 2024) puts ProRAW files at “10 to 12 times larger than HEIF or JPEG files”, and Alpha Shooters measured the 61 MP Sony a7R V’s RAW files:

Format Per photo Per 10,000 photos Source
12 MP HEIF, phone about 2 to 2.5 MB 20 to 25 GB derived from Apple’s ProRAW ratio
12 MP ProRAW about 25 MB 250 GB Apple, Apr 19, 2024
48 MP ProRAW about 75 MB 750 GB Apple, Apr 19, 2024
61 MP RAW, compressed 64 to 73 MB 640 to 730 GB Alpha Shooters, Nov 29, 2022
61 MP RAW, lossless compressed, full size 68 to 83 MB 680 to 830 GB Alpha Shooters, Nov 29, 2022
61 MP RAW, uncompressed 125 to 135 MB 1.25 to 1.35 TB Alpha Shooters, Nov 29, 2022

Switching a phone from HEIF to ProRAW, or a camera from JPEG to uncompressed RAW, multiplies a library’s growth by ten or more.

A phone is sized by what has to stay on it, not by the library. With Optimize Storage on, Apple’s iCloud Photos page (September 14, 2026) says “your device keeps space-saving versions of your photos and videos”, with the originals in iCloud. What has to stay is the system, the apps, offline media, and whatever is shot before it uploads: an hour of 4K60 is 24 GB (video). A 256 GB phone, the floor across the iPhone 17 line since MacRumors reported it on September 9, 2025, covers that for most people; 512 GB is for a phone that regularly shoots 4K60 or ProRes or keeps its library offline. Apple’s iCloud page lists, in the US, 50 GB for $0.99 a month, 200 GB for $2.99, 2 TB for $9.99, 6 TB for $29.99 and 12 TB for $59.99, after a free 5 GB. A photo library in a single cloud account is one copy, not a backup (backups). Kept at home, it grows by its software’s share: the photo server Immich says in its requirements that thumbnails and transcoded video “can increase the size of the photo library by 10-20% on average”.

Two worked libraries, with the assumptions labeled:

family of four, phones only (assumptions: 3,000 photos and 2 hours of 4K30
video per person per year)
  photos   4 x 3,000 x 2.5 to 5 MB                 =  30 to  60 GB a year
  video    4 x 2 h x 10.2 GB an hour (4K30 HEVC)   =        82 GB a year
  total                                            = 112 to 142 GB a year
  five years, self-hosted, +20% for thumbnails     = about 0.67 to 0.85 TB

working photographer (Donadi's measured history, April 2024)
  growth                                           = 1.1 to 1.3 TB a year
  three more years at 1.2 TB, from 5 TB            = about 8.6 TB
  her purchase for a five-year horizon             = one 12 TB drive

The family library fits a 2 TB cloud plan for a decade; the photographer’s needs a NAS, and at about five times for proper copies the 8.6 TB library becomes several tens of terabytes of drives. For a photographer the formula’s multiplier is the whole answer, because every frame is irreplaceable and every frame is large.

Video storage is sized by bitrate, and “an hour of 4K” runs from 7GB to 1.8TB

The Post Flow’s video storage calculator (Alex Bartz, updated July 28, 2026) gives the rule of thumb, and it is exact:

GB per hour  =  Mbps  x  3,600 seconds  /  8 bits per byte  /  1,000
             =  Mbps  x  0.45

“4K” names a resolution, not a bitrate, and bitrates span three orders of magnitude:

What is recorded Bitrate GB per hour Source
Netflix, Ultra HD stream streaming up to 7 Netflix Help Center
iPhone, 1080p30 HEVC about 60 MB a minute 3.6 iOS 11 figures, reported by iMore, Sep 14, 2017
iPhone, 4K30 HEVC about 170 MB a minute 10.2 iOS 11, via iMore, 2017
iPhone, 4K60 about 400 MB a minute 24 iOS 11, via iMore, 2017
Sony XAVC S, 4K 100 Mbps 45 The Post Flow
DJI Osmo Action 5 Pro, top bitrate 120 Mbps 54 DJI specifications
ProRes 422, UHD 30p 589 Mbps 265 Apple ProRes white paper, Apr 2022
Sony XAVC S-I, 4K 60p 600 Mbps 270 The Post Flow
ProRes 422 HQ, UHD 30p 884 Mbps 398 Apple, Apr 2022
ProRes 422 HQ, UHD 60p (what iPhone records at 4K60) 1,768 Mbps 795 Apple white paper; Apple asks for a drive that writes at least 220 MB/s
ProRes 4444 XQ, UHD 60p 3,977 Mbps 1,790 Apple, Apr 2022

The often-quoted “an hour of 4K takes 7 GB” is Netflix’s streaming figure, and 4K recorded by a camera is between about one and a half and 250 times larger. Editing adds proxies (ProRes Proxy is 20 GB an hour at 1080p 30p), a render cache and exports, while YouTube’s recommended upload bitrates put a finished 4K upload at 16 to 20 GB an hour, the smallest file in the chain. A creator shooting an assumed 3 hours a week of 4K in XAVC S at 100 Mbps fills 7.0 TB a year with originals; the same hours in ProRes 422 HQ at UHD 30p fill 62 TB. A codec choice is a storage decision of about nine times, made in the camera menu.

For a home or small studio the working rule is two tiers: the project in progress on a fast SSD sized to the largest active project, and the finished archive on a parity array of 3.5-inch hard drives, backed up like any irreplaceable data. A 4 TB NVMe drive holds about ten hours of ProRes 422 HQ at UHD 30p, which is why footage moves to the archive when a project closes.

Music hardly registers; a Plex or Jellyfin film library is sized by the disc it came from

Apple’s figures, quoted in 9to5Mac’s Apple Music guide, put a three-minute song at about 6 MB at 256 kbps AAC, 36 MB in Lossless at 24-bit/48 kHz and 145 MB in Hi-Res Lossless at 24-bit/192 kHz, so a 10,000-song library is 60 GB, 360 GB or 1.45 TB. Only a large hi-res collection needs planning.

Films are sized by the disc they came from: the Blu-ray Disc Association’s May 2015 release gives Ultra HD Blu-ray discs of 66 and 100 GB, and at the 128 Mbps maximum in Audioholics’ summary an hour is 57.6 GB, so a full copy of a two-hour 4K film, a remux, lands near the size of the disc:

500 films
  4K remux, about 55 to 66 GB each           27.5 to 33 TB
  re-encoded at 20 Mbps (assumption)         500 x 2 h x 9 GB  =  9 TB

A media library of 500 films is a 9 TB or a 33 TB problem depending on one decision about format, and if the discs are kept, it is replaceable: it needs parity for convenience but not three copies. A six-drive RAIDZ2 at 80% full holds 33 TB of remuxes on about 62 TB of drive labels (33 / 0.667 / 0.8, with no unit conversion because disc sizes are already decimal), six 12 TB drives with room to spare. Keep shingled drives out of that array; CMR vs SMR explains why.

Local AI models run from 1GB to 404GB each, and collections only grow

Ollama’s library lists DeepSeek-R1 downloads in seven sizes in its default quantization: 1.1 GB at 1.5b, 4.7 GB at 7b, 5.2 GB at 8b, 9.0 GB at 14b, 20 GB at 32b, 43 GB at 70b and 404 GB at 671b; one copy of each comes to 487 GB. A hobbyist comparing three quantizations of two 70B-class models such as Llama 3.3 70B holds about a quarter of a terabyte. Model files download again, so they need capacity but not backup copies, unlike fine-tunes and datasets made from them, and they are read whole every time a model starts: a 43 GB model loads in about 8 seconds at 5,500 MB/s and takes nearly 3 minutes from a hard drive at 250 MB/s. Keep the models you use on NVMe and the archive of models you might use on anything. The memory they need once loaded is in how much RAM you need.

Backups are the multiplier: 3-2-1 means three copies before versions

The 3-2-1 rule is the largest factor in the formula for anything irreplaceable. Its federal statement is a 2012 paper for US-CERT by Carnegie Mellon’s Paul Ruggiero and Matthew A. Heckathorn, Data Backup Options:

Keep 3 copies of any important file: 1 primary and 2 backups.

The paper adds two media types and one copy off-site; Backblaze’s 3-2-1-1-0 variant adds one copy offline or air-gapped and zero errors when restores are tested. Three copies means three times the data in capacity before a single old version is kept, and the primary usually costs more than one times, because it sits on redundant storage with free space. Redundancy is not a backup: a mirror or a parity array copies a deletion, a corrupted file or a ransomware encryption to every drive within milliseconds. Sync is not a backup either, unless the service keeps versions long enough to step back past a mistake.

Versions are what make a backup useful, and they take space

A backup that keeps only the latest copy restores yesterday’s mistake. A rough multiplier, assuming every changed file is stored again whole, is 1 plus the share of data changed per month times the months kept: 1.1 for documents changing 10% a month kept one month, 2.2 for active projects at the same rate kept a year, and about 1.0 for a photo library, where new photos are growth, not versions. It overstates block-level tools that store only the changed parts.

Time Machine keeps hourly, daily and weekly backups and deletes the oldest only when the disk is full, so the size of its disk sets how far back you can go, which is why Apple’s rule is twice the Mac. Virtual machine snapshots grow fastest: Broadcom’s snapshot guidance recommends using “only 2 to 3” in a chain, says “Do not retain a single snapshot for more than 72 hours”, and notes that the snapshot file “continues to grow in size the longer it is kept”. A snapshot is an undo button with a meter running, not a backup.

What the off-site copy costs

Backblaze B2 “Starts at $6.95 / TB / mo”, so 5 TB off-site is $34.75 a month, $417 a year. Amazon’s S3 price list for US East (N. Virginia), read on October 2, 2026, puts Glacier Deep Archive at $0.00099 per GB-month, $4.95 a month for the same 5 TB, with retrieval within 12 hours and a 180-day minimum. For a household, a cloud copy is usually the off-site copy, a single external drive the local one, and the primary sits on the computer or a NAS: three copies, two places.

Usable space starts below the label: the units, then the filesystem

Drive makers count in powers of ten; Windows and most Linux tools use powers of two under the decimal names, so a 4 TB drive shows as 3.63 TB in Windows, 3.7T in df -h and 4 TB on a Mac. Microsoft confirms the binary half in “Plan volumes on Azure Local and Windows Server clusters” (Microsoft Learn, March 9, 2026): “storage quantities in Windows appear in binary (base-2) units.” The ratio is 10^12 / 2^40 = 0.9095 at every size, so 9% of every terabyte you buy disappears into the units before anything else touches it. Drive capacity explained has every size.

The filesystem takes the next share. On ext4 it is a 5% reserve for root (“The default percentage is 5%”, says the mke2fs manual), a full terabyte on a 20 TB data volume, which tune2fs -m 1 reduces; OpenZFS holds back 1/32 of a pool as “slop space”, capped at 128 GiB in the source code; and Synology’s RAID calculator page says “Each drive in the RAID must reserve approximately 10 GB of system space”, with Btrfs volumes reserving 4% for metadata. On a four-bay Synology the shares stack like this:

four 12 TB drives, Synology SHR (one drive of parity), Btrfs
  raw                      4 x 12 TB                = 48.00 TB
  system space             4 x 10 GB                = -0.04 TB
  one drive of parity      (48 - 0.04) x 3/4        = 35.97 TB
  Btrfs metadata reserve   -4%                      = 34.53 TB
  as the NAS reports it    34.53 x 0.9095           = 31.41 TiB, 65% of the label

Four 12 TB drives make about 31 “TB” on the screen, before the free space the free-space table says to keep.

How much NAS storage you get: RAID returns half to four-fifths of the raw capacity

Any layout that survives a drive failure pays for it in raw capacity: a fixed share for mirrors and classic RAID, slightly more for RAIDZ. For 12 TB drives, with usable space in the binary units the system reports:

Bays Layout Survives Share of raw that holds data Usable, 12 TB drives At 80% full
2 mirror 1 drive 50% 10.91 TiB 8.73 TiB
4 two mirrors (RAID 10) 1, sometimes 2 50% 21.83 TiB 17.46 TiB
4 RAID 5 or RAIDZ1 1 75%; 72.7% for RAIDZ1 31.7 to 32.7 TiB 25.4 to 26.2 TiB
4 RAID 6 or RAIDZ2 2 50% 21.83 TiB 17.46 TiB
5 RAIDZ1 1 80% 43.66 TiB 34.92 TiB
6 RAID 6 or RAIDZ2 2 66.7% 43.66 TiB 34.92 TiB
8 RAID 6 or RAIDZ2 2 75%; 71.1% for RAIDZ2 62.1 to 65.5 TiB 49.7 to 52.4 TiB
12 RAIDZ3 3 75%; 72.7% for RAIDZ3 95.2 to 98.2 TiB 76.2 to 78.6 TiB

The RAIDZ figures are for 128 KiB records on 4 KiB sectors, worked in drive capacity explained. Matt Ahrens’s analysis of RAIDZ space shows that “RAIDZ-p is no better than p-way mirrors for recordsize=4K or 8K”, so a pool of virtual machine disks or databases with small blocks should usually be built as mirrors, which also rebuild faster; photos, video and media land close to the table. The Btrfs status page marks its RAID5 and RAID6 profiles “unstable”, so Btrfs planning means mirrors.

OpenZFS 2.3.0, released on January 14, 2025, can grow a RAIDZ group a drive at a time, but its manual page for zpool attach warns that “old blocks retain their old data-to-parity ratio”. Expansion adds capacity at the old efficiency for everything already written, so a pool planned at its final width keeps the better ratio for all of it; the TrueNAS capacity calculator checks a layout before buying.

Choose the layout from the bay count and the drive size, then size the drives. Two bays make a mirror. Four bays make two mirrors or a RAIDZ2 with large drives, and a RAID 5 only with small ones. Six or more bays make a RAIDZ2, the layout this guide recommends for most home servers. Rebuild time is why double parity becomes the default as drives grow, and drives for a NAS works through it.

How full is too full for an SSD, a NAS pool or a hard drive

Free-space advice in print runs from 10 to 25 percent, but the answer differs by medium:

Medium or system Keep free Why Source
Consumer SSD, TLC or QLC 15 to 20% the SLC write cache is carved from free space; write amplification rises as the drive fills HDD or SSD on this site
ZFS pool, any drives 20% as the planning line fragmentation and allocator pressure; at about 96% ZFS switches to best-fit allocation TrueNAS, Aug 14, 2026
Btrfs volume similar to ZFS; Synology already holds 4% copy-on-write needs free space for metadata Synology RAID calculator
ext4 or NTFS on a hard drive 5 to 10% inner tracks are slower; ext4 already reserves 5% mke2fs manual; HDD or SSD
Windows system drive with Recall at least 25 GB; 50 GB to enable Recall pauses its snapshots below 25 GB Microsoft Support
Camera recorder (NVR) disk none; runs full by design the oldest footage is deleted to make room Frigate documentation
Time Machine disk none; runs full by design the oldest backups are deleted to make room Apple Support

HDD or SSD works out that a 2 TB TLC drive at 90% full keeps about 67 GB of its fast cache and at 98% essentially none, and SSD endurance explains why free space also slows wear. A ZFS pool that crosses 80% is not broken, but one that will cross 90% before its next expansion was sized too small. Other files on a camera or Time Machine disk shorten how far back it reaches. This guide uses 20% free for SSDs that take steady writes and for ZFS pools, 15% for an SSD that mostly holds installed games, 10% for a plain hard drive, and zero for a disk whose software deletes the oldest data by design.

CCTV and NVR storage is cameras times bitrate times days

A camera recorder writes a fixed stream, keeps it for a set time, then deletes it:

storage  =  bitrate (Mbps)  x  0.45 GB per hour per Mbps  x  24  x  days  x  cameras

one camera, 4 Mbps, 30 days         4 x 0.45 x 24 x 30           =  1.30 TB
eight cameras, 4 Mbps, 30 days      x 8                          = 10.37 TB
                                    as the recorder reports it   =  9.43 TiB

In the EU, 30 days needs a reason: the European Data Protection Board’s video guidelines (January 2020) want most footage erased “after a few days”, and ask for more justification the longer it is kept past 72 hours, about 1 TB for those eight cameras.

The bitrate is the input to get right: GuardSource HQ’s NVR storage calculator (July 2, 2026) uses H.265 baselines of 2, 4, 5 and 8 Mbps for increasing resolutions, and recording only on motion, about eight hours a day, cuts continuous storage to about a third.

The drive’s workload rating is the second limit, and the sum below checks it. A rating counts data read and written per year, and a recorder writes all day. Western Digital’s WD Red Plus datasheet (September 2025) rates those NAS drives at 180 TB a year, and Seagate rated the SkyHawk AI 24TB at 550 TB a year in December 2023, for “up to 64 HD video camera streams and 32 additional AI streams”:

180 TB a year   = 180 x 10^12 / 31,536,000 s  =  5.7 MB/s  = 45.7 Mbps
                  at 4 Mbps a camera          =  11 cameras of continuous writing,
                                                 before any playback is read
550 TB a year   = 17.4 MB/s                   = 139.5 Mbps
                  across 64 cameras           =  2.2 Mbps a camera
                  64 x 2.2 Mbps fills 24 TB   in about 16 days

Eight cameras at 4 Mbps write about 126 TB a year, inside a 180 TB rating but not by much once someone reviews footage. Drives for a NAS takes the ratings apart, and drives sold for the job are on surveillance-rated hard drives. A two-drive mirror is the minimum for footage that matters, and the exported clip of an incident is the part that needs backup copies.

A homelab is sized by its virtual disks, its snapshots and the copies of both

A home server has three pools, named or not: fast storage for the guests, bulk storage for data and media, and somewhere for the backups of both. The guests are sized by what they use, but the pool must survive what they were promised: a thin-provisioned 128 GB virtual disk holding 40 GB takes 40 GB, and a pool whose guests have been promised more than it holds fails for all of them at once when the promises come due. Templates and images deduplicate well: Microsoft’s Data Deduplication overview (June 20, 2025) puts typical savings at 80 to 95% for virtualization libraries, while photos, video and anything compressed or encrypted reduce close to 1:1.

Guests write in small blocks, on which RAIDZ is no better than a mirror (RAID), so the guests’ pool is usually a mirror of two SSDs (NVMe arrays covers building one, and NVMe caching putting flash in front of a hard drive pool instead). A worked homelab, with every guest size an assumption: a Windows desktop VM at 80 GB, five Linux VMs and containers at 30 GB each, a 200 GB ISO and template library and snapshots at about 20% of the guest disks (46 GB) come to 476 GB, which at 80% full on a two-SSD mirror means two 1 TB NVMe drives. A homelab’s backup job covers the guests’ disks and their configuration, a few hundred gigabytes, not the multi-terabyte pool beside them, unless that pool holds irreplaceable data, which needs copies of its own; the ISO library downloads again. The boot drive is the smallest decision: VMware ESXi 8.0 asks for a 32 GB boot device and 128 GB for its data volume, according to Broadcom TechDocs, and Proxmox sets no minimum.

A small office should measure its shares before trusting “per employee” figures

The figure most often printed for small business storage, “Plan for 100-200 GB per employee minimum” in Burgi Tech’s 2026 guide, comes with no derivation. An office already has its data on a server, a NAS or in a cloud tenant, and the measured size of it beats any per-head figure: the size of each shared folder from the server, the NAS or the admin console, its size a year ago from the oldest backup still kept, and the split between working files, which need versions, and the archive, which needs retention.

The cloud tenant may already be smaller than the share: SharePoint’s shared storage is 1 TB plus 10 GB for each licensed user, as CIAOPS summarized Microsoft’s limits in May 2025, so a 1.5 TB file share moved there by 25 users overflows on day one. A worked office of 25 people, with the measured size and growth rate as labeled assumptions:

measured shared data today (assumption)       1.5 TB, as the server reports it
growth, from last year's backup (assumption)  20% a year
in three years                                1.5 x 1.2^3       = 2.59 TB
with a month of versions at 10% change        2.59 x 1.1        = 2.85 TB
usable needed at 80% full                     2.85 / 0.8        = 3.56 TB
as drive labels                               3.56 / 0.9095     = 3.92 TB usable
four-bay NAS, two mirrors (RAID 10)           3.92 / 0.5        = 7.8 TB raw
                                              -> four 4 TB drives, with room past
                                                 year three
on-site backup, 90 days of versions           a NAS or drive of about the same
                                              usable size
off-site copy, Backblaze B2 list price        2.85 / 0.9095 x $6.95 = about $22 a month
"100-200 GB per employee"                     2.5 to 5 TB, with no versions,
                                              parity or backup in it

Retention rules add their years of growth to the archive: the IRS asks for tax records to be kept 3 years in general, 4 for employment tax, 6 if unreported income exceeds 25% of gross and 7 for worthless securities or bad debts, HIPAA documentation is kept 6 years under 45 CFR 164.316, and broker-dealers keep specified records not less than 6 years on non-rewriteable storage or with a complete audit trail under SEC Rule 17a-4. A deletion schedule for what no rule requires is the cheapest capacity an office can add. The seats follow the laptop section, with their contents in the shared store, which is what gets backed up.

How many drives, and which sizes: rebuild hours, bays and cost per usable terabyte

The formula gives a usable capacity, the layout turns it into a count of drives, and three things decide the drive size.

Rebuild time grows with the drive. The floor on a rebuild is capacity divided by sustained transfer rate, which Western Digital gives as up to 196 and 260 MB/s for the two 7,200 rpm WD Red Plus 12 TB models in its September 2025 datasheet and up to 287 MB/s for the 26 TB WD Red Pro in its January 2025 datasheet:

12 TB at 260 and 196 MB/s   12 x 10^12 / 260 or 196 x 10^6  =  12.8 to 17 hours
26 TB at 287 MB/s                                             =  25 hours
44 TB at 287 MB/s (announced sizes)                           =  43 hours

Those are floors, since “up to” rates are outer-track figures; drives for a NAS tabulates the range, from 200 MB/s on an idle array down to 50 MB/s on a busy one, and does the failure probability properly. A single-parity array has no protection left while it rebuilds, and a larger drive keeps it unprotected for longer, so this guide uses double parity for any array of drives of 12 TB or more.

More drives means more failures to rebuild from. Backblaze’s Drive Stats for the second quarter of 2026 (September 29, 2026), across 354,415 drives, put the lifetime annualized failure rate at 1.41%. At that rate, the chance that at least one drive in an array fails in a year is:

Drives Chance of at least one failure in a year, at 1.41%
2 2.8%
4 5.5%
6 8.2%
8 10.7%
12 15.7%

Fewer, larger drives fail less often and rebuild more slowly; more, smaller drives do the opposite and spend less on parity. Bays are the scarce resource, not terabytes: a full chassis can grow only by replacing every drive, so plan the array at the width it will end at, in one drive size, since classic RAID and ZFS count every member as the smallest; Synology’s SHR exists to use the difference. One cold spare on the shelf is worth more in 2026 than in most years.

The price per usable terabyte is the price per raw terabyte times a multiplier

The listing pages rank drives by price per raw terabyte, the number on the label. What a layout delivers per usable terabyte is that price times a fixed multiplier:

multiplier  =  1 / (share of raw that holds data  x  0.9095  x  share kept full)
Layout Share holding data Kept full Multiplier on price per raw TB, per usable TiB
single hard drive 100% 90% 1.22
single SSD or ZFS drive 100% 80% 1.37
five-wide RAIDZ1 80% 80% 1.72
four-wide RAIDZ1 72.7% 80% 1.89
twelve-wide RAIDZ3 72.7% 80% 1.89
eight-wide RAIDZ2 71.1% 80% 1.93
six-wide RAIDZ2 66.7% 80% 2.06
mirror, or two mirrors 50% 80% 2.75

Multiply the price per terabyte a listing shows by the multiplier for your layout, and that is what each usable terabyte costs. Two more copies for irreplaceable data add their own: a six-wide RAIDZ2 primary plus two single-drive backups at 90% full comes to 2.06 + 1.22 + 1.22 = 4.5 times the price per raw terabyte for each TiB of data, or 4.95 with a month of versions, which is the formula’s “about five” again from the other end.

So a cheaper price per raw terabyte on a larger drive is worth having only if the layout can use the capacity: two large drives in a mirror pay 2.75 times over, while six smaller ones in RAIDZ2 pay 2.06. The gap between the two media is a live ratio; read it from the hard drive listings and the SSD listings, and how it has moved from Trends. A used enterprise drive is often the cheapest terabyte on the page, with its own checks in buying used drives on eBay and enterprise drives.

Plan three years ahead, buy eighteen months at a time

Growth is the number most often underestimated. TrendForce said on September 30, 2026 that PC brands were cutting SSD capacities in mainstream models as flash costs rose, so a 2026 base configuration is where the maker’s costs stopped, not a statement about what the buyer needs. Plan on your own measured rate, and use 25% a year where there is no history. Published industry rates run from 22% a year, Western Digital’s exabytes shipped in its fiscal fourth quarter of 2026, to 43%, Seagate’s nearline exabytes in the quarter to July 2026, and Western Digital told its results call of August 5, 2026 that it sees exabyte demand “growing at above 25%”. At 25% a footprint doubles in a little over three years and triples in five:

Growth a year After 3 years After 5 years
10% 1.33 x 1.61 x
20% 1.73 x 2.49 x
25% 1.95 x 3.05 x
30% 2.20 x 3.71 x
40% 2.74 x 5.38 x

Size the plan for three years of your measured growth, and buy the next twelve to eighteen months of it now wherever the layout lets you add the rest. Three years decides a pool’s width, bays and parity once; twelve to eighteen months is as far ahead as anyone should buy at 2026 prices, which is where buy storage now or wait lands. Order the expansion when the pool crosses 70% full, so that it arrives before 80% even with a long delivery; for data-center nearline drives, TrendForce reported in September 2025 that lead times had “ballooned from just a few weeks to over 52 weeks”. Both media became expensive at once: in the US, SSD prices roughly doubled, while hard drive prices rose about 15 to 90% depending on the line, and Tom’s Hardware found a Samsung 990 Evo Plus 2 TB it had recommended at a $113 deal price on Prime Day 2025 on sale for $363 on July 29, 2026.

Do not buy year three at today’s price where a NAS has free bays, a mirror can take a second pair or a desktop has a free M.2 slot; buy a soldered laptop’s storage for its whole life at checkout. And count deletion as capacity: the duplicate photo library, the ISO folder that downloads again, the camera footage past its retention period and the old VM snapshot are terabytes that cost nothing to recover.

Related guides

Affiliate links:we earn from qualifying eBay purchases. eBay's live price is final. Full disclosureAffiliate disclosure:We are a member of the eBay Partner Network and earn a commission from qualifying purchases made through links to eBay on this site. Prices and availability are captured periodically and may have changed - the live price is always the one shown on eBay.