Official Casualties: Unknown PC requirements, what the store page leaves out, Steam Deck status and the settings that matter on low-end hardware.
Casualties: Unknown System Requirements: PC and Steam Deck
Casualties: Unknown is a 2D pixel-art simulation, not a 3D showcase. The official requirements are correspondingly light: a 64-bit Windows 10 machine, an Intel Core i3-8130U and 500 MB of storage. The store page does not list a GPU or a RAM minimum, which is either reassuring or unhelpful depending on how you read it.
This page reproduces the official requirements, explains what the missing entries mean in practice, and covers the one platform question the store page does not answer: Steam Deck.
Official source: Casualties: Unknown on Steam ↗

Official requirements
| Minimum | Recommended | |
|---|---|---|
| OS | Windows 10 64-bit | 64-bit Windows |
| Processor | Intel Core i3-8130U 2.20 GHz | Not specified |
| Memory | Not specified | Not specified |
| Graphics | Not specified | Not specified |
| Storage | 500 MB | Not specified |
| Additional notes | 16:9, 16:10 and ultrawide supported | — |
The recommended column is almost empty. That is common for small indie releases: the developer tests on the minimum machine and does not publish a second tier. The absence of a GPU entry strongly suggests the game runs on integrated graphics, which the i3-8130U has.
What the missing RAM and GPU entries mean
The store page is not hiding a heavy requirement. A 2D game with pixel-art sprites, a tile-based cave and a physics simulation of limbs can run on very little. The simulation is CPU-bound, not GPU-bound: the game is tracking bleeding rates, limb states, temperature, AI and item condition every tick.
Practical guidance, clearly labelled as guidance rather than an official minimum:
- RAM: 8 GB is comfortable on Windows 10/11. 4 GB will boot the game but leaves little room for a browser and Discord.
- GPU: any integrated GPU from the last decade should handle the sprites. The CPU matters more for simulation ticks.
- Storage: 500 MB is the game. Add a few hundred MB for saves, shader cache and Steam overhead.
- CPU: the i3-8130U is a dual-core laptop chip. A modern four-core CPU will run the simulation more smoothly at high time speed.
If you are on a laptop from before 2018 with 4 GB of RAM and a spinning hard drive, the game may still run, but expect longer loads and slower fast-forward.
Why the CPU matters more than the GPU
The game simulates a body, not a world of polygons. Every limb has muscle, skin, bone and bleeding state. Every wound runs an infection check on a timer. Temperature, hunger, thirst, mood, pain, blood pressure and consciousness are all updated continuously. When you press 3 to fast-forward, the simulation runs faster, not the renderer.
That is why the processor is the only component the developer names. A weak GPU will lower your resolution or frame rate; a weak CPU will make fast-forward sluggish and large fights choppy.
The demo is the best benchmark. It contains the same simulation and the first five layers, and it is free. If the demo runs well on your machine, the release will run the same or better after launch patches.
Steam Deck status
There is no native Linux build. The game runs on Steam Deck through Proton, and the store page does not carry a Verified badge at the time of writing.
What to expect on Deck:
- Controls: the game is keyboard-and-mouse first. Movement, inventory dragging, crafting tabs and the health panel all assume a mouse. A community layout can map the trackpads, but inventory management will be slower.
- Readability: the HUD uses small text for item durability, blood volume and status icons. On a 7-inch screen, some of that will be hard to read without zoom.
- Performance: the simulation is light enough that a Deck should handle it, but fast-forward and large fights are the stress points.
- Battery: a 2D game usually draws less power than a 3D one, but the CPU-bound simulation keeps the chip awake.
If you only play on Deck, try the demo through Proton first. It is the same engine and the same interface.
Can you run it? A quick checklist
- Check Windows version. Windows 10 64-bit or Windows 11. The game does not support 32-bit Windows.
- Check free space. 500 MB for the game plus save overhead.
- Check your CPU. The i3-8130U is the floor. Anything from the last five years is fine.
- Check your RAM. 8 GB is the comfortable number; 4 GB is possible but tight.
- Run the demo. If the demo holds 60 FPS in Overgrown Depths, the release will be fine.
- Update your drivers. Integrated GPU drivers on laptops are often years out of date.
Settings that matter on low-end hardware
The game does not publish a graphics settings list, and the demo's options are limited. If a build gives you the choice, prioritize these:
- Resolution scale / window size. The pixel art scales cleanly. Drop to 1280×720 before you drop the simulation speed.
- Fullscreen vs borderless. Fullscreen usually gives a little more performance on integrated graphics.
- Ambient light and fog. These are gameplay settings, not just visuals. Turning ambient light up makes the game easier and can reduce the number of dynamic light sources.
- Time speed. Fast-forward multiplies simulation work. On a slow CPU, use 2× rather than 3×.
Do not lower the simulation settings that affect gameplay — infection chance, bleeding rate, metabolism — to gain performance. They do not affect frame rate, and changing them changes the game.
Laptop and handheld notes
The game is a good fit for a laptop because it does not need a discrete GPU. Two caveats:
- Keyboard: the default bindings use the whole left side of the keyboard plus mouse buttons. A laptop keyboard is fine, but an external mouse is much better than a trackpad for inventory dragging.
- Heat: the simulation keeps the CPU busy. On a thin laptop, expect fan noise during long fast-forward sessions.
On a handheld Windows device, the same applies: the game will run, but the interface is the limiting factor, not the hardware.
The simulation ticks limbs, blood and AI on the CPU. A modest GPU with a weak laptop CPU will struggle more than the reverse.
FAQ
Is there a Mac version? No. Steam lists Windows only.
Is there a Linux version? No native build. Proton is the only option, and it is not officially verified.
How much RAM does it need? The store page does not specify. 8 GB is a safe practical number for Windows 10/11.
Will it run on integrated graphics? The named minimum CPU has integrated graphics, so yes, integrated graphics are expected to work.
Does it support ultrawide? Yes. The store page explicitly lists 16:9, 16:10 and ultrawide support.
Is the demo a good benchmark? Yes. It uses the same simulation and rendering path. If the demo runs, the release will run.
Sources and further reading
Related guides
More Casualties: Unknown Guides
Every weapon in the Casualties: Unknown demo ranked: damage, swing speed, durability, ammo and which weapon fits which layer.
How blood volume, bleeding rate, tourniquets and transfusions work in Casualties: Unknown, and the order to treat a bleeding limb.
The three playable characters in Casualties: Unknown, what Experiment can do in the demo, and what is actually confirmed about Milky and Dune.
How crafting works in Casualties: Unknown: the five tabs, Intelligence requirements, failure tiers, blueprints and the recipes worth making first.
What the free Casualties: Unknown demo includes, how long it takes, where it ends, what carries over and how to install it on Steam.
All six Casualties: Unknown presets plus the 41 custom run settings, with defaults, ranges and the options that actually change survival.
Casualties: Unknown endings explained: the confirmed story goal, the unreleased final layers, what the demo does at layer 5, and what is still speculation.
Every enemy in Casualties: Unknown, its layer, attack pattern and drops, plus the Elder Thornback fight and the traps that kill more players than monsters.
