yunyoo

Documentation

Backups and migration

Last updated:Nov 8, 2026

A backup saves a cloud phone's data at a point in time. You can restore it, create a new environment from it, or export it as a .wp package to share it or move it to another node.

Create a backup

Create backups on the Backups tab of the environment's details. There are two kinds:

  • Full device: saves all of the cloud phone's data. The environment must be running.
  • App data: saves the data of the apps you pick, up to 5 at a time, also while the environment is running. It works on every Root version; non-root versions need an image that supports it.

For environments on local nodes, you choose where to save: Only this computer or Cloud, with the first selected by default. A backup kept only on this computer is not uploaded and can only be restored on that computer, and each environment keeps a limited number of them. Backups saved to the cloud count toward your backup quota. Each account keeps up to 20 backups and 50 GB in total, and backups do not expire on their own.

On Linux local nodes, backups saved to the cloud run between 2 and 6 a.m. node local time by default; ones created outside that window are queued, unless you tick Run now.

Restore

A full restore needs the environment stopped and happens at its next start; the model and Root version must match the backup. An app data restore happens while the environment runs and needs the same device identity and the same signed version of the app.

Click New environment from backup on a full backup; the new environment restores it the first time it starts.

Export and share

Click Export as .wp on a backup to create a backup package, which expires after 72 hours by default. Full backup packages leave out the device identity seed by default; including it asks for your account password, and a full package with a seed can't be shared.

On a package, click Share via QR code to create a share link and QR code. Links last 1, 24 or 72 hours and allow 1, 5 or 20 downloads, and recipients must sign in to claim the package. You can revoke a link at any time, and links stop working when the package is deleted or expires.

Import

Choose Import .wp on an environment to restore into that environment (stop it first), add it as a new data environment, or do an app data restore. When environment packages are turned on, Import environment package on the Environments page creates a new environment straight from a package.

Migrate to another node

When you have at least two nodes that can run environments, the environment menu shows Migrate to…. A migration shuts the environment down on its current node, makes a full backup, prepares the target node, starts it there, checks the device identity and then switches billing. If it takes more than 40 minutes it counts as failed, and the environment stays on its original node. After a successful migration, the data on the original node is kept for 24 hours by default before it is cleared.

To migrate to a local node, that node must be online, have a free slot and have the image ready. If you would rather not touch the original environment, use Move via package…: it creates a new environment on the target node from a backup package and leaves the original as it is.