Fix: Godot 4 ResourceLoader.load Not Finding Imported Asset

In editor, load("res://art/icon.png") returns a Texture2D. Build and run the export — load returns null. The asset is in the project, it imports cleanly, but at runtime it’s gone. Two paths fix it; one of them is the right one.

The Symptom

load() works in editor playtest but returns null in export builds. Or a scene’s preloaded resource is fine but a runtime-loaded one breaks. No error is raised; the resource is simply not found.

What Causes This

Godot strips source files (.png, .wav, .glb) from exports. The PCK contains only converted resources (.ctex, .ogg, .scn). Loading by source path works in editor because the import system has the source in the project, but in export the source is gone.

Additionally, the export Filter includes only files that are referenced by scene tree or in the include filter. An asset loaded purely at runtime via a string path is not statically known to the exporter and may be stripped.

The Fix

Pattern 1: Load by UID. Right-click the asset in FileSystem → Copy UID. Use the resulting uid://... string.

var tex := load("uid://b73h9wkdex2c") as Texture2D

UIDs are stable across renames and re-imports. They’re also tracked by the export system, so the asset is included automatically.

Pattern 2: Add to export Filter. Project → Export → Resources tab → Filters to export non-resource files: list explicit paths or wildcards (e.g. art/*.png). For resources that are runtime-loaded, this guarantees they ship.

Pattern 3: Statically reference somewhere. Add the asset as an @export var field on a script in your scene. The exporter follows the scene tree and includes anything statically referenced.

extends Node

@export var spawn_icons: Array[Texture2D] = []   # filled in editor

func get_icon(name: String) -> Texture2D:
    for t in spawn_icons:
        if t.resource_path.contains(name):
            return t
    return null

Async Loads

For large textures or audio, prefer threaded loads:

ResourceLoader.load_threaded_request("uid://abc")
while ResourceLoader.load_threaded_get_status("uid://abc") == ResourceLoader.THREAD_LOAD_IN_PROGRESS:
    await get_tree().process_frame
var tex := ResourceLoader.load_threaded_get("uid://abc")

Diagnosing in an Export

Open the .pck with the Godot editor (drag the file into a fresh project) or use the godot-pck-tool. List contents; confirm your asset is present. If absent, the export filter excluded it.

Verifying

Run the export build with --verbose and grep for “load_threaded_request” or “load_failed.” The console prints which paths failed and why.

Understanding the issue

Asset pipelines transform source content into runtime data. Each stage can lose information, change behavior, or introduce platform-specific variations. Bugs at this layer are often invisible until the cooked build runs.

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

Bugs of this class are particularly easy to ship past internal QA because they often depend on specific runtime conditions - hardware combinations, network states, or asset configurations that QA didn't reproduce. Players hit them in the wild, file reports that are hard to repro, and the bug accumulates negative reviews while engineering tries to recreate the failure mode.

At the engine level, the behavior comes from a deliberate design decision in Godot. 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

Verifying this fix in isolation is straightforward: reproduce the bug, apply the change, confirm the bug no longer reproduces. The harder verification is regression - did this fix introduce a new bug elsewhere? Run your standard regression suite, plus any tests that exercise the same code path with different inputs.

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

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

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

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

Diagnostic approach

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

For Godot-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 Godot, 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

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

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

When this bug class affects multiple teams (often the case for cross-system issues), early communication prevents duplicate work. The team that owns the symptom may not own the cause. A 15-minute conversation at the start of triage often saves hours of independent investigation.

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.

“UIDs over paths. Static references where possible. Filter the export. Loads succeed in builds.”

Related Issues

For Godot export template missing, see export template. For preload vs load, see preload circular.

UID. Filter. Static ref. The asset ships.