✅ 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 Lenovo Legion Go 2, with Lenovo Legion Go S as a strong alternative.

Save states are bookmarks you place on purpose, and the input lag guides on this site deal with the opposite direction of time. Rewind is a third thing: a rolling recording of your last few seconds of play, kept in memory, that lets you hold one key and watch a missed jump or a wrong turn un-happen. Players describe it with a VCR metaphor, but it works nothing like a video. It is a buffer of save states, written continuously, asked for or not.

As an Amazon Associate, we earn from qualifying purchases.

That mechanism explains everything else about rewind: why it is free on an NES game and a real setting on a PlayStation game, why some emulators offer it and others never will, and why one achievement platform bans it outright. This guide covers the cost, where RetroArch and DuckStation expose it, how to tune it, and the hardware that feeds it. It assumes games dumped from your own cartridges and discs; no emulator ships with games.

This article contains affiliate links. If you buy through one of them, we may earn a commission at no extra cost to you.

Quick Answer

Rewind is a rolling buffer of save states held in RAM. The emulator snapshots the machine at set intervals, and holding the rewind key plays those snapshots backward until you let go and resume. The cost scales with the console’s state size, so rewind is effortless on NES and SNES, a tunable setting on PS1, and largely absent on PS2-class cores.

A Rolling Buffer, Not a Video

A save state is a serialized snapshot of the entire emulated machine: CPU registers, RAM, video memory, sound state, frozen into one blob. Rewind takes that snapshot automatically, again and again, at an interval you choose, and keeps the most recent ones in a ring buffer in system RAM. Hold the rewind key and the emulator loads them in reverse, fast enough that play appears to run backward. Release it and the newest snapshot is the present; everything after it is discarded.

Two consequences follow. First, rewind only exists where save states exist: a core must support serialization before any frontend can build a buffer from it. Second, the buffer is finite. When it fills, the oldest snapshots are overwritten, so your undo window is measured in seconds, set by two numbers you control: how often a snapshot is taken, and how much memory the buffer may hold.

Why the Cost Scales With the Console

A snapshot costs roughly what the original machine held in memory, and console memory grew fast. The NES worked with 2 KB of main RAM, the SNES with 128 KB, so a state from either is tiny and a buffer holds minutes of play for a few megabytes. The PlayStation jumped to 2 MB of main RAM plus 1 MB of video RAM, and its states grow further when you upscale, with the larger framebuffer the emulator tracks. The PlayStation 2 carried 32 MB of main RAM and a far more complex graphics state, where the maths turns hostile: snapshots are big, expensive to write many times a second, and its cores the least likely to support the feature.

This is not theory. DuckStation calculates the bill for you: its settings screen shows the approximate rewind duration your choices buy, with the estimated RAM and VRAM cost. RetroArch’s small default buffer, sized for 8-bit and 16-bit systems, leaves newer hardware with only a few seconds of history until you raise it.

Where Rewind Actually Lives

RetroArch is where most players meet the feature. Rewind is off by default; you enable it under Settings, then Frame Throttle, then Rewind. Three settings govern it: the toggle, a frames setting for the interval between snapshots, and a buffer size in megabytes capping the ring’s memory. The default hotkey is R, rebindable to a controller button. Per-core overrides let you disable it for one core or game only.

DuckStation exposes the same idea with its own names. Under Settings, then Emulation, an Enable Rewinding toggle sits beside a Rewind Save Frequency, how often a state is captured, and a Rewind Buffer Size, how many are kept. The project is candid about the price: the settings carry its warning that enabling rewind may significantly increase system requirements. One documented conflict matters: rewind is disabled while DuckStation’s runahead latency feature is active.

Beyond those two, the map thins out. The Libretro documentation for PCEE2, the PlayStation 2 core, lists States as supported and Rewind as not supported, and standalone PCSX2 documents save states as its time tool, with no rewind feature. Dolphin’s Libretro core lists rewind as supported, while the standalone builds are documented around save states. Past the PlayStation era, rewind becomes the exception.

The Rule That Settles the Cheating Argument

Whether rewinding is cheating depends on who keeps score, and one scorekeeper has published a ruling. RetroAchievements’ documentation states that its Hardcore mode disables save state loading, rewind and slow motion, with fast-forward as the only accepted exception. Its compliance requirements repeat the point: rewind is disabled in Hardcore, and an emulator allowing it there would fail verification. Creating save states in Hardcore is still permitted, for practice or debugging, but cannot be loaded until you leave the mode. Casual mode allows rewind, save states and cheats openly.

That split summarises the wider argument. The purist objection is real: these games were balanced around mistakes being permanent, and a bottomless undo changes what finishing one means. The other side is equally concrete. Rewind lets you repeat one hard jump forty times in a minute instead of replaying four minutes to reach it, and it is an accessibility aid for players whose reflexes or hands turn difficulty spikes into a wall. Single-player, the choice is yours; with a leaderboard involved, the rule above answers it.

Tuning: Granularity, Buffer Size and the Stutter Tax

Granularity is the smoothness dial. Capturing every frame gives frame-precise undo and the smoothest backward motion, at the highest cost. Capturing every few frames makes rewind visibly steppier and harder to stop at one exact moment, but each skipped snapshot is memory and CPU time saved, and the buffer reaches further back. DuckStation’s save frequency is the same dial under another name.

Buffer size is the memory dial, converting directly into seconds of history. A small buffer on a PS1 game may hold only a few seconds; raising it buys a longer window at a straight RAM price. Neither dial is free in the other direction. Writing a serialized state costs CPU time every interval, and the impact scales mostly with the size of the state being written, which is why a stuttering game usually calms down when you raise the granularity, shrink the buffer, or switch rewind off for that title. DuckStation’s guidance for stutter is the same: shorten the buffer or turn the feature off.

