ROG Ally storage guide

How to move ROG Ally games to microSD without losing the library

Use the game launcher’s storage tools—not a blind folder drag—to move an installed game from an original ROG Ally or ROG Ally X to microSD. This source-informed workflow protects the old install until the new library is recognized and the game launches. It is not a card benchmark or a promise that every launcher exposes the same controls.

Safe sequence: check saves → verify the card and free space → add a launcher library on microSD → move one small game → verify files → launch it → restart the launcher → only then move the next title.

Before moving anything: identify the model and storage path

ASUS lists a UHS-II-compatible card reader on both the original ROG Ally and ROG Ally X, supporting SD, SDXC, and SDHC media. The internal drives differ: the published original Ally configurations use an M.2 2230 PCIe 4.0 NVMe drive, while the listed Ally X configuration uses a 1TB M.2 2280 PCIe 4.0 NVMe drive. Those specifications confirm the available storage interfaces; they do not establish a game’s load time on a particular card.

Open File Explorer → This PC and record three things before proceeding: the microSD drive letter, its displayed capacity, and the free space on both the card and internal drive. If the card is absent, disconnects, reports the wrong size, or contains files you cannot replace, stop and use the ROG Ally microSD troubleshooting guide before attempting a move.

The pre-move safety gate

1 · Save data

Confirm cloud sync and local backups

Exit the game normally. Check the launcher’s cloud status when available, then copy irreplaceable local saves or mods separately. Moving an installation is not the same as backing up user data.

2 · Card health

Prove capacity before trusting it

Use a reputable card and seller, confirm the expected Windows capacity, and validate a new or suspicious card before placing the only copy of anything on it.

3 · Working room

Leave space on both drives

Launchers may need room for downloads, unpacking, shader data, patches, and temporary files. Do not plan a move that leaves either drive effectively full.

4 · Stable power

Plug in and close active games

Use a known-good 65W USB-C power path, pause other large downloads, and do not sleep, restart, eject the card, or unplug storage during the transfer.

Use the storage planner to total the active library and preserve update headroom. Microsoft’s Windows storage guidance also recommends reviewing categories and removing unused content when freeing space; moving every title should not be the automatic answer.

Move a Steam game to microSD

Steam’s interface changes over time, so follow the current labels rather than treating this as a screenshot-perfect script. The safe concept is stable: make the card a recognized Steam storage location, ask Steam to move the title, and let Steam update its own records.

Open Steam’s storage settings. In the desktop client, open Settings and locate Storage. If the card is not listed, add its drive or create/select a Steam library folder on it.
Verify the destination. Confirm the path is on the microSD drive letter you recorded—not another external drive or a folder on the internal SSD.
Start with one small, non-critical game. Select the installed title and use Steam’s move control to choose the microSD library.
Wait for completion. Keep Steam open and the card inserted. Do not manually delete the original folder while Steam is working.
Verify through Steam. If Steam offers file verification for the title, run it after the move, especially if the transfer was interrupted or Windows reported an error.
Launch and test. Start the game, load a save, close it normally, restart Steam, and launch once more. Confirm cloud synchronization completes where the title supports it.

Valve’s support documentation covers moving Steam installations and games. Prefer Steam’s current storage-management path because it maintains the library metadata. Avoid copying only a game folder and assuming Steam will discover it automatically.

Xbox app, Epic, EA, Ubisoft, and other launchers

Windows handhelds can have several independent library managers. A storage location added to Steam does not configure the Xbox app or another publisher launcher. Treat each launcher as a separate system.

What the launcher offers	Safest action	What to verify afterward
A built-in Move or Change location command	Use it and select the microSD destination inside that launcher	Installed status, launch, update path, save/cloud status
A backup plus restore/import workflow	Create the backup, verify it, then restore to the card through the launcher	Launcher recognizes files without a full duplicate download
Locate, discover, or verify existing files	Follow that launcher’s current official instructions exactly	Correct folder, manifest, permissions, anti-cheat, update succeeds
No supported move or locate control	Back up saves, uninstall the game through its launcher, set the card as the new install location, then reinstall	Save recovery and a clean launch before deleting backups

Do not assume Windows Apps settings can move every desktop game. Some packaged apps expose a Move button; many traditional launcher-managed games do not. If a publisher’s current support instructions conflict with a generic workflow, use the publisher’s instructions for that title.

How to verify the move before reclaiming space

Location: the launcher reports the game inside the microSD library, and the card’s used space increased by a plausible amount.
Integrity: the launcher’s verify/repair operation finishes without repeatedly redownloading the same files.
Launch: the game starts from the normal launcher shortcut after a launcher restart—not only from an executable opened in File Explorer.
Saves: a known save loads, and cloud synchronization shows no unresolved conflict where supported.
Updates: a queued patch recognizes the destination and has enough temporary working room.
Removal behavior: after closing the game and launcher, the card can be removed safely; when reinserted, Windows assigns the expected drive letter and the launcher restores the library.

