# Timing Insights

**URL:** <https://forums.unrealengine.com/t/timing-insights/2762582>\
**Category:** Roadmap\
**Tags:** q3-scale-perform, unreal-editor-for-fortnite, fortnite-creative, fortnite\
**Created:** [September 4, 2026, 3:00pm UTC](https://forums.unrealengine.com/t/timing-insights/2762582 "2026-09-04T15:00:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ThomasC\_Epic](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/thomasc_epic/32/1203341_2.png) [@ThomasC\_Epic](https://forums.unrealengine.com/u/ThomasC_Epic)\
**Post date:** [September 4, 2026, 3:00pm UTC](https://forums.unrealengine.com/t/timing-insights/2762582/1 "2026-09-04T15:00:00Z")

</div>

### **Status**

Complete

Timing Insights breaks each frame down into the individual operations that consumed it, so a hitch can be attributed to the specific work that caused it.

Timing Insights records the operations making up each frame of a live session and displays their cost on a timeline — the same view Unreal Engine developers use for CPU profiling. Developers chasing hitching or low framerate currently narrow the cause by disabling systems one at a time and re-testing. Timing Insights measures frame time, not memory, and it requires a live session.
