Skip to content

No. 0401 TE TechEQLabs Pro

Widget Blueprint Auditor

UE 5.4–5.85/52.0.5

Module: Tech · Category: Performance · Tool ID: WidgetBlueprintAuditor

Project-wide UMG audit. Scans every UWidgetBlueprint for: deep nesting (>10 levels), excessive bindings (per-frame evaluations), high widget count (>100 per BP), tick-enabled widgets, invisible-but-active widgets with bindings (an easy-to-miss perf issue). CSV export for UI team review.

Auditor after scan, mixed Critical / Warning / Good widget BPs visible with column for each metric.
Auditor after scan, mixed Critical / Warning / Good widget BPs visible with column for each metric.
  • UI performance pass: finding the widgets eating frame time
  • Tick-enabled UMG audit: usually a bug
  • Invisible-but-active widget hunting: they still consume binding cost
  • Pre-shipping UMG cleanup
  • Don’t expect runtime UMG profiling. See Runtime Insights for that.
  • Don’t expect this to fix issues. Surfaces; per-BP fixes happen in the WBP editor.
  1. Open the EQLabs Hub and search for Widget Auditor (or browse to Tech → Performance).
  2. Click the tool card.
  3. Click Scan.
FieldWhat it does
ScanWalks every UWidgetBlueprint
SearchFilter by name
Problems OnlyHide healthy BPs
Export CSVSaves the audit
Copy ResultsPlain-text dump
StatsTotal Widget BPs / problematic count
Results listPer-BP row: name, widget count, max depth, binding count, ticking widgets, invisible-active count, severity, issue text
SeverityMeaning
GoodWithin thresholds
WarningCrossed at least one threshold
CriticalMultiple severe issues
  1. Click Scan.
  2. Toggle Problems Only to focus.
  3. Sort by severity / metric of interest.
  4. Single-click pings the WBP; double-click opens it in the UMG editor.
  • In-panel widget BP list.
  • CSV export
  • Clipboard. Copy Results.
  • Tick-enabled UMG widgets are almost always a bug. UMG ticks per-frame; refactor to event-driven.
  • Bindings cost per-frame evaluation. High binding counts add up. Replace with event-driven updates where possible.
  • Deep nesting (>10) often indicates an authoring problem. Splitting into multiple WBPs improves clarity and perf.
Report an issue with this tool

Opens our feedback form in a new tab with the tool name pre-filled.