Set up Roblox Studio on Mac

Outcome and prerequisites

You will open Studio, create a Baseplate, test it, and save a local place file. You need a supported Mac, an internet connection and a Roblox account you control. No paid subscription or game purchase is needed to install Studio.

Studio and the player are different tools

Roblox Studio is the development application. The Roblox player runs games for players. Installing the player alone does not give you the editor. Studio is officially available for Windows and Mac; you do not need Windows virtualization for this course. Xbox and mobile devices are player targets, not the Studio development environment.

As checked on 2026-10-03, Roblox lists macOS 10.14 and 3 GB RAM as minimums, and recommends macOS 14+ and 8 GB RAM. A modern Apple-silicon Mac with 16 GB RAM is a sensible learning setup, although complex scenes and many simultaneous test clients increase resource use. This is a suitability judgment, not a performance benchmark. Check Studio setup for changes before troubleshooting an older machine.

Install from the official source

1. Open the official Studio setup page and use its Download Studio control
2. Open the downloaded RobloxStudio.dmg and follow the installer
3. Launch Studio and sign in with your own account
4. If macOS blocks the app, read the message before acting. Verify that the installer came from Roblox; do not disable system security to make an unknown download run
5. Let Studio finish updating before starting a lesson

Do not paste passwords, cookies, recovery codes or authentication tokens into a tutorial, chat or script. A lesson never needs those secrets. Do not create an account for someone else as a shortcut to playtesting; account age and parental controls matter later.

Make your first local place

Select the Baseplate template. The central viewport shows a flat world and a spawn. If a welcome panel obscures it, close that panel rather than deleting objects in Explorer.

Open Explorer and Properties using Studio's Window menu or available toolbar controls. Open Output too. Menu arrangement changes; search for the panel name if it is not where a screenshot suggests. On a Mac laptop, a mouse with a scroll wheel makes 3D navigation easier, but a trackpad is workable.

Select the Baseplate in Explorer. In Properties, change its Color. Press the Play/Test button. Move your avatar, jump and confirm that you are in the scene you edited. Press Stop to return to editing. Avoid using the Run mode for this first check: it simulates without inserting your avatar.

Use Studio's local save option, typically File → Save to File, and save as obby-workshop-01.rbxl in a folder you can find again. Verify the file in Finder. Save a new numbered checkpoint before a major experiment; you can reopen an earlier local file if the experiment goes wrong. A local save is different from publishing to Roblox.

Understand edit and play mode

Studio creates a runtime simulation when you press Play. Objects created by scripts during that simulation normally disappear when you Stop. Changes you make while testing should not be treated as permanent edits. Stop first, then make the intended change in the edit data model.

This distinction explains a common frustration: a newly inserted coin can work during a test and then vanish on Stop. You added it to runtime state. Build persistent scene objects in edit mode, or deliberately generate them in a script at the start of every run.

Verify

• Studio opens without a startup error
• Baseplate and SpawnLocation are visible in Explorer
• Play inserts an avatar; Stop returns to edit mode
• A deliberate Color change made in edit mode remains after a test
• You can close and reopen the saved local place

Troubleshooting

You only see the Roblox game launcher: launch Studio, not the player. Your changes disappeared: check whether they were made during Play. Performance is poor: close extra test clients, begin with a Baseplate, and record the specific lag before changing graphics or system settings. A function key changes volume: use the visible Test controls; Mac keyboard settings can affect function keys.

Exercise

Create a second local save with a different color. Reopen the first, then the second. Explain which action saves your work locally and which action would upload it. Do not publish yet; the publishing lesson covers access and current requirements.

Sources and navigation

Verified 2026-10-03: Studio setup, testing modes, publishing and places.

Previous: Start here · Next: Studio data model · Related: Project map