Hardware That Feeds the Buffer

Rewind spends two things: RAM for the buffer, and spare CPU cycles for the constant state-writing behind your game. Storage holds the libraries, cores and state archives around it. These five picks cover that spread.

Lenovo Legion Go 2

Lenovo Legion Go 2

Lenovo Legion Go 2

Check price on Amazon

The most rewind-friendly handheld here: its 32GB of memory is double the usual allocation, so long PS1 buffers and heavy upscaling leave memory to spare, and its eight Zen 5 cores absorb the state-writing tax.

Specs:
– Chip: AMD Ryzen Z2 Extreme, Zen 5, 8 cores and 16 threads
– Memory: 32GB LPDDR5X
– Storage: 2TB NVMe SSD, M.2 2280
– Display: 8.8-inch OLED, 1920 by 1200, 144Hz with variable refresh
– Battery: 74Wh
– System: Windows 11

See it on Amazon

Lenovo Legion Go S

Lenovo Legion Go S

Lenovo Legion Go S

Check price on Amazon

The balanced option. Its 16GB is plenty for generous buffers up to PS1, and its variable-refresh panel forgives the frame dips the serialization tax causes on a four-core chip.

Specs:
– Chip: AMD Ryzen Z2 Go, Zen 3, 4 cores and 8 threads
– Memory: 16GB LPDDR5X-6400
– Storage: 512GB NVMe SSD, M.2 2242
– Display: 8-inch IPS, 1920 by 1200, 48 to 120Hz variable refresh
– Battery: 55.5Wh
– System: Windows 11

See it on Amazon

ASUS ROG Xbox Ally

ASUS ROG Xbox Ally

ASUS ROG Xbox Ally

Check price on Amazon

The lighter route to the same feature set. Sixteen gigabytes handles 8-bit and 16-bit rewind without thought, and PS1 rewind with a sensibly sized buffer, in a lighter 60Wh body.

Specs:
– Chip: AMD Ryzen Z2 A, Zen 2, 4 cores and 8 threads, RDNA 2 graphics
– Memory: 16GB LPDDR5X
– Storage: 512GB NVMe SSD, M.2 2280
– Display: 7-inch IPS, 1920 by 1080, 120Hz, FreeSync Premium
– Battery: 60Wh
– System: Windows 11

See it on Amazon

Samsung T7 Portable SSD 1TB

Samsung T7 Portable SSD 1TB

Samsung T7 Portable SSD 1TB

Check price on Amazon

The library drive. Rewind never touches storage, but a serious multi-system library of your own disc dumps, plus the save state archives kept alongside it, outgrows internal drives quickly, and this one moves them at USB 3.2 Gen 2 speeds.

Specs:
– Model: MU-PC1T0T/AM
– Capacity: 1TB
– Interface: USB 3.2 Gen 2, Type-C
– Read speed: up to 1,050 MB/s as Samsung rates it
– Write speed: not stated

See it on Amazon

SanDisk 1TB Extreme microSDXC

SanDisk 1TB Extreme microSDXC

SanDisk 1TB Extreme microSDXC

Check price on Amazon

The card every handheld above accepts. A full cartridge-era library with room for state archives fits easily, and a card library moves between handhelds intact.

Specs:
– Model: SDSQXAV-1T00-GN6MA
– Capacity: 1TB
– Format: microSDXC, UHS-I
– Read speed: not stated
– Write speed: not stated

See it on Amazon

How to Choose

Start with the systems you actually play. If your library is NES, SNES and Genesis, rewind costs so little that any current handheld runs it with the default buffer; choose on screen and controls instead. If PS1 is your centre of gravity, prioritise memory headroom and read the DuckStation settings estimate before assuming a buffer length; 16GB machines are comfortable. Heavy upscaling grows the state, so budget the buffer accordingly. Finally, check the software first: no amount of RAM adds a feature a core does not support.

Who Should Skip

Skip rewind if you hunt achievements in RetroAchievements Hardcore mode, where it is disabled by rule and no setting can restore it. Skip it if your library is mostly PS2 and GameCube: the flagship cores document save states, not rewind, and buying hardware around a missing feature is wasted money. Skip it if you play by original-hardware rules and find the undo changes the game for the worse. And skip it on any game already struggling to hold full speed, because the serialization tax makes the stutter worse.

FAQ

Does rewind work in every emulator?

No. Rewind requires a core that can serialize its full state, and support is decided per emulator and per core. RetroArch exposes it for supporting cores, DuckStation builds it in for PS1, and Libretro’s documentation for the PCEE2 PlayStation 2 core lists rewind as not supported.

Why does my game stutter when rewind is on?

Because the emulator writes a complete machine snapshot at every interval, at a cost that grows with the state size. Raise the granularity so snapshots are taken less often, shrink the buffer, or disable rewind for that game through a per-game override.

Is rewinding cheating?

In single-player it is your call. Where a scoreboard exists, the published answer is no: RetroAchievements Hardcore mode disables rewind, save state loading and slow motion, leaving fast-forward as the only accepted exception, while Casual mode permits all of them.

Should I use rewind or save states?

Both, for different jobs. Rewind is reactive and short-range, an undo for the last few seconds. Save states are deliberate bookmarks placed before a boss or at a session break and returned to days later. Rewind forgives reflexes; states manage your time.

Final Verdict

Rewind is the most honest convenience in emulation: a simple mechanism, a visible price, and a clear line where competition is concerned. On cartridge-era systems it is effectively free and transforms how you practise hard games. On PS1 it is a setting worth tuning rather than flipping blindly. Past that era it mostly disappears, and save states take over again. Give it RAM and CPU headroom, and it gives you back your last mistake.

Explore Our Guides & Free Tools