[quote]
[Update] July 10, 2026
Hi Creators,
Today, we’re excited to launch the new Scene Analysis tool that lets you quickly identify and resolve performance issues in your game, on both client and server. You should be able to catch and debug issues before they impact your players, and our goal is to give you the tools to do it
With it, you’ll be able to flip through different modes, including script memory, unparented instances, audio memory, animation memory, and an instance composition view. It also provides an extended scene triangle breakdown with counts for things like particles and terrain triangles. Each view will give you a real-time treemap view of what is consuming the most resources, both in the editor and when you open a test session, and then directly trace it back to the instances causing the usage.
You can also access Scene Analysis data programmatically through Class.SceneAnalysisService,more on the service here. Each method returns tables containing nested children with the same data the visual display uses.
Why should I use this tool?
We highly recommend opening the Scene Analysis tool every now and then throughout development, especially when you’ve recently written a lot of code or added a bunch of assets. It’s most powerful when you have it open during a test session; it’s the easiest way to spot “silent killers” like scripts cloning unparented parts, heavy memory usage from scripts, sounds or animations, or that “simple” new asset that’s secretly rendering a million triangles.
Regularly checking will allow you to tackle any issues faster; letting it accrue for too long and you may create a tangle of tech debt that you’ll need to spend time to unwind and resolve.
To try Scene Analysis:
- Enable the Scene Analysis beta feature in File > Beta Features.
- In the menu bar, select Window > Performance Summary > Scene Analysis.
Scene Analysis Views
-
Script Memory View: Pinpoints Luau memory usage across scripts and modules to help you optimize table and script allocations. Right-click any script to jump directly to it in the Explorer.
-
Unparented Instance View: Detects scripts holding onto object references to help you identify and fix potential memory leaks. Scripts holding onto Instances is completely normal on its own, but if you’re investigating a memory leak this view makes it easy to spot a script doing something unexpected. It pairs well with the Dev Console’s Luau Heap Memory Profiler when you need deeper allocation info.
-
Instance Composition View: Provides a high-level audit of all active instances to help you balance scene complexity and reduce replication costs. Maybe you didn’t mean to have 25,000 particle emitters - this view will let you know.
-
Audio Memory View: Monitors the memory footprint of audio assets and locates all active instances for efficient resource unloading. Right-click any audio asset to select all instances referencing it.
-
Animation Memory View: Tracks the lifecycle of animation assets to prevent common memory leaks caused by lingering script references. Animations are one of the most common memory leaks we see in production: Roblox aggressively unloads unused animation assets, but scripts often cause animations to stick around after their parent model has been destroyed. Right-click any animation to select all instances using it.
-
Triangle Composition View: Breaks down drawcalls and triangles to help you optimize viewport performance and scene density.
Hover over each rectangle in the treemap to understand what the asset is, and click to jump directly to the responsible instances in the list view below.
Script Memory Usage - On the left, you can see how much memory each script is using; the larger the rectangle, the more memory is being used.
Instance Composition - This provides a count of how many instances are in the scene; the larger the rectangle, the more instances.
What’s next for performance tooling
We plan to expand the Scene Analysis tool to include more metrics and different views, and we’ll share more as soon as it’s ready. Scene Analysis currently shows values from your local machine only, and memory usage will vary on players’ devices. We’re planning a device performance simulation API for tighter Scene Analysis integration with simulated devices.
We’re also building alerts into analytics so you know when there’s a spike in crash rates and other major regressions. The Assistant and MCP Server can already tap into Scene Analysis data through the APIs, and we’re working on ways to make it even more useful in your agentic workflows.
In the meantime, we’d love to hear what else you’d like to see us add here! Leave a comment or question with your thoughts below!
Big thanks to @KoalaSpaceProgram, @BobaTops, @MontxiMontxi and @Rusi_002 for their work in building this, and special thanks to @IcyTides and @ignotuscaligo.
