Does editing in Studio remove Roblox Build status?

The September RDC integration direction does not yet change the rule below. Roblox describes connecting management and future scene workflows, not a released guarantee that Studio-edited versions can return to Build. See the RDC change record and Scene Generator plan.

Roblox Creator Hub says editing a Build game in Studio permanently turns that version into a standard Studio game and removes its Build status. That cannot be undone for the edited version.

Creator Hub also says the prompt history is saved, so recreating the game through Build may be possible. Recreation is not the same as converting the Studio-edited version back into a Build game.

Build status and the automatic Moderate rating are not the same thing

Build status is the product state described by Creator Hub. Its current wording says Studio editing removes Build status from that edited version.

The automatic Moderate rating is a separate publishing workflow described by Roblox Support. Support says changes beyond prompting—for example, adding custom code—can remove the automatic rating. The creator must then complete the content and maturity questionnaire before publishing.

Support does not say that merely opening the project in Studio removes the rating. Its current wording ties that consequence to changing the game beyond prompting.

When should you move a Build game to Studio?

Move only when the project needs a Studio capability worth the handoff, such as deeper manual editing or custom code. Before moving:

  1. Playtest the current Build version.
  2. Record its core loop, controls and known issues.
  3. Identify the exact Studio change the project needs.
  4. Assume the handoff is not reversible for that version.
  5. Re-test the complete game after editing.
  6. Re-check the publishing and rating requirements.

If full 3D world editing is the reason for moving, read the current 3D support status before deciding. Roblox’s official pages do not yet agree on Build’s present 3D capability.

Make the handoff deliberately

  1. Open the Build project in Roblox Studio using the available project workflow.
  2. Confirm the correct project and current playable state.
  3. Make one focused manual change.
  4. Test the complete loop, not only the changed element.
  5. Repeat for additional edits.
  6. Review the publishing and maturity-label flow before release.

Treat the move as a one-way handoff for that version, not a reversible experiment. After changes beyond prompting, complete the content and maturity questionnaire when Roblox requires it.

Publishing after Studio edits

Run a fresh safety and content review of the actual Studio version. Check all generated and manually added content, then follow the rating and publishing steps shown by Roblox.

The publishing guide explains the initial 16+ audience, while Build vs Studio helps choose the right transition point.

Publish with Notes after the Studio handoff

In Studio, File → Publish with Notes can draft a publish summary from the version notes written since the previous publish. The creator can edit, write or dismiss it; nothing is published without manual approval. No version notes means no generated summary. The current feature summarizes notes, not an independently inferred history of every place-file change.

This is a Studio workflow, not a Build-chat feature. It does not reverse the loss of Build status for the edited version. See the official Publish Notes announcement and the separate post-publish Build update path. For platform access, use PC/Mac status; Studio installation and Build-tab eligibility are different questions.

Common problems

  • The wrong version is edited: verify the playable baseline before changing it.
  • A custom edit breaks the loop: test start, progress, fail and restart paths.
  • The old rating is assumed to persist: complete the questionnaire when required.
  • Publishing expectations changed: follow the current Studio-side flow for the edited project.

If deeper dimensional editing is the reason for the handoff, review the current 3D support conflict before treating a broader Roblox AI capability as universal Build-tab availability.