Z-fighting in Blender often shows up as flickering surfaces, jagged stripes, or a pattern that changes whenever the camera moves. It is particularly frustrating in product visualization, architectural scenes, and models intended for games or web viewers because the asset may look fine in one view and broken in another. The problem is not always caused by the same defect. Sometimes two polygons occupy exactly the same position; other times the renderer cannot distinguish surfaces separated by a very small distance. The most effective repair depends on knowing which situation you have. This guide explains how to diagnose the source, clean overlapping geometry, adjust clipping settings, and test real-time exports without introducing new modeling errors.

Why surfaces flicker even when the model looks correct

A model can look stable from one angle and suddenly display crawling lines, striped patches, or rapidly changing colors when the camera moves. This effect is commonly called z-fighting. It happens when two surfaces compete for nearly the same depth value, making it difficult for the renderer to decide which one should be visible. The result may resemble a broken material, but changing textures usually does not solve it. Z-fighting can appear in Blender’s viewport, in game engines, in glTF exports, and in architectural walkthroughs. The useful first step is to separate overlapping geometry from depth precision problems. Both can produce similar symptoms, yet they require different fixes.

Identify the symptom before changing geometry

Orbit around the object and watch whether the pattern changes with viewing distance. If stripes occur only on one wall, panel, decal, or duplicated object, overlapping faces are likely. If many distant surfaces shimmer as the camera moves, depth-buffer precision may be involved. Switch temporarily to Solid shading to remove complex material nodes from the investigation. Then hide nearby objects one at a time in the Outliner. If the flicker stops when an object is hidden, inspect the relationship between that object and the remaining mesh. Record the camera distance and shading mode where the problem is easiest to reproduce; these details help distinguish an actual geometry defect from a display artifact.

Find duplicate objects and overlapping faces

Accidental duplicates are a frequent cause of flickering. An object copied in place may have exactly the same coordinates as its original, so both draw in the same location. In Object Mode, select the suspect mesh and use the Outliner to check for similarly named copies. Hide rather than delete a suspected duplicate first. In Edit Mode, inspect whether two sets of faces occupy the same surface. A duplicated wall, roof, or product panel may have been joined into one mesh, so looking only at object names is not enough. Wireframe or X-Ray view can help reveal stacked geometry, although coincident vertices may still appear as one.

Clean overlapping vertices without damaging the model

Blender’s Merge by Distance operation can combine vertices that are within a chosen tolerance. Select the relevant geometry in Edit Mode, open the Merge menu, and use By Distance. Start with a very small distance and inspect the reported number of merged vertices. This tool is useful for duplicate vertices inside the same mesh, but it does not automatically remove every overlapping polygon or decide which of two complete surface layers should remain. Large merge thresholds can collapse narrow details, alter UV seams, or damage carefully modeled mechanical features. Save a copy before aggressive cleanup, and examine the mesh afterward in face selection mode to remove redundant faces deliberately.

Remove internal faces and coplanar panels

Some models contain hidden internal walls left behind after joining objects or applying booleans. Other assets use a separate decorative panel placed exactly on a cabinet door or vehicle body. If two visible faces occupy the same plane, remove the unnecessary face or introduce an intentional offset. When deleting faces, consider whether they define a closed solid, a material boundary, or an important UV island. For manufacturing and 3D printing, simply moving a face away from the original may introduce gaps or non-manifold geometry. For real-time display, a small physically meaningful separation can be appropriate, especially when the second surface represents an actual sticker, plate, or trim piece.

Check modifiers and duplicated geometry in the stack

Mirror, Solidify, Array, and Boolean modifiers can create overlapping regions when their inputs are not configured correctly. A Mirror modifier may place two halves on top of each other if the source mesh crosses the mirror plane. An Array modifier with the wrong offset can stack repeated elements. Solidify can create intersections around tight corners or thin surfaces. Temporarily disable modifiers one by one in the viewport to locate the stage where the flicker begins. Do not apply all modifiers merely to hide the problem; doing so makes troubleshooting harder and can turn a reversible setup issue into permanent mesh geometry.

Understand depth-buffer precision

A depth buffer stores information used to decide which visible surface is closest to the camera. Its precision is finite, and the available precision depends on the rendering pipeline and camera projection. When two surfaces are extremely close together, their depth values may become indistinguishable. Perspective depth precision is also uneven across distance. A scene with a very small near clipping distance and an extremely large far clipping distance may have less useful precision for distant geometry. This explains why a scene can flicker even without exact duplicate faces. Different renderers and export viewers use different depth formats and settings, so a fix that works in one application may not carry over automatically.

