Into the Fire System Requirements

The Steam store page for Into the Fire still prints TBA for CPU, GPU, and storage. That is not a wiki failure. Starward has, however, posted concrete playtest hardware targets in community FAQs while they run technical tests. This page copies those numbers, labels them as playtest-reported, and tells you how to think about them before Early Access in 2026. When the store block updates, release date and this page should move together.

If you only want a yes/no, use the PC checklist. If you want to join a live build, also read playtest.

Playtest-reported minimum

Posted for technical tests (64-bit Windows only):

• OS: Windows 10 64-bit
• CPU: AMD Ryzen 5 3600 or Intel Core i5-10400F
• RAM: 16 GB
• GPU: NVIDIA GTX 1660 6 GB / GTX 1060 6 GB or AMD RX 5600 XT 6 GB
• API: DirectX 12
• Storage: 30 GB, SSD required
• Target: 1080p, Low, about 30 FPS

That minimum is already heavier than a lot of indie survival pages. The 16 GB RAM line and SSD requirement are the ones people skip, then hit hitching during fire spread and earthquake debris. Fire simulation and collapsing geo are the expensive bits, not a giant texture pack.

Playtest-reported recommended

• OS: Windows 10/11 64-bit
• CPU: Ryzen 7 5700X / 5800X or Intel Core i5-12400F / i7-10700
• RAM: 16 GB
• GPU: RTX 3060 12 GB / RTX 2070 Super 8 GB or RX 6700 XT 12 GB
• Storage: 30 GB SSD, NVMe recommended
• Target: 1080p High 60 FPS, or 1440p Medium/High with upscaling

Playtest-reported high-end

• OS: Windows 11 64-bit
• CPU: Ryzen 7 5800X3D / 7700 or Intel Core i5-13600K
• RAM: 32 GB
• GPU: RTX 4070 / 4070 Super or RX 7800 XT
• Storage: 30 GB NVMe
• Target: 1440p High/Ultra 60+ or 4K High with DLSS/FSR

If you are buying a card for this game alone, wait. Early Access in 2026 will move these lines. If you already own a 3060-class GPU, you are in the conversation for playtests.

What the technical tests were looking at

Starward told testers they were watching crashes, settings, hardware compatibility, loading, controls, and first-hour UX. That is why this wiki refuses to publish a fake “ultra 4K 120 benchmark.” The useful action is: update GPU drivers, install to SSD, cap FPS if your GPU is at the minimum line, and turn hazard warnings up so you can drop settings without dropping tells. Controls and hazards both depend on those tells.

Laptops, handhelds, consoles

Steam Deck compatibility is listed as unknown. A 16 GB RAM minimum plus DX12 fire sims is not a confident handheld pitch yet. Interviews say Early Access starts on Steam, with PS5 and Xbox Series in the studio’s sights later, and Switch 2 being explored. None of that is a ship date. Do not buy a dock expecting a 2026 console patch.

GOG is also an announced PC storefront. Requirements should match Steam when they appear. Family Sharing is listed on Steam; that does not change the hardware floor.

Settings that actually matter

Until an official graphics menu is documented, treat these as playtest hygiene:

• Prefer 1080p if you are on the minimum GPU. Fire fill-rate is the tax.
• Keep effects that telegraph bombs and quakes readable. Saving 8 FPS by muting a warning is how you donate a run.
• Store on SSD. The FAQ is not shy about it.
• Close overlays if the technical test is hunting crashes.
• Rebind before you lower quality. Input lag plus Low fire visuals is a worse combo than Medium with a sane cap.

How this ties to the rest of the wiki

A machine that can run the menu but hitch during a carry is a rescue problem. A machine that overheats on three-skull maps is a hazards problem. Check hardware before you write the game off. Then check Getting Started so the first hitch is not also your first tutorial.

When Starward replaces TBA on the store, we will mark which lines were playtest-only. Until then, use the tables above as a planning ceiling, not as a legal spec sheet.