Fix: Unreal Texture Streaming Pool Exceeded Warnings

Here is how to fix Unreal “Texture streaming pool over budget” warnings. Your game runs, textures appear blurry at random, and the log or screen shows a streaming pool warning. Cranking r.Streaming.PoolSize makes it go away but hides the real problem. The actual issue is that your level is asking for more texture data than the GPU pool can hold at once, and the streamer is evicting or demoting mips to fit.

The Symptom

On-screen log: Texture streaming pool over 1024.00 MiB budget, usage 1289.12 MiB. Textures appear blurry or low-res intermittently. Distant objects’ textures pop in as the camera approaches. In packaged builds the warning is usually suppressed but blurry textures remain.

Variant: one camera angle is fine, another pans over a blurry wall. Or the game starts clean but gets worse the longer you play a map.

What Causes This

Pool size too small for the scene. The streaming pool is a GPU memory budget (default 1000 MiB on PC). Every texture visible on screen contributes to usage. Big scenes with high-res textures easily exceed this.

Non-streaming textures eating the budget. UI textures, render targets, and any texture with Never Stream = true are loaded at full size all the time. They do not count against the streaming pool but they count against total GPU memory, and many teams leave large textures as non-streaming by mistake.

High texture resolutions on small objects. A 4K texture on a pebble wastes 16 MB of budget. Matching texture resolution to the screen-space size of the object is the cheapest fix.

LOD bias wrong. Texture assets have LODBias and MaxTextureSize. Default is to stream full resolution when near, which is fine, but shipping packages can strip mips if MaxTextureSize is set wrong.

Cooked data mismatch. The editor may show 2048 textures but packaging cooks them at a different size due to TextureGroup settings. Production builds differ from editor.

The Fix

Step 1: Measure actual pool usage. In the console:

r.Streaming.PoolSize 2000
stat streaming

The stat streaming HUD shows Current Used, Max Required, and pool budget. If Required is 1800 MiB and pool is 1000 MiB, you have an 800 MiB deficit. Either raise the pool or reduce required.

Step 2: Raise pool size in DefaultEngine.ini.

; Config/DefaultEngine.ini
[/Script/Engine.RendererSettings]
r.Streaming.PoolSize=2000
r.Streaming.LimitPoolSizeToVRAM=1

2000 MiB is a reasonable value for modern PC GPUs with 6 GB+ VRAM. On consoles, match the platform’s memory budget — PS5 and Xbox Series X have less headroom than 2026-era PCs.

Step 3: Reduce high-res textures on small objects. In the Content Browser, filter by Texture. Sort by Resource Size. Anything over 4 MB and used only on small props should probably be 1024 instead of 4096:

// In the Texture editor, set:
// Compression Settings: Default (DXT1/5)
// Max Texture Size: 1024
// LOD Group: World or WorldSpecular

Or set it via C++ for batch processing:

for (UTexture2D* Tex : Textures)
{
    Tex->MaxTextureSize = 1024;
    Tex->PostEditChange();
}

Step 4: Use Texture Groups. Texture Groups let you apply LOD bias across whole categories. For UI, set NeverStream. For Characters, apply moderate bias in shipping. Edit in Project Settings > Engine > Texture Streaming > TextureLODGroups, or via config:

[/Script/Engine.TextureLODSettings]
@TextureGroup=Group=World,LODBias=0,MaxLODSize=2048
@TextureGroup=Group=Character,LODBias=0,MaxLODSize=2048
@TextureGroup=Group=UI,LODBias=0,NeverStream=true

Step 5: Disable streaming on always-visible assets. For textures that are in every frame (sky, UI, main character), NeverStream = true keeps them resident full-size and avoids pool churn. Count them against overall GPU memory, not streaming budget.

Debug with Texture Streaming Stats

The most useful tools:

• stat streaming — overall pool usage
• stat streamingdetails — per-texture breakdown
• ViewMode TextureStreamingPrimitives — color code primitives by texture usage
• ViewMode TextureStreamingAccuracy — shows if textures are under/over streamed

Green = ideal resolution. Red = under-streamed (pool exhausted). Blue = over-streamed (more resolution than needed).

Per-Actor Streaming Control

For specific actors that should prefetch textures regardless of camera distance (cinematic actor, hero NPC):

MeshComp->PrestreamTextures(5.0f, true);

This tells the streamer to bring those textures to full mip for the next 5 seconds regardless of screen size. Useful right before a cutscene triggers so cutscene actors do not show blurry.

“Pool over budget means your scene wants more mips than you reserved. Raise the pool or lower the ask.”

Related Issues

For performance profiling more broadly, see Physics Constraint Drive Not Working. For content pipeline questions, SplineComponent Tangent Wrong Direction covers related asset issues.

Measure first, then raise pool or reduce ask. Small objects do not need 4K textures.