This page separates two different things, because they get mixed together everywhere else: what the game officially requires, and what players report. The first is a fact. The second is a report, and we label it as one.

What the game officially requires

Straight from the Steam store page:

Component Minimum
OS Windows 10 64-bit or later
Processor Intel Core i3 / AMD equivalent, 2.0 GHz or better
Memory 4 GB RAM
Graphics Any GPU with WebGL or DirectX 11 support (Intel HD Graphics 4000 or better)
DirectX Version 11
Storage 1 GB available space
Sound Windows-compatible sound card

Linux minimums are the same hardware tier, with glibc 2.31 / Ubuntu 20.04.

Two notes on reading this. First, the graphics requirement is deliberately low — the game is a 2D cartoon sandbox, not a 3D renderer. Second, 1 GB of storage is the requirement for the game itself, not for downloaded user levels, which are stored separately after the offline-download feature was added.

If your machine meets those numbers and the game still stutters, the problem is almost certainly configuration or a known bug rather than raw hardware.

What players report

Player reviews and forum discussion since the 21 September 2026 launch have raised a recurring set of issues. These are reports, not official statements, and some may already be fixed by the time you read this:

  • Frame-rate caps. Reports mention a frame-rate cap and inconsistent frame rates between levels.
  • Sluggish menus. Menu and UI responsiveness reported as worse than gameplay.
  • Controls feeling unresponsive, particularly on controller, which players report as the least finished part of the port.
  • Some levels behaving oddly, which players have linked to frame-rate handling.

The developer’s launch and patch notes confirm that work is ongoing on “bug fixes” and controller/Steam Deck support, so check the patch notes first.

Practical things to try

None of these are magic, but they are the settings that actually matter for a 2D physics game:

  1. Update your GPU driver. The requirement is DirectX 11 with WebGL support, and a stale driver is the most common cause of a browser-engine game performing badly on hardware that should be fine.
  2. Turn off overlays you do not need. Overlay issues have been an active bug area — the 1.99.2 patch specifically fixed a Steam overlay problem on Linux.
  3. Cap or uncap deliberately and test one level. If you suspect a frame-rate cap is interacting badly with a specific level, test the same level twice with different settings rather than judging from one run.
  4. Close background GPU users. Browsers with hardware acceleration and recording software compete for the same resources.
  5. Check whether the level itself is the problem. A user-created level with enormous numbers of objects will run worse than an official one. The editor has documented object limits, but a level near those limits is heavy.
  6. Verify your files. Steam’s own “verify integrity of game files” catches partial downloads, and the launch patch notes mention startup issues on some configurations.

When it is not your machine

If you are on Linux, note that the 1.99.1 and 1.99.2 patches fixed a Wayland startup crash and a Steam overlay issue on Linux, and a Windows 11 duplicate/ghost window bug. If your symptoms match one of those, updating is the fix, not tuning.

Reporting it properly

If you still have a problem, the fastest route is the official channels: the Steam community hub for the game, or the official Discord linked from the store page’s support information. Include your OS, GPU, the exact level and whether it happens in the browser version too — that last detail is the fastest way to tell a port bug from a general one.