Zombies Aren't Real Low FPS: Settings & Performance Checklist

What setting should you try first?

Start with the Low graphics preset. That is the developer’s official recommendation for a smoother experience. We have not benchmarked a best-settings combination, so this guide provides a repeatable test method rather than an FPS promise.

First check the PC requirements guide. The listed minimum is a compatibility baseline, not evidence that every city and outbreak stage will run at a particular frame rate on that machine.

Create a comparison you can repeat

Use the same scenario and display setup for your first two tests. Record what you were doing when performance became uncomfortable: moving around the map, beginning the outbreak, watching a busy area or playing online. These observations are more useful than reporting only that the whole game is slow.

Try Low, then compare the same part of the scenario again. If you change the map and several options together, you cannot tell which change affected the result. If the game exposes other graphics options, test one at a time; we are not claiming specific controls are available in the current menu.

Record results without inventing a benchmark

If you do not have a frame-rate measurement, describe the symptom honestly. “Camera motion pauses near this event” is useful; an estimated FPS number presented as measured data is not.

Distinguish local rendering from online problems

If you notice the problem in co-op, compare the same kind of content in single-player. A smooth local run alongside an online problem is a reason to investigate the session context; it is not proof of a specific network cause. If both are affected, preserve that observation for a technical report.

A freeze, a crash and low frame rate are also different symptoms. Record whether the program remains responsive, returns to the desktop or displays a message. For exits or launch failures, use the launch and crash checklist instead of repeatedly changing graphics options.

When to stop changing settings

Once you have a short, reproducible example, stop making unrelated changes and document it. Include your baseline, the change you tried and the observed result. Steam’s general launch guidance includes checking system requirements and updating Windows and drivers; use official update sources for your device.

A useful performance report does not need a speculative claim that a particular component is the bottleneck. It needs conditions another person can compare. If you later repeat the test after a game update, retain the old result and identify which version produced each observation.