// lab · roblox performance tool
MicroProfiler viewer
Drop in a MicroProfiler dump to see where the frame time goes: the slow frames, the busy threads, the timers that cost the most, and what each one usually means.
$ open dump
drop a dump here, or
● Read in your browser. The file is never uploaded, and this page's security policy stops it from sending data to any other site.
where do I get a dump?
- In the Roblox client or Studio, open the MicroProfiler with Ctrl+Alt+F6 (Mac: ⌘⌥F6).
- Stand where the problem happens and give it 10 to 30 seconds to settle.
- Open the profiler's Dump menu and pick a frame count. Roblox exports at most 60 at a time, and the full 60 gives the steadiest numbers.
- The file lands in the Roblox logs folder:
%LOCALAPPDATA%\Roblox\logson Windows,~/Library/Logs/Robloxon macOS.
Reads MicroProfilerDump_*.html, microprofile-*.html, log_*_microprofile_*.html and .gprx captures, from 2023 dumps to today's LibMP format. A few dumps from mid-2024 crash the parser packed inside them and can't be opened here. Game-server dumps come from the Developer Console (F9 → MicroProfiler → Server).
$ file
$ frame times
click a frame to inspect itCPU frame spike GPU time · dashed lines: 60 and 30 fps budgets
$ frame
engine scripts waiting · drag across the chart to zoom in, double-click to zoom out
$ busiest threads ms/frame
$ main thread own time, ms/frame
$ spikes
$ all threads summed, ms/frame
$ scripts inclusive, ms/frame
$ who calls the top timers
$ engine counters
Analysis follows Roblox's own parsers: older dumps run the parser packed inside them, newer ones use Roblox's LibMP (MIT). Explanations tagged roblox docs come from Roblox's MicroProfiler tag table; likely and a guess are informed readings, so confirm them with a before-and-after capture.