Current rollout

Build entered public alpha on July 28, 2026, beginning with New Zealand. Current Support names New Zealand, Serbia and Singapore during initial testing and lists Android and iOS mobile devices. It still does not publish a complete future rollout schedule.

The September 11 RDC announcement now explicitly adds desktop access, an asset library and iterative control to the expansion. Support still names Mac in Availability but not in its mobile-only checklist. Read current desktop access before assuming universal Windows/macOS availability.

Treat the Build tab itself as an account-level availability signal—not proof that the feature is global. If the tab is missing, work through the Build not showing checklist instead of trying unsupported region workarounds.

Eligibility checklist

  1. Use the Roblox app on an Android or iOS mobile device under the current eligibility checklist.
  2. Confirm the account holder is at least 9 years old.
  3. Complete the required age check.
  4. Confirm Build is available in the account’s region.
  5. Close and reopen the Roblox app after completing the requirements.

Meeting one requirement does not override the others. See the availability guide, Android setup, iOS access and age-check guide for the separate checks.

Create, test and refine

Open the Build tab and describe a small game loop in natural language. Let Build generate the first version, play it, then ask for one clear change at a time. If generation stops before the game is complete, Roblox Support recommends typing please continue.

Playing and playtesting do not use the daily AI allowance; AI messages and changes do. Creator Hub still contains conflicting Playtest wording, so use the controls actually available and read the private playtest status. Start with how to create and the prompt builder.

Roblox’s current official documentation is inconsistent on 3D: Creator Hub describes a 2D/2.5D focus with 3D expansion ahead, while Support says both 2D and 3D games can be created. The 3D support status keeps those statements separate.

AI usage and Robux

Build is free to start and does not currently require a subscription. Creator Hub treats each message, including follow-up changes, as one prompt. Free prompts reset daily; after they run out, a creator can wait for the reset or buy more credits with Robux. Creator Hub says purchased credits do not expire, while Support documents optional automatic top-ups and a daily spend limit.

Roblox has not published one universal daily prompt count or Robux rate in the reviewed official pages. The AI usage guide explains what counts without inventing a number.

Publishing and audience

Publishing starts with a safety check. Newly published Build games are initially available to age-checked players age 16 or older, with some regional exceptions. Eligible Build games can pursue Roblox Select for ages 9–15. Roblox’s current engagement benchmark is 250 unique plays from Highly Engaged age-checked users within 60 days; Build games still cannot be made available to Roblox Kids ages 5–8. Read the 16+ audience and Select guide for the detailed entry and maintenance rules.

Build games use Roblox’s normal retention-based discovery system. AI-generated content receives no special discovery preference. Read the publishing workflow, then use discovery and Gameplay Videos and Creator Analytics to understand results after release.

Studio handoff

RDC describes analytics and monetization management from Build, with phone-based ad campaigns coming soon. Use Creator Analytics and the monetization hub to separate current management from future features. The integration roadmap does not yet reverse the documented Studio editing consequence.

Build and Studio can work with the same project. Moving beyond prompt-based edits—for example, by adding custom code in Studio—can remove Build’s automatic Moderate rating. The creator must then complete the content and maturity questionnaire before publishing.

Plan that transition with Build vs Studio and editing a Build game in Studio.

Common problems

  • Build tab missing: verify region, age, age check and Android/iOS device; review Mac separately.
  • Generation paused: type please continue.
  • Generation stuck: use the documented recovery and check Creations before restarting.
  • Robux charged but no game: separate the project, credit and top-up records before Support.
  • Prompt blocked: remove restricted or protected material; do not evade safeguards.
  • Daily AI usage empty: wait for the next-day reset or review the in-app Robux option.
  • Safety check failed: revise the issue described by Build and retry publishing.
  • Studio or manual edits: review the handoff consequences before changing the project beyond prompting.
  • Published game removed: read the moderation notice and use the documented appeal path.