PolyTrack Tips: Faster Lines, Better Ghosts, Tracks Worth Sharing

PolyTrack is a low-poly racing game where the clock is the only opponent worth worrying about, and the track under your car might be one you built yourself. It runs in a browser tab, on Windows, macOS, Linux and Android, and it costs nothing to start. Version matters here. The game is still in development, so everything below reflects 0.6.3, released on September 16, 2026. We're not affiliated with Kodub, the developer, and nothing here replaces the instructions on the game's own page.

The PolyTrack tips below aren't a driving lesson. They're the small decisions that separate a run you finish from a run you keep.

Set Up PolyTrack Before Your First Timed Run

Five minutes in the settings menu changes how the next hour goes, and almost nobody spends them. PolyTrack controls are plain enough: WASD or the arrow keys to drive, R or Enter to restart, C or M to switch to the cockpit camera, Space or P to pause. Settings holds the switches that matter, including the reset hint, the ghost car, particles, skidmarks, and a full key binding page.

Two toggles earn their keep. Turning off particles and skidmarks gives an older laptop more headroom, and a frame hitch in the middle of a jump tends to end the run before your hands can react. Killing the reset hint is the other one. It looks like a trivial preference until you notice how often your eyes drop to the corner of the screen during a clean attempt.

Restart is the cheapest move in PolyTrack. One key, no menu, no loading screen, no confirmation. Use it as a probe rather than a punishment: change one input, keep everything else identical, and let the time tell you whether the change worked. Drivers who restart constantly learn faster than drivers who protect one tidy-looking lap.

Why the Air Brake Changes Everything in PolyTrack

Patch 0.5.0 slipped the air brake into the notes with a six-word description: it reduces rotation mid-air. That reads like a minor addition until a run dies because the car came down sideways off a ramp. The note gives no number, so treat it as a dial you learn by feel. Your car keeps rotating in the air, and it doesn't build speed there either. Land straight and you keep the momentum you left the ramp with.

Find the binding before you need it. Open Settings, then Key bindings, and check which key your build uses. Layouts have shifted across updates, and a habit built on the wrong key is worse than no habit at all. Then take a jump you know well and watch the nose on the way down. If it lands pointing at the barrier, a short tap in flight is usually enough to level the car out.

Where the air brake pays for itself: blind crests, the second jump in a chain, and any ramp that throws you toward a wall instead of down the road. Where it doesn't: long flat straights, since there's nothing to correct.

How Do PolyTrack Checkpoints Change the Way You Practise?

Checkpoints took on a second job in 0.5.0. They still respawn you after a crash, and now they log a split time as you pass. Most players use the first feature and ignore the second, which leaves the most useful number in the game sitting on the screen.

A split is the closest thing PolyTrack has to a coach. Load a ghost, run the track, then compare your times at each checkpoint instead of staring at the finish. Level at the first checkpoint and three tenths down at the second means the problem lives in one stretch of road, not in your whole approach. Fix that stretch before you touch anything else, and resist the urge to rebuild the opening corner because it feels slow.

Respawning also lets you rehearse the back half of a long community track without replaying a dull opening every time. Set a checkpoint just before the hard part, drive into it, crash on purpose, and you're back at the section you actually wanted to learn.

PolyTrack Ghosts: Watch Three, Not Ten

Since 0.5.0 you can race or watch up to ten ghosts at once, and since 0.3.0 you can pick those opponents straight from the leaderboard. Generous features like that invite abuse. Ten translucent cars on a narrow road hide the corner you're trying to read, and you'll spend the run dodging shapes instead of learning a line.

How many ghosts should you actually load? Two or three is plenty. One should be slightly quicker than your best time, close enough that the line looks achievable. Another can be the fastest time on the board, purely to show whether a shortcut exists. Leave the rest switched off until you've closed the first gap.

Watching beats racing for diagnosis. Switch to watch mode, use the frame stepping buttons added in 0.6.0, and stop the replay at the exact point where your line and the ghost's line split apart. The advanced graph window plots speed against distance, which turns a vague feeling of "I'm losing time here" into a specific corner with a specific number attached.

One check before you trust any ghost: the leaderboard now shows the date a record was set. Physics and track parts have changed across updates, so a time from an old build may reflect handling you can't reproduce today. Compare like with like, and ignore the ancient record that looks unbeatable.

Inside the PolyTrack Track Editor

Camera control is half of building, so start there. The left mouse button places parts, the middle button rotates the view, the right button pans, Shift with the scroll wheel lifts you up or down, R rotates the selected part, and X or Delete removes it. Undo and redo arrived in 0.5.1 and copy and paste in 0.6.0, so a bad ten minutes is no longer permanent.

Build in a fixed order: start point, road, finish, checkpoints, features, decoration. The finish line goes down early because a track without one can't be tested properly, and testing is the only way to find the ramp that launches cars into empty space instead of onto the next platform.

Checkpoints belong after every blind jump and before every banked corner. A respawn that drops you two meters from a wall isn't a checkpoint, it's a punishment. Parts can now overlap, rotate on any axis, and snap to a smaller grid, while 0.6.0 added banked curves, Y-intersections and wall slopes for sections that carry speed rather than interrupt it.

Give the first corner more thought than the showpiece jump. Make the entry wide and the sightline clear, and leave players one obvious line through it. An opener that demands precision means every restart begins with a failure, and most builders quit long before the track is finished.

Sharing is built in. Fill in the track author field, hit the share button, and the game gives you a code other players can import. Track of the Week, added in 0.6.3, gives those codes somewhere visible to land.

Where PolyTrack Multiplayer Fits In

Multiplayer is experimental as of 0.6.0 and runs on Kodub's servers, so expect a few rough edges. It's still the quickest way to see a line you'd never invent, because a faster driver takes the corner right in front of you and you can copy the entry speed while it's happening. Treat a session as a classroom rather than a scoreboard. The leaderboard remains the record that counts, and experimental modes come and go.

Mistakes That Cost You Whole Seconds in PolyTrack

Most PolyTrack tips tell you to practice more. These are the ones that change what practice does.

• Braking late into a banked turn. The bank carries you for a moment, then throws you into the outside wall.
• Rebuilding a track after two bad runs. Twenty laps teach you more than twenty edits.
• Decorating before testing. Props rarely break a track, but ramps do, and a ramp is what you're checking.
• Buying grip with car parts. Paint patterns and rims are cosmetic, and so are exhausts.
• Copying a world-record line before you can hold your own. You'll lose the speed you gained before the next corner arrives, and you won't know why.

What to Do With Your Next PolyTrack Session

1. Open the game at Kodub's itch.io page or launch the Android build, then pick one official track rather than a community map.
2. Go to Settings, then Key bindings, and move restart and the air brake under fingers that already rest there.
3. Choose two ghosts, one near your best time and one far ahead.
4. Run ten attempts with exactly one change per attempt, keeping the ghost visible the whole time.
5. Read your checkpoint splits, then rebuild only the section where the gap opens.
6. Share the track code with one person and watch where they crash. That spot is your next edit.

A faster lap in PolyTrack rarely comes from a heroic run. It comes from knowing which key restarts the track, which corner is costing you a tenth, and which parts of your own build are fighting the car. Get those three things right and the clock starts moving in your favor. If you'd rather begin with a description than a grid of blocks, our own Binkbink turns a text prompt into a small playable game you can share by link, which is a low-pressure way to learn what makes a track worth finishing before you build one by hand.