Verified on PolyTrack v0.6.0 (March 2026). v0.7.0 Campaigns mode notes are based on community reporting — check the current version at kodub.itch.io/polytrack to confirm what’s live.
PolyTrack is one of the fastest-growing gaming search terms of 2026 and the gap between its player count and available guides is absurd. The game is free, loads in any browser in seconds, and punishes every bad brake point with uncomfortable precision. If your times are stuck, the cause is almost never reaction speed — it’s technique. Specifically, where you brake, how you land, and whether you’ve actually understood how the physics engine works.
This guide covers all of it: what the game is and how to access it for free, how the Bullet Physics Engine creates the behaviour you’re experiencing, all 17 official tracks ranked from easiest to hardest with what makes each one hard, the speed techniques leaderboard regulars rely on, ghost racing done right, the track editor, and a specific transition guide for anyone arriving from Trackmania or Forza Horizon.
What Is PolyTrack and How to Access It
PolyTrack is a browser-based time-trial racing game built by a single developer, Kodub. The concept: drive a low-poly car through tracks built from ramps, jumps, loops, and tight corners, racing against the clock and the ghost replays of faster players. It draws obvious inspiration from TrackMania, runs on any modern browser including mobile, and costs nothing to play [1].
No download required. Open any browser and go to polytrack.dev, or find it on CrazyGames or Poki. No account, no install, no waiting. Click Play, select Official Tracks, and you’re racing in under 10 seconds. Desktop builds for Windows, macOS, and Linux are available at itch.io as pay-what-you-want (including €0) and are worth grabbing for offline access and keyboard precision [1].
PolyTrack has packed a complete time-trial experience — global leaderboards, ghost racing, real-time multiplayer, and a full track editor — into something that loads like a webpage. It’s one of the strongest hidden gem games of 2026. Development pace has been fast: v0.6.0 in March 2026 added real-time multiplayer and a complete C++ physics rewrite. Most existing guides predate these changes.
Quick Start: From Zero to Competitive in 5 Minutes
The fastest path from first launch to meaningful improvement:
- Open polytrack.dev in any browser — no login or install
- Select Official Tracks → Summer 1; this is the physics tutorial
- Controls: W/Up to accelerate, S/Down to brake, A/D or Left/Right to steer, R or Enter to restart instantly
- Drive Summer 1 flat-out once — find the point where the car starts sliding (this is your grip limit)
- Complete Summer 1, 2, and 3 before touching Winter or Desert tracks
- After Summer 3, load any leaderboard ghost and watch them through every corner before your next run
- Enable real-time multiplayer (v0.6.0+) once you can complete a clean lap without stopping
Which section matters most for you?
| You are… | Read this first |
|---|---|
| Brand new to time-trial racers | Physics Engine section below |
| Casual — want to beat a friend’s time | Speed Techniques section |
| Competitive — aiming for top-100 times | Ghost Racing section |
| Here to build tracks | Track Editor Basics |
| Coming from Trackmania or Forza | Transition Tips at the bottom |
How PolyTrack’s Physics Engine Actually Works
PolyTrack runs on the Bullet Physics Engine — a C++ physics library that was rewritten from scratch in v0.6.0 for better precision and performance [1]. Understanding what Bullet actually simulates explains almost every technique in the game.
1. Momentum is a resource the engine conserves ruthlessly. Every time you brake, you spend kinetic energy that takes 2–4 seconds to rebuild at full throttle. Hard braking mid-corner doesn’t just slow you through the bend — it puts you at reduced speed on the exit straight too. Top times look almost throttle-only because fast drivers arrive at corners already pre-slowed enough that no emergency braking is needed [2].
2. Landing angle determines exit speed — not luck. When you leave a ramp, the Bullet engine calculates the impulse force on landing and converts it based on your car’s angle at impact. Land flat or with the nose slightly down and the force vector points forward — you exit the landing faster. Land nose-up and the force points down and backward — you bounce, lose speed, and arrive at the next corner off-balance [2]. This is the mechanism behind the nosedive technique: during airtime, pitch the front wheels fractionally down before contact. It’s the biggest single technique gap between mid-tier and top times on any jump-heavy track.
3. Uphill slopes act as passive brakes. The engine’s gravity simulation means any positive incline actively decelerates the car. Braking before an uphill corner is redundant — the slope removes the speed you’d otherwise brake away [3]. This single rule, correctly applied, saves most intermediate players 1–2 seconds per lap. Brake only on flat and downhill sections.
What separates fast from average drivers isn’t reaction time — it’s brake timing and landing angle. A beginner brakes when they feel fear. An intermediate player brakes at a consistent reference point. A fast driver brakes as late as the physics allow and has already set the car’s angle for the landing or corner entry before needing to react.
All 17 Official Tracks, Ranked by Difficulty
PolyTrack ships with 17 official tracks across three environments: Summer (asphalt), Winter (ice), and Desert (sand). Winter and Desert both reduce grip relative to Summer, which creates difficulty jumps between environments that often outpace the jump between tracks within them [2].
Difficulty ratings based on community consensus and v0.6.0 track states. Summer 6 was revised in v0.6.0 — its sideways drop was replaced with a longer slope and extended S-curves [1].
| Rank | Track | Surface | Difficulty | Key Challenge |
|---|---|---|---|---|
| 1 | Summer 1 | Asphalt | Easy | Tutorial — learn grip limits; no complex jumps |
| 2 | Summer 2 | Asphalt | Easy | First jumps; practice flat landings here before Summer 4 |
| 3 | Desert 1 | Sand | Easy–Medium | Sand debut; wide lines and gentle curves forgive small errors |
| 4 | Summer 3 | Asphalt | Medium | Elevation changes; gravity-braking rule is critical here; WR under 14s [3] |
| 5 | Winter 1 | Ice | Medium | Ice debut; brake 30% earlier than the equivalent Summer corner |
| 6 | Summer 4 | Asphalt | Medium | Chained jump sequences — nosedive technique required for competitive times |
| 7 | Desert 2 | Sand | Medium | Sand in tighter corners; smooth inputs mandatory, no snap throttle |
| 8 | Winter 2 | Ice | Medium–Hard | Ice corners at speed; late steering causes long unrecoverable slides |
| 9 | Summer 5 | Asphalt | Medium–Hard | No easy sectors — mixed jumps and technical flat corners throughout |
| 10 | Desert 3 | Sand | Hard | Sand combined with elevation — never brake on the uphill sections |
| 11 | Winter 3 | Ice | Hard | Long ice stretches; rhythm over reaction, one mistake chains into two |
| 12 | Summer 6 | Asphalt | Hard | Extended S-curves (v0.6.0 revision); sustained precise throttle all the way through |
| 13 | Desert 4 | Sand | Hard | Tight desert bends; grip unpredictable on corner exits at speed |
| 14 | Winter 4 | Ice | Expert | High-speed ice sections with almost no run-off room for errors |
| 15 | Summer 7 | Asphalt | Expert | Full Summer skill check — aggressive jump sequences punish hesitation |
| 16 | Winter 5 | Ice | Expert | Hardest ice track — no forgiveness on corner entry, one mistake ends the run |
| 17 | Desert 5 | Sand | Expert | Hardest overall — every mechanic combined at pace on unpredictable sand |
Track-specific notes:
- Summer 3: Start steering 2–3 car lengths earlier than instinct in the opening sector. Treat the multi-jump finale as one continuous arc — your landing from Jump 1 sets the approach angle for Jump 2. WR benchmark is under 14 seconds [3].
- Winter tracks: Ice doesn’t change what you do — it removes the margin when you do it wrong. Move every brake marker forward by roughly 30% versus the equivalent Summer corner type.
- Desert tracks: Light off-road contact isn’t heavily penalized by the Bullet engine [5], but sustained sand contact bleeds more speed than asphalt. Stay on the racing line and treat sand like low-grip asphalt rather than a completely different surface.
Speed Optimization — Brake Points, Throttle Modulation, and Draft
These five techniques apply across all 17 tracks and compound with each other. Any single one drops your times immediately.
Threshold braking — the single biggest gain available. Brake at the latest possible moment before the car begins to slide. Finding this point takes deliberate practice: identify a visual reference one piece before your current brake point and brake there for three laps. If you maintain clean control, move the marker one piece later. Incremental extension is faster than guessing at the perfect point [2].
Out-In-Out racing line. Approach from the outside edge of the corner, clip the apex (innermost point), then exit wide. This geometry straightens the arc and lets the car carry more entry speed than a mid-track line. The method is identical to real-world racing theory and applies directly inside PolyTrack’s physics model [2].
Progressive throttle after the apex. Snap to full throttle immediately after a corner and the wheels spin — delaying speed rebuild by 0.5–1 second. Apply throttle progressively over about a second as the car exits and the tyres hook up faster. The instinct to floor it immediately is wrong here [2].
The nosedive landing. During any airtime, pitch the car’s nose fractionally downward before contact. When the front wheels touch first, the Bullet engine converts the landing impulse forward. Back-wheel-first or flat landings waste the jump’s momentum [2]. This is the technique that most separates mid-tier times from top-tier times on Summer 4, Summer 7, and any track with chained jump sequences.
Draft in real-time multiplayer. Sitting directly behind another player in v0.6.0 multiplayer reduces your air resistance and produces a measurable speed gain on long straights — the same slipstreaming effect from real motorsport and TrackMania competition [2]. Use it on straights, but brake at your own marker entering corners. Don’t follow the car ahead if they brake earlier than your optimal line.
Ghost Racing and Multiplayer — How to Actually Use It to Improve
Ghost racing is PolyTrack’s best coaching tool and most players misuse it. Racing against a ghost during your lap splits your attention between your own inputs and the ghost’s position. The ghost distracts more than it teaches when active mid-run.
PolyTrack supports up to 10 simultaneous ghosts [1], and the replay interface includes a speed graph showing a player’s exact throttle and brake inputs at every checkpoint split [2]. This is telemetry, not decoration — it tells you precisely where you’re losing time.
The correct ghost workflow:
- Run your lap without the ghost active — build your own consistent line first
- After finishing, switch to ghost playback from an angle that shows your worst corner
- Identify one corner where the ghost’s speed graph shows full throttle and yours shows a lift or brake
- Restart and fix that one corner specifically — use R aggressively
- Re-enable the ghost only after you’ve completed three clean runs through that section
Fixing the single biggest time-loss corner before moving to the next is how speedrunners approach optimisation. Trying to fix five corners simultaneously produces inconsistent laps that are hard to diagnose [2].
Real-time multiplayer (v0.6.0): Live races against other players add pressure calibration — you find out quickly whether your pace is competitive or not. The optimal racing line doesn’t change in multiplayer; what changes is your risk tolerance in corners when someone is gaining on you [1].
Weekly Shorts (v0.7.0, community-reported [6]): Short curated challenge tracks rotating weekly with global leaderboards. These are the fastest way to benchmark your skill against the wider community without committing to a full official track optimisation cycle.
Track Editor Basics and Campaigns Mode
The editor is the part most players ignore and then spend hours in. A functional first track takes under 5 minutes [4].
Core controls:
- Camera: Right-click + drag to rotate; middle-click + drag to pan; scroll wheel to zoom
- Placing pieces: Left-click to place; Delete to remove; R to rotate 90°; Shift+R for 15° fine rotation
- Power shortcuts: Ctrl+C/V to copy/paste segments (added v0.6.0); Ctrl+Z/Y undo/redo; Ctrl+S to save; Space to pause test mode; Escape to exit test [1][4]
Building your first track — minimum viable circuit:
- Place the Start Line piece from the Special category at origin (0,0,0) [4]
- Add a short straight of 3–4 pieces — players need room to reach speed before the first corner
- Add one medium turn, then one jump — these are PolyTrack’s two primary mechanics, and every player needs to encounter both early
- Place a checkpoint after the jump [4] — respawn here on a crash rather than the start
- Watch for green highlights on connection points — grey means the pieces aren’t aligned and the gap will break the track
- Click the flag icon to enter test mode; verify all jumps are clearable and the circuit loops correctly
- Export to generate the track code, then share the string to Discord, Reddit, or polytrackcodes.com
What makes a track work: Flow (players can anticipate what’s coming), Risk vs. Reward (an optional risky line exists alongside a safe one), and fair checkpoint spacing [4]. Tracks that frustrate players most return them to a checkpoint too far back — they quit before improving.
Campaigns mode (v0.7.0, community-reported [6]): Campaigns offer structured sequences of developer-curated tracks with progression goals — the first time PolyTrack has had a guided progression path rather than free-choice track selection. For track builders, Campaigns mode opens the possibility of creating linked track series with escalating difficulty rather than standalone circuits. Verify whether this is live at the official itch.io page as the update status at time of writing was unconfirmed on the official devlog.
Coming from Trackmania or Forza Horizon?
Both games train habits that work against you in PolyTrack. The fixes are specific.
From Trackmania: Racing line theory, braking timing concepts, and momentum management all transfer directly [5]. What doesn’t: Trackmania’s surface-specific friction physics, Speed Drift, Neo-Slide, Bug Slide, and the frame-perfect precision mindset [5]. Trackmania is deterministic — the same input at the same frame always produces the same result. PolyTrack rewards flow. A “good enough” corner that carries momentum beats a technically perfect line that required a brake.
The key advantage for Trackmania players: PolyTrack grants significant air control — you can pitch and yaw the car mid-jump to correct a bad takeoff [5]. Trackmania offers almost nothing here. Bad air in Trackmania is bad air. Bad air in PolyTrack is fixable. Use this — it means you can commit harder to jump entry speeds and recover imperfect launches that would end a Trackmania run.
From Forza Horizon: Forza is a simulation-adjacent open-world racer with ABS-like assists, car tuning, and a rewind feature. PolyTrack has none of these — no assists, no tuning, and instant R to restart. The hardest adjustment: Forza trains you to recover a botched corner by lifting and rebalancing the car. In PolyTrack, recovery driving is slower than restarting. The moment a run goes off-line, press R. The restart is instant — no load screen penalty [2]. Our Forza Horizon 6 beginner’s guide covers the fundamentals that inform this comparison if you want the full picture on how Forza’s physics model works before switching contexts.
Forza players specifically: move your brake markers forward compared to Forza muscle memory, especially on Winter tracks. Forza’s braking assists allow later inputs than PolyTrack’s physics tolerates. The resulting slide is more dramatic, travels further, and compounds into the next corner rather than resolving.
Universal adjustment for both audiences: Get comfortable with aggressive restarts. Both Trackmania and Forza develop the habit of managing a mistake — rewind, recovery line, attempting to salvage the lap. PolyTrack punishes this approach. Press R the moment a run goes off-line. The fastest mental model is “clean lap or immediate restart,” not “see if this recovery works.” A compromised lap costs 5–10 seconds across the correction sequence; a restart costs zero.
Frequently Asked Questions
Is PolyTrack really free with no catches?
Completely. The browser version plays in any modern browser with no account, no login, and no storage install. Desktop builds at itch.io are pay-what-you-want including €0. Car customisation (paint, rims, exhaust) is cosmetic only — no microtransaction affects gameplay [1].
Is keyboard or controller better for PolyTrack?
Keyboard (WASD or arrow keys) dominates competitive play — the vast majority of leaderboard times are set on keyboard. The game’s digital input model (on/off throttle and brake) suits keyboard well, and the restart key (R) is faster to hit under pressure. Controller works in the desktop build but offers no advantage for precision time-trial play.
What makes Desert harder than Winter at the top end?
Winter ice is consistently reduced grip — you adapt your brake markers once and apply the adjustment mechanically across the track. Desert sand at the higher track numbers has more variable surface behaviour combined with more complex geometry. Desert 5 is considered the hardest official track overall rather than Winter 5, because sand behaves less predictably on corner exits at speed and the track design is more demanding.
How do I get competitive on Summer 3?
The world record benchmark is under 14 seconds [3]. Three specific improvements matter: (1) start steering 2–3 car lengths earlier than instinct in the opening sector; (2) never add brake input on uphill sections — gravity decelerates you; (3) treat the multi-jump finale as one continuous arc — your landing angle from Jump 1 determines your approach line for Jump 2.
Can I play PolyTrack on mobile?
Yes. The HTML5 browser version works on mobile, and an Android build is available at itch.io [1]. Mobile touch controls function, but competitive players universally use keyboard — the precision requirement on tight corners is difficult to replicate on a touchscreen. The game’s 10–90 second run lengths make mobile sessions viable for casual improvement between keyboard sessions.
Sources
- “PolyTrack by Kodub” — Kodub (official developer page). kodub.itch.io/polytrack
- “PolyTrack Complete Beginner’s Guide 2026” — PolyTrackCodes. polytrackcodes.com
- “PolyTrack Summer 3 Speedrun Guide” — PolyTrackCodes. polytrackcodes.com
- “PolyTrack Track Editor Tutorial” — PolyTrackCodes. polytrackcodes.com
- “PolyTrack vs TrackMania Comparison” — PolyTrackCodes. polytrackcodes.com
- “PolyTrack 0.7.0 Update Guide” — PolyTrackCodes (community anticipatory). polytrackcodes.com
I've been playing video games for over 20 years, spanning everything from early PC titles to modern open-world games. I started Switchblade Gaming to publish the kind of accurate, well-researched guides I always wanted to find — built on primary sources, tested in-game, and kept up to date after patches. I currently focus on Minecraft and Pokémon GO.