How to Configure Rewind in RetroArch

RetroArch’s rewind feature lets you instantly step backward through recent gameplay, frame by frame — built on the same underlying save-state serialization mechanism as manual save states, but capturing many small snapshots automatically instead of one deliberate save.

Step 1: enable rewind

RetroArch → Settings → Frame Throttle → Rewind →
  Rewind Support → ON

Some cores don’t support rewind at all (a small number of especially complex or performance-sensitive cores disable it) — the option simply won’t have any effect if the loaded core doesn’t implement the serialization rewind depends on.

Step 2: set the rewind buffer size

RetroArch → Settings → Frame Throttle → Rewind →
  Rewind Buffer Size → 20-100 MB (start around 50 MB)

This is how much memory is reserved to store recent frame snapshots — a larger buffer lets you rewind further back in time, at the direct cost of RAM usage that scales with how much per-frame state a given system needs to save.

Step 3: understand the performance cost per system

Rewind works by saving a full state snapshot on an interval and reconstructing frames backward from it — systems with larger memory footprints (a 3D console like the PlayStation) cost more per rewind-frame than simpler 8-bit systems (NES, Game Boy), meaning the same buffer size in megabytes rewinds much further back on simpler systems.

Step 4: bind the rewind hotkey

RetroArch → Settings → Input → Hotkeys →
  Rewind → bind to a held key or button (commonly R2/held)

Rewind is typically a hold-to-rewind control — held down, gameplay runs backward continuously; released, it resumes forward from wherever you stopped.

Step 5: test rewind depth against the configured buffer

Play normally for 30-60 seconds → hold the rewind hotkey →
  observe how far back you can actually go before hitting
  the buffer limit

If you consistently hit the buffer’s limit before rewinding as far as you’d like, increase the buffer size — if you never approach the limit, a smaller buffer frees up memory without any practical loss of rewind depth.

Step 6: consider disabling rewind for a genuine challenge run

RetroArch → Quick Menu → Options → Rewind → OFF
  (per-core or globally, matching your intent)

Because rewind is such a significant gameplay-altering convenience, it’s worth deliberately disabling for a run where you specifically want the original difficulty and consequence structure the game shipped with intact.

Step 7: distinguish rewind from run-ahead

Rewind moves gameplay backward after something already happened, purely a convenience/practice feature; run-ahead is a completely different, forward-looking technique that reduces perceived input lag — the two features share underlying save-state technology but solve unrelated problems, and both can be enabled simultaneously without conflict.

Why rewind’s cost scales with the system being emulated, not with RetroArch itself

The buffer size setting is a fixed memory allocation, but how many actual seconds of gameplay that buffer holds varies enormously by system — a setting that feels generous on an NES core can feel cramped on a PlayStation or N64 core, simply because there’s dramatically more per-frame state to snapshot on the more complex system. Tuning the buffer per-system, rather than using one global value everywhere, gets meaningfully better results than a single “reasonable-sounding” number applied universally.