Do not use the Recycle Bin as the verification step. Let the launcher complete its move and prove the new install. If an abandoned duplicate remains, identify it against the launcher’s reported path before deleting anything.

If the moved game appears uninstalled

Do not format the card or point the launcher at a new empty folder.
Confirm the card is mounted in Windows and still has the expected drive letter and occupied space.
Open that launcher’s storage/library settings and re-add the existing library location when supported.
Use the launcher’s locate, discover, verify, repair, or import function if it provides one.
If the drive letter changed, close the launcher before correcting it in Windows Disk Management; do not choose a letter already used by another device or network location.
When files remain readable but the launcher cannot adopt them, preserve saves and personal files before using the launcher’s documented reinstall path.

If multiple cards rotate through the Ally, give each card one purpose and avoid reusing the same library folder name for unrelated launchers. Close all launchers before swapping cards. A launcher updating in the background can write to a library even when no game window is open.

Which games should stay on the internal SSD?

This site has not benchmarked these cards or titles. Use a small personal comparison instead of a blanket “all games work the same” claim. Keep a game on the SSD when its publisher requires internal storage, the launcher behaves unreliably with removable media, updates repeatedly fail, streaming stutters or load times are materially worse in a repeatable test, or the title is too important to lose when the card is absent.

microSD is most useful as deliberate overflow: smaller or less frequently updated games, installers you are willing to redownload, and titles that pass your own launch/update test. The SD Association’s A1/A2 Application Performance Class describes minimum random and sequential performance criteria; it does not prove authenticity or guarantee a specific game result.

microSD shopping checks—not performance promises

ASUS lists UHS-II reader support, but a faster interface label alone does not establish value for a particular game. Compare capacity, the card’s own bus and speed-class markings, a reputable manufacturer and seller, return policy, warranty, and a full-capacity validation plan. Do not buy from a marketplace capacity/price claim that appears implausible.

UHS-I A2 microSD cards for original ROG Ally

Verify the exact card, seller, capacity, UHS interface, warranty, and return policy. No load-time or FPS result is implied.

UHS-II microSD cards for ROG Ally X

Verify the exact card, seller, capacity, UHS interface, warranty, and return policy. No load-time or FPS result is implied.

USB-C microSD readers for file recovery and card checks

Verify the exact card, seller, capacity, UHS interface, warranty, and return policy. No load-time or FPS result is implied.

Disclosure: these are broad Amazon searches, not named recommendations or live-price claims. Handheld Settings Lab appends an Associates tag only when a real tag is configured. Continue with the microSD gear checklist and microSD versus SSD guide before buying.

Frequently asked questions

Can I move Steam games from ROG Ally internal storage to microSD?

Yes. Add the mounted microSD card as a Steam storage location, select the installed title in Steam’s storage settings, and use Steam’s move control. Menu wording can change with client updates. Keep the Ally powered, do not remove the card during the move, and launch the game from the new location before deleting or repurposing any old files.

Should I copy a ROG Ally game folder in File Explorer?

Use the launcher’s move or locate-existing-files workflow whenever it offers one. A manual copy can leave the launcher database, manifests, permissions, anti-cheat components, or update path pointing to the old location. File Explorer is useful for inspecting capacity and backing up personal files, not as the default game-library migration tool.

Will my game saves move with the installed game?

Do not assume so. Saves may be synchronized by the launcher, stored in Documents, AppData, Saved Games, or another per-user folder, while some games keep local data elsewhere. Confirm cloud-sync status where available and back up irreplaceable local saves separately before moving, uninstalling, or formatting anything.

Why is the move-to-microSD option missing?

First verify that Windows sees the card with a drive letter and expected capacity. Then confirm that the launcher has a library or install location on that drive. Some launchers or games do not expose a move command; use that launcher’s documented backup, uninstall/reinstall, or locate-existing-files process instead of dragging folders blindly.

Can I remove the microSD card after moving games to it?

Only after closing the game and launcher activity that may be reading or updating the card, then using Windows safe-removal behavior when offered. The moved games will be unavailable while the card is absent. Reinsert the same card and confirm its drive letter and library path before launching.

Is microSD as fast as the ROG Ally internal SSD?

This guide does not claim equal performance or provide fabricated load-time data. ASUS lists PCIe NVMe internal storage and a microSD reader; those are different storage paths. Results vary by card, reader, game access pattern, updates, free space, temperature, and background activity. Keep games sensitive to storage performance on the SSD when a repeatable comparison shows a meaningful problem.

Sources and method

The five public sources below returned HTTP 200 on September 5, 2026. ASUS supplied the official original Ally and Ally X storage and card-reader specifications. Valve supplied its game-migration support reference. Microsoft supplied Windows storage-cleanup context, and the SD Association supplied the meaning of Application Performance Class. The launcher sequence is conservative editorial guidance designed to preserve the old install until the moved copy is verified; no transfer-speed, load-time, FPS, card-endurance, or hands-on claim was fabricated.

After storage is stable: use the ROG Ally game-settings hub to tune resolution, frame target, and power mode one game at a time. Moving storage is capacity work, not an FPS upgrade.