Source check needed for build.playtest. The supporting documentation has not been verified within its review window. Consult the current official sources before relying on this rule.
Create the link when the control is available
Use this sequence only if the intended account exposes the testing and sharing controls. If either is absent, record that state and stop the relevant procedure; do not infer access from a tutorial.
- Open the current Build project.
- Play the latest version yourself once.
- Choose Share.
- Choose Get Playtest Link.
- Send the link only to the intended testers.
A playtest link lets you gather feedback before the publishing flow and its public-release rules apply. Roblox Support documents this control, but official rollout wording is not fully aligned.
How many friends can join a Roblox Build playtest?
Roblox Creator Hub says a private playtest link can be shared with up to 10 friends. Each tester needs a Roblox account and must be age 9 or older.
This is a sharing limit, not a concurrency figure. Roblox does not state how many testers can be active at once in the reviewed official page.
Give testers a focused brief
Ask about behavior they can observe:
- Was the goal clear in the first 30 seconds?
- Did the main interaction work every time?
- Where did progress become confusing?
- Could they tell when the round ended?
- Did any control or interface element block play?
Focused questions produce revisions that are easier to turn into a single Build prompt.
Convert feedback into changes
Group duplicate observations, reproduce the issue yourself and request one change at a time. For example:
Testers could not see when the round ended. Add a centered results panel showing score and a restart button. Keep the current arena and controls unchanged.
Use the prompt framework for the revision and playtest again before publishing.
AI allowance during testing
Playing and playtesting do not use AI allowance. Chat messages and AI changes do, so separate observation from revision: test freely, decide what matters, then spend usage on the clearest change.
The AI usage guide explains why every AI instruction should be treated as usage even though the playtest itself does not consume the allowance.
Why is the Playtest button missing?
Roblox’s current first-party pages are not fully aligned on playtest rollout. Support documents Playtest and playtest links as part of the Build flow. Creator Hub also contains a notice that playtesting is coming soon, immediately alongside usage instructions.
If the control is missing on an otherwise eligible account, its cause remains unconfirmed; neither rollout nor app version is a diagnosis for that account. Verify regional availability, Android or iOS mobile access, age-check eligibility and record the installed Roblox app version. Support now names New Zealand, Serbia and Singapore. Mac is mentioned in Availability but omitted from eligibility; read that separate conflict. Do not bypass region or account restrictions.
Common problems
- The link is shared too widely: treat it as a private test link and control recipients.
- Testers see unclear instructions: rewrite the goal inside the game rather than explaining it only in a message.
- Every comment becomes a prompt: prioritize repeated or blocking issues first.
- The project changes after sharing: generate a fresh test pass for the version you intend to publish.
- The Playtest control is missing: recheck eligibility and app version; the current official rollout wording conflicts.
Read the documented creator and private-sharing boundaries alongside the unresolved availability note. After publishing, a clear gameplay capture can support Moments and discovery, but it cannot guarantee reach.
Keep link, version and recipient results separate
Hypothetical session record: intended version—delivery cue revision; link action—not yet attempted; recipient label—invited tester; entry result—unknown; task—complete a delivery without coaching; feedback—blank until observed. A copied link is not an observed successful entry, and a recipient error is not a gameplay failure.
After entry succeeds through an authorized path, check that the intended version opens, attempt the task and record its result. After a revision, verify that version again rather than carrying an earlier pass forward. If entry fails, retain the visible error and stop short of an in-game conclusion; do not ask for credentials or invent a link-reset procedure.