Steamworld Build

SteamWorld Build is a city builder with a split personality: half frontier town management on the surface, half digging operation in the mine below, wrapped in the series' trademark robot western charm. It is also, by the standards of this site, a genuinely easy game to run. Across more than 3,700 measured CPU and GPU combinations in our database, the average system records 95 FPS at 1080p Ultra, 60 FPS at 1440p Ultra, and 32 FPS at 4K Ultra. The fastest combinations push 442 FPS at 1080p Low; the slowest combinations in our data sit at 25 FPS at 1080p Ultra. That spread tells you the real story: the ceiling is enormous, the floor is low but not catastrophic, and what separates the two ends is less about raw GPU grunt than about how hard the simulation side of a Unity city builder can lean on a processor once your town grows.

The engine: Unity, two maps, one simulation

SteamWorld Build runs on Unity, and it behaves like a Unity management game rather than a Unity shooter. The renderer is doing modest work: an isometric camera, stylized low-poly art, small texture loads, no ray tracing, no sprawling open world to stream. Any mid-range graphics card from the last several years is honestly overpowered for this game at 1080p, which is exactly what a 95 FPS average across thousands of hardware combinations is telling you.

The load that matters lives on the CPU. A city builder is a simulation first and a picture second. Every citizen pathing to a job, every goods delivery chain, every building tick, and every one of the underground mining crews runs through game logic that Unity titles historically handle with a heavy main thread plus limited helper threading. Early in a run, with a handful of buildings, almost anything plays it well. The interesting question is always the late game: a dense surface city stacked on top of a fully developed three-floor mine is where weaker processors start to show up in frame times, and where the 25 FPS floor in our 1080p Ultra data comes from. That figure is the tail of the distribution, old quad-cores and low-power laptop chips under developed saves, not a warning about the average experience.

Memory and storage are the quiet supporting cast. Sixteen gigabytes of RAM is comfortable headroom; the game itself does not demand more, and 8 GB systems play it, though the usual advice about closing the browser applies. If you are speccing a fresh gaming PC build around management games in general, dual-channel DDR5 matters more than people expect in CPU-limited titles, since simulation work is latency-sensitive and single-channel memory measurably costs minimums. An NVMe SSD is not strictly required, but map loads and save operations are short and frequent enough that the game clearly belongs on solid-state storage rather than a spinning drive.

1080p: the home resolution, and it shows

At 1920x1080 the game is in its element. A 95 FPS average at Ultra across 3,700-plus combinations means the median gaming PC does not merely clear 60, it clears it with room for a high-refresh monitor. This is the resolution where the game's priorities are obvious: the gap between our average and our ceiling, 95 versus 442 FPS at Low, is the gap between the GPU idling and the GPU being let off the leash entirely. Settings reductions at 1080p recover enormous headroom because the graphics load was never the real constraint in the first place.

Read the floor carefully, though. A 25 FPS minimum at 1080p Ultra is not this game being secretly heavy; it is the signature of simulation-bound behavior. The systems at the bottom of our 1080p Ultra table are the ones with weak or old processors, and their struggle gets worse as the save develops. If your own experience starts at 120 FPS in year one of a town and sags below 60 by the time the mine's third floor is a maze of conveyor logic and worker patrols, you have met the same wall our slowest combinations meet earlier. The practical takeaway for 1080p players is simple: any discrete GPU from the GTX 1660 / RX 6600 class upward is fine, and your money is better spent on a competent six-core CPU than on anything with more VRAM.

For players eyeing a 144Hz monitor, 1080p tuned settings get most modern builds into triple digits, and a 240Hz monitor is not absurd for this title given that 442 FPS ceiling, though honestly the genre does not reward refresh rate the way a shooter does. A city builder at 100 FPS feels lovely; at 240 it is mostly bragging rights.

1440p and 4K: where the bill finally arrives

At 2560x1440 the average drops to 60 FPS at Ultra, which is the cleanest result in the whole dataset. Sixty at 1440p Ultra, averaged across thousands of machines including plenty of weak ones, means a typical mid-range system holds the refresh rate of a standard monitor at this resolution without touching a slider. The GPU now does real work, the isometric scene fills more pixels, and the balance between CPU simulation and GPU rendering is roughly even on mid-range hardware. If you play at 1440p and want headroom for the late-game CPU dips described above, this is the resolution where a balanced build, decent six-core plus a card in the RTX 4060 / RX 7600 class or better, is the correct answer rather than a GPU-heavy one.

