✅ Updated Nov 2026
Affiliate Disclosure: As an Amazon Associate, we earn from qualifying purchases. Links marked "Check on Amazon" are affiliate links — learn more.
⭐ Key Takeaways
Quick answer: Our top pick is Samsung T9 Portable SSD 2TB, with Crucial T705 2TB PCIe Gen5 NVMe SSD as a strong alternative.

Every drive advertises one big sequential number, and every gaming forum argues about whether doubling it makes games faster. On Linux the honest answer is layered: storage speed decides some waits completely, touches others barely, and is irrelevant to a third group that players routinely blame on the drive. It is having each job a game gives its storage running on media suited to that job.

This explainer separates the jobs: what loading screens actually wait on, why open worlds stutter on slow media despite respectable sequential numbers, what shader compilation does to a drive on Linux, and why a handheld’s microSD card behaves nothing like an NVMe drive. It is a mechanism guide, not a benchmark chart.

As an Amazon Associate, we earn from qualifying purchases.

Quick answer

Storage speed on Linux mostly decides loading screens, install and update time, and whether open-world streaming hitches on slow media. It barely changes frame rates once assets are in memory, and shader compilation is a CPU job whose results are cached on disk. A mid-range NVMe drive covers nearly every gaming workload; the fastest drives pay off mainly for huge installs, updates and content work.

The three jobs storage does for a game

A game asks its drive to do three different things, and each stresses a different property of the media. The first job is the bulk load: reading a level, a texture pack or a video file as one long stream. That is the sequential work the headline number describes, and modern drives of every class do it well.

The second job is the scatter load: thousands of small files and small reads inside large archives, requested in whatever order the engine needs them. Scatter work depends on latency and small-read behaviour, not on the sequential headline, which is why two drives with similar big numbers can feel different at a loading screen.

The third job is the write side nobody shops for: installs, updates, patch verification and cache building. A modern update can rewrite large parts of an install while reading the old files to verify them, which turns a patch day into the heaviest storage workload most gaming PCs ever run. Stutter during play on an old drive is usually the second job arriving late; updates taking forever is the third.

Sequential versus random, honestly

The sequential rating is measured on long, uninterrupted transfers, and it is real, but it describes the easiest thing a drive does. Game loading sits between the extremes: big asset bundles stream sequentially for stretches, then the engine interrupts with small reads for the index, the audio and the scripts. Load times improve as drives get faster, but with sharply diminishing returns once the bottleneck moves to the CPU decompressing what arrived.

That decompression step is the part the storage debate usually misses. Assets ship compressed, and a faster drive delivers compressed data to a CPU that still has to unpack it before the GPU can use it. Past a certain point the drive waits on the processor, not the other way round, and doubling the sequential rating changes the wait by very little. This is also why the jump from a hard drive to any solid-state drive transforms a system while jumps between solid-state generations are subtle: the first jump removes a mechanical seek from every scatter read; the later ones mostly widen a pipe that was no longer the narrowest point.

The Linux layer: page cache and shader caches

Linux adds two behaviours that change how storage speed feels. The first is the page cache: the kernel keeps recently read file data in spare memory, so a game’s second launch and second visit to an area often come from RAM rather than the drive. With generous memory, a slower drive can feel fast after the first load, because Linux quietly did the caching work the drive could not.

The second behaviour is shader compilation. On Linux, most Windows games run through a translation layer that compiles their shaders for your GPU, and the results are stored in cache folders on disk so each shader is built once. Building them is processor work, and no drive makes compilation itself faster. What the drive affects is everything around it: reading the cache back at launch, writing new entries during play, and the stutter pattern of a title whose cache is still young. A nearly full or very slow drive makes cache behaviour worse in ways players misread as a graphics problem, so keeping headroom on the library drive is a genuine gaming setting on Linux. Proton prefixes add a smaller habit: each game’s prefix holds the registry and configuration files the translation layer reads at startup, so a saturated drive shows up there first as mysterious launch delays.

The microSD reality on handhelds

A microSD card in a Steam Deck or a Linux handheld is not a small NVMe drive, and judging it by the same expectations produces bad decisions. Its sequential rating describes camera-style transfers. Gaming asks it for scatter reads, sustained mixed work during updates, and constant small writes from caches and saves, through an interface with far less bandwidth and a far simpler controller than an internal drive’s.

The practical consequences are specific. Games on the card load more slowly in scatter-heavy stretches, most visibly in open worlds that stream as you move. Updates to card-resident games take disproportionately long, because patching is the write-heavy third job running on the media least suited to it. None of this makes the card useless: it is excellent overflow for finished games and lighter titles. The mistake is treating it as a second internal drive and putting daily, weekly-patched games on the slowest media in the system.

When a faster drive is wasted money

The honest cases where drive speed buys nothing are worth naming. Frame rates in a loaded, running game are set by the GPU and CPU; once the assets for the current area are resident, the drive is mostly idle, and no upgrade changes the rendering maths. A faster drive also cannot fix compilation stutter, network lag, or a game whose Linux problem lives in its anti-cheat or its translation layer rather than its storage.

