How to Save Builds in Build Whatever

The sentence on the Roblox page is the whole save system: builds save in free private servers. Players miss it because they treat “private” as a paid VIP product. In this experience, createVipServersAllowed is off. The developer shipped a free instance type instead. If you only remember one mechanic from this wiki, remember that.

Why public plots vanish

A public server is a 22-player sandbox with rockets. When the last people leave, or when the instance recycles, your parts go with it. That is normal Roblox instance behavior unless the developer wrote a per-player datastore for public plots. Build Whatever advertises persistence on the private path. Building a cathedral in a public lobby is performance art, not a save.

Average session length sits near fourteen minutes. That number matches the grief loop: spawn, place, get slapped, leave. If you want a week-long project, you must step off that loop.

How to open a free private server

1. Open the official Build Whatever experience.
2. Use the Servers tab or the in-game private/create flow the client shows on your platform.
3. Create a free private instance. Do not hunt a Robux VIP listing — the game is not selling those as the save hook.
4. Join it alone first. Place a unique marker (a colored corner block) so you can prove the reload later.
5. Leave fully, then rejoin the same private server. If the marker is there, you are on the persist path.

Mobile hides server tabs behind the experience page, not always inside the first pause menu. If you cannot find the control, create the private server from the Roblox website or app listing, then launch.

Friends and saves

A private server you own is the right place to play with friends. Grant access to people you trust. A friend with a Bat Gamepass can still delete your week if you never set social rules. Persistence is not protection. Pair this page with how to protect your build.

If someone else hosts, their shutdown can still strand you. Keep a personal private server as the canonical copy. Rebuild once from a visit if you must; do not treat every hangout as the master save.

What does not save

• Parts you placed only on a public instance
• Client-side ghosts from a failed place
• Inventory you never purchased (Gamepasses stay on the account, placed parts stay on the instance)
• Progress from a sister game such as Build Anything With Friends — different universe, different datastore

Scripts that promise “save anywhere” are not official. Read the scripts list for risk notes. A leaked loadstring can copy parts and also copy a ban.

Recovery habits

Take a screenshot of the exterior every session. If a friend griefs the private plot, you still have a reference. Name your project in chat once so the host remembers which slot or server you meant. After a platform outage, rejoin the same private server before you start a new one — duplicates are how people lose the “real” house.

If the marker is gone after a patch, check the latest update before you rage-rebuild. Store resets happen. We will note them.

When to stay public on purpose

Public is correct for slap fights, rocket tests, and showing off a finished build you already copied to private. It is wrong for the first three hours of a castle. The server mode advisor is a short decision tree if you keep mixing the two.

Save first. Troll second. That order is the difference between a sandbox hobby and a fourteen-minute loop.