How to make a game on Roblox: from Studio to a public game
A game starts as a single place in Studio, goes live through File Publish to Roblox — and is born PRIVATE: releasing it to the public is a separate step, afterwards. The whole path is below, step by step, with the official Roblox document that supports each one.
Produced with AI from the sources cited below and checked by automated verification against those same sources. The editor has not read this text yet; once he does, this notice will show who read it and when. Editorial Policy

Making a game on Roblox has two parts that people routinely collapse into one. The first is building: opening Studio, laying out the world, writing what happens. The second is publishing, which is what makes the game exist outside your own computer.
The confusion is expensive for beginners, because publishing is not the same as releasing. You can publish a game today and have it stay invisible to everyone — and that is how it is born, by design of the platform itself. This article walks the whole path, in order, with what Roblox's own documentation states at each step.
The short answer
A game on Roblox starts as a place. When you create a new project in Studio, it already comes with a single place, which is where players load in the first time they join. A game can have several places later, but it starts with one.
To put that place online, the path is File ⟩ Publish to Roblox. What happens on that click is concrete: Roblox stores the data model of your start place as a .rblx file in the cloud. That matters more than it sounds, because it is what ties the game to your account — from then on you can open and work on it from any computer.
And here is the part that catches almost everyone: a new game is born private. The documentation is explicit — by default, new games are set to private, accessible only to you as the creator, to users with Edit or Playtest access, and to group members with the right permissions. Releasing it to the public is your decision, later, as a separate step.
How to do it, in order
1. Open Studio and pick a template. Do not start from nothing as a matter of principle. Baseplate already comes with a spawn point and a floor; Platformer already comes with platforms, coin pickups and double-jump, dashing, rolling and long jump mechanics; Racing already comes with a car that drives. A template is not cheating — it is not spending your first week reinventing the floor.
2. Build, and test while you build. Roblox's documentation says it is important to test your game in various modes before releasing it to the public, and the reason is technical: the game runs on a client-server model, so there are things that work on your screen and not on anyone else's. Two shortcuts cover most of it:
- F5 (Test) starts the simulation and inserts your avatar at the spawn point or around coordinates (0, 100, 0).
- F8 (Run) starts the simulation without inserting your avatar. Useful for watching the world run from outside, with the Studio camera.
3. Test with more than one player, before publishing. This is the step almost nobody takes, and it is what separates a game that works from a game that "broke when the second player joined". The option is called Server & Clients, and it launches several Studio sessions at once — one acting as the server, the others acting as each client. Choose how many clients you want and press Play or F7. One or two clients is usually enough, though you can simulate up to eight.
4. Read the Output with an eye on colour. During a test, messages in the Output window are labelled blue when they come from the client and green when they come from the server. When something only breaks for one of the two, the colour of the message is your first clue about where to look.
5. Publish. File ⟩ Publish to Roblox opens the Publish Experience window, which asks for a few fields: name and description, the creator (you or a group) and the devices the game will support. For someone starting out, the default device options are fine. Click Create.
6. Only then release. Once published, the game is in the cloud and private. When you are ready for everyone to come in, that is when you release it to the public — and you can mark it as a beta if you want.
The table: where each step lives
The table below is the same path, organised by where each thing happens: inside Studio, in the publishing window, or afterwards, in the game's configuration. It exists because the question that comes up most is not "how do I publish", it is "I published and nobody can get in".
Look at the last column. Each row names the official document that supports that step and the day the page was consulted — because the Studio interface moves things around over time, and a button's name in 2026 may not be its name next year.
The catches
Publishing is not releasing. It is confusion number one, and it has a practical consequence: your game can be online, with a link and everything, and still return "unavailable" to the friend you invited. If that happens, the problem is not the link — it is that the game is still private.
Changing the name every week hurts you, it does not help. The documentation warns about it directly: renaming a game too often reduces the chances that players can find it using a previous name. The name is what a player types into search months later; every change erases a path that already existed.
Stuffing the name and description with repeated words can sink the game in discovery. The official text is blunt: frequent repetition of words or phrases may result in demotion of your game. That pattern of a name with the same word five times and a description listing famous games is not cleverness — it is the behaviour the platform penalises.
The first sentence of the description is the one that works. The official guidance is to summarise what the game is about in the first sentence, because that is where you get your chance to give the most accurate impression of its genre and content. Excessive emoji, by the same document, confuses players who want to identify the game quickly.
Closing a test window does not end the test. In multi-client mode, the right way to finish is the End Session button, from any of the sessions — it closes all simulated clients and the simulated server at once.
The next step
If you have never published, run the whole cycle today with the silliest game you can manage: a Baseplate with one block. Publish it, leave it private, invite one person with Playtest access, release it, and watch the game appear. The cycle takes minutes, and it is the one you will repeat for every game you ever make — with the detail that the second time, you already know where every button is.
If you have published and nobody shows up, the routine is different: check first that the game came out of private, then open a test with Server & Clients and join with two clients at once. A good share of what looks like no players is a game that breaks the moment the second one arrives.
And one thing worth keeping about the craft itself: the client-server model is not a programmer's footnote. It is the reason testing alone on your screen gives one answer and the live game gives another. Learning that in your first week saves you months of "it works here".
Sources
Ready-to-use artifact
| Step | Where it lives | What the official documentation says | Source, consulted 28/09/2026 |
|---|---|---|---|
| Create the project | Studio, **Open a Template** screen | the project starts with a single place, where players load in on joining | Create and publish games and places |
| Test alone | Studio, **F5** (Test) / **F8** (Run) | F5 inserts your avatar; F8 simulates without inserting an avatar | Studio testing modes |
| Test with several | Studio, **Server & Clients**, **F7** | launches several sessions — one server, the others clients; up to eight | Studio testing modes |
| Tell client from server | **Output** window | a blue message is the client, a green one is the server | Studio testing modes |
| End the multi-client test | **End Session** button | closes all simulated clients and the simulated server | Studio testing modes |
| Publish | `File ⟩ Publish to Roblox` | stores the start place as `.rblx` in the cloud and ties the game to your account | Create and publish games and places |
| Fill in the publish form | **Publish Experience** window | asks for name/description, creator and supported devices | Create and publish games and places |
| Release to the public | game configuration, after publishing | a new game is born private; releasing is a separate step, beta optional | Create and publish games and places |

