Share the handheld, not necessarily the adventure
You can take turns using one retro handheld without wanting to share one campaign. The buying question is whether the exact game and installed software provide an understandable way to keep your progress separate. A numbered emulator state slot is not automatically a user profile.
Start with the game's own separate files where supported, or a documented configuration that genuinely separates each person's progress. If neither is established, do not improvise with valuable saves. A second device may make sense for simultaneous use or personal ownership, but more storage alone does not create two protected accounts.
The enjoyable part: two discoveries, one familiar console
One person might return to a story over several evenings while another explores a different classic during lunch. Or both might enjoy the same release at their own pace. Taking turns can be part of the pleasure when everyone knows which adventure they are opening.
That is different from cooperating inside one campaign, passing a controller after a failed attempt or playing simultaneously. Decide which experience you actually want before purchasing hardware to solve a problem you may not have.
First decide what belongs to whom
For a shared campaign, agree that both people are advancing the same adventure. For independent campaigns, identify two distinct progress records and the actual way each is selected. For separate games, check their saving arrangements without assuming every title stores data the same way.
Also decide who may change settings. A personal button preference, a global emulator option and a campaign save are different things. Having separate game files does not establish that controls, automatic loading and every configuration preference are isolated too.
1. Three meanings of a save slot
| What you see | What it can mean | What it does not establish |
|---|---|---|
| A file choice inside the game | The release provides its own progress records. | Every record, unlock or setting is separate; check the exact game. |
| A numbered emulator state | A snapshot selected through the emulator. | A separate user account, private storage or independent backup. |
| A launcher entry or favorite | A convenient way to find content. | A distinct underlying save destination merely because the label differs. |
| A documented user or isolated configuration | A software-specific separation mechanism. | That it exists on every handheld or delivered firmware. |
Libretro documentation distinguishes saves made inside a game from emulator snapshots, and separately documents state-slot controls. Use that distinction to ask better questions, not as a universal set of R36S instructions. An installed emulator, its version and its actual settings still matter.
2. The game's own files are the first place to investigate
If the exact release supports multiple independent adventures, learn what its file-selection screen shows and what choosing a file actually changes. Look for meaningful identifiers such as the character name, progress or location, where the game supplies them.
Agree which record belongs to each person and which actions replace or erase it. Do not test an unfamiliar New Game or file-management command on someone's valued campaign. A name on a piece of paper can help organize a supported system, but it does not add a password or overwrite protection.
Some releases handle progress differently. Do not generalize a familiar three-file menu to an entire platform or franchise. The original release, edition and mode are the useful reference, not simply the character on the box.
3. Why two state numbers are not two accounts
Reserving one state number for each person may look tidy, but it is not enough to establish independent campaigns. You still need to know which state is selected, whether automatic loading bypasses that choice and how loading and saving interact with the game's normal progress.
The RetroArch menu documentation lists separate state, automatic-load and SaveRAM-related settings, including an option about not overwriting SaveRAM when loading a state. This is why we do not present a generic slot-number recipe as guaranteed separation. Actual behavior depends on the configuration and core.
Do not randomly toggle those settings to experiment with valuable progress. Follow matched documentation and establish a low-stakes routine first. A state on the same active card is also not an independent backup of that card.
4. A shared-handheld acceptance check
Once a documented suitable method is identified, use disposable new progress, not an existing important campaign, to verify the complete handover. Follow the actual game's and device's instructions for saving, exiting and reopening.
- Identify the setup. Note the exact release, emulator or core, firmware and relevant save method.
- Create player A's test progress. Use an identifiable low-stakes point and the supported saving routine.
- Open player B's intended record. Confirm it is genuinely different before advancing or saving.
- Return to player A. Reopen through the agreed routine and identify the expected checkpoint.
- Return to player B. Confirm that record also remains correct after the second handover.
- Write down the successful routine. Keep the method understandable and preserve suitable independent copies before valuable use or changes.
This is a proposed acceptance check, not a test performed for this article. A successful result would establish the observed configuration, not permanent protection across every game, future update or mistake.
5. Choose one device when turn-taking actually works
Keeping one handheld can be a sensible first choice when the games fit, a supported progress arrangement is clear and you are happy to alternate sessions. There is no need to buy a second console merely because two people enjoy classics.
A short handover note can record whose turn it is, which game record to open and whether an agreed setting changed. It should not contain passwords or become a substitute for checking the correct campaign before saving.
Keep the routine simple enough for both people to use. If only one person understands an elaborate file arrangement, it may be unsuitable for the household even if technically possible. Ease of ownership is a real preference, not a test score.
6. When separate devices earn their cost
Separate physical units are worth considering when both people want to play at the same time, want their own device available away from home or prefer not to negotiate a shared setup. Those are concrete benefits beyond nominal storage.
They still need identification, ordinary saving and backups. Two units do not automatically transfer a campaign, synchronize it or connect for multiplayer. For moving existing progress, use the existing-save migration guide as a separate buying question.
If the goal is simultaneous play together, establish the exact game's mode and complete controller or connection route. Buying two identical handhelds is not proof of that route.
7. An exact R36S budget, without a false upgrade
The current R36S offer is a compact candidate for suitable classic games. It lists a 3.5-inch IPS screen at 640×480, RK3326, 1GB DDR3L and a Linux-based environment with ArkOS community firmware. None of those facts certifies independent user profiles on the delivered build.
| Order idea | Device subtotal | What the spending changes |
|---|---|---|
| One R36S, Bundle: 64G | $79.99 | One physical console to share, if its routine fits. |
| One R36S, Bundle: 128G | $89.99 | More nominal storage, still one physical console. |
| Two R36S, both 64G | $159.98 | Two physical units, not certified linked multiplayer. |
| One 64G and one 128G | $169.98 | Separate units with different nominal capacities. |
| Two R36S, both 128G | $179.98 | Separate units and the larger storage choice. |
These are arithmetic device subtotals, not bundle discounts or delivered totals. Shipping, taxes and any other applicable checkout items are separate. The offer's complete fourteen variants were available for sale when checked; that is not a stock reservation.
Each capacity is listed in Purple, Black, White, Red, Yellow, Green and Blue. Different colors can help you identify two physical units, but they do not create separate profiles on one unit or change performance. Do not use color as proof of a particular firmware revision.
Review current R36S options8. Choose the games before the extra hardware
For two people exploring different suitable classics, game choice may make turn-taking easier than insisting on the same adventure. For two people who specifically want independent runs of one release, its progress system becomes a purchase condition.
The R36S listing positions GBA, SNES and PS1-oriented classic play as relevant directions. This article does not certify a named game's performance or inclusion. N64 and PSP results remain title-dependent; do not select it for Android apps or PS2 games.
A favorite franchise can span very different platforms. Identify the exact release and the meaningful actions you want, rather than expecting a bigger card or a second unit to make an unsuitable version work. Screen artwork in this guide is presentation, not a compatibility demonstration.
9. Make the handover sustainable
Agree on who handles non-routine maintenance, what must be preserved before changes and how both people recognize their own progress. Do not reformat storage, replace firmware or rename another person's files to make a surprise shared setup.
Use the delivered revision's instructions for power and shutdown. USB-C is not a charging-voltage or fast-charge specification. Do not remove storage while it is active or writing, and confirm any needed cable, adapter, reader or case separately from the photographs.
If the console is a gift, ask whether the recipient wants shared ownership. A shared gift does not require shared progress, and an independent gift should not silently create an ongoing technical job for someone else.
10. Keep a working setup when it meets the need
If you already alternate happily and can reliably recognize both campaigns, there is no demonstrated need to replace the device. Invest time in a clear routine and appropriate preservation rather than treating another purchase as automatic progress protection.
If simultaneous use is the real frustration, extra storage will not resolve it. If independent progress is the only unresolved issue, establish the supported software arrangement before deciding that two consoles are necessary.
For the separate question of sound, screen light and interruptions around other people, use the shared-space buying guide. Being considerate in the room and keeping two campaigns separate are different tasks.
Shared-device questions
Can two people have separate progress on one handheld?
It depends on the exact game's files and the installed software. Establish the supported separation method and check a low-stakes handover; the device name alone is not enough.
Are save-state slots separate user accounts?
No automatic account separation is established. State selection, normal save data and automatic loading can have different roles.
Is a favorite or duplicate launcher entry a separate campaign?
Not by its label alone. Confirm what underlying content and save location it actually uses, without altering valuable files as a guess.
Does 128G make shared saves safer?
No such protection follows from capacity. It provides more nominal storage, not separate accounts, independent backups or immunity to overwriting.
Do two R36S devices guarantee multiplayer?
No. Simultaneous independent use and a connected multiplayer mode are different requirements. The latter needs a verified complete route.
Will every R36S have the same menus?
No fixed firmware or universal menu path is promised. ArkOS builds and emulator configurations can differ; follow the actual delivered setup.
What should we buy if we are unsure?
First resolve the essential shared-progress method. Keep a working device if it fits; choose separate units for a wanted personal or simultaneous-use benefit, not an unverified software promise.
Are pictured games, stand and accessories included?
The photographs do not establish those inclusions. Check the current selected package and exact content separately.
Sources and limits
By iGameConsole Editorial Team. Current product description, all fourteen variants and all fourteen media records were reviewed October 31, 2026. The three selected existing images were viewed individually. They illustrate complete-device, in-hand and control roles, not a shared-save test, new measurement or supplied-title inventory.
Technical distinctions draw on Libretro's save-file and state definitions, its saving-menu map and state-slot controls. These general references do not certify the current R36S build. No user-profile isolation, campaign handover, recovery or multiplayer test was performed for this article.
Buy for the way you want to share
One handheld can be enough when turn-taking and the supported progress routine work for both of you. Two can be worthwhile when each person wants their own physical console or overlapping playtime. A bigger card answers a storage need, not that ownership decision.
Confirm the games and save method first. Then choose the actual number of units, capacity and finish that meet the need.
Check the exact R36S selectionThis link opens the product. It does not select a variant, add units to a cart, reserve availability or confirm a shared-save configuration.
