Squishy Tower checkpoints

Checkpoints are the only progress bar Squishy Tower really gives you during a climb. There is no published mid-tower continue screen, no split-screen shared save, and no co-op host who can drag you up. You touch a checkpoint, you fall, you return to that checkpoint. That loop is how a 50-player public server stays playable and how an R6 avatar survives cute floors that hide kill bricks. This page is about how that save works, when skipping is a time loss, and how checkpoints relate to wins without being wins themselves.

If you just joined, pair this with Getting Started so spawn is your first save, not a cutscene you ignore. If you are already mid-tower, keep How to Beat open for kill bricks and sink pads. The article index is the Guides Hub.

How a checkpoint actually saves you

Walk onto the checkpoint part until you are sure you have it. In a noisy ASMR tower it is easy to graze a save while looking at a dumpling and assume you are protected. If you are not sure, step off and on again. Falling then returns you to the last checkpoint you truly captured, not the one you meant to touch.

Spawn is a checkpoint. That matters because a first death that dumps you at the lobby camera feels like a full reset even when it is working as designed. After you have a second save, the same fall is cheap. The design is teaching you to bank progress before you experiment with a strawberry edge or a keycap gap.

Leaving the experience is not the same as falling. If you disconnect, you should expect to rejoin a public server and start from the bottom unless a future patch says otherwise. We do not have a published cross-session tower save as of the 7 July 2026 update. Treat a checkpoint as protection inside the current climb, then read updates and the launch recap if Aru Games ever ships a different rule.

What happens when you fall

A void fall, a kill brick, or a sink pad that eats you all resolve the same way: you are placed back at the last checkpoint. You do not lose the Completed badge you already own. You do not lose coins already collected in a way we can document as a penalty table — we simply do not have an official coin-drop chart, so do not plan around a made-up tax. You do lose the time and the floor rhythm you had after that save.

That is why camera and sound on controls matter at the checkpoint itself. Look back at the death. If a brick was under a paw pad two jumps past the save, your next attempt should land short of that pad. If a Needoh-like sink started the moment you left the checkpoint, wait longer before the first jump of the section. A checkpoint is a lab bench, not a launch ramp.

Other players in the 50-person lobby can stand on your save. They cannot capture it for you. Independent climbs mean your friend’s checkpoint is not yours. Do not skip a save because someone else is already standing on the next cute mesh.

When not to skip

Skip culture from other obbies is how people waste Squishy Tower runs. A skip that looks clean on a thumbnail often crosses:

• a kill brick tucked under a squishy
• a sink pad that only looks solid from one camera angle
• a decorative bun rim that is not standable
• the gap between keycaps
• the second cheese section, which exists specifically so you do not treat cheese as solved

If the skip avoids a checkpoint, do not take it on a first finish. The time you save in ten seconds is smaller than the time you lose when the skip fails and you replay the whole section. After you own Completed Squishy Tower, you can experiment. Until then, walk the save.

Hard mode is the other reason not to skip. The creator has talked about hard mode abuse. We will not invent a rule that hard mode deletes checkpoints, but we will say this: if a harder path exists, skipping the only recovery tool you have is the abuse that ends a run. Play the boring line.

Checkpoints versus wins

A checkpoint is progress inside one climb. A win is a summit touch. Looping for extra wins, tracked on wins, starts the problem again: you still need saves on the way up. Do not confuse a high checkpoint with a stored win count. Do not confuse Welcome Squishy Tower (the join badge) with a checkpoint either. Badge definitions live on badges and the players hub.

Coins sitting near a checkpoint are usually safe to take. Coins hanging past a sink pad after the save are the ones Coins and Blind Boxes tells you to ignore until a later loop. There are no public promo codes as of September 2026, so a checkpoint is also not a code stall. Keep codes and how to redeem for a real drop.

Using saves as a practice tool

Once you have a checkpoint in a theme you hate — butter, hamburger clutter, the creator-favorite ASMR squishies — stay there. Practice the next three jumps until they are boring. Mark the floor on the floor checklist only after you can leave that save without a panic jump. Compare how nasty the theme felt against the floor tier list and the tier list hub. Rankings are opinions; a checkpoint is evidence.

If you are tilting, stop on a save, not in a void. Rotate the camera, turn sound back up, read controls if R6 still feels short, then continue. Resetting the Roblox character from a menu to “feel fresh” is how people throw a checkpoint chain. Leaving to hunt executors is worse: scripts will not touch a save more honestly than your feet, and script safety exists because accounts are more expensive than a fall.

Official place and group links stay on the links hub. Extra utilities that are not walkthroughs sit in tools. Play the tower on Squishy Tower on Roblox and treat every glowing save like it is the only inventory that matters until the summit.

The short version you should actually remember: touch the checkpoint, look under the next squishy, fall if you must, and do not skip the save to impress a server that is not climbing with you.