# Switching computers

> Public channel — documentation of app 3.6.3. Follow the availability notices of each service.

Source: [Switching computers](/en/application/projet/changer-d-ordinateur/)

No repurchase, no license to re-enter: your account holds your projects.

New PC, a laptop in addition to the desktop, full reinstall: you don’t need to export anything before you go. Your code and its version history are waiting for you as soon as you sign in with the same account. However, your images, sounds and 3D models do not follow on their own, and you need to know that before you wipe the old machine.

## Open your project on the new machine

1.  Install VibeStarter on the new computer. See [Install on Windows](/en/application/premiers-pas/installer-windows/) or [Install on Mac](/en/application/premiers-pas/installer-mac/).
2.  Sign in **with the same email address** as on the old machine. See [Create your account and connect your computer](/en/application/premiers-pas/connexion/).
3.  Open the Projects list. Your project appears there under your game’s name, with the note “Owner · in the Cloud.” A project hosted before 3.6.0 keeps the name of its folder until it has been synced from an app on 3.6.0.
4.  Click Open here. The status changes to “Opening…” while the app downloads your backup and rebuilds the project locally. The folder created takes the name of the original folder, not the name of the game.
5.  The project is there, with its version history.

## What follows you, and what doesn’t

Two columns. On the left, what comes back on its own: your code, your version history, the project configuration, the projects you are invited to. On the right, what you carry yourself: your images and icons, your sounds and music, your 3D models and their sources, your local asset library. — COMES BACK ON ITS OWN — YOU CARRY YOURSELF — Your code — Your version history — The project configuration — Projects you are invited to — Your images and icons — Your sounds and music — Your 3D models and their sources — Your local asset library — A project has no folder to copy: export your assets and keep an archive of your projects.

The online backup contains only code. Everything that is images, sound or 3D models stayed on the old machine and must be carried by you.

## Carry your assets

A project cannot be copied from the file explorer: it has no separate folder on your disk, it lives in the agents’ environment. What you can carry, to prepare before you leave the old machine:

| Method | What it carries | Good to know |
| --- | --- | --- |
| Export to downloads, on an asset in your local library | The asset file, saved to your Downloads folder | Asset by asset. On the new machine, drop the file into an agent’s panel |
| Export Blender source, on a model in the Blender workshop | The model’s Blender source | What you need to edit the model later |
| An archive from Settings → Storage → Backups | Your project folders: code, media and Blender sources kept in the project | A `.tar.gz` file to copy from the storage folder. See below |
| Share your assets with the community before you go | The assets you chose to share | This is **public sharing**, not a private backup |
| Republish from Roblox | Nothing: Roblox keeps your published assets, not their source files | A Roblox ID lets you reuse an asset, never edit it |

### Your project archive

The app archives your projects every day, and Back up now creates one right away. Archives are `project-….tar.gz` files, stored in the storage folder, under `vm`, then `backups` and `projects` — the path of the storage folder is shown in Settings →

Storage. Each one contains your project folders, without the folders a project rebuilds on its own (`node_modules`, `out`…). The app only keeps the most recent ones: copy the one you want to keep to an external disk.

An archive copied by hand into this folder only appears in the list if it is named exactly `project-<number>.tar.gz`. The number is a Unix date, in seconds. It then follows the same retention rule as the others: the app may remove it. To be restorable, it must contain the projects under `projects/<project name>/…`.

