Fix: Editor Utility Widget Not Appearing in Unreal

Editor Utility Widgets are one of Unreal Engine’s most useful tools for building custom editor interfaces—asset management panels, batch processing tools, debug dashboards. But they have a frustrating failure mode: you create the widget, set up the UI, hit play, and nothing happens. No error, no window, no feedback. The widget simply doesn’t appear.

Check the Parent Class

The single most common cause of invisible Editor Utility Widgets is inheriting from the wrong class. When you create a new Widget Blueprint in the Content Browser, Unreal defaults the parent class to UserWidget. An Editor Utility Widget must inherit from EditorUtilityWidget instead.

Open your widget blueprint and click the “Class Settings” button in the toolbar. Look at the “Parent Class” field. If it says UserWidget, that’s your problem. You cannot simply reparent an existing widget blueprint to EditorUtilityWidget in all cases—depending on your engine version, the reparent may silently fail or lose widget bindings.

The safest approach is to create the widget correctly from the start. In the Content Browser, right-click and choose Editor Utilities → Editor Utility Widget. This creates a blueprint with the correct parent class already set. If you have an existing UserWidget with complex UI that you want to convert, create a new Editor Utility Widget and copy your widget hierarchy over using the designer view.

Running and Registering the Widget

Unlike regular UMG widgets, Editor Utility Widgets don’t appear automatically. You need to explicitly run them. Right-click the widget asset in the Content Browser, select Asset Actions → Run Editor Utility Widget. This opens the widget in a new editor tab.

If the “Run Editor Utility Widget” option doesn’t appear in the context menu, the asset’s class is not recognized as an editor utility. Double-check the parent class as described above. Also verify that the Blutility plugin is enabled in your project settings under Edit → Plugins.

For C++ editor modules that need to spawn a widget programmatically, register a tab spawner in your module’s startup:

// In your editor module's StartupModule()
void FMyEditorModule::StartupModule()
{
    FGlobalTabmanager::Get()->RegisterNomadTabSpawner(
        TEXT("MyCustomTool"),
        FOnSpawnTab::CreateRaw(this, &FMyEditorModule::SpawnToolTab))
        .SetDisplayName(FText::FromString("My Custom Tool"))
        .SetMenuType(ETabSpawnerMenuType::Hidden);
}

TSharedRef<SDockTab> FMyEditorModule::SpawnToolTab(const FSpawnTabArgs& Args)
{
    // Load and create the Editor Utility Widget
    UEditorUtilityWidgetBlueprint* WidgetBP = LoadObject<UEditorUtilityWidgetBlueprint>(
        nullptr,
        TEXT("/Game/EditorTools/MyWidget.MyWidget"));

    UEditorUtilitySubsystem* Subsystem =
        GEditor->GetEditorSubsystem<UEditorUtilitySubsystem>();
    Subsystem->SpawnAndRegisterTab(WidgetBP);

    // Return a dock tab (the subsystem handles the actual widget)
    return SNew(SDockTab).TabRole(ETabRole::NomadTab);
}

void FMyEditorModule::ShutdownModule()
{
    FGlobalTabmanager::Get()->UnregisterNomadTabSpawner(TEXT("MyCustomTool"));
}

Forgetting to unregister the tab spawner in ShutdownModule is a common source of crashes when the editor shuts down or when hot-reloading modules.

Module Dependency Issues

If your Editor Utility Widget uses a custom C++ base class or references types from other modules, you need the correct dependencies in your .Build.cs file. Missing dependencies don’t always produce compiler errors—sometimes the module loads but the widget class silently fails to resolve.

At minimum, your editor module should include these dependencies:

// MyEditorModule.Build.cs
PublicDependencyModuleNames.AddRange(new string[]
{
    "Core",
    "CoreUObject",
    "Engine",
    "Slate",
    "SlateCore",
    "UMG",
    "UMGEditor",
    "Blutility",
    "UnrealEd"
});

The Blutility module provides the EditorUtilityWidget base class. UMGEditor provides the editor-side widget infrastructure. If either is missing, your widget may compile but fail to register as an editor utility. Also ensure your module is listed with Type = ModuleType.Editor in your .uproject file. A runtime module cannot load editor-only dependencies.

Troubleshooting Widget Visibility

If the widget runs but appears blank or shows incorrect content, check these common issues. First, verify that your widget’s root element has a non-zero size. Editor Utility Widgets don’t automatically fill their tab—set the root Canvas Panel or Size Box to “Fill” in the designer. Second, check for construction script errors by looking at the Output Log when you run the widget. Blueprint errors during Construct or PreConstruct will silently abort widget creation.

If your widget previously appeared but stopped showing after an engine upgrade, the internal widget registration may be stale. Delete the Saved/Config directory in your project (or at minimum the EditorPerProjectUserSettings.ini file) and restart the editor. Unreal caches tab layouts and widget registrations, and stale entries can prevent widgets from spawning.

For widgets that appear in Editor builds but not in Development Editor builds, check your build configuration. Some modules may be conditionally compiled out depending on the build target. Use #if WITH_EDITOR guards around editor utility code and ensure the module loading phase is set to PostEngineInit in your .uproject descriptor.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Unreal Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

This bug class disproportionately affects late-stage development. The work to surface it is interactive testing in realistic conditions, which only really happens after the gameplay is in place and assets are populated. Catching it early requires deliberate testing of conditions that look unimportant.

At the engine level, the behavior comes from a deliberate design decision in Unreal. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

After applying the fix, the verification step has three parts: confirm the original repro is resolved, confirm no obvious regressions in adjacent functionality, and (for shipping titles) deploy to a small player cohort first and watch the crash and report rates. Each step catches something the others miss.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

For shipping titles with a long support window, watch for this issue resurfacing after dependency updates. Engine upgrades, driver updates, OS releases - each one can resurface a bug class you thought you'd fixed because the underlying behavior changed slightly. Regression tests catch the obvious ones; player reports catch the rest.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

Diagnostic approach

Before applying any fix, gather enough context to be confident you're addressing the actual cause and not a similar-looking symptom. The cheapest diagnostic step is reproducing the bug deterministically - if you can't get the same failure twice in a row, your fix attempts will be hard to evaluate. Lock down the reproduction first.

For Unreal-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

Within Unreal, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Edge cases for this class of issue often involve specific timing: the first frame after a state change, the last frame before a transition, frames where multiple subsystems update simultaneously. Reproducing these reliably is part of what makes the bug class hard to test.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

Editor Utility Widgets are powerful once they’re working—the setup just has a few gotchas that aren’t well documented.