Roblox's Create page, at create.roblox.com/dashboard/creations, is where you make one experience public and attach a Game Pass, and the work splits into two settings that have to match: the experience's own Playability and Public/Private switch, and the Game Pass item's sale status. Miss either and buyers see nothing. The experience must be published before it has a Playability setting at all, and a Game Pass stays invisible until it is priced and set for sale from its own Configure page.
What the Create Dashboard Actually Shows When You Open Creations
The Creations page is a table of everything your account owns, split into Experiences, Places, and Development Items, and each row carries the experience's visibility state in plain text. Before you touch anything, read that column. Roblox marks unpublished work as Private automatically, so a new experience slots into the list with no public listing and no way for anyone outside your account to reach it.
The number of rows you see depends on how much you've built. A creator with a single test place sees one entry; a studio account can have dozens, and Roblox's own Creator Hub interface paginates that list rather than showing everything at once. Find your target by name in the Experiences tab rather than scrolling blindly.
Two things on this page cause most confusion. First, the Creations list is a management view, not an editor β nothing you click here changes your game's code. Second, the visibility label in the table can lag behind what you just changed in the experience's settings until you refresh the page. If the label looks wrong after an update, reload before assuming the change failed.
Your account also needs to be able to publish at all. Roblox requires age verification or ID verification for creators in some regions before publishing is unlocked, and the requirement surfaces as a blocked publish button rather than an error message. Confirm the Publish option is available on your account before planning a launch around it.
Publishing Your Experience First Because Private Games Have No Playability Setting
A game that has never been published has no audience setting to change, and this trips up nearly everyone doing this for the first time. Roblox only presents Playability options, including Public, after the place exists on the server. You publish first, then open the settings, then choose who can join.
| Stage | Where you are | What the visibility control says | What a visitor sees |
|---|---|---|---|
| Never published | Studio, local save only | No Playability option exists | Nothing β no page at all |
| Published, default | Creator Hub experience settings | Private | Nothing β no listing |
| Published, set to Public | Creator Hub experience settings | Public | The experience page, joinable |
| Public plus Game Pass on sale | Experience page, Store tab | Public | Store section with a buy button |
The practical order is: finish the build in Studio, publish it from Studio's File menu, then return to the Creations page to flip visibility. Publishing from Studio and changing visibility from the browser are two separate actions, and Roblox keeps them separate on purpose so a save in the editor doesn't accidentally expose unfinished work.
If the Publish option is greyed out in Studio, check that you're signed into the correct account and that the place belongs to a group you have publishing rights in. Group-owned places require the group role to include place editing; a personal account can't publish into a group's experience list without that permission.
One more boundary: publishing an experience does not publish its places as separate public games. Sub-places stay reachable only through the main experience unless you deliberately list them, which is why some creators think their game is public when only a hub is.
Switching One Experience From Private to Public Without Exposing the Rest
Roblox treats visibility as a per-experience setting, so you can open one game to the world while twenty others stay locked. That's the whole point of the "make one public" half of this task, and the mechanism is a single radio control inside the experience's settings rather than a bulk action.
Steps, in the order the interface presents them:
1: Go to create.roblox.com/dashboard/creations and sign in with the owning account. 2: Open the Experiences tab and click the name of the game you want to expose. 3: On the experience's page, open the Settings or Configure area. 4: Find the Playability section and select Public. 5: Save the change and reload the Creations list to confirm the row now reads Public.
Failure handling matters here. If the Public option is disabled, the experience usually has an age-rating or content-maturity questionnaire outstanding β Roblox requires the experience questionnaire to be completed before it can be listed publicly, and the settings page links directly to it. Complete that first, then return.
If the save appears to work but the game still isn't discoverable, the cause is often the experience being set to private at the start-place level or restricted to friends. Check the same Playability panel for a friends-only or private override, and confirm no access code is set.
Adding a Game Pass Through the Experience's Own Store Tab
A Game Pass in Roblox is a one-time purchase attached to a single experience, and it lives inside that experience's page rather than in your account-wide inventory. You create it from the experience's Store or Passes section, give it a name, description, icon, and price, then set it for sale.
1: Open the now-public experience's page from the Creations list. 2: Go to the Store or Passes tab under that experience. 3: Choose Create a Pass, then fill in the name, description, and icon image. 4: Set the price in Robux. Roblox takes a 30 percent marketplace cut, so a 100 Robux pass returns 70 Robux to you. 5: Open the pass's Configure page and confirm its sale status is On Sale, not Off Sale.
The failure mode that wastes the most creator time is a fully built pass sitting at Off Sale. Roblox creates passes in an unsold state, and a pass that isn't explicitly on sale shows no buy button on the experience page even when the game is public. The pass's own sales setting is independent of the experience's visibility, which is exactly why both have to be checked.
Pricing deserves a beat of thought. Because the 30 percent cut applies to every sale, a pass priced at 50 Robux nets 35, and Roblox's minimum and maximum price boundaries shift with platform policy, so confirm the current allowed range on the pass configuration page rather than assuming a figure.
The Two Switches That Must Agree or Buyers See Nothing
Here's the part the scattered tutorials skip: making an experience public and putting a pass on sale are two separate permissions, and the store only renders when both say yes. A public game with an off-sale pass shows an empty store. A private game with an on-sale pass shows nothing at all.
| Experience visibility | Pass sale status | What a visitor experiences |
|---|---|---|
| Public | On Sale | Store visible, buy button works |
| Public | Off Sale | Store empty or pass hidden |
| Private | On Sale | No experience page reachable |
| Private | Off Sale | Nothing, as expected |
The clean verification loop is short: after saving both changes, open the experience page in a logged-out browser or a second account. If the store section appears with a purchasable pass, both switches agree. If the page loads but the store is blank, revisit the pass's Configure page first β that's the more common of the two failures.
Roblox's commerce system also processes pass purchases through its own servers, so a newly created pass can take a short while before the buy button renders for other users even when everything is configured correctly. If the store is missing on a second account immediately after publishing, wait and re-check before hunting for a settings error.
One edge case worth knowing: a pass whose icon fails moderation review will be withheld from sale until it clears. Roblox moderates pass icons and names, and a rejected asset leaves the pass in a state that looks like it's on sale in your dashboard but isn't purchasable. Check the pass's moderation status if a correctly priced, correctly enabled pass still won't sell.
Why a Public Experience Can Still Be Invisible in Search
Public is a permission, not a promotion. Roblox's discovery surfaces β the charts, the recommendations, the search results β rank experiences by engagement signals, and a freshly public game with no players has almost none of them. Setting visibility to Public puts your page on the internet; it doesn't put your game in front of anyone.
The experience's name, description, and thumbnail do the first filtering job. Roblox search matches on title text and genre tags, so a game named something nobody types will not surface regardless of its public status. Genre selection happens in the same settings area as Playability, and an unset genre keeps an experience out of genre-filtered browsing entirely.
Age ratings interact with discovery too. Roblox restricts certain experiences from younger users based on the content maturity questionnaire, so an experience marked for older audiences loses a large share of the platform's audience in recommendations. That's a deliberate policy choice, not a bug, and it's worth filling the questionnaire accurately rather than optimistically.
What actually moves a public game toward visibility is retention β session length and return visits. Roblox has said publicly that its discovery algorithms weight engagement, and no amount of settings tweaking substitutes for players staying in the game. Treat visibility as the last step, not the first.
How Group-Owned and Individual Experiences Differ in This Workflow
If the experience belongs to a Roblox group rather than your personal account, every step changes hands. The Creations page shows group-owned experiences only when you switch the owner context, and the public/private toggle requires a group role with sufficient permission.
Steps for a group-owned game:
1: On the Creations page, switch the owner selector from your username to the group. 2: Confirm your group role includes experience editing and publishing rights. 3: Open the experience and change Playability to Public as normal. 4: Create the Game Pass from the group-owned experience's Store tab, not your personal one. 5: Verify the pass's revenue routes to the group's funds, which Roblox pays out through its group payout system.
The mistake to avoid is building the pass under your personal account and assuming it attaches to the group game. Passes belong to the experience that created them; a personal-account pass cannot be sold inside a group experience, and the Store tab won't offer it.
Group payouts also carry their own schedule and thresholds set by Roblox's group payout rules, so revenue from a group pass doesn't land in your personal Robux balance automatically. If you're the developer being paid by a group owner, that arrangement is separate from the pass sale itself.
Timing and Verification: What to Check and When
Roblox doesn't publish a fixed propagation window for visibility or store changes, so the honest guidance is to verify rather than wait a stated number of minutes. The reliable test is a second account or a logged-out browser, and the reliable trigger is a hard refresh of the experience page.
Work through the checks in this order when something looks wrong. First, is the experience actually published and Public in its settings? Second, is the pass On Sale in its own Configure page? Third, did the pass icon pass moderation? Fourth, is the viewing account old enough for the experience's age rating? Each question eliminates one layer, and the order matches how often each one is the culprit.
Caching affects what you see more than what buyers see, because your own browser holds the creator dashboard state aggressively. If the Creations row still says Private after you set Public and saved, log out and back in before assuming the save failed β the settings page itself is the source of truth, not the list view.
For a launch, do the settings work well before you announce anything. Flipping visibility and enabling a pass takes a few minutes, but moderation of new pass icons and any age-rating review can take considerably longer, and those are the delays you can't click your way out of.
Common Errors and What Each One Actually Means
Every failed attempt at this task produces one of a small set of symptoms, and each symptom points at a specific cause. Matching symptom to cause saves the guesswork.
| Symptom | Most likely cause | Fix |
|---|---|---|
| Publish button greyed out in Studio | Not signed in, or no group publish rights | Sign in with the owning account; check group role |
| Public option disabled in settings | Content maturity questionnaire incomplete | Complete the questionnaire, then retry |
| Experience page loads, store empty | Pass set to Off Sale | Open the pass's Configure page and enable sale |
| Pass shows On Sale but no buy button elsewhere | Icon or name failed moderation | Replace the asset and wait for review |
| Second account can't find the game | Age rating excludes that account, or search ranking buries it | Check rating; share the direct link instead |
| Changes not reflected in Creations list | Dashboard cache | Refresh, or sign out and in |
Two of these deserve emphasis. The greyed-out publish button is almost never a Roblox outage β it's an account or permission problem, and checking your group role resolves it more often than waiting does. The empty store with a public game is almost always the off-sale pass, because that default catches first-time creators constantly.
If none of the fixes land, the remaining path is Roblox's own support documentation for experiences and passes, which is updated as the Creator Hub interface changes. Confirm the current menu labels there if your dashboard doesn't match the paths described above, since Roblox renames sections periodically.
FAQ
Does making an experience public automatically make its Game Passes purchasable?
No. A pass stays unsold until you open its own Configure page and set it to On Sale, and Roblox creates every new pass in an off-sale state by default. The experience's Public setting governs who can load the game; the pass's sale status governs whether the buy button renders. Treat them as two separate approvals that both have to be granted.
Can I make just one experience public while others stay private?
Yes, because visibility is stored per experience rather than per account. Each row in the Creations list carries its own Playability setting, so opening one game leaves every other game exactly as it was. There's no bulk publish control on the Creations page, which means there's also no risk of a stray click exposing a whole portfolio.
Why is my Game Pass not showing up in my game after I made it?
The usual cause is the pass sitting at Off Sale, followed by a pass icon that failed Roblox's moderation review. A third possibility is that the pass was created under a different owner than the experience β a personal-account pass won't appear in a group-owned game's store. Check the pass owner first, then its sale status, then its moderation state.
What percentage does Roblox take from a Game Pass sale?
Roblox deducts a 30 percent marketplace fee on each pass sale, so a pass priced at 100 Robux returns 70 Robux to the creator. That rate applies to passes the same way it applies to other avatar and marketplace items. Confirm the current fee on Roblox's own developer documentation before setting prices, since platform economics can change.
Do I need to publish from Studio before I can change visibility on the website?
Yes. An experience that has only ever been saved locally has no Playability setting, because Roblox has nothing on its servers to configure. Publish the place from Studio's File menu first, then return to create.roblox.com/dashboard/creations, where the experience will appear with a Private label and a working Public option.
How long does it take for a newly public experience to appear in search?
There's no published delay Roblox commits to, and search ranking depends on engagement rather than a timer. A brand-new public game with no players typically won't rank for anything, so the direct experience link is the reliable way to share it early. Discovery follows retention, not visibility.
Can a private experience have a Game Pass on sale?
You can configure a pass as On Sale while the experience is still private, but nobody can reach the store because nobody can load the experience. The pass configuration isn't blocked by visibility β it's simply useless until the game opens. That's why the order of operations matters: public first, then verify the store.
What happens to Game Pass revenue for a group-owned experience?
Revenue from a group experience's pass goes to the group's funds, not to the individual who created the pass, and the group distributes it through Roblox's group payout system on its own schedule. If you're building for a group as a contractor, your payment arrangement sits entirely outside the pass sale and needs to be agreed separately with the group owner.