PolyTrack backup and device transfer: progress, tracks and cloud sync
PolyTrack driving data starts in the current browser. Before clearing data or changing devices, download a backup or confirm that selected data reached the cloud. Follow save, transfer and check in that order; signing in alone does not upload your game data.
PolyTrack driving guide editors · Updated
Check whose data you are saving before clearing the browser
Guests can open the account page and choose Download local game backup. Save the file somewhere easy to find outside browser storage and confirm the download finished. It contains the current guest’s data; downloading does not enable cloud sync or send the file to anyone.
After sign-in, local game data is kept separately for each account. If the page offers guest or previous-account data, review the import choice before merging it into the current account. Nicknames, comments and support tickets are not part of this game backup; restoring it does not recover deleted comments or alter published posts.
Full backup or one track file?
For a signed-in account, Download complete backup includes game records and retained track versions. Restore is under Backup and restore and requires sign-in; the file must not exceed 25,000,000 bytes (25 MB). Check the downloaded name and size, and keep the original content intact.
The editor’s Export JSON saves only the current custom route, without lap times or account data; its Import file limit is 64 KB. Send a track file to share one route, and use a full backup or cloud sync to transfer your progress. Do not put either file into the other restore/import entry.
Choose what to save before enabling automatic sync
PolyTrack cloud sync lets you select progress, best times and history, custom tracks, and car appearance separately. Custom-track and automatic sync start off. Save your choices, then upload; a manual upload does not enable automatic sync. Back up first, select what you need, and check the success or failure message.
Sound, volume, language and control settings stay on each device. Sync does not need to replace those preferences on another device. Cloud actions require a connection and valid sign-in. If an action fails, retain your local copy and retry online; do not clear the only local copy to attempt another upload.
Merge and check after changing devices
Confirm the old device’s upload finished. Sign in with the same email on the new one, check save choices, then Download and merge cloud data. For a file transfer, sign in, open Backup and restore, choose the earlier backup and confirm the merge into the current local account. File restoration itself does not upload to the cloud.
File restore merges progress and custom tracks according to your current choices; it does not automatically apply the backup’s car or colors. Appearance is handled separately by optional cloud sync, and locally changed appearance may stay. Check bests, history and routes in the game; review save choices if a category is missing, and inspect retained track versions in the account.
Why does the game not show every retained record?
The game lists the latest 100 finishes and up to 30 custom tracks. The account and complete backup may retain more records and versions. A shorter game list does not alone mean older data was deleted. Inspect retained account data and download a complete backup rather than repeatedly importing the same file.
Local and cloud data can be cleared separately. Clearing one does not erase the other. After a cloud reset or change, automatic upload may pause and ask for reimport confirmation; review retained data before uploading. Data already erased without any backup or upload cannot be recovered by this guide. Keep the file and contact support if restore fails.
Read next: PolyTrack editor: create, import and export routes →