Short version

BTD6 slows down late because the game has to simulate every bloon, projectile and pop each frame, and that work explodes in freeplay. A faster GPU barely helps. Fewer, stronger towers help a lot. And if the run is already recorded, the lag is baked into the file as repeated frames, which is a separate problem with a separate fix.

Why late rounds lag

Bloons TD 6 does most of its work on the CPU. Each frame it moves every bloon on the track, advances every projectile, checks what each one hits, and resolves every pop, including the children that spawn out of a popped bloon. In the early game that's a few hundred things. By the 200s it's tens of thousands, and the cost grows faster than the round number does.

A few things pile on at once in freeplay:

  • B.A.D.s every round from 231, Fortified B.A.D.s from 251. Each one spawns layers of children when it pops, and those children all need simulating.
  • Zero-spacing stacks. From round 511, rounds guarantee stacks of 5 B.A.D.s and 5 Fortified B.A.D.s with no spacing. Dense stacks mean every projectile has many possible targets to check against.
  • Projectile-heavy defenses. Towers that fire lots of small projectiles (darts, tacks, spike piles, splash explosions, chain reactions) multiply the number of collision checks per frame. Community round-1000 runs built around chain explosions reported rounds taking around 40 minutes each because of the slowdown.

This is why people with high-end hardware still report dropping to 30-40 FPS against tier 5 bosses. The limit is how much simulation the game can do per frame, and that work is hard to spread across cores.

What actually helps in-game

  1. Fewer, stronger towers. Spamming cheap towers is the single biggest lag multiplier. A handful of high-tier towers that one-shot groups produces far fewer projectiles and pops per frame than fifty towers chipping away.
  2. Avoid projectile-spam setups when you don't need them. Chain-reaction and pierce-everything builds look great but are the heaviest on the simulation. Save them for rounds that need them.
  3. Lower the visual load. Turning down resolution and graphics quality in Settings won't fix the simulation cost, but it frees up headroom on lower-end machines and laptops so the frames the game can produce get drawn.
  4. Close everything else. Browsers with many tabs, Discord video, and especially a recording app are all competing for the same CPU. See the recording section below.

What doesn't help much: a GPU upgrade. If you're already above 30-40 FPS in the early game, the graphics card isn't the bottleneck in the 200s.

If you're recording, the lag is worse and it ends up in the file

Recording software like OBS captures at a fixed frame rate. When the game stalls and doesn't deliver a new frame in time, the recorder writes the previous frame again to keep the file's timeline even. OBS won't report this as a dropped frame, because from its point of view nothing was dropped.

The result is a recording full of repeated frames: a 30-second clip at 30 fps might contain only a few hundred genuinely different images. Speeding the clip up in an editor doesn't fix it, because the repeated frames are still there, just faster. We cover the mechanics in why your gameplay recording has duplicate frames.

Two things reduce how much lag you record:

  • Use a hardware encoder (NVENC, AMD VCE/AMF, Apple VideoToolbox) rather than x264 on the CPU, so the recorder isn't fighting the game for CPU time.
  • Record at 30 fps if the game can't hold 60. You'll get fewer duplicated frames and smaller files.

Fixing footage you've already recorded

If the run is done and the recording is laggy, you have two options. You can scrub through in an editor, find each stall and each pause-menu visit, and cut them by hand. For a long late-game session that's hours of work.

Or you can detect the repeated frames automatically. LagCut scans a BTD6 recording in your browser, finds pause menus and frames that are near-identical to the one before, removes them, and exports a video-only MP4 at one consistent game speed. On real creator footage it has removed 600+ repeated frames from a 30-second round-268 clip, turning it into 8.8 seconds of continuous gameplay.