Short version

BTD6's late-game slowdown is CPU-bound, and the work doesn't spread well across cores. The GPU draws the frame; the CPU has to decide where every bloon, projectile and pop is first, and in freeplay that's the part that can't keep up. A new graphics card won't fix round 200. Fewer entities will.

What the CPU and GPU each do in BTD6

Every frame, the game has to advance the simulation: move each bloon along the track, move each projectile, check which projectiles hit which bloons, resolve each pop and spawn the children. That's integer-heavy logic with lots of branching and lookups, which is CPU work. Only after the simulation step is done does the GPU draw the result, and drawing a few thousand 2D sprites is cheap for any modern graphics card.

In the early game both steps are trivial. In freeplay the simulation step grows with the number of entities, and the number of pairwise checks grows faster than that. The GPU step barely changes. So when the frame rate collapses in the 200s, it's the simulation that's late, not the rendering.

How we know

Ninja Kiwi hasn't published an engine breakdown, but the evidence is consistent:

  • Players on top-end GPUs report the same late-game drops as everyone else. On the Steam forums a user with an i9, 32 GB of RAM and an RTX 3070 ties the lag to the number of active entities and attacking towers, not to graphics load, and others report the game using mainly one core (thread).
  • Lowering resolution and graphics quality changes very little in late rounds, which is what you'd expect if the GPU isn't the bottleneck.
  • Changing the defense changes a lot. Replacing many weak towers with a few strong ones, or removing specific projectile-heavy upgrades, visibly restores frame rate. Those changes affect simulation cost, not drawing cost.

What to upgrade, if anything

Single-core speed is what matters: a CPU with high clock speed and strong per-core performance helps more than more cores. But even the fastest desktop CPU stalls somewhere in freeplay, because the entity count keeps growing. Think of hardware as moving the wall back a hundred rounds, not removing it.

A GPU upgrade helps only if you were GPU-limited in the first place, which for BTD6 usually means an integrated laptop GPU at high resolution. If you already hold a smooth 60 fps in the early game, the graphics card isn't your problem.

What helps without new hardware

  1. Fewer, stronger towers. The single biggest lever. Towers that one-shot groups produce far fewer projectiles and pops per frame than many towers chipping away.
  2. Drop projectile-spam upgrades you don't need. Forum users specifically report relief from removing things like 2-x-x Subs, x-x-3 Monkey Aces and x-x-1 Ninjas, which spend a lot of CPU finding targets. Spike Factories and Perma-Brew are also commonly blamed. These are player reports, not official guidance, but they match the simulation-cost model.
  3. Turn off music and sound effects. Reported to free a little CPU. Small, but free.
  4. Close CPU-hungry apps. Browsers, Discord video, and especially software video encoders compete for the same core.

More detail on what the late rounds throw at the simulation is in why BTD6 lags in late rounds.

Why this matters for recording

Because the bottleneck is the CPU, a recorder that encodes on the CPU (OBS with x264) makes the game lag more. Use a hardware encoder so the GPU does the encoding instead; it has capacity to spare. Setup is in OBS settings for BTD6.

And when the game does stall, your recording fills the gap with repeated frames. Those are detectable and removable after the fact: LagCut does it in the browser.