Gaming · Platform not recorded
Create a Roblox Game Pass
Source-checked About 10 minutes
Answer
Publish the experience, open its Creator Dashboard page, then select Monetization > Passes to create a one-time Roblox game pass.
Confirm the starting state
Before following the procedure, confirm ownership of a published accessible experience, the intended pass benefits, icon rights, price implications, and the Creator Dashboard account before creating an asset. Record the current state so the result can be compared without guessing or erasing useful evidence. Note any affected data, permissions, purchases, security controls, or files that must remain intact.
Publish and select the experience
Ensure the experience is published and accessible, then open it from Creations in Creator Dashboard.
Create the pass
Open Monetization > Passes, choose Create pass, upload an eligible icon, then enter the pass name, description, and category.
Configure sale settings when ready
After creation, open the pass's Sales settings, enable Item for Sale, set the Robux price, and save the change.
Verify the result
After completing the supported steps, confirm that the pass appears under the intended experience with the correct asset ID and a controlled test confirms any scripted benefit before sale. Repeat the original task once so a cached or temporary result is not mistaken for a durable fix, then check that the protected account, data, permissions, and settings still have their intended state.
Troubleshoot Create a Roblox Game Pass
If the experience is unpublished, ownership or permissions differ, moderation is pending, the pass is attached to the wrong experience, or the implementation never grants the promised benefit, stop broad resets and return to the last known safe state. Record the exact message, account or device scope, versions, and failed step before using the linked official support route.
Video walkthrough
Sources and verification
Checked against official documentation on . Scope: Platform not recorded.
Freshly re-qualified against the linked current first-party documentation; follow that source if labels differ after a platform update.