At 3840x2160 the average falls to 32 FPS at Ultra, and that number deserves honest interpretation. Thirty-two is an average across everything in the database, weak laptops included; a purpose-built gaming PC does far better. But the shape of the result is real: 4K Ultra is the one configuration where SteamWorld Build can genuinely outrun a modest graphics card, because the pixel count finally dominates the modest geometry. There is no ray tracing to blame and no upscaling crutch required the way AAA releases lean on DLSS or FSR; the game is simply rendering four times the pixels of 1080p. If native 4K60 Ultra is the goal, you want a genuinely capable card, the RTX 4070 / RX 7800 XT tier and up, and you want the CPU side sorted so that simulation dips do not stack on top of GPU dips in the late game.

The genre argument for 4K is stronger here than in most games, by the way. City builders live and die on text, icons, and fine structural detail, and a dense town at 2160p is visibly easier to read and manage than at 1080p. Players who spend on resolution for shooters and skip it for management games have the priority backwards.

Recommended settings: our tested configuration

The spread between our averages and the 442 FPS ceiling at 1080p Low tells you settings matter more here for headroom than for survival, since even Ultra is playable on average hardware. Our recommended configuration keeps the game looking essentially identical to maxed while buying back the frame-time stability that matters when the simulation gets busy.

Shadow quality is the first reduction, high instead of maxed: in an isometric stylized game, the difference is nearly invisible at normal zoom levels and shadows are consistently the most expensive per-pixel cost in this class of Unity title. Anti-aliasing stays on, because jagged building edges are the one artifact that is genuinely visible in a game made of straight lines. Effects and post-processing can drop one notch without any visual cost you will notice mid-session. Draw distance and level-of-detail settings deserve care: this is a game you play zoomed out half the time, so keep them reasonably high for readability, but the top notch is where diminishing returns hide. Vertical sync or a frame cap slightly below your monitor's refresh rate is worth enabling for a reason specific to this genre: city builders run long sessions, and an uncapped Unity title will happily pin your GPU at 100 percent for six hours to render frames you cannot perceive, heating the room and boosting the fans for nothing. Cap it, and the game runs cooler, quieter, and indistinguishably.

One genre-specific note: if your late-game frame rate sags, the fix is rarely in the graphics menu at all. Simulation load is simulation load. Closing background applications that compete for CPU time does more for a struggling developed save than any slider.

What hardware do you need?

Entry level (older quad-core, 8 GB RAM, entry or older GPU): This tier is exactly who our 25 FPS floor at 1080p Ultra describes, and the fix is free: drop to Medium or Low and the same hardware lands in playable territory, since the ceiling data shows how light the renderer can be. A GTX 1050-era card with a four-core CPU plays the early and mid game fine; developed megacities are where this tier feels its age.

Mid-range (modern six-core, 16 GB dual-channel RAM, RTX 4060 / RX 7600 class): The sweet spot, and the tier our averages effectively describe. Expect roughly 90 to 120 FPS at 1080p Ultra and around 60 at 1440p Ultra, with late-game dips that stay above the annoyance threshold. This is the best graphics card for SteamWorld Build in the value sense: anything faster buys you frames the genre does not convert into wins.

High-end (modern eight-core or X3D, 16 to 32 GB fast RAM, RTX 4070 / RX 7800 XT class): Locked 1440p high-refresh, and 4K Ultra becomes realistic at or near 60 with light tuning. The large-cache CPUs earn their keep specifically in developed saves, where simulation minimums hold up noticeably better.

Flagship (fastest available CPU and GPU): 4K Ultra at high-refresh, or 1080p numbers deep into the 442 FPS territory our fastest combinations recorded. Entirely unnecessary, entirely pleasant, and the correct choice only if the machine also serves heavier games than this one.

Laptop playability

This is one of the more laptop-friendly games in our database, full stop. The modest renderer, the isometric camera, and the pause-friendly genre all suit portable play, and a gaming laptop with a mid-range mobile GPU matches the desktop mid-range tier's experience almost exactly. The more interesting case is integrated graphics: modern RDNA-based and recent Intel Arc-integrated iGPUs handle the game at 1080p with tuned settings, which makes it one of the few titles on this site we can recommend for thin-and-light machines without a long list of caveats. The caveat that remains is the CPU one. Low-power U-series chips trade simulation speed for battery life, and a developed city on a 15-watt processor will show the same late-game sag our floor data records, just sooner. For couch and travel play, though, this is close to an ideal handheld and laptop title, and its day-one presence on subscription services means many players will meet it exactly there.

Streaming and content creation

City builders are underrated streaming games, slower pacing gives a broadcaster room to actually talk, and SteamWorld Build's dual-layer structure makes for naturally watchable sessions. The good news for a single-PC streaming setup is that the game leaves hardware resources on the table. At 1080p, where most streamers play it, the GPU is nowhere near saturated on a mid-range card, so hardware encoding is essentially free: NVENC on Nvidia or AMF on AMD produces a clean 1080p60 broadcast with no measurable cost to your own frame rate, and it should be your default choice here. Software x264 encoding is also more viable than usual, since the game only truly saturates a CPU in developed late-game saves; a modern eight-core can run a veryfast x264 1080p60 stream alongside the early and mid game without either side noticing. If your city is enormous and your CPU is already working hard, fall back to the hardware encoder and reclaim the cores.

