PolyTrack Backup & Working Mirrors

If you opened this page, the PolyTrack link you saved probably stopped loading. That is not bad luck — it is how most of the unofficial copies of the game work, and it is the reason a search like "PolyTrack backup" exists at all.

PolyTrack is a browser game made by Kodub, and the official version at kodub.com has been stable for years. But the copies most people actually play during a school break or a work lunch are not on kodub.com. They sit on free hosting platforms — Google Sites, GitHub Pages and similar — run by players and small site owners who wanted a version that loads on a locked-down network. Those pages come and go. When one goes, everyone who bookmarked it goes looking for a replacement.

So this page does two things. It explains why the links keep moving and how to find one that works right now. And it shows you how to protect the only parts of the game that are genuinely yours: your track records and your custom tracks.

Why PolyTrack backup links keep disappearing

There are three usual reasons a working copy goes dark.

It gets added to a blocklist. A page becomes popular, someone reports it, and school or workplace network filters pick it up. The page itself is still online — you simply cannot reach it from that network any more.

The owner stops maintaining it.Most of these pages are side projects. The domain expires, the free host changes its rules, or the person moves on. Nothing dramatic happens; the page just stops being updated and slowly drops out of the results.

The host removes it. Free hosting platforms occasionally take down pages that are mostly an embedded game, especially when the page is a thin wrapper with little original content around it.

Notice what is not on that list: the game breaking. PolyTrack itself has not gone anywhere. What moves is the wrapper around it. That distinction matters, because it tells you where to look for a replacement and where not to.

Where to play PolyTrack right now

There are three routes, and they are worth understanding in order of reliability.

The official version. kodub.com is the source. It is the newest build, it is maintained by the developer, and it is the one that will still be there next year. If your network allows it, this is where you should be playing.

Google Sites copies. Because sites.google.com is a Google-owned domain, it is rarely included in school or workplace blocklists — which is exactly why so many unofficial copies ended up there. These pages usually wrap a slightly older build, but the gameplay is the same. The catch is that they change address often, so a link from a forum post six months ago is probably dead.

GitHub Pages copies. Same idea, different platform. Developer domains like github.io tend to be treated as neutral infrastructure rather than gaming sites, so they often slip past filters too.

If you just want to race and do not care which route you take, Play PolyTrack unblocked — it loads in the browser, needs no download and no account, and comes with the full community track library.

One habit worth building: if you find yourself constantly hunting for a fresh link, stop hunting and bookmark two or three sources instead of one. The copies go down one at a time, not all at once.

How to tell a safe backup link from a bad one

Not every page offering a "PolyTrack backup" is offering the game. Some are ad traps; a few are worse. Three checks filter out almost all of them.

No download, no installer. A real PolyTrack copy runs in the browser. If a page asks you to download an .exe file, or to install a "player" or "launcher" first, close the tab. There is no legitimate version of this game that requires an installer.

No account, no extension. You should never have to sign up, hand over an email address, or add a browser extension to race. A browser game needs a browser — nothing else.

Track codes still work. This is the practical test. A genuine copy keeps the community features alive: you can paste a track code and load someone else's circuit, and export your own. If the code field is missing or throws errors, you are looking at a stripped-down or fake build.

A softer fourth signal: the page should be able to tell you what it is. A page with no explanation of what build it hosts, who runs it, or why it exists is a page that will be gone in a month.

How to keep your records and tracks safe

This is the part most guides skip, and it is the part that actually costs you something when a link dies.

Two things live on your side of the screen rather than on a server.

Your custom tracks. Every track you build in the editor can be exported as a track code — a short string of characters that contains the whole map. That code is your backup. Copy it somewhere you control: a notes app, a text file, an email to yourself. If you ever lose access to a copy of the game, the code is all you need to rebuild your track elsewhere. Nothing else about your track needs saving.

Your records and ghost times.These are stored against the browser you played in, which means clearing site data, switching browsers, or moving to a different device will take them with it. There is no account to sync them to. If a time matters to you, screenshot the result screen the moment you set it. It sounds old-fashioned; it is the only method that survives a browser reset.

The habit that prevents most of this: export your track codes the same day you finish a track, not later. The links you play on are temporary. Your codes are portable.

Browse PolyTrack track codes to see how other players share their builds, and to grab the codes for the community tracks worth keeping.

Can you still play an old version of PolyTrack?

Occasionally someone goes looking for a specific older build — 0.4.1 and 0.6.0 come up most often. The honest answer is that it is rarely worth the effort. Old builds are not hosted anywhere official, the copies that exist are scattered across code repositories and archives, and most require you to assemble something yourself rather than click and play. Track code compatibility between versions is also inconsistent: a code that loads in one build may not load in another.

If you want an old version because the current one will not run on your machine, an older build is unlikely to solve that. If it is nostalgia, the community track library is a better use of your time.