Build's creation entry is absent or remains locked on the intended account. An opened but empty or loading surface is a different state, not proof that the entry is missing.

Record the intended account, actual app surface and visible entry state before changing anything. Keep identity documents, passwords and private verification images out of the record.

Check the requirements in order

  1. Supported region: current Support names New Zealand, Serbia and Singapore in initial testing. Check the availability guide for the rollout boundaries.
  2. Age: the account holder must be at least 9 years old.
  3. Completed age check: finish the required age check on that account.
  4. Android or iOS mobile: both are in the current checklist. See Android setup or iPhone/iPad status.
  5. Fully close and reopen: for a missing entry, reopen Roblox after checking the requirements and preserving unfinished changes. Do not interrupt an active generation to apply this absent-entry recommendation.

This order separates region access from account and platform checks. A missing tab alone does not establish a bug.

If the tab still does not appear

Check that the age-check result belongs to the account currently signed in. Seeing the tab on another account does not prove access on yours. If the tab is present but locked, complete the age check through the prompt or account settings and reopen Build.

Roblox's documented troubleshooting steps do not include VPNs, region switching or account-location manipulation.

Mac has a separate documentation conflict

Support’s Availability wording mentions Mac desktops, but its eligibility checklist still only lists Android or iOS mobile devices. Creator Hub remains mobile-first. Missing Mac access leaves the account result unresolved; the documentation conflict does not diagnose its cause or prove a broken account.

The PC/Mac guide keeps those statements together. Windows is not currently listed in Build’s access requirements.

Common problems

  • Age 9+ without an age check: the profile age alone is not enough.
  • Age checked but no tab: region and platform conditions still apply.
  • App left open during setup: after the missing-entry checks, preserve unfinished work and use the ordinary reopen step only when no active generation would be interrupted.
  • Old advice says iOS is unsupported: the current Support checklist now includes it.

What Roblox has not confirmed

There is no complete future country schedule, exact unlock delay or guaranteed access date for every eligible account. Save the account’s visible status and any error message if you need to explain the problem to Roblox Support.

Choose the branch from the visible state

No creation entry is visible

Check each documented condition on the intended account, keeping unmet and unknown conditions separate. Use the missing-tab reopen recommendation only after those checks and when active work will not be interrupted.

The entry is visible but locked by an age-check request

Follow the actual prompt or account-settings age-check path, then reopen Build. Record the outcome rather than assuming a completed capture screen proves successful verification.

The device wording conflicts with the expected entry

Retain the conflicting source sections beside the account observation. Ask which documented workflow applies; do not install an unofficial client or move the project into Studio as an access test.

An entry opens an empty or loading area

Keep the fact that the entry exists and use the visible-state guide to distinguish an empty area, loading indication and explicit notice. Do not delete or replace a project to test navigation.

Preserve a small observation record

The least-destructive action is to read the current requirements and record the exact entry state without changing truthful account information, clearing app data or creating a replacement project.

Hypothetical comparison: the intended account shows a completed age check, the ordinary app has no creation entry, and the device source wording remains conflicting. After a safe ordinary reopen the entry is still absent. Record completion, unresolved device scope and unchanged absence separately; no account defect, fixed unlock deadline or tested workaround follows from this example.

Retest the entry, not a new game

  • Compare the same intended account and app surface before and after any documented action.
  • Name the result as absent, requirement-blocked, interface-open, empty or loading; a newly visible locked entry is not full creation access.
  • Preserve any unresolved condition and the actual notice. If no safe comparison is available, mark it not checked rather than interrupting active work.

When to ask for official help

If the documented checks leave an unexplained absence or contradictory requirement, send Roblox Support the redacted state record, relevant source section, device/app context, observation time and actions already tried. Share private account details only through the legitimate official support flow; this site does not collect verification material or promise an unlock.