Exos capacity planning authority

Best Seagate Exos Capacity: 18TB vs 22TB vs 24TB vs 28TB vs 30TB vs 32TB

The best Exos capacity is not automatically the largest or the cheapest per terabyte. It is the smallest exact-model plan that meets usable-capacity, redundancy, growth, bay, compatibility, spare and support requirements at an acceptable lifecycle cost.

Exos specifications reviewed August 5, 2026 X18 through Exos M 3+ Generation, interface and model verification required

Quick answer

For value, begin with mature 18TB or 22TB exact-model offers. For a balanced current platform, compare 24TB X24 and Exos M. For limited bays, 28TB, 30TB and 32TB Exos M can reduce chassis count. Treat 36TB separately until exact documentation, service terms and replacement supply meet the deployment’s requirements.

Compared capacities18TB–32TB36TB evaluated separately

Main constraintUsable capacity per bayAfter parity and reserve

Key buying unitComplete arrayNot one drive

Mandatory checksModel, interface, formatPlus seller and warranty

Exact model data

Representative exact SATA models by capacity

Capacity	Model	Generation	Interface	Sector format	Security	Recording	Cache	Max sustained	Status
18TB	`ST18000NM003D`	Exos X20	SATA	512e/4Kn FastFormat	Standard	CMR	256MB	285MB/s	Established generation
22TB	`ST22000NM001E`	Exos X22	SATA	512e/4Kn FastFormat	Standard	CMR	512MB	285MB/s	Established generation
24TB	`ST24000NM002H`	Exos X24	SATA	512e/4Kn FastFormat	ISE	CMR	512MB	285MB/s	Current X24 channel model
24TB	`ST24000NM001K`	Exos M	SATA	512e/4Kn FastFormat	ISE	HAMR-CMR	512MB	240MB/s	Current Mozaic channel model
28TB	`ST28000NM003K`	Exos M	SATA	512e/4Kn FastFormat	ISE	HAMR-CMR	512MB	270MB/s	Current Mozaic channel model
30TB	`ST30000NM004K`	Exos M	SATA	512e/4Kn FastFormat	ISE	HAMR-CMR	512MB	275MB/s	Current Mozaic channel model
32TB	`ST32000NM004K`	Exos M	SATA	512e/4Kn FastFormat	ISE	HAMR-CMR	512MB	285MB/s	Current 32TB channel model
36TB	`ST36000NM003K`	Exos M 3+	SATA	Verify exact model documentation	Verify exact model documentation	HAMR-CMR	Verify	Verify	Special product record; inventory and service bundle vary

The table includes both X24 and Exos M at 24TB because capacity alone does not identify the platform. The 36TB record remains a specialist option with unverified technical fields rather than inheriting 32TB data.

Live catalogue

Current exact-model Exos offers by capacity

Verified exact-model identity remains eligible for at least 336 hours after successful confirmation. Amazon prices and images refresh separately on 24-hour clocks. If Amazon exposes buying options without one featured numeric price, the card shows Price Options. Generation, interface, capacity, security class and exact model are enforced.

Search offers Sort

Checking the current Cloudzat catalogue…

Interactive decision tool

Find the first Exos capacity that meets the plan

Enter usable storage, chassis bays, redundancy and growth. The tool uses a 15% operating reserve and identifies the first tracked capacity that meets the target.

Usable storage needed today (TB) Available drive bays Redundancy layout Expected annual growth (TB) Years of growth to include Planning priority

Start with usable capacity, not raw capacity

Drive labels show raw decimal terabytes. Filesystem formatting, parity or mirrors, snapshots and a free-space reserve reduce what the application can safely use. A plan that needs 100TB should not buy exactly 100TB of raw media.

The calculator applies redundancy and a 15% reserve. Adjust the inputs to reflect actual growth, then verify the result with the storage platform’s own capacity calculator.

18TB: mature value and broad secondary-market visibility

Exos X18 and X20 18TB models are established and often price-competitive. They are sensible when bays are available, an existing fleet uses the same capacity, or a newer-density premium is not justified.

The trade-off is bay consumption. In a large build, moving from 18TB to 30TB can eliminate drives, enclosures, ports and power overhead.

22TB: the top X22 capacity

Twenty-two terabytes offers conventional CMR density with SATA, SAS and multiple security variants. It can bridge older 18TB fleets and 24TB-plus designs without moving to the Exos M roadmap.

Its value is sensitive to price. If 24TB X24 costs nearly the same, the extra two terabytes per bay may be worthwhile. If 22TB inventory is discounted and already qualified, it can be the better operational choice.

24TB: compare X24 with Exos M

Twenty-four terabytes is not one decision. X24 provides SATA, SAS and security breadth with up to 285MB/s published on tracked models. Exos M ST24000NM001K starts the Mozaic channel range and publishes 240MB/s.

Choose by exact model, interface, qualification and roadmap. Do not combine both in a single “24TB Exos” line item.

28TB: a density step without paying for the maximum

Twenty-eight terabytes can be the practical point where Exos M density starts to reduce bay count without moving all the way to 30TB or 32TB pricing. It is especially useful when the array target narrowly exceeds a 24TB design.

Compare it with 30TB in total dollars. A small price difference may make 30TB more attractive, while a large premium may leave 28TB as the better value.

30TB: strong bay efficiency

