Textures blurry in Unreal Engine 5 usually have one of four causes. The texture streamer has not loaded the full resolution, often because its memory pool is full. A scalability or texture setting is capping the resolution. The texture has no mipmaps because its size is not a power of two. Or the surface simply has too few pixels for its size. The fastest check: open the texture asset and compare its source size with the Max In-Game size in the Details panel. If they match, start with streaming. If Max In-Game is smaller, a setting is shrinking it.
Each cause is covered below, with how to spot it and how to fix it. We checked the settings and console variables against Epic's Unreal Engine 5 texture documentation. Labels can differ slightly between 5.x versions.
Why are my textures blurry in Unreal Engine 5?
Use this table to narrow it down before changing anything.
| What you see | Likely cause | Fix |
|---|---|---|
| Sharp after a few seconds or when you move closer | Texture streaming still loading mips | Usually nothing; check the pool if it never sharpens |
| Many textures stay soft, worse in big levels | Streaming pool too small | Check STAT STREAMING, raise r.Streaming.PoolSize |
| Everything got soft after changing quality | Texture quality set low in Engine Scalability | Set Textures back to High or Epic |
| One texture is soft, others are fine | LOD Bias, Maximum Texture Size, or Texture Group | Check the texture's Level of Detail settings |
| Soft at a distance, shimmer-free but mushy | Mipmaps, filtering, or Mip Gen Settings | Check Filter and Mip Gen Settings |
| Texture never gets sharp and has an odd size | Non-power-of-two dimensions | Resize to 1024, 2048, 4096, and so on |
| Soft everywhere, even fully loaded | Too few pixels for the surface size | Tile more, or use a higher resolution texture |
| The whole frame is soft, not just textures | Screen percentage or upscaling | Check render resolution, not texture settings |
How to check what resolution a texture is actually using
Before changing settings, find out what the engine is doing.
- Open the texture asset. Double-click it in the Content Browser. In the Details panel, the Texture Asset Editor docs describe two useful readouts: Displayed, the size currently shown in the preview, and Max In-Game, the largest size the texture can be in game. Max In-Game is never larger than the imported source, but configuration and texture settings can make it smaller.
- Check the streaming stats. Open the console and type
STAT STREAMING. Epic's texture streaming metrics page explains the counters. The one to watch is Required Pool. Epic notes it can exceed 100% of the streaming pool, and when it does, some textures will not load at their required resolution. - Use the texture streaming view modes. Unreal has texture streaming accuracy view modes, including Required Texture Resolution, which shows the relationship between the streamed resolution and the resolution the view needs. In Epic's legend, red means two or more mips are missing, yellow means one is missing, white means good data, and cyan and green mean extra mips are loaded.
If Max In-Game is lower than you expect, go to Fix 3. If the stats or view modes show missing mips, start with Fix 1.
Fix 1: Let texture streaming catch up, or give it more memory
Unreal does not keep every texture at full resolution all the time. The texture streaming overview describes how the streamer computes an ideal resolution for each texture from the mesh bounds, the texel size of its UVs, and the camera position, then checks whether the memory pool can hold it. If it cannot, it lowers the planned quality of selected textures one mip at a time until the plan fits the budget.
That is why a texture can look soft for a moment after loading a level and then sharpen. That part is normal. If textures stay soft, the pool is likely too small for the scene.
- Build texture streaming data. Click the dropdown arrow next to Build in the toolbar and choose Build Texture Streaming. Epic says this generates the component and level data the streamer uses at runtime.
- Check the pool with
STAT STREAMING. If Required Pool is well over the streaming pool, the streamer is dropping mips to stay in budget. - Raise the pool size. The texture streaming configuration docs describe
r.Streaming.PoolSizeas the pool size in MB available for textures. Typer.Streaming.PoolSize 3000in the console to test a larger value. The pool also holds UI textures, cubemaps, and textures set to never stream, so it fills faster than you might expect. - Make the change permanent only if it helps. Console commands reset when you restart. If a larger pool fixes it, set it in your project's config or device profile, and check it against the graphics memory your target hardware actually has.
Two more console variables come up in forum answers. r.Streaming.FullyLoadUsedTextures 1 streams all used textures to their maximum available resolution and keeps them in memory. r.TextureStreaming 0 turns the streamer off, and Epic notes that every mip then loads fully, even for textures that are never rendered. Both are useful to confirm that streaming is the cause. Neither is a good default for a large project, because they spend memory on detail the camera cannot see.
Fix 2: Check Engine Scalability texture quality
If everything turned soft at once, check the quality preset. In the editor, open the viewport's Performance and Scalability menu. The scalability reference lists what each Textures level changes:
| Textures level | sg.TextureQuality |
r.Streaming.MipBias |
r.Streaming.PoolSize |
r.MaxAnisotropy |
|---|---|---|---|---|
| Low | 0 | 2.5 | 200 | 0 |
| Medium | 1 | 1 | 400 | 2 |
| High | 2 | 0 | 700 | 4 |
| Epic | 3 | 0 | 1000 | 8 |
At Low and Medium, the mip bias tells the streamer not to load the largest mips, and the pool is smaller. Anisotropic filtering also drops, which makes floors and roads lose detail faster at grazing angles. Set Textures to High or Epic while you judge materials. If you set a lower level on purpose to keep the editor fast on a weaker machine, remember that it changes how every texture looks.
Fix 3: Check the texture's own settings
If one texture is soft and the rest are fine, the cause is usually on that asset. Open it and look at these properties, all described in the Texture Asset Editor docs:
- LOD Bias (Level of Detail). A bias to the index of the top mip level to use. A value of 1 skips the full-resolution mip, 2 skips two. Set it to 0. Epic's texture settings page notes that this value is added to the LOD Bias of the texture's group.
- Texture Group (Level of Detail). Each group has its own LOD Bias and maximum size set in the project's device profiles. A world texture placed in a group meant for small or distant assets can be clamped without anything looking wrong on the asset itself.
- Maximum Texture Size (Compression, advanced). The maximum resolution for generated textures. 0 means the maximum size for the format on each platform. If someone set this to 512 or 1024 to save memory, the texture is capped there.
- Downscale (Level of Detail, advanced). Only applies to textures without mips. A value above 1.0 scales the texture down.
After any change, check that Max In-Game now matches the size you expect.
Fix 4: Use power-of-two texture sizes
This one catches textures exported from photo tools or cropped by hand. Epic's Textures in Unreal Engine page says power-of-two sizes can be mipmapped and streamed, and non-power-of-two sizes are never streamed and do not generate mipmaps.
A 1500 by 1500 texture therefore has no smaller versions to pick from at a distance. Depending on the view it can look harsh and noisy, or soft. Resize the source to a power of two, such as 1024, 2048, or 4096, and reimport. Square is not required. 2048 by 1024 is fine.
Fix 5: Check Mip Gen Settings and Filter
Mipmaps are smaller copies of the texture used when it covers fewer pixels on screen. They are the reason distant surfaces look smoother than the full image. That is correct behavior, but two settings change how soft the result looks:
- Mip Gen Settings defines how the mips are made. Options include SimpleAverage, Sharpen, Blur, NoMipMaps, and FromTextureGroup. If a texture was set to one of the Blur options, its mips are softened on purpose. The Sharpen options apply sharpening when the mips are generated.
- Filter (Texture settings, advanced) sets the sampling mode: Nearest, Bi-linear, Tri-linear, or Texture Group. For pixel art that should keep hard pixel edges, use Nearest. For photo textures, leave it on Texture Group.
Do not set Mip Gen Settings to NoMipMaps just to make a texture sharper at a distance. It usually trades blur for shimmer and aliasing. We cover this in more detail in our guide to Unreal Engine PBR texture import settings.
Fix 6: Give the surface enough pixels
If the texture is fully loaded and every setting is right, it may just be stretched over too much surface. A 2048 pixel texture across a 10 meter floor gives you about 2 pixels per centimeter. That reads fine from a distance and soft from close up.
You have two ways to fix it:
- Tile the texture more. For a seamless material, add a TexCoord node and raise UTiling and VTiling, then connect it to the UVs input of every Texture Sample so the maps stay lined up. Our guide to making a material in Unreal Engine 5 walks through this.
- Use a higher resolution texture. Worth it for surfaces the camera gets close to. Our 1K vs 2K vs 4K PBR textures guide covers when the extra pixels actually show.
Tiling more is usually the better first move, because larger textures cost memory in every map of the set and add to the streaming pool. The catch is visible repetition if the texture has strong one-off features. If the mesh uses unique UVs instead of a tiling material, small UV islands get few pixels. Unreal's Mesh UV Density Accuracy view mode is one of the streaming accuracy views listed in the streaming overview, and fixing island sizes happens in your modeling tool. In Blender, our UV unwrapping guide covers it.
Fix 7: If the whole frame is soft, check render resolution
If everything looks soft, including edges and lighting, the textures are probably fine and the frame is being rendered at a lower resolution and upscaled. Epic's screen percentage page explains that screen percentage renders a lower or higher resolution image than the one presented. At 83% on a 1920 by 1080 screen, the render targets are about 1600 by 900 before upscaling. Epic notes that some material detail is lost at lower screen percentages, even with temporal upsampling. Check your screen percentage and upscaler settings before changing any textures.
When the texture itself is the problem
Sometimes every setting is right and the image is just soft. An out-of-focus photo, a heavily compressed JPEG, or a 1K image saved as 4K will not look sharp in any engine, because the detail was never there. Open the source file at 100% zoom outside Unreal to see what you actually have.
If you need a sharper version of the same surface, look for a higher resolution download from the same source. Our list of free PBR texture sites compares where to look and what each license allows. twirl's public concrete, brick, and wood materials download for free without an account, as separate albedo, normal, roughness, metallic, and height maps. twirl can also generate a surface you cannot find. It generates PBR sets at 1024 by 1024, a power of two, and paid plans can upscale to 2x or 4x for closer shots. We make twirl, so weigh our opinion of it accordingly. There is no Unreal plugin yet, so you import the files by hand. A bigger texture will not fix a full streaming pool or a capped texture group, so check the fixes above first.
FAQ: blurry textures in Unreal Engine
Why are my textures blurry until I get close in Unreal Engine?
That is texture streaming. The engine loads higher mips as the surface needs them. If they never load, or load only when you are very close, check STAT STREAMING and raise r.Streaming.PoolSize, then build texture streaming data.
How do I fix "texture streaming pool over budget" in Unreal Engine 5?
The streamer wants more texture memory than the pool allows, so it drops mips. Raise r.Streaming.PoolSize within what your graphics memory allows, reduce Maximum Texture Size on textures that never get close to the camera, and make sure distant or small assets are not using 4K maps.
Should I turn off texture streaming to fix blurry textures?
As a test, yes. r.TextureStreaming 0 loads every mip fully. As a fix, usually no. Epic notes it loads all mips even for textures that are never rendered, which can use a lot of memory in a large level.
Why is one texture blurry but the others are sharp?
Check that texture's LOD Bias, Maximum Texture Size, Texture Group, and dimensions. Compare Max In-Game with the source size in the texture editor.
Why are my textures blurry in a packaged build but not in the editor?
Epic notes that the editor and the game have separate Texture Group settings, and scalability levels can differ between them. Check the device profile and scalability settings for your target platform, and check STAT STREAMING in the build.
Is a blurry texture the same as a wrong-looking material?
No. Blurry is about resolution. A material that looks washed out, too shiny, or inverted usually has a color space, compression, or green channel problem. See our guides to PBR texture color space and the Unreal Engine normal map green channel. If you work in Blender too, see why textures are blurry in Blender.
Sources
- Epic Games: Textures in Unreal Engine
- Epic Games: Texture Asset Editor
- Epic Games: Texture Format Support and Settings
- Epic Games: Texture Streaming Overview
- Epic Games: Texture Streaming Configuration
- Epic Games: Texture Streaming Metrics
- Epic Games: Building Texture Streaming Data
- Epic Games: Scalability Reference
- Epic Games: Screen Percentage with Temporal Upscale
