Features Pricing Scanner Docs
Tools
Profiler Viewer Blog Discord Dashboard
Free tool · Profiler Viewer

Every millisecond,
with a name on it.

Drop a FiveM profiler capture. We rebuild the full call tree and trace each span to the resource that actually ran it: obfuscated threads, event handlers and export calls included. No more “unknown”.

Drop your profiler .json here

or pick it from your computer

Stays in your browser 100 MB+ captures welcome Truncated files still load
Capture

Record a profile in under a minute

Record during the moment that feels slow: peak players, a lag spike, a busy scene.

Server

txAdmin live console or the server window.

  1. 1
    Start recording 1000 frames (about 50 seconds)
    profiler record 1000
  2. 2
    Wait until profiler status says it is done, then save
    profiler saveJSON profile.json
  3. 3
    The file is written next to your server's start script (run.bat / run.sh). Drop it above.

Client

In game, open the F8 console.

  1. 1
    Record 1000 frames while the problem is happening
    profiler record 1000
  2. 2
    Save it as JSON
    profiler saveJSON profile.json
  3. 3
    Or run profiler view and use Save profile in DevTools. Both formats work.
What you get

Built for finding the actual culprit

Real ownership

Anonymous threads and callbacks inherit the resource from their parent tick or event, the same way resmon bills them.

Frame flame chart

Click any frame to see exactly what ran inside it, nested, to the microsecond. Jump straight between hitches.

Injected code, exposed

Switch to “source owner” to move shared code (libraries, include scripts) back to the resource that wrote it.

Private by design

Parsing runs in a Web Worker on your machine. The capture is never uploaded, logged or stored anywhere.

Drop to analyze