Verified Steam scope
The target product is CONTROL Resonant on Steam, AppID 3669870. The official Steam page currently lists the game as coming soon and gives a 24 September 2026 release date. It describes a single-player experience and identifies Remedy Entertainment as both developer and publisher. This technical hub is scoped to the base-game Steam product and the Windows PC requirements shown by Steam; it does not merge information from another Control product, an edition grouping, or a platform store page.
The official Remedy page also names PlayStation 5 and Xbox Series and notes a later Mac release in its platform messaging. That is useful identity context, but a Windows system-requirements table must not be presented as a Mac, console, or cloud-streaming requirement. When a platform-specific article is added, it should carry its own source and version boundary.
Official minimum requirements
The Steam listing currently gives Windows 10 or Windows 11 64-bit as the operating-system scope. Its minimum hardware includes 16 GB of RAM, a GTX 1070 or RX 5600 XT graphics class, and 100 GB of available storage. The minimum processor line and every driver or feature requirement should be copied from the live store page when this article is revised; this page must not fill an unverified field with a guess.
A minimum specification is a compatibility floor, not a promise of a fixed frame rate or a high-quality preset. The final game, driver version, resolution, ray-tracing choice, and background applications can change the result. Players should leave additional storage headroom for patches and confirm the current store metadata before launch because pre-release requirements can change.
Official recommended requirements
The current Steam page gives an RTX 3070 or RX 6700 XT graphics class as the recommended GPU tier and retains the 16 GB memory and 100 GB storage context. As with the minimum table, a recommended tier is not a benchmark. It does not establish a target resolution, a locked frame rate, or whether every visual feature is enabled. Those recommendations require launch testing on a controlled build.
The eventual performance article should publish test methodology: CPU, GPU, driver, game version, resolution, upscaling mode, graphics preset, scene type, and frame-time result. A single screenshot of a menu is not a benchmark. If a patch changes streaming or shader compilation, keep the old result under its version label rather than replacing it silently.
First-launch settings checklist
After installation, allow the game to complete any shader preparation shown by the live build. Set the display resolution and refresh rate first, then make one graphics change at a time. Record whether the game offers upscaling, frame generation, ray tracing, motion blur, field of view, subtitle size, color options, aim assistance, or other accessibility controls. This checklist is intentionally a research method; the existence and name of each setting must be confirmed in the shipped PC build.
For a first test, use an ordinary exploration space rather than a cinematic. Walk through the same route with a baseline preset, then compare a single change. Watch frame-time stability, traversal stutter, input response, and visual readability, not only an average frame count. If a setting is expensive but has a small visual benefit, record the trade-off without declaring a universal best preset.
Storage, updates, and version hygiene
The official listing states 100 GB of storage. Keep extra free space for downloads, unpacking, shader caches, saves, and future patches. A launcher may report a different temporary requirement than the final installed size, so a future article should label each number as download, installed, or free-space guidance when the live client provides those values.
Technical support also belongs in Updates when an official patch changes requirements, fixes a crash, alters shader compilation, or changes a graphics option. Link the patch note and date. Do not turn a social-media report into a universal fix, and do not promise that deleting a cache or changing a driver solves every stutter. The technical page should prefer reversible troubleshooting steps and tell readers when to verify files or contact official support.
What is deliberately not claimed
This page does not claim a final FPS target, a ray-tracing requirement, a specific CPU tier beyond what the current Steam listing states, a universal best preset, or a confirmed Mac specification. It does not infer console performance from PC hardware and does not treat a preview build as a benchmark. Those omissions are part of the page’s accuracy boundary, not missing filler.
Before launch, use this hub to verify the current store metadata and prepare disk space. At launch, update the tables from the live Steam page, add controlled tests, and link settings articles only after the options can be reproduced. That workflow gives a prospective player a useful answer today and a stable technical reference later.
If the store page changes while the game is still unreleased, retain the old value only in a dated change note and mark the current value as authoritative. If the published build contradicts a preview requirement, prefer the live Steam metadata for installation guidance and label any test result with its actual build. This keeps the technical hub useful to both a reader checking a purchase decision and a returning player diagnosing a later patch.
Keep screenshots and benchmark captures tied to the same build so that later comparisons remain meaningful.
Sources: Steam store page, Remedy official game page, Remedy news.
This complete topic entry is source-backed; revisit it after release when official mechanics, requirements, and update notes change.