On the new machine, first reopen the project with Open here: the code comes back through the Cloud. The Restore button only lists the archives of the computer you are on, and the app has no button to import an archive from somewhere else. The archive stays an ordinary file: open it with your system’s archive tool, then drop the images, sounds or sources you need into an agent’s panel, asking it to put them in the project. See [Drop files into an agent](/en/application/agents/lancer-et-piloter/#drop-files-into-an-agent).

Blender sources stay in the project

When an agent makes a 3D model for an open project, the app stores its Blender source and its render **in the project folder**, next to the code. They are therefore included in your project archives. The online backup, however, only holds code: it does not contain them. See [3D models](/en/application/assets/modeles-3d/).

Your local library is not synced

The local library exists only on the computer where it was filled: no sync carries it anywhere else. If you wipe the old machine without copying these files, they are lost — even if the matching assets are already published on Roblox. See [Where your assets go](/en/application/assets/ou-vont-tes-assets/).

## The two-device limit

Your account can be linked to **two VibeStarter installations at the same time**. Beyond that, sign-in is refused with the message:

> “This account is already linked to 2 VibeStarter devices. Remove a device from your account before signing in here.”

So you need to free a slot before connecting a third computer. The steps are detailed in [Create your account and connect your computer](/en/application/premiers-pas/connexion/#two-devices-per-account).

A second cap also applies if you switch machines often: **four different devices in 30 days**, including the ones already in place. Once it is reached, removing a device no longer frees a slot before those 30 days end; computers already linked still reconnect. Support can reopen a slot: write to [support@vibestarter.pro](mailto:support@vibestarter.pro).

Two installations do not mean two people: a license stays strictly personal. To work as a pair, see [Work with others on a project](/en/application/projet/equipe/).

## Several accounts on the same computer

The projects on a computer are kept in the same place, whichever VibeStarter account is signed in. Each project, however, stays linked to the account that created, cloned or imported it: another account that signs in on this computer does not get it from its Cloud.

In the projects list, a project that is not yours shows a note in place of the Cloud status:

| Note | What it means |
| --- | --- |
| “Other account” | The project was created with another VibeStarter account on this computer |
| “No account” | The project predates version 3.6.0 and is not linked to anyone |

When you open such a project, the app asks you what to do:

-   Open without the Cloud: you work on it on this computer. Nothing is saved online or shared, and the project stays with its account.
-   Make my own copy (project from another account): the app duplicates the folder. The copy is a new project of yours, saved to your Cloud; the original does not change.
-   It’s mine (project with no account): the project is linked to your account and saved to your Cloud.

After updating to 3.6.0

Your projects already saved online are recognized on their own at your first sign-in. For those that never were, the app asks you a single question: “N projects on this PC are not linked to any account.” If you are the only person using VibeStarter on this computer, answer They’re mine. Otherwise, choose

Leave them as they are: each person links their own from their account. :::

If a project shared with you only has another account’s copy on this computer, it is offered to you with Open here: you get your own copy.

## Special cases

**“This folder already matches another game — new identity created”** The message appears after a click on Host on Cloud, in the advanced options of the

Versions panel, when the folder is a copy of a project already linked to another Roblox experience. The app gave it a new identity, and so its own online project, rather than overwriting the existing one. Check that you are working on the project you think you are.

**“Sync paused — this folder and its Cloud project do not point to the same Roblox experience”** Only the owner sees this block; a collaborator’s copy is realigned on its own. Open the game’s place in Roblox Studio, linked to this project: the project follows this experience and the sync resumes on its own. See [The project’s Roblox experience](/en/application/projet/equipe/#the-projects-roblox-experience).

**The project opens empty on the new machine** This can happen if nothing was ever integrated in the team’s version. Let the app finish its sync: it knows how to recover the content of work already saved.

## Frequently asked questions

**Do I have to buy VibeStarter again for my second computer?** No. You reinstall, sign in with the same email address, and your projects are there.

**Can I work on the same project from both my computers?** Yes, one after the other. Let the sync finish before switching to the other machine.

**How do I get my code if I no longer want to use VibeStarter?** The project has no separate folder on your disk. An archive from the Backups section (Storage tab of the settings) contains your projects, code included. It is an ordinary `.tar.gz` file, which you copy and open with the tools of your choice.

**Can I restore an archive made on the old computer onto the new one?** The app does not offer this: Restore replaces the projects on this computer with one of its own archives. The code comes back through Open here; the rest is recovered by opening the archive by hand.

## Going further

-   [Where your project lives](/en/application/projet/)
-   [Your code is saved automatically](/en/application/projet/sauvegarde/)
-   [Create your account and connect your computer](/en/application/premiers-pas/connexion/)
-   [Where your assets go](/en/application/assets/ou-vont-tes-assets/)
-   [Where your data is on the disk](/en/application/reglages/donnees-sur-le-disque/)