ReStory's official Steam page publishes minimum requirements for Windows and macOS. Confirm the platform column before using performance fixes; the Mac build requires Apple silicon, while the Windows listing specifies DirectX 11. These values come from the current Steam store listing. No recommended tier is published there, so higher settings and frame-rate targets should not be presented as guaranteed hardware tiers.
Official minimum requirements
These values come from the current Steam store listing. No recommended tier is published there, so higher settings and frame-rate targets should not be presented as guaranteed hardware tiers.
| Windows minimum | macOS minimum | |
|---|---|---|
| OS | Windows 10 x64 | macOS 14 or newer |
| CPU | 2-core / 4-thread CPU | Apple M1 |
| Memory | 4 GB RAM | 8 GB RAM |
| Graphics | GTX 750 Ti | Apple integrated GPU (M1) |
| API | DirectX 11 | Not separately listed |
| Storage | 1 GB available | 1 GB available |
Keep removed parts visible and grouped by layer. Use the recorded order as a reference; if your Notebook shows something different, follow the game.
Mac compatibility boundary
The current store requirement says Apple M1 and notes that an Apple processor is required. An older patch note saying the game should work on old Macs (Intel) conflicts with the current store requirement; for a new purchase, follow the current store listing and ask Steam Support or the developer before assuming Intel support.
Before calling low FPS a bug
Compare the machine with the official minimum, update the OS and GPU driver, make sure a laptop uses the dedicated GPU, verify game files, and temporarily disable overlays. The developer's pinned troubleshooting post requests platform, steps, screenshots or video, error text, and the ReStory folder when a problem persists.
Storage and save files are separate
The 1 GB figure is installation storage, not a backup allowance. Keep free space beyond that minimum and copy saves before testing reinstalls or destructive workarounds. Use the Save File Location guide for current Windows, Mac, and Steam Deck paths.
Before buying: match the store table to your machine
Start with the current official Steam requirements shown on this page, then compare every line with the exact operating system, processor, memory, graphics hardware, and free storage on the computer that will run the game. A laptop model name is not enough because one product family can ship with different CPUs and GPUs. On Windows, use System Information and Task Manager's Performance tabs; on macOS, use About This Mac and System Information. Save the date of the store check because requirements can change after patches. Meeting a minimum is a compatibility floor, not a promise of one frame rate at every resolution, scene, or thermal condition. If any component is below the published minimum, treat a successful launch as an observation rather than guaranteed support.
Windows and Mac preflight checklist
On Windows, confirm version and architecture, identify which GPU the game uses, update the graphics driver from the hardware vendor, install pending operating-system updates, and restart before the first controlled test. On macOS, record chip model, memory, operating-system version, and display resolution. Preserve the page's Apple-silicon evidence note instead of turning one community success report into a universal guarantee. A game launching on one M-series machine does not establish identical behavior on every chip or macOS release. Begin with default settings, close overlays only for testing, and change one variable at a time. If the game fails before a menu appears, keep the exact error text and use launch troubleshooting rather than applying low-FPS advice to a startup failure.
- Record OS, CPU or chip, memory and GPU
- Confirm the active graphics device
- Update and restart before testing
- Change one setting at a time
- Keep the exact error or symptom
Storage, saves, and a repeatable performance test
The storage figure describes installation capacity, not extra space needed for system updates, caches, screenshots, cloud synchronization, and backups. Leave headroom rather than filling the drive to the stated minimum. Before reinstalling or moving the game, copy SaveData and BackupSaveData together and label the archive with date and build. For low FPS, choose one location and save, record resolution, display mode, frame cap, preset, driver, power state, and whether the symptom is constant or tied to one device. Repeat the same short sequence after each change. Do not delete saves as a first test, and do not report one momentary counter value as an average. A consistent before-and-after comparison is more useful than a long list of simultaneous tweaks.
| Record | Why it matters |
|---|---|
| Build and save location | Separates patch and scene differences |
| Resolution and preset | Makes graphics comparisons valid |
| GPU and driver | Identifies the rendering path |
| Power and temperature state | Explains laptop throttling |
| Exact symptom | Separates launch, loading and frame-rate defects |
What this requirements page can and cannot prove
Use the official table for published minimums, current-build testing for observed performance, and clearly labelled community reports for edge cases. This page cannot certify untested hardware, guarantee an unsupported operating system, infer a future patch date, or convert one successful launch into official support. Hardware above the minimum can still encounter a driver, corrupted file, save state, or game defect; hardware below it can sometimes launch without becoming supported. A useful report includes specifications, build, store, exact symptom, reproduction steps, settings, and troubleshooting already attempted. Keep purchasing advice separate from diagnosis: the first asks whether a machine matches public requirements, while the second asks why a particular installation behaves differently. That evidence boundary is more honest than a simple yes-or-no compatibility badge.