The second waste case is generational: a slot running an older PCIe generation caps any newer drive at the slot’s speed, and a handheld’s internal bay has its own ceiling. Matching the drive to the slot is free performance; paying past it is decoration. The third case is capacity sacrificed for speed: a smaller, faster drive that forces constant deleting and reinstalling costs more time at the download screen than it saves at the loading screen.

How to choose

Choose by the job your library actually gives the drive. A single internal NVMe drive of the current mainstream class is the right default for almost everyone: it removes storage from the list of problems and leaves budget for capacity. Step up to the fastest class only if your routine includes very large installs, frequent giant updates, or moving game-sized files for other work, and only when your slot can feed it. Keep a SATA solid-state drive in service without guilt in older machines and secondary libraries; its weakness is patch day, not play. Whatever you buy, leave free space on it: solid-state drives slow as they fill, and Linux shader caches need room to grow.

Who should skip this

Skip the upgrade thinking entirely if your games already load from an NVMe drive and your complaints are about frame rates, shader stutter in new games, or online lag, because none of those live in the storage layer. Skip it if the real problem is capacity. And skip the fastest class if your motherboard or handheld cannot run it at its rated interface, since the ceiling belongs to the slot, not the sticker.

Five drives, one per class

Crucial T705 2TB

The ceiling class: a PCIe 5.0 drive for slots that can feed it, here so the top of the market is represented honestly rather than recommended blindly.

Specs:
– Capacity: 2TB
– Interface: PCIe 5.0 x4, NVMe, M.2 2280
– Model: CT2000T705SSD3
– Maker-rated speeds: up to 14,500 MB/s read, 12,700 MB/s write
– Note: bare drive; use the motherboard heatsink for sustained loads

WD Black SN850X 2TB

The flagship PCIe 4.0 class most current gaming boards run at full speed, and the practical top end for game libraries.

Specs:
– Capacity: 2TB
– Interface: PCIe 4.0 x4, NVMe, M.2 2280
– Model: WDS200T2X0E
– Maker-rated speeds: up to 7,300 MB/s read, 6,600 MB/s write
– Endurance: 1,200 TBW

Samsung T9 Portable SSD 2TB

Samsung T9 Portable SSD 2TB

Samsung T9 Portable SSD 2TB

Check price on Amazon

The portable class: a fast USB drive for moving a library between machines and keeping an install backup that restores quicker than a re-download.

Specs:
– Capacity: 2TB
– Interface: USB 3.2 Gen 2×2, external
– Model: MU-PG2T0B/AM
– Maker-rated speeds: up to 2,000 MB/s read and write
– Enclosure: rubberised, drop-resistant shell per maker

Crucial MX500 1TB

The SATA class: still the sensible upgrade for older machines, and the honest baseline showing how much of gaming speed is simply leaving mechanical media behind.

Specs:
– Capacity: 1TB
– Interface: SATA III, 2.5-inch
– Model: CT1000MX500SSD1
– Maker-rated speeds: up to 560 MB/s read, 510 MB/s write
– Endurance: 360 TBW

SanDisk Extreme 1TB microSDXC

The handheld overflow class: a well-rated card for the games you keep installed but play occasionally, with the daily library kept on internal storage.

Specs:
– Capacity: 1TB
– Format: microSDXC UHS-I, A2 rated
– Model: SDSQXAV-1T00-GN6MA
– Maker-rated speeds: up to 190 MB/s read, 130 MB/s write
– Use case: handheld and Switch-style overflow storage

FAQ

Will a faster NVMe drive raise my frame rate?

No. Once a game’s assets for the current area are loaded, rendering is GPU and CPU work and the drive is largely idle. Storage speed changes loading, streaming headroom and patch time. If frame rates are the problem, the answer lives in graphics settings, the driver or the translation layer, not in a drive upgrade.

Why do my games stutter in new areas even on an SSD?

On Linux the usual cause is shader compilation, not storage: the translation layer builds each shader the first time it appears and caches it for later, and the stutter fades as the cache matures. Keeping free space on the drive helps the cache work, but no drive compiles shaders faster.

Is a microSD card good enough for my main library on a handheld?

It works, with costs: slower scatter-heavy loads, much slower patching, and the worst version of young-cache stutter. The arrangement that plays best is daily games on the internal drive and the card as overflow for finished or occasional titles.

Does the file system change how fast my games load?

At the margins. The folder’s dedicated file-system guide covers the trade-offs; for loading specifically, the media class and free space matter far more than the choice between mainstream Linux file systems.

Final verdict

Storage speed for Linux gaming is a story of three jobs with three different answers. Bulk loads stopped caring about drive class once solid-state media became normal. Scatter loads and streaming still reward latency and punish mechanical drives and microSD cards in exactly the places players feel it. Installs and updates reward raw throughput more than any gameplay does. Buy for the job your library performs most, and keep the drive from filling up.

Crucial T705 2TB PCIe Gen5 NVMe SSD

Crucial T705 2TB PCIe Gen5 NVMe SSD

Check price on Amazon

WD Black SN850X 2TB NVMe SSD

WD Black SN850X 2TB NVMe SSD

Check price on Amazon

Crucial MX500 1TB SATA SSD

Crucial MX500 1TB SATA SSD

Check price on Amazon

SanDisk Extreme 1TB microSDXC Card

SanDisk Extreme 1TB microSDXC Card

Check price on Amazon

Explore Our Guides & Free Tools