Adjust viewport and camera clipping carefully

In Blender, check the viewport clipping values in the View sidebar settings and the active camera’s Clip Start and End properties. A near clipping distance that is unnecessarily tiny can make depth precision less favorable. Raise Clip Start only as far as your work allows, and reduce Clip End when the scene does not need an enormous viewing range. For example, a product visualization confined to a few meters should not automatically require the same far clipping distance as a landscape. Changing clipping can hide nearby or distant geometry, so test the full camera path before accepting new values. These settings can improve precision-related flicker but will not resolve truly coincident surfaces.

Use offsets for decals with clear intent

Labels, road markings, signage, and painted details often need to sit visually above a base surface. One approach is to place the detail a small distance above the underlying mesh along its normal. The offset should be large enough to remain distinguishable at expected viewing distances but small enough to avoid an obvious floating appearance. A decal shader, texture projection, or material-based detail may be a better solution than a separate polygon layer when the asset will be viewed from many angles. For assets intended for virtual environments, test the detail in the destination engine rather than relying only on Blender’s viewport.

Inspect normals and mesh topology

Incorrect normals do not usually cause true z-fighting by themselves, but they can create misleading shading artifacts that resemble it. Enable Face Orientation overlay to distinguish front-facing and back-facing regions. Recalculate normals where appropriate and inspect suspicious surfaces for inverted faces, loose geometry, or non-manifold edges. Triangulation may also expose unexpected coplanar overlaps in imported CAD models. If the mesh is intended for export, combine these checks with a non-manifold geometry inspection. Treat shading problems and depth conflicts as separate diagnostic categories so that correcting one does not conceal the other.

Troubleshoot CAD imports and architectural models

Imported DWG, DXF, OBJ, and FBX assets may include coincident walls, duplicate layers, or overlapping surfaces generated by different source systems. A floor slab might coincide with a finish layer, while a window frame might contain stacked trim pieces. Inspect collections and object names before joining everything into one mesh. If a CAD drawing contains multiple representations of the same geometry, remove redundant source layers before export when possible. Keep a clean source copy and document intentional overlaps. For larger projects, establish consistent units and coordinate origins; validating model scale and units can also prevent offsets from becoming imperceptibly small or disproportionately large.

Check real-time engines and GLB exports separately

A GLB file stores geometry and materials, but it does not guarantee identical rasterization behavior across viewers. If a model looks stable in Blender and flickers in a browser-based viewer, inspect duplicate primitives, thin decal geometry, and the viewer’s camera near and far planes. Some engines support polygon offset or depth bias for specialized materials; these are renderer-specific techniques rather than universal Blender export settings. Avoid assuming that a viewport workaround will be embedded in the GLB. Follow a repeatable export check, including the GLB material and texture verification workflow, then test the exported file in the actual target viewer.

Build a controlled test scene

When the cause remains unclear, duplicate the file and isolate one problematic object in a new scene. Use one camera, one simple material, and a neutral background. Remove unnecessary lights, animations, and modifiers temporarily. First test the original geometry. Next hide the upper surface, then change clipping values, then introduce a tiny offset, recording which action eliminates the flicker. This sequence is more reliable than changing many settings at once. For repeated asset production, create a short checklist covering duplicate objects, overlapping faces, modifier intersections, clipping range, normals, and destination viewer behavior. A small reproducible test is especially valuable when several artists or technical teams work on the same file.

Avoid fixes that only mask the defect

Increasing the distance between two surfaces can stop flicker, but it may also change the model’s silhouette or cause visible shadows beneath labels. Deleting all internal faces can improve a mesh, yet it can damage objects that intentionally contain nested shells. Increasing texture resolution does not fix depth competition, and changing the render samples is unlikely to solve coincident geometry. Likewise, moving the entire scene closer to the origin may help with some large-coordinate precision issues but does not remove duplicate polygons. Choose the smallest intervention that addresses the verified cause, and test it under the actual delivery conditions. For 3D product models, inspect close-up details as well as full-object views.

Conclusion

Z-fighting is best treated as a geometry and depth-precision problem rather than a generic material failure. Begin by identifying where the flicker occurs, isolate stacked objects and coplanar faces, then inspect modifiers and camera clipping. Use small offsets only when layered surfaces are intentional, and confirm that the final model behaves correctly after export. A disciplined test process preserves important details while eliminating the visual instability that can make an otherwise accurate Blender model appear unfinished.