Source check needed for build.devices. The supporting documentation has not been verified within its review window. Consult the current official sources before relying on this rule.

RDC desktop expansion and the current Mac checklist

The official RDC announcement names desktop access alongside the asset library and iterative control. Availability and features vary by age and region. This page keeps that dated statement alongside the current device documentation rather than treating an earlier site snapshot as the latest news.

Roblox Support mentions Mac desktops in Availability, with Android and iOS mobile devices in New Zealand, Serbia and Singapore during initial testing.

The same article’s Who can use Build checklist still only names Android or iOS mobile devices, alongside age 9+, age check and region. Mac is omitted there. Creator Hub continues to describe a mobile-first rollout starting with New Zealand.

Support’s sections remain inconsistent, but the newer RDC statement now explicitly confirms a desktop expansion. The combined evidence still does not supply a device-model list or an unlock date for every account. Absence of the tab on a Mac is not enough evidence to label an account broken.

Current Windows status

Windows is not specifically named in the reviewed Support checklist. RDC's broader “desktop access” announcement should not be rewritten as universal Windows availability. A Roblox desktop-app installation or Studio access does not prove Build-tab eligibility.

Roblox has not published a confirmed Windows Build-tab date in these sources. The availability guide tracks region changes without extending them to unannounced platforms.

Android and iOS alternatives

Both mobile platforms are explicitly included in the current checklist. Build requires users to be age 9 or older. Follow Android setup or iOS access, then verify the age check and region. A listed operating system does not override the remaining requirements.

Use the ordinary Roblox app and your own account. Region manipulation or modified clients are not documented access fixes.

Build tab versus Roblox Studio

Make a desktop evidence record

Start with the actual desktop operating system and the account you intend to use. Copy the source section name beside each statement: Support Availability, Support eligibility checklist and the dated RDC announcement. Then inspect the ordinary Roblox app without installing an unofficial Build client.

For an editorial example, a Mac reader sees no Build entry even though Availability names Mac. Record “Mac named in Availability; absent from checklist; entry absent on my account.” That is an unresolved account observation, not proof of a broken installation or a Windows compatibility conclusion.

If an entry is present, record whether it reaches the creation interface or stops at a requirement prompt. If it is absent, leave account access unconfirmed. The evidence check fails if the conclusion says universal desktop access while its only support is the broad expansion announcement; keep that conclusion narrower than the announcement.

Build uses prompts and chat to generate and refine a game. Studio offers deeper manual editing in a separate creator environment. Installing Studio does not add Build access to an otherwise ineligible account.

The Build vs Studio comparison helps decide whether a project needs that extra control. Prepare the core loop and test plan first so the choice follows the work you need to do.

Moving a Build project into Studio

Before the handoff, playtest a stable Build version and save a description of its observed behavior. Creator Hub says editing in Studio permanently turns that version into a standard Studio game and removes Build status. Support separately says edits beyond prompting can remove its automatic Moderate rating and require the maturity questionnaire.

Read editing a Build game in Studio before making the change. Opening the same project in another interface does not make the product-state transition reversible.

How this status will be updated

The RDC hub records the new desktop statement. We will keep Mac, Windows and mobile access separate until the official sources justify a more specific compatibility claim. Prepare a first brief with the prompt builder while checking your account; do not use modified clients or region workarounds.