For the video side, the honest comparison is this: any machine that can cut a 4K timeline in a video editing suite renders SteamWorld Build as an afterthought, and creators building one PC for both workloads should spec for the editing workload, workstation-class CPU, 32 GB of RAM, fast NVMe scratch storage, and treat this game as a free passenger. Recording locally, the game's low encode complexity, flat colors, predictable motion, means modest bitrates still look clean, which your archive drive will appreciate.

Common problems and fixes

Frame rate that degrades as the save develops: This is the CPU simulation wall, not a bug and not your GPU. Lower crowd and visual density options where available, close background applications, and accept that the last third of a big run is the most demanding part of the game on every system in our data.

Stuttering when switching between the surface and the mine: Layer transitions re-load a chunk of scene state. Installing to an NVMe SSD rather than a hard drive smooths this noticeably, and keeping 16 GB of RAM free of competing applications prevents the hitch from becoming a pause.

Long initial loads and slow save operations: Storage-side again. The game saves often, autosaves included, and on a spinning disk those moments are felt. Solid-state is the fix, full stop.

Fans screaming during long sessions on a powerful PC: Uncapped frame rate. The game will render 400-plus FPS if you let it, and your cooling will pay for frames you cannot see. Cap to your refresh rate and the problem disappears.

Blurry text at non-native resolution: Unity titles scale UI poorly at non-native resolutions. Run at your panel's native resolution and tune settings downward instead, the readability loss from a scaled image is worse than any settings reduction.

Upgrade priorities for SteamWorld Build players

If this game is a primary title and your experience falls short, the upgrade order is clear. First, the processor, if you are on an old quad-core or a low-power laptop chip and your developed saves sag, a CPU upgrade to a modern six or eight-core is the single change that moves the late-game floor, and nothing else comes close. Second, memory: getting to 16 GB of dual-channel DDR5 (or the best dual-channel configuration your platform supports) is cheap and directly helps simulation minimums. Third, storage: the game on an NVMe SSD is a small but real quality-of-life improvement in loads, saves, and layer transitions. The graphics card comes last, and only matters at all if you play at 1440p high-refresh or 4K; at 1080p, our data says the card you likely already own is not your problem. The worst money spent on this game is a flagship GPU for a 1080p monitor.

Frequently asked questions

Q: Is SteamWorld Build CPU or GPU intensive?

A: Mostly CPU, unusually so for a 2023 release. The renderer is light, the simulation is the load, and our 1080p data shows it clearly: a 95 FPS average with a 25 FPS floor that belongs almost entirely to weak processors in developed saves.

Q: What is the best graphics card for SteamWorld Build?

A: A mid-range card in the RTX 4060 / RX 7600 class is the value answer, covering 1080p and 1440p Ultra comfortably. Only 4K60 Ultra justifies stepping up to the RTX 4070 tier, and anything beyond that is wasted on this game alone.

Q: Can I play it on integrated graphics or a laptop?

A: Yes. Modern integrated GPUs handle it at 1080p with tuned settings, and it is one of the most laptop-friendly games in our database. The only real caveat is low-power processors sagging in late-game cities.

Q: How much RAM does SteamWorld Build need?

A: 16 GB is comfortable and recommended; 8 GB works with a clean system. Dual-channel configuration matters more than raw capacity for this title's simulation load.

Q: Why does my frame rate drop late in a run?

A: Simulation scaling. A dense city plus a developed multi-floor mine multiplies the CPU work, and this hits older and low-power processors hardest. It is the same behavior our 25 FPS floor at 1080p Ultra records, and no graphics setting fully fixes it.

Q: Does it need an SSD?

A: Need is strong, but it clearly belongs on one. Loads, frequent autosaves, and surface-to-mine transitions all benefit, and NVMe drives are cheap enough that this is the easiest fix on the list.

To summarize: SteamWorld Build in 2026

Two-plus years after release, SteamWorld Build has settled into its niche: a mid-size, well-made management game that will never headline a GPU launch and never needed to. Its place in our database is the useful kind, a reference point for how far the definition of a demanding game has drifted. A title can ship in the same era as path-traced showcases and still average 95 FPS at 1080p Ultra across thousands of real systems, because its ambitions were simulation and readability rather than pixel count. For hardware advice, that makes this one of the simplest pages on the site: do not buy a graphics card for this game below 4K, do not skimp on the processor if you love enormous late-game cities, and do not overthink it. For the game itself, the honest summary is that it is a charming, accessible city builder with a clever second act underground, kind to modest machines, pleasant on powerful ones, and one of the rare modern releases where the answer to "can my PC run it" is, for the overwhelming majority of our readers, simply yes.