THE SHORT ANSWER
Roblox Studio's new Server Inspection beta adds a read-only Server view to Team Test sessions, letting developers inspect the live server's instance tree, properties, 3D world, and server-side scripts with breakpoint debugging. The feature is enabled via File > Beta Features > Server Inspection. Known limitations include empty scripts for runtime-created scripts, unlocked editing tools in the Server view that don't persist changes, and single-user debugging per session.
- Server Inspection beta adds a read-only Server view to Team Test sessions in Roblox Studio
- View shows live server DataModel including ServerScriptService, ServerStorage, and all runtime instances
- Supports breakpoint debugging on server scripts, building on the Remote Breakpoints beta from May 2026
- Server view receives full place data even with StreamingEnabled, unlike client view
- Known issues: empty scripts for Instance.new/ cloned scripts, editable UI that doesn't persist, single debugger per session
Roblox has released a Studio beta that lets developers watch the server side of a Team Test session in real time. The new Server Inspection feature adds a read-only Server view showing the live Data Model, including ServerScriptService and ServerStorage, with the ability to open server scripts and set breakpoints.
What Server Inspection Adds
During a Team Test session, Studio now opens a second connection to the test server. That connection appears as a Server view alongside the existing Client view. The Server view displays the server's complete instance tree, properties, attributes, and 3D world. Instances created at runtime — clones, spawned parts, and similar — appear as soon as the server creates them.
Places with StreamingEnabled behave differently between views. The Client view still streams content normally based on player proximity. The Server view receives the entire place and never streams content out, so developers can inspect parts far from any player. Every player's character moves and animates in the Server view as they play.
Script Access and Debugging
Double-clicking any script in the Server Explorer opens it with the source the server is currently running. This includes scripts in ServerScriptService, ModuleScripts and Scripts stored in ServerStorage. Breakpoints work the same way they do in solo Test mode, building on the Remote Breakpoints beta released in May 2026.
How to Enable
- Open Studio and go to File → Beta Features
- Check the Server Inspection box
- Click Save and restart Studio if prompted
- Open a Team Create place, select Team Test in the ribbon's test-mode selector, and click Start
Known Limitations
The beta has several issues the team is actively addressing:
- Some scripts appear empty. This affects scripts created with Instance.new("Script"), loaded from assets, cloned scripts, and scripts in the Team Test client view. A fix for cloned scripts and client scripts is expected next week; runtime-created scripts will follow.
- The Server view's Explorer, Properties window, command bar, and script editor still accept edits. Those edits never reach the server and are lost when the session ends, but the UI doesn't prevent them yet.
- Scripts show the source from when the session started. Edits made in Edit mode after Team Test begins, plus uncommitted drafts, won't appear.
- Only the person who started the Team Test session can debug with breakpoints. Other participants get their own Server view but cannot set breakpoints.
- Early-execution breakpoints may not trigger, consistent with the Remote Breakpoints behavior.
- Only ServerScriptService and ServerStorage are exposed from server-only services.
Part of a Broader Testing Push
Server Inspection joins Remote Breakpoints as part of Roblox's ongoing work on collaborative testing tools. The Studio team referenced the RDC Creator Keynote for additional testing features in development. Feedback on the beta will shape the full release.