Skip to content
Tutorials Center
My learning

Topics

Lesson 32 of 37 ยท Publishing and Monetization

Publishing Your Experience: Settings, Testing and Launch

Take your Roblox experience from Studio to the public: save and publish, configure game settings, test with multiple players, write a good icon and description, and follow a launch checklist.

An experience that only exists on your computer cannot have players. Publishing uploads it to Roblox, gives it a page where people find it, and lets anyone you allow join. Publishing is not a one-time event: you will publish updates many times, so it helps to learn the workflow and a safe testing habit now.

The Roblox steps are described in words and read-only snippets because Studio and the Roblox website are not available on this site. The runnable code is a small JavaScript stand-in for a pre-launch checklist.

Save versus publish

Studio has two similar-looking commands, and mixing them up is a classic beginner problem.

  • Save to Roblox stores your work in the cloud, as a version, but players still see the previously published version.
  • Publish to Roblox makes your current work the live version that players join.
  • Save to File stores a .rbxl file on your computer, useful as a backup.

When you publish an experience for the first time, Studio asks for a name, description, genre, devices and an optional starter place. After that, publishing again simply replaces the live version. Roblox keeps old versions, so on the experience's page under Version History you can revert if a bad update goes out.

Save or publish?

Save to Roblox Stored in the cloud. Not live.
Publish This version goes live.
Save to File A backup on your computer.

Publish only after testing. Revert from Version History if needed.

1 / 2

Experience settings that matter

Open Home > Game Settings (or the Creator Hub page of your experience).

  • Basic info: name, description, genre and the devices you support (computer, phone, tablet, console, VR). Do not tick a device you have not tested.
  • Permissions: the experience starts private. Switch it to public when you are ready, or share it with specific friends or a group for testing.
  • Avatar: rig type (R15 is the modern default), body scaling and whether players can use their own avatar or you force one.
  • Security: the toggle Enable Studio Access to API Services (for DataStores) and whether scripts may make HTTP requests.
  • Maturity and compliance: you answer a questionnaire describing the experience so Roblox can assign it a content maturity label. Answer honestly: a wrong answer can get an experience restricted.
  • Servers: maximum players per server and whether to allow private servers.
  • Localization: translate the name, description and text if you want a global audience.

Many settings sit in the Creator Hub on the web instead of Studio. Look there when you cannot find an option.

Test before you publish

Studio offers several test modes, and each one catches different bugs.

Test What it checks
Play Starts the game with you as a player in Studio: quick checks
Run Runs the server only, with no character: great for scripts that spawn things
Play Here Starts at the current camera spot
Start with several players Opens a local server and several clients to test multiplayer
Team Test Invites teammates to edit and test the same place together
Device Emulator Previews phone, tablet and console screens and controls

Remember that testing in Studio is not the same as a real server. Studio ignores some network latency, and your DataStore access is switched by a setting. Once published, join the live game on a phone and on a PC, with a friend, before you tell anyone about it. Use Test > Local Server with 2 to 4 players to check remote events, leaderstats and round logic.

Look at the Output window while you test. Red lines are errors, orange lines are warnings. A clean log during a full play-through is a good sign.

The icon, thumbnails and description

The experience page is your shop window. Players decide in seconds.

  • Icon: a clear, square image that is readable at a small size. Show the main character or action; avoid tiny text.
  • Thumbnails: several wide screenshots or short videos showing real gameplay, not mock-ups. Roblox reviews images for appropriateness.
  • Name: short, memorable, accurate. Avoid misleading claims.
  • Description: what you do, how to play, and what is new. Put the key information in the first two lines.

Updating safely

After launch, you will fix bugs and add content. A safe update routine:

  1. Make changes in a separate copy or a test place of the experience (a "dev" place in the same experience) so the live game is untouched.
  2. Test with several players.
  3. Publish during a quiet time if possible, so fewer players are in servers.
  4. Remember that running servers keep the old version until they close. Roblox offers server shutdown on update in the settings, which makes players rejoin onto the new version. Use it for important fixes only.
  5. Watch the output and your analytics for new problems and be ready to revert.

A launch checklist you can run

This JavaScript stand-in encodes a checklist as data and reports what is still missing. It shows how to turn habits into something checkable.

JS Pre-launch checklist (JavaScript stand-in)

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Fix each FAIL, then rerun. The same list can live in your project notes.

JS Version history and revert

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Common mistakes

  • Publishing straight to the live game without testing.
  • Forgetting to make the experience public, then wondering why nobody can join.
  • Claiming console or phone support without testing controls and interface scaling.
  • Skipping the maturity questionnaire details, which can lead to moderation problems later.
  • Not keeping a backup .rbxl file before a big refactor.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the difference between Save to Roblox and Publish to Roblox?

    Saving keeps your work in the cloud without changing what players see. Publishing replaces the live version.
  2. 2. Which test mode helps you check multiplayer behavior like remote events?

    A local server with multiple clients lets you see how the server and several players interact.
  3. 3. Why should you open the experience on a real phone before announcing it?

    Touch controls, screen sizes and performance differ, so real devices reveal problems the PC does not.
  4. 4. After you publish an update, what do already running servers use?

    Existing servers keep running the old code. New servers use the new version, unless you shut down the old ones on update.

Summary

  • Save to Roblox stores a cloud version; Publish makes it live; Save to File makes a local backup.
  • Configure name, genre, devices, permissions, security and the maturity questionnaire in Game Settings and the Creator Hub.
  • Test with Play, Run, several-player local servers, Team Test and the Device Emulator, then on real devices.
  • The icon, thumbnails and description are your shop window.
  • Update through a test place, publish carefully and use Version History to revert.

Next: Monetization: Gamepasses, Products and Premium