Skip to content Home Free launch checklist FREE RESOURCE / 20 PRACTICAL CHECKS Before you publish,run the checklist. Use this with any Roblox project, whether you started from a template or a blank baseplate. Work through setup, gameplay, data, and release checks without losing track of the basics.
Download the text checklist ↓ Free to use and adapt for your projects. Updated August 27, 2026. This is a manual planning aid, not an automatic audit or a guarantee of security, platform approval, or earnings.
0 of 20 checked Progress stays on this browser and device. No account or email needed.
Clear checks 01 Start with a safe working copyKeep the original source untouched Save a separate working copy and a version you can return to after each major change. Run a baseline playtest Record the starting behavior and Output errors before editing so you can distinguish existing issues from regressions. Review scripts and dependencies Identify server entry points, LocalScripts, ModuleScripts, external dependencies, and unfamiliar code before running or replacing it. Confirm the destination and source license Use the intended Roblox account or group and check that your license covers the experience you plan to publish. 02 Make the experience your ownReplace project branding Review the game name, icons, thumbnails, UI text, welcome messages, and credits. Check asset permissions Verify that required images, audio, animations, meshes, and packages load for the destination experience. Review experience-specific identifiers Check purchase, badge, group, place, and other configuration IDs. Replace values that belong to a different experience. Test the first-time player journey Start with a fresh test profile. Can someone find the objective, perform the first action, and understand the reward? 03 Play through the awkward casesTest with separate clients Use a server with at least two test clients. Compare what each player sees and what the server records. Handle departures and respawns Try leaving during a round, resetting a character, joining late, and starting a second round. Check touch and smaller screens Use Studio's device tools and, when possible, a real phone. Check buttons, readable text, camera behavior, and essential actions. Review errors and performance Repeat the core loop while watching client and server Output. Investigate repeated errors and avoidable work before release. 04 Protect progress and purchasesKeep tests away from live player data Use an isolated test experience or data setup. Do not enable Studio access to production stores just to clear an error. Test saving and returning Earn a reward, leave, and rejoin. Check the result with fresh and existing test accounts, including a simulated failure path. Validate important actions on the server Do not let client-provided values decide currency, inventory, wins, or purchase fulfillment without server checks. Verify each purchase and reward path Check IDs, displayed prices, cancellation, duplicate receipt handling, and the correct reward. A visible shop alone is not proof of fulfillment. 05 Prepare a release you can supportReview current publishing requirements Check the destination experience's access, supported devices, content settings, and Roblox's current publishing requirements. Make the public listing accurate Use screenshots and descriptions from your own finished version. Do not promise systems or rewards that are not available. Play the published test version Verify joining, the core gameplay loop, UI, asset loading, and a return visit outside your local editing session. Keep a recovery plan Save the release version, know how to return to a working build, and provide a way for players to report problems. Turn on JavaScript to save checkmarks, or download the text version to use offline. All checklist items are readable above.
NEED THE WORKFLOW BEHIND THE CHECKS? Learn it.Then test it. Our creator guides cover fishing-game customization, speed-escape balancing, multiplayer test cases, and choosing editable source.
Official references: Studio testing · Data stores · Publishing
Read the guides →