# Where your assets go: your computer or the community

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

Source: [Where your assets go: your computer or the community](/en/application/assets/ou-vont-tes-assets/)

Sharing with the community is on by default.

Every asset you generate or import has a destination: your computer, or the VibeStarter community. The destination decides who can see it and where you will find it. Publishing to Roblox is a third step, which replaces neither of the other two.

Diagram: a created asset goes either to the computer, into the private local library, or to the community, into the shared public bank; in both cases it can then be published to Roblox, where players can see it. — An asset is created or imported — On this computer — One-hour transit, then brought back — Local library, “Local” badge — Private: only you can access it — No sync between computers — Community — Kept online, “Cloud” badge — Other members find it — in the bank and reuse it — A distributed asset cannot be recalled — publishing — Published on Roblox — Visible to players in your game — Reusable by its ID — The source file stays where it is

The two destinations of an asset, and what others see of them. Publishing to Roblox makes the asset usable in the game, but it never keeps your source file safe.

## Choose the destination

1.  Open Settings, then Storage.
    
2.  Go to the Asset destination section. You make two separate choices there: one for Generated assets and one for Imported assets.
    
3.  For each one, choose:
    
    -   The On this computer option: private, saved in your local library, available on this computer only;
    -   The Community option: kept online and shared with the other VibeStarter users.
4.  Your choices are saved automatically.
    

Sharing with the community is **on by default**. The Data step of the first launch asks the same question, with two separate switches:

Share my generated assets and Share my imported assets. After that, the choice is changed only in Asset destination. It applies to new assets; to move the ones you already have, see below.

The My assets tab reminds you of this choice at the top, under Destination for upcoming assets: the Edit link opens the setting.

## The trap of turning off sharing

Turning off sharing does not mean “kept privately online.” There is no lasting private backup of your assets on VibeStarter servers: the bank is public and shared.

An unshared asset waits on the server for about an hour, while the app downloads it into your local library. The badge then shows the time remaining, then Local once the copy is made. The app retries this download when you connect, when the network comes back, every five minutes, and each time you open My assets.

Wait for the Local badge before closing VibeStarter

The app writes it under the setting: “Assets generated online download here: wait for the “Local” badge before closing VibeStarter.” If you close the app during the transit window, the asset expires and you have to create it again.

The other way around, an asset already shared and downloaded by other members cannot be recalled. The consent checkbox says so before you turn sharing on.

## The asset panel badges

| Badge | What it means |
| --- | --- |
| Local | The file is on this computer, in your library, private |
| Cloud | The file is shared in the VibeStarter community |
| Expires in N min | The file is in transit: it is waiting to be brought back |

## What does not follow your account

The local library does not sync between computers. To take an asset with you, use Export to downloads, then copy the file to the other machine. The export folder is separate from the library.

Publishing to Roblox does not change this: a published asset stays reusable in the project through its Roblox ID, including from another computer, but this ID does not replace the source file when you want to edit it.

Deleting a local asset is often permanent

The delete dialog says so when the asset is not shared: it is its only copy, and there is no undo. If the asset also exists online, it will not be downloaded again automatically: a temporary asset expires at its deadline, and a shared asset stays in the community.

## Move what you already have

1.  Open Settings, then Storage and Storage usage and management.
    
2.  Choose the block to work on: On this computer, with the Manage and free up space button, or My community assets, with Manage my cloud assets. Cloud projects appear there for information only, with no list or action.
    
3.  Filter, sort, and select, then run Migrate to local storage, Migrate to community, or Delete. The action applies only to the items that are selected **and visible** with the active filter: a selection hidden by the filter is neither migrated nor deleted.
    
4.  Follow the migration, which you can Pause, Resume, or stop with Stop this migration.
    

Each destination is read again and verified before the source is deleted, and stopping a migration never undoes copies already made. A migration does not change the destination of your future assets.

For a single local asset, right-clicking its card in My assets is enough: choose Share with the community.

## When the bank is full

Your account has a storage limit in the asset bank, shown in Settings, on the Storage tab. When it is reached, nothing breaks: online archiving pauses and your new assets are kept in your local library. Your choices stay saved and resume as soon as you free up space. An email warns you once.

This limit only applies to the asset bank. Your Cloud projects continue to back up and sync normally.

The Usage screen adds up two things

The “used of …” total on the Usage screen adds the asset bank and Cloud projects together, although only the bank has a quota. The two detail lines, Assets and Cloud projects, show the actual breakdown.

## Limits

-   Searching your local library looks at the file name; searching by meaning only exists in the community bank.
-   An image-to-3D conversion does not start from a file kept only locally: it must first be shared or sent.
-   Blender sources stay on your computer, whatever the destination of the accepted asset.

## Frequently asked questions

**Are my assets private?** Not by default: sharing with the community is on. You can change it in the settings, but this change does not recall what has already been distributed.

**Why don’t my generated assets appear in My assets?** This tab only shows what you created or imported, and the asset must have finished its transit. Open the panel: this restarts the download.

**The app says the source of an asset is no longer available.** If it had been kept locally, it is in My assets with the Local badge. Otherwise it expired before it was published to Roblox, or it was deleted. You need to create or re-import it.

**I change computers. Do I get everything back?** Your project and its history follow your account; your local library does not. See [Switching computers](/en/application/projet/changer-d-ordinateur/).

## Going further

-   [Assets: search before you create](/en/application/assets/)
-   [Check what the agent suggests to you](/en/application/assets/valider/)
-   [Where your data is on disk](/en/application/reglages/donnees-sur-le-disque/)
-   [Link your Roblox account and your Open Cloud key](/en/application/studio/compte-roblox/)
-   [Where your project lives](/en/application/projet/)