Guide updated
Guest progress is not persistent. A local account saves only in that game origin and browser profile; a cloud account also keeps a local cache and uploads to its authenticated identity. Before switching devices, wait for the cloud-save indicator to report success, then sign in with the same username account or the same Google account and compare your collection and upgrades.
Choose a save mode deliberately
Scroll sideways to read every column.
| Mode | Where progress survives | Result / next action |
|---|---|---|
| Guest | Memory only; closes with the game document. | Use an account before expecting persistent collection. |
| Local account | This game origin, browser and profile; not another device. | Keep original-site storage; return to the same profile. |
| Cloud account | Authenticated cloud identity plus a local cache. | Use the same sign-in method and wait for Saved in the cloud. |
Read the save indicator before switching devices
Scroll sideways to read every column.
| Game message | Meaning | Result / next action |
|---|---|---|
| Saved in the cloud | Latest upload succeeded. | Now compare on the second device using the same account. |
| Saving… | An upload is running. | Keep the connection and wait for completion. |
| Saving… (queued or pending) | The same visible label also covers cached changes waiting for their scheduled cloud upload; it does not prove the upload has completed. | Stay online; finish safely and check for Saved in the cloud before relying on another device. |
| Offline: it will upload when you’re back | Cloud is unavailable; local cache remains. | Reconnect on this device; keep its site data and avoid parallel spending. |
| Saved only in this browser / Guest: not saved | Local mode / guest mode, not cloud sync. | Waiting longer cannot create a cloud save; use the original online game and intended account. |
A safe two-device comparison
- On device A, finish or safely pause the run and note the account/sign-in method, owned Pokémon, a permanent upgrade level and coin balance. Keep this browser’s site data.
- Remain online until the cloud indicator is saved. Saving/queued/offline states mean another device may still see an older copy.
- On device B, open the original game and choose the same login method and identity. A similarly named local account or a different Google account is not the same cloud save.
- Compare collection and permanent upgrades before spending on B. If A still has the richer copy and a pending indicator, return A online first rather than deleting it.
What merges, and what does not add up
Scroll sideways to read every column.
| What you see | What to do | Success / next step |
|---|---|---|
| A owns Charmander; B owns Squirtle | Same-identity collections are unioned; shiny and recorded completions also retain collected entries. | Both collection entries remain after the merge. |
| Upgrade level 2 on A and 4 on B | Merge uses the maximum upgrade/stat progress, not the sum of levels. | The result is level 4, not 6. |
| 100 coins on A; newer save B has 250 | Coins and partner follow the newer save; the merge does not add both balances. | 250 coins in this example, not 350. Check pending devices before parallel purchases. |
Open the next useful page
Tools
Related pages
Game data & sources
The linked game files show where these stats, costs and rules come from. Updates to the game may change them.
Data version: a9b21f09
- https://pokesurvivor.com/en/guide/
- https://github.com/JPTER78/pokesurvivor/blob/a9b21f091d7e2e0b10bc9ef94836447bf63cddeb/README.md
- https://github.com/JPTER78/pokesurvivor/blob/a9b21f091d7e2e0b10bc9ef94836447bf63cddeb/js/core/db.js
- https://github.com/JPTER78/pokesurvivor/blob/a9b21f091d7e2e0b10bc9ef94836447bf63cddeb/js/ui/login.js
- https://github.com/JPTER78/pokesurvivor/blob/a9b21f091d7e2e0b10bc9ef94836447bf63cddeb/js/ui/ui.js