Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11The safest way to move progress between retro handhelds is to copy the source save before changing anything, identify whether it is an in-game save or an emulator save state, and place the copy in the destination emulator’s configured save directory. File extensions, folder names, capitalization rules and compatibility depend on the firmware, emulator and core, so a path that works on OnionOS is not a universal map for every handheld.
Use an in-game save whenever possible for a cross-device move. Save states are tied more closely to a particular emulator and core and can overwrite newer memory-card data when loaded. Verify the destination by launching the game and checking the expected progress before deleting the original.
As an Amazon Associate I earn from qualifying purchases.
What you are actually transferring
Retro emulators commonly keep two different kinds of progress. Treating them as interchangeable is the most common cause of a transfer that appears to have failed.
In-game save files
An in-game save is created through the game’s own menu or checkpoint system. The emulator writes the game’s save data to a file, often beside other files managed by the same core. Because the game, rather than the emulator session, defines the data structure, an in-game save is usually the best choice when moving to another handheld that runs the same game with a compatible core.
#1 Best Overall
- 【Ultra-Fast Data Transfer】Experience blazing-fast 5Gbps data transfer with this USB 3.0 SD Card Reader, ensuring quick and efficient file transfers for photos, videos, and other media. Backward-compatible with USB 2.0 for added flexibility. Easily review and transfer data from security cameras, wildlife monitors, or car cameras, gopro without hassle(📌Note:only reads and transfers data from the SD and TF card, not directly connect to the camera)
- 【Simultaneous Dual-Card】Save time and boost productivity with dual card slots that allow simultaneous reading and writing on both microSD and SD cards. USB-A and USB-C dual header design makes the micro SD Card Reader perfect for photographers, video editors who need quick and efficient file management(📌Note:Thick cases may prevent full insertion）
- 【Compact & Travel-Friendly】Designed for convenience, the slim and lightweight card reader for camera memory card fits perfectly in your camera bag or laptop sleeve. Protective covers at both ends shield the ports from dust and liquid, while the attached cord keeps everything secure and easily accessible. A reliable companion for on-the-go professionals and creatives(📌Note: "SD"card and "Micro SD" card not included.）
- 【Plug-and-Play】The SD Card Reader for PC does not require driver or software installation, just connect to your device and start transferring files instantly. Compatible with Windows 11/10/8/7, macOS, and most Android devices. Crafted from heat-resistant aluminum materials, this SD Card Reader for PC delivers reliable performance and enhanced durability, even during long working(📌Note: SD Slot does not support CF express Type A/B/C Cards; SIM, XQD, MS Cards and Memory Stick）
- 【Wide Device Compatibility】The USB C SD Card Reader works seamlessly with PCs, computers, laptops, cameras, smartphones and tablets featuring USB-C or USB-A ports, including MacBook Air/Pro, XPS, iPhone 15/16, iPad Pro, Samsung Galaxy S23, Microsoft Surface, Acer Aspire, and Predator series. Perfect for quickly accessing files directly on your device without additional apps or internet connections(📌Note:Not compatible with “Lightning” port devices）
Save states
A save state captures the emulator’s working memory at a particular moment. It can restore a scene even when the game itself has no save point, but it also records emulator- and core-specific state. A state made by one core may not load in another, and a state can depend on the exact game revision, video settings or runtime conditions. Do not assume a state made on one handheld is portable simply because both devices display the same ROM.
OnionOS keeps these categories separate: in-game saves are under a saves path and states under a states path. That separation is a useful model for other systems even when their folder names differ.
Before you copy anything: a safe transfer checklist
- Close the game normally and shut down the source handheld through its operating-system menu. Removing a card while the emulator is writing can leave a partial file.
- Make a working copy of the source save on a computer or a second card. Leave the untouched original in place until the destination loads the expected progress.
- Record the exact ROM filename, including capitalization and extension. Many emulators derive the save filename from that name.
- Identify the emulator and core used on the source and destination. A matching core gives a state the best chance of working; an in-game save may still require a compatible format.
- Check free space on the destination card and confirm that it is mounted read/write.
- If your computer lacks a suitable card slot, a USB microSD card reader can provide the connection. OnionOS documentation warns that bundled cards and readers can be prone to corruption or failure, so do not treat the bundled hardware as your only backup.
The documented procedures support copying individual files. They do not establish a universal, full-card imaging procedure for every handheld, so do not assume that cloning one card will recreate another device’s folder layout or firmware settings.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Manual transfer method: SD card or computer
Manual copying is the most transparent method when you can access both cards. It lets you inspect filenames, preserve an original and correct a path without involving a synchronization service.
- Make the source save. Use the game’s own save menu, wait for the write to finish, then exit the game. If you need a state as well, create it after the in-game save and keep the two files in separate backup folders.
- Remove the source card safely. Power down completely before taking out the card. Insert it into the computer and open the card’s save directory rather than searching only the ROM folder.
- Copy, do not move. Copy the relevant save file to a dated backup folder on the computer. Keep the original filename and capitalization. A filename such as
GameName.srmis not equivalent to a differently capitalized name on systems that treat names as case-sensitive. - Prepare the destination. If the destination already has a save with the same name, copy that file elsewhere before replacing it. This gives you a rollback if the transferred progress is older or incompatible.
- Place the file in the configured directory. Follow the destination firmware’s documented path and its emulator/core naming convention. Do not create a second, guessed folder merely because it looks plausible.
- Test before cleanup. Start the game, load through its normal menu and confirm a known checkpoint, inventory item or play time. Only after that test should you consider removing an old destination copy.
If the destination shows no progress, stop and preserve both copies. Check the extension, filename, capitalization, selected core and actual save directory before trying another conversion or replacing more files.
OnionOS: importing an in-game save
OnionOS provides a specific convention for most imported in-game saves. The instructions below apply to OnionOS documentation; they are not a generic path for unrelated firmware.
Use the core-specific profile folder
Most imported in-game saves should use the .srm extension. Name the file exactly like the ROM, preserving capitalization, and copy it to:
Rank #2
- 【Dual Slots Design】 - This usb sd card reader has Micro SD Card Slot and SD Card Slot with USB 3.0 plug, It could easily transfer the file you need between different devices or review the photos/videos quick.
- 【5Gbps Speed】 - Extremely fast transfer speed allows you to transfer more files in less time, reducing waiting time, suitable for photographers, studios, and those who need to transfer large files
- 【Wide Compatibility】 - Memory card reader compatible with Windows system , Mac OS system , Linux and Android. Support SD, MMC, SDHC, DV, Micro SD, T-Flash card.
- 【Plug and Play】 - Memory card reader for computer and laptop, which can be transmitted through the SD card reader without driver. What’s more, card reader not only relieve the pressure of mobile memory , but also share photos and videos with family and friends anytime and anywhere.
- 【Compact and Portable】 - This USB card reader body is lightweight , strong heat dissipation and cost-effective. Multifunction card reader for any devices with USB port.
Saves/CurrentProfile/saves/[CORENAME]
Replace [CORENAME] with the core that runs the game. The bracketed text is a variable, not a literal directory name. If the ROM is named ExampleGame.zip, the save’s base name should match the ROM’s base name according to the core’s convention; do not add a second game name or a random suffix.
When the source file is .sav
OnionOS says a .sav file may be renamed to .srm. Renaming changes the extension only; it does not convert the internal data. If the original format is something else, the data may require conversion, and a simple rename may not work. Keep the original extension in your backup so you can return to it if the renamed copy is rejected.
Clear a stale state when the save is ignored
If you launched the game on OnionOS before importing the in-game save, a matching state can take precedence or prevent the new save from appearing. Preserve a backup, then remove the corresponding file from:
Saves/CurrentProfile/states/[CORENAME]
Reinsert the card or restart the system, launch the game and use its normal load option. Delete only the state associated with that game; removing an entire states directory would discard unrelated progress.
Recommended Free Tools
Moving saves from an older Miyoo stock card
OnionOS documents a legacy location for saves originating on a Miyoo stock SD card or an early Onion installation:
RetroArch/.retroarch/saves/[CORENAME]
That legacy path is a source location, not the current destination for a normal OnionOS profile. Copy the save out of the legacy folder, apply the required extension and exact filename, and place it in Saves/CurrentProfile/saves/[CORENAME] on the current system. Keep the legacy file unchanged until the game has loaded successfully.
If the old card contains several similarly named files, match each one to its ROM and core. Copying every file into a new folder can introduce collisions or cause a game to read data from the wrong revision.
Rank #3
- Simultaneously read and write on two cards to save yourself the effort of constant unplugging and re-plugging.
- USB 3.0 enables data transfer rates of up to 5Gbps for faster sync times, backward compatible with USB 2.0 / 1.1.
- Fully powered via your USB port — no additional power supply required.
- No drivers required for Windows 10/ 8 / 7 / Vista or Mac OS X 10.2 and above.
- Package contents: Anker SD/TF Card Reader, hassle-free 18-month warranty.
Save states: when they work and why they fail
Best-case compatibility
A state has the best chance of opening when the destination uses the same emulator, the same core, the same ROM revision and a sufficiently similar configuration. Even then, test it from a backup rather than making the state your only copy of progress.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsCross-core and cross-device limits
Different cores can represent CPU, timing, controller and memory information differently. A state file that is accepted by another core may restore incorrectly, freeze or return to the wrong scene. For a move between unlike handhelds, load the in-game save instead and create a fresh state on the destination.
PCSX ReARMed memory-card risk
PCSX ReARMed documentation describes a specific hazard: loading an old state can overwrite the memory-card save. Its settings include an option to prevent SaveRAM from being overwritten when a state is loaded. If you use this core, review that setting before opening an old state, and retain a separate copy of the memory-card file. The setting protects the card data from the state-loading operation; it does not make a state portable to another core.
Choosing a transfer method
| Method | Data best suited to it | Compatibility requirement | Main overwrite risk | When to choose it |
|---|---|---|---|---|
| Manual card or computer copy | In-game save files; states when the emulator and core match | Correct extension, exact filename and destination directory | Replacing a newer destination file or deleting the only original | One-time moves, troubleshooting and controlled backups |
| OnionOS profile import | Most in-game saves converted to the expected format | Core-specific folder, matching ROM name and usually .srm |
A stale state can prevent the imported save from appearing | Moving progress into an OnionOS profile |
| RetroArch Cloud Sync | RetroArch-managed saves and states | Both installations configured for the same sync service and manifest | Direct edits can desynchronize or corrupt the managed sync state | Keeping multiple RetroArch devices aligned over time |
| State-only transfer | Short-term continuation at an exact emulator moment | Usually the same core, game revision and compatible runtime | Loading a state can replace newer SaveRAM on some cores | Same-system continuation when an in-game save is inconvenient |
The table’s compatibility conditions are practical safeguards, not guarantees. The documentation does not establish a universal success rate for any method.
Using RetroArch Cloud Sync safely
Libretro’s Cloud Sync workflow manages save files and states through a manifest that tracks hashes. That manifest records what the sync system believes is present and current.
Let RetroArch manage synchronized files
Configure Cloud Sync through RetroArch on each device, authenticate the same service, and allow the synchronization process to complete before launching a game on the other handheld. The exact menu labels and service requirements can vary by RetroArch build, so use the labels shown by your installed version.
Do not edit managed files behind its back
Directly renaming, replacing or deleting files that Cloud Sync tracks can leave the manifest out of step with the card. If you must recover a file manually, first make an independent backup, then use the sync workflow to reconcile the devices rather than repeatedly editing the managed directory. Cloud synchronization is not a substitute for an offline backup; keep a separate copy for important progress.
Rank #4
- Super-Speed Data Transmission: Transfer a weekend’s worth of travel photos, 4K Trail Camera footage, or large project files in seconds with this Micro SD card reader — thanks to SuperSpeed USB 3.0 up to 5Gbps
- Built for Photographers on the Move: Slim, lightweight, and stylish — this UGREEN SD card reader USB C is designed to fit easily in your camera bag or laptop sleeve. A reliable companion for photographers, videographers, and content creators on the go
- Easy to Use: Plug-and-play with no drivers or power needed—just connect and transfer files instantly. Compatible with Windows, macOS, and most Android devices
- 2-in-1 USB C & USB A: This USB C SD card reader with dual interfaces combined in one compact design offers versatile connectivity and convenience, compatible with PC laptops, tablets, iPhone 15/16/17 Pro/Pro Max, and other USB-C & USB-A devices
- 2 Cards Work Simultaneously: UGREEN Micro SD Card Reader Adapter is able to read SD and microSD cards at the same time, which helps to avoid repeatedly plugging/unplugging and improves your efficiency
Resolve a conflict deliberately
When two devices have changed the same game, determine which checkpoint is newer before accepting a replacement. Save the current files from both devices into separate folders, compare their timestamps and in-game progress, and only then allow one version to become the synchronized copy. A timestamp alone can be misleading after a card is copied, so verify inside the game.
How to find the right save directory on another firmware
There is no single save path shared by every retro handheld, Android emulator, Linux image or standalone emulator. Use the device’s own configuration instead of copying the OnionOS example verbatim.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →- Open the emulator’s settings and look for labels such as Save directory, SaveRAM, Save files or System directory.
- Check which core or standalone emulator is assigned to the game. The active core often determines the final subfolder.
- Create a disposable in-game save, exit, and inspect which file changed. This identifies the live directory without guessing, provided you first backed up existing data.
- Compare the new file’s base name and extension with the ROM. Record the result for future transfers.
- Copy the backed-up source file into that directory, preserving the naming convention, and test the game.
If the emulator hides its storage on Android or another restricted system, use its built-in directory picker or documentation rather than moving files into an arbitrary visible folder. A file manager may show a path that the emulator cannot access.
Troubleshooting a save that does not appear
The game starts with no progress
- Confirm that the ROM and save have the same base name and required capitalization.
- Check that the extension is the one expected by the core. On OnionOS, most imported files are expected as
.srm; a rename from.savis permitted, but other formats may need conversion. - Verify that the file is in the active core’s directory, not a similarly named folder for another core.
- On OnionOS, check for and back up a matching state under
Saves/CurrentProfile/states/[CORENAME], then remove that state if it is blocking recognition. - Make sure the destination is running the same game region or revision. A save from a different revision may be incompatible even when the visible title is identical.
The emulator reports a corrupt file
Return to the untouched source copy. A corrupt destination copy should not be repeatedly opened or renamed. If the original also fails, the format may be unsupported or the source file may have been damaged before transfer. Look for a documented conversion path for that emulator and retain the original while testing any converted output.
The game loads an older checkpoint
Do not overwrite more files. Check whether a state, memory-card image or cloud-sync copy contains the older data. For PCSX ReARMed, loading an old state can overwrite SaveRAM; protect the memory-card file and use the core’s SaveRAM-overwrite prevention setting before testing states.
The card is unreadable or files keep changing size
Stop using that card as the only copy. Copy whatever remains readable to a separate location, safely eject it and test with another reader if available. The OnionOS FAQ’s warning about bundled cards and readers is a reason to keep independent backups, not evidence that every bundled device will fail.
How to organize backups for future moves
A small, consistent naming scheme prevents confusion when several handhelds use the same library. For each game, store the original save, any converted save and any state in separate subfolders. Include the handheld, core and date in the folder name, for example GameName/OnionOS-CoreName-2026-10-16/. Do not rename the actual save file unless the destination requires it; put descriptive notes in the surrounding folder.
Best Value
- 【USB 3.0 + USB C】 Both interfaces support high-speed data transfer up to 5 Gbps, allowing you easily transfer 1G files in seconds. Dual Card Slots, support SDXC, SDHC, SD, MMC, RS-MMC, Micro SDXC, Micro SD and Micro SDHC cards from Camera/ Gopro/ Dash Cam/ Surveillance camera. Backwards compatible with USB 2.0 and USB 1.1. (📌Note: "SD"card and "Micro SD" card not included.）
- 【Double duty】 Simultaneously reading and writing on two cards to save the constant plugging and pulling of plugs. Enjoy fast photo downloads, smooth video editing and fast 3D Printer file transfers. Double your productivity with simultaneous microSD/SD card access. View recordings of your security cameras, wildlife monitors, private surveillance cameras and car monitors instead of bringing them home to you.(📌Note:only reads and transfers data from the SD and TF card, not directly connect to the camera)
- 【Plug and Play】uni Card Reader for camera memory card has handy covers at both ends to keep out liquid and dust. Its slim profile makes it easy to store in your camera bag or backpack, and the useful cord keeps it from getting lost and provides convenient access to micro/SD cards when needed. No driver is required in Windows 11/10/8/7/Vista or Mac OS X 10.2 and later. No additional power supply is required. (📌Note:Not compatible with “Lightning” port devices）
- 【Wide Compatibility】Compatible with iPhone 15 Pro/Pro Max, MacBook Pro (2023~2016), MacBook (2022~2015), iMac Pro (iMac), Acer Aspire Switch 12S/R13, Predator 15/17X, XPS 13/15/17, Alienware 13/15/17, Spectre x360, Microsoft Surface Pro, Book 2, Razer Blade 15/Stealth 13/Pro 17, Samsung Galaxy Tab Pro, S23/ S22 Ultra/ S21/ S20 and most other USB-C / A devices. (📌Note: SD Slot does not support CF express Type A/B/C Cards; SIM, XQD, MS Cards and Memory Stick）
- 【No Camera Software Required】uni high speed Memory Card Reader connects directly to your Android phone's USB-C port, allowing you to instantly view your footage and manage photo videos without the need for additional apps or Wi-Fi connections. Share your experiences in real-time and never miss an exciting moment again! uni Micro SD USB Adapter with 24/7 customer service and effortless 18-month 𝗐𝖺𝗋𝗋𝖺𝗇𝗍𝗒. Please rest assured we stand behind our products and customers.
- Keep one untouched source copy.
- Keep one working copy used for conversion or renaming.
- Keep a note of the ROM filename, region, revision, emulator and core.
- Record whether a file is an in-game save, a state or a memory-card image.
- After a successful import, create a fresh in-game save on the destination and back that up as the new known-good copy.
This organization makes it possible to return to an earlier version without guessing which file was modified during troubleshooting.
Practical decision guide
You are moving to a different handheld
Use the game’s in-game save. Identify the destination core and its save directory, convert only when the documentation requires it, and create a new destination state after the save loads.
You are moving to a new SD card on the same OnionOS device
Copy the current profile’s in-game saves, including the core-specific folders, then test one or two games before copying the rest. If a game was launched on the new card first, check for a stale state before judging the save missing.
You switch between several RetroArch handhelds
Cloud Sync can coordinate RetroArch-managed saves and states, but configure it on every device and avoid direct edits to files tracked by its manifest. Maintain an offline backup for recovery.
You only have a save state
Try it only when the destination uses the same core and game revision. Make a separate copy of any memory-card or SaveRAM file first, because some cores can overwrite it while loading a state. If the state fails, obtain or recreate an in-game save and continue from that instead.
What the evidence does not establish
The documented examples cover OnionOS, RetroArch Cloud Sync and one PCSX ReARMed overwrite hazard. They do not provide an authoritative folder table for every Anbernic, Android, Linux or standalone-emulator setup, and the surfaced documentation does not state universal firmware versions or a cross-device compatibility guarantee. Treat each path as specific to the named software, check the current documentation for the version installed on your handheld and verify the result in the game.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Free tools Windows power users keep installed
One-click scans. No signup required.
