How to move Steam Deck games to a microSD card safely
Use SteamOS Storage controls to relocate an installed game without redownloading it. This is official-source-informed baseline guidance, not a card benchmark or a promise that every game loads identically from microSD and NVMe storage.
Disclosure: optional shopping links are broad Amazon searches marked sponsored/nofollow. We did not hands-on test every result, and the site adds an Associates tag only when a real tag is configured.
Quick move checklist
- Open SteamOS Storage settings. In Gaming Mode, open Settings → Storage. Wording and button placement can change between SteamOS versions.
- Confirm both storage locations. The internal drive and microSD card should each appear with a capacity and free-space summary.
- Select one installed game. Open the current options for that title and choose the move-content action.
- Choose the microSD card as the destination. Recheck the destination and available capacity before confirming.
- Leave the Deck powered and the card inserted. Let Steam finish without sleeping, rebooting, or starting another large storage task.
- Test before moving more. Launch the game, restart the Deck, and launch it again from the card.
Prepare the card and the game first
It must already be Steam storage
If the card is new, use SteamOS to format it for a dedicated Deck game library. Formatting is destructive. If a previously working card has disappeared, troubleshoot detection before erasing it.
Leave working room
Do not plan around the game’s rounded store-page number alone. Installed size, updates, shader data, compatibility files, and temporary work can require additional space.
Cloud is not universal backup
Check the game’s Steam Cloud status, then separately protect irreplaceable local saves, mods, screenshots, emulator files, and non-Steam data. A library move should not be the only copy event you trust.
Move one installed game in SteamOS
Valve can revise SteamOS navigation, so follow the labels on the current stable interface rather than forcing an old screenshot or command-line path. The safe workflow is consistent: identify the source library, select the title, choose the move action, verify the destination, and let the operation complete.
| Stage | What to verify | Stop if… |
|---|---|---|
| 1. Storage screen | Internal storage and the microSD card both appear, with plausible capacity figures. | The card is missing, repeatedly disconnects, or reports a wildly wrong capacity. |
| 2. Game selection | The chosen title is fully installed and not currently downloading, updating, or running. | Steam is patching the game or another storage operation is active. |
| 3. Destination | The microSD card is selected and has comfortable free space beyond the displayed game size. | The destination is ambiguous or nearly full. |
| 4. Transfer | The Deck has stable power, airflow, and time to finish. | The card disconnects, the Deck becomes unusually hot, or storage errors appear. |
| 5. Verification | The game launches, survives a restart, and still appears on the expected storage device. | Steam requests a full reinstall or the card vanishes after reboot. |
Set the microSD card for future installs
If the card is your preferred library, select it as the default installation location in the current Storage settings. This changes where new installs are offered by default; it does not automatically relocate every game already on the internal SSD. Continue to read the destination shown during each install, especially when the card is absent or low on space.
- Keep frequently patched or storage-heavy games on the internal SSD when card write time becomes inconvenient.
- Use microSD for games that fit comfortably and do not need the SSD’s additional performance headroom.
- Leave free space on both drives for updates, shader data, and temporary files.
- Do not fill a travel card the night before a trip without launching each important game once in the mode you will use.
Which games should stay on the SSD?
There is no honest universal percentage or loading-time promise. Valve lists a high-speed microSD slot on current Steam Deck specifications, while the SD Association’s A1 and A2 marks describe application-performance minimums under defined conditions. Those facts do not establish the result for a specific game, card, seller, filesystem state, or patch.
Smaller, stable, rotation-friendly games
Consider games with modest install sizes, infrequent giant patches, and no observed asset-streaming problem in your own play. A card is also useful for a deliberate travel library.
Large updates and storage-sensitive titles
Favor NVMe storage for games that patch constantly, contain huge numbers of small files, stream assets aggressively, or show repeatable stalls from the card in your own comparison.
Frame rate is mainly a rendering workload, so do not assume a faster card raises FPS. Storage can affect install, patch, verification, loading, and asset-streaming behavior. Use the Steam Deck settings hub to tune a game after its storage location is stable.
If the move fails or gets interrupted
- Do not format the card. A failed move does not automatically mean the filesystem should be erased.
- Keep both storage devices available. Leave the card inserted and restart SteamOS once after any active operation has clearly stopped.
- Check Storage again. Confirm where Steam now lists the game and whether either drive shows the expected used space.
- Use Steam’s verify function if offered. Let Steam check the installed files before deleting folders manually or redownloading everything.
- Pause competing work. Stop other downloads and updates, connect stable power, and retry with one smaller game.
- Investigate repeated disconnects. If the card disappears or becomes read-only, switch to the microSD detection guide and protect readable files.
Moving a library versus downloading over the network
If the game is not installed on this Deck, a storage move is the wrong tool. Steam’s official Local Network Game Transfers feature can copy eligible installed game files from another Steam client on the same local network, subject to Valve’s settings and eligibility rules. That can reduce internet downloading, but it is a separate process from moving a game between the Deck’s internal SSD and its inserted card.
For a second Steam Deck, desktop PC, or replacement card, decide which workflow you actually need:
- Same Deck, two drives: use SteamOS Storage move controls.
- Another Steam client on the network: review Valve’s Local Network Game Transfers support page and its current permissions.
- Card contains non-Steam files: make a file-level backup with a compatible system rather than assuming a Steam library move covers them.
- New or repurposed card: follow the Steam Deck formatting guide before choosing it as an install target.
Plan capacity before buying another card
Use the storage planner to total the games you actually want installed, then reserve working room for patches and temporary files. Capacity should solve a real library constraint; a new card will not fix a damaged slot, an unmounted library, or a game that needs repair.
512GB A2 microSDXC cards
Compare seller reputation, warranty, return policy, genuine capacity, UHS-I compatibility, and A-class markings. No marketplace result is automatically endorsed.
Sponsored search1TB A2 microSDXC cards
Compare seller reputation, warranty, return policy, genuine capacity, UHS-I compatibility, and A-class markings. No marketplace result is automatically endorsed.
Sponsored searchUSB-C UHS-I microSD card readers
Compare seller reputation, warranty, return policy, genuine capacity, UHS-I compatibility, and A-class markings. No marketplace result is automatically endorsed.
For card labels and buying checks, read the Steam Deck microSD speed and compatibility guide and the microSD gear guide.
Frequently asked questions
Can I move an installed Steam Deck game to a microSD card?
Yes. When SteamOS recognizes a formatted microSD card as a Steam storage location, use the current SteamOS Storage controls to select an installed game and move it between internal storage and the card. Menu labels can change, so read the destination and free-space summary before confirming.
Will moving a Steam game to microSD delete my save?
The Steam storage move is intended to relocate installed game data, not erase a save. Still, verify Steam Cloud status where the game supports it and back up irreplaceable local saves, mods, screenshots, and non-Steam files. Not every title or file is covered by Steam Cloud.
Can I remove the microSD card after moving games to it?
Only after downloads, updates, shader processing, and moves have stopped. Use the current SteamOS eject or safe-removal control when available, then remove the card. Games stored on it will be unavailable until that library card is reinserted and recognized.
Why is Move Content unavailable or greyed out?
The destination may lack enough free space, the card may not be mounted as Steam storage, another download or update may be using the game, or SteamOS may need a restart. Confirm the card appears in Storage, pause other activity, and leave extra working space before retrying.
Is a game slower from microSD than the internal SSD?
The internal NVMe SSD has more performance headroom, but the practical difference varies by game and workload. Large streaming-heavy games, frequent updates, and file-heavy installs are stronger SSD candidates. Do not treat a card label as a guaranteed loading-time or frame-rate result.
Can I share one Steam Deck microSD library between two Decks?
A compatible card may be recognized by another Steam Deck, but account access, game ownership, updates, shader data, compatibility layers, and local saves still matter. Shut down or safely eject before moving the card, and verify one game before relying on the library away from home.
Sources and method
Valve’s Steam Deck technical specifications, Steam Deck basic-use support, and Local Network Game Transfers support pages were fetched on September 4, 2026. Valve establishes the Deck’s microSD capability and the supported local-transfer feature; the SD Association source explains Application Performance Class. The ordered storage-move and recovery workflow is conservative editorial guidance. No transfer-speed benchmark, failure rate, game-specific loading result, search volume, or hands-on card claim is fabricated.