Thirty terabytes is often a compelling density compromise. It adds meaningful raw capacity over 28TB and can meet targets that would otherwise require another chassis or expansion shelf.

Check whether 32TB is close in price, and whether the platform has validated the exact 30TB model. The best capacity is the one that avoids an expensive infrastructure step, not necessarily the one with the lowest unit price.

32TB: current flagship channel density

ST32000NM004K is the current broadly documented 32TB Exos M channel model. It maximizes capacity in a fixed number of bays and can simplify very large arrays.

Density also increases the amount of data represented by each failure and spare. Confirm 32TB qualification, replacement supply and backup capacity. Keep ST32000NM003K separate unless its own documentation is verified.

36TB: a separate procurement decision

Thirty-six terabytes should not be inserted into the normal ladder as though it were simply another fully documented channel model. Its exact product record and service bundle need separate validation, and replacement supply may be uneven.

For critical storage, a well-documented 32TB model with a clear support route may be a better business choice than a denser but harder-to-replace 36TB model.

Array-level price per terabyte

Calculate the cost of all data drives, parity drives and spares, then divide by planned usable capacity. Add the cost of extra bays, HBA ports, power, cooling and backup. This can reverse a simple drive-price ranking.

Use Cloudzat’s live Exos prices to compare fresh offers, but exclude unavailable prices and unverified conditions from the math.

Growth and expansion strategy

Forecast at least the period before the next realistic maintenance window. Some RAID and ZFS layouts cannot expand one drive at a time without restrictions or long operations. Buying enough headroom now can avoid a disruptive migration.

Overbuying also has costs. Unused capacity ages, consumes power and may be replaced before it is needed. Use a realistic growth range rather than a single optimistic number.

Compatibility, acoustics and operations

A capacity that fits the spreadsheet can still fail the deployment if the chassis firmware, sector format, interface, cooling or noise environment is wrong. SATA and SAS are not interchangeable, and enterprise drives can be loud in a home office.

Standardize exact models where possible, document acceptable substitutes and validate a drive before adding many units.

Bottom-line capacity recommendation

Choose the smallest capacity that meets usable storage, parity, reserve and growth without forcing an expensive bay expansion. Prefer a current larger model when bays are scarce. Prefer a mature smaller model when value, existing qualification and replacement supply dominate.

Always finish the decision with exact-model price, interface, warranty and platform checks. Capacity is the output of the plan, not the starting assumption.

How Cloudzat evaluates Exos drives

Cloudzat attaches generation, interface, sector format, security class, recording technology, cache, transfer rate and warranty only to an exact model. Exos X18, X20, X22, X24, Exos M and the verification-required Exos M 3+ records remain separate. This prevents a SATA listing from inheriting SAS specifications or an Exos M drive from inheriting X24 data.

Live offers are screened for new single internal 3.5-inch drives and matched to an exact model. SATA and SAS are kept separate. SSDs, external drives, accessories, enclosures, servers, multipacks, MACH.2, Exos Xz host-managed SMR, other drive families and non-new listings are rejected. Warranty source and delivered-label verification remain essential.

Frequently asked questions

Best Exos capacity questions answered

What is the best-value Seagate Exos capacity?

It changes with live exact-model prices. Calculate array-level cost per planned usable terabyte, including parity drives and a spare. Mature 18TB or 22TB models may win on price; 28TB-to-32TB can win when they avoid another chassis.

Is 32TB always better than 30TB?

No. Compare total price, platform qualification, replacement supply and how much extra capacity the array actually needs. If 30TB meets the growth target with comfortable reserve, paying more for 32TB may not add operational value.

Should I buy 24TB X24 or 24TB Exos M?

Choose X24 for SAS, broader security variants, existing qualification or its higher tracked 24TB sustained rate. Choose Exos M for the current SATA Mozaic roadmap and a path to 28TB-to-32TB. Compare exact models.

How much free space should I leave?

Cloudzat uses 15% for planning, but the correct reserve depends on filesystem, snapshots, workload and vendor guidance. Performance and management can degrade when an array is nearly full.

How many parity drives should I use?

That depends on drive count, failure tolerance, rebuild exposure and the storage platform. Larger drives increase rebuild stakes. Dual parity is common in larger arrays, but parity is not a backup.

Can I mix different Exos capacities?

Many systems allow it, but usable capacity can be limited by the smallest drive and expansion rules vary. Mixing models also complicates spares, performance and support. Follow the platform documentation.

Does a larger drive always save power?

It can reduce the number of drives and associated ports and fans, but individual model power differs. Calculate the complete design rather than assuming capacity alone determines energy use.

Should a home user avoid Exos M?

Not automatically. Confirm SATA compatibility, capacity support, cooling and noise tolerance. Enterprise acoustics can be intrusive, and warranty route must be verified for marketplace units.

Why is 36TB not recommended as the default maximum?

The tracked 36TB product requires separate documentation, service and supply checks. A fully documented 32TB channel model may be easier to qualify, support and replace even though it offers less density.

What is the best way to compare current prices?

Use exact model numbers, same condition and warranty source. Exclude listings without a verified price from price-per-terabyte calculations, but retain them as availability signals. Calculate cost at array level.

Primary sources

Cloudzat may earn a commission from qualifying purchases. Product availability, pricing and specifications can change. Confirm the exact Exos model, generation, interface, sector format, security variant, seller, condition and regional warranty route before buying.