Confirmed rollout facts
Roblox Support now names New Zealand, Serbia and Singapore during Build’s initial testing. The July 16, 2026 announcement scheduled the New Zealand public alpha for July 28, 2026. That launch announcement is different from the current named-market list.
| Platform | Current Support wording | What it establishes |
|---|---|---|
| Android mobile | Listed in Availability and eligibility | Supported platform; other requirements still apply |
| iOS mobile | Listed in Availability and eligibility | Supported platform; account/region rollout still applies |
| Mac desktops | In Availability, absent from eligibility | An unresolved official documentation conflict |
| Windows | Not currently listed | No confirmed Windows Build-tab availability |
The table records current Support wording, not the whole post-RDC story. The September 11 announcement explicitly adds desktop access to the expansion. The Mac contradiction remains within Support; RDC does not provide a universal OS/account matrix. The PC/Mac status guide and RDC change record explain the combined evidence.
How to read country status
A named market is an official rollout statement, not proof that every account there qualifies. Distinguish current named markets from future plans: Roblox has not provided a complete expansion timetable.
Use the Android guide, iOS guide and age-check guide for their separate requirements. An app-store listing or another person’s screenshot is not evidence of country-wide Build availability.
Check your own access
- Check the latest official market statement.
- Build requires users to be age 9 or older.
- Complete the account age check.
- Use an Android or iOS mobile device under the current eligibility checklist.
- Fully close and reopen Roblox.
If the tab is still missing, use the Build not showing checklist. For Mac, review the conflicting documentation before treating absence as a broken account. Do not use VPNs or account-location changes as an access workaround.
What is still unpublished?
Record an account observation
For an editorial example, a reader in a named market records an Android device and a completed age check, but the Build tab is absent. The market statement and account observation belong in different fields: the observation does not erase the official market listing, and the listing does not establish access for that account.
After reopening the intended account, record whether the Build entry is absent, opens an age-check prompt, or reaches the creation interface. The observable success condition for this access check is reaching that interface on the intended account; a store listing, a friend's screenshot or merely restarting the app is not that result. Keep an unresolved record for Support rather than marking access confirmed.
Roblox has not published a complete future country schedule, a universal account unlock delay, or a Build-specific device-model table. The three named markets above are the current confirmed initial-test markets; this page does not infer additional countries.
Common problems
- A friend nearby has Build: eligibility and rollout can differ by account.
- The Roblox app opens: that alone does not establish access to every Build feature.
- An older guide says Android-only: current Support explicitly lists iOS too.
- Mac is named in one paragraph: read the same page’s checklist before assuming universal access.