Background blur is the Studio Effect everyone actually uses — and the one whose failure is most visible, because your messy room stays stubbornly sharp on every call. The toggle is on, the preview shows no blur, or the blur flickers and drops mid-meeting. Other effects may work fine while blur alone refuses.

Blur is the most computationally demanding of the standard effects: real-time person segmentation on every frame through the NPU. That makes it the canary — the first effect to fail when the NPU is struggling, the camera feed is odd, or an app interferes.

This guide fixes blur specifically, from the NPU to app conflicts. If eye contact is also failing, see eye contact effect not working . For audio-side AI, see Voice Focus not working — it shares the NPU. If your camera is not detected at all, start with camera not detected .

Why this happens

  • NPU under strain or driver issues: Blur needs sustained NPU throughput. A struggling NPU drops blur first while lighter effects survive.
  • Low light or cluttered background: Segmentation models fail in poor lighting or extremely busy backgrounds, producing no blur or flickering edges.
  • App applying its own blur: Teams and Zoom have their own background blur. Two blurs fighting over one stream breaks both.
  • Camera resolution too low: Very low-resolution feeds give the segmentation model too little to work with.
  • Effect applied in the wrong place: Blur toggled in Windows but the call app overriding camera settings cancels it.
  • Outdated camera or NPU driver: Driver bugs in either pipeline manifest as blur specifically failing.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Improve the scene for the segmentation model

Background blur is real-time person segmentation, and segmentation models need something to work with: decent light, a distinguishable subject, a reasonable distance. Poor lighting, a bright window behind you, or extreme clutter defeats the model before software ever enters the picture. Fixing the scene is free, instant, and resolves a large share of ‘blur does nothing’ reports.

  1. Face a light source; avoid sitting with a bright window directly behind you.
  2. Reduce extreme background clutter if the blur flickers at edges.
  3. Sit at a normal distance — too close or too far hurts segmentation.
  4. Test again in good light before blaming software.

Fix 2: Turn off the app’s own blur

Running Windows background blur and Teams’ or Zoom’s own blur simultaneously guarantees failure — two segmentation pipelines fighting over one stream. The fix is choosing a single source of truth: Windows blur with the app set to none, or the app’s blur with Windows’ off. Never stack them; the conflict is architectural, not a settings subtlety.

  1. In Teams/Zoom camera settings, set background effects to ‘None’.
  2. Apply blur only in Windows Studio Effects (Settings > Bluetooth & devices > Cameras).
  3. Never stack Windows blur with app blur — pick one.
  4. If the app lacks a ’none’ option, disable Studio Effects blur and use the app’s instead.

Fix 3: Check NPU and camera drivers

Blur is the hungriest Studio Effect, so it is the first to fail when the NPU or camera driver struggles — while lighter effects like eye contact keep working, creating a confusing partial failure. Updating both drivers from OEM sources restores the headroom blur needs. When blur alone fails and everything else works, drivers are guilty far more often than settings.

  1. Update the NPU driver from your laptop maker’s support page.
  2. Update the camera driver via Device Manager > Cameras.
  3. Restart and test blur in the Windows camera preview.
  4. Sustained blur in the preview means the drivers were the issue.

Fix 4: Test in the Windows preview, not the call app

Testing in the Windows camera preview removes the conferencing app from the equation entirely. If blur works in preview but dies in calls, the app is overriding or blocking it — check its camera settings for effect overrides and restart it after changes. A working preview proves Windows’ pipeline is healthy and moves the investigation downstream.

  1. Open Settings > Bluetooth & devices > Cameras and preview with blur on.
  2. If blur works in preview but not in calls, the call app is overriding it.
  3. Check the app’s camera settings for effect overrides.
  4. Some apps need a restart after you change Windows-level effects.

Fix 5: Lower the load on the NPU

A saturated NPU sheds its heaviest load first, and that load is background blur. Other AI features running concurrently — translation, Recall indexing bursts — all draw from the same neural-processor budget. Closing what you do not need and disabling unused effects gives blur the headroom to stabilize, which you can verify on the NPU graph in Task Manager.

  1. Close other AI-heavy apps (Live Captions with translation, Recall indexing bursts).
  2. Turn off Studio Effects you do not need — each one consumes NPU budget.
  3. Check Task Manager > Performance > NPU for saturation.
  4. Blur should stabilize once the NPU has headroom.

Fix 6: Check for Windows known-issue rollbacks

Microsoft occasionally ships Known Issue Rollbacks for effect bugs — fixes that deploy silently outside the normal update flow. Checking update history and the support pages for rollbacks affecting Studio Effects takes minutes and occasionally reveals that the fix already exists, waiting only for the update channel to deliver it.

  1. Go to Settings > Windows Update > Update history.
  2. Look for recent quality updates mentioning camera or effects.
  3. Check Microsoft’s Windows support hub for Known Issue Rollbacks affecting Studio Effects.
  4. Install anything pending; rollbacks deploy automatically but need the update channel open.

Fix 7: Test blur at different camera resolutions

Segmentation quality scales with the feed it gets: higher resolutions and cleaner pixel formats give the model more to work with. A camera stuck in a low-resolution or heavily compressed mode starves the model regardless of driver health. Trying different resolutions and formats in the camera settings is a quick experiment with immediate visual feedback.

  1. In the camera app or device settings, try a higher resolution.
  2. Avoid very low resolutions that leave the model guessing.
  3. If your camera offers MJPEG vs H.264/NV12 modes, try each.
  4. The sharpest stable feed gives blur its best chance.

Closing

Background blur fails for understandable reasons: poor lighting for the segmentation model, a second blur fighting it in the call app, or an NPU/driver issue. Fix the scene, pick one blur source, and keep drivers current. When blur works in the Windows preview, any remaining failure is the call app’s doing, not Windows’.

Frequently asked questions

Why does background blur work in preview but not in Teams?
Teams is likely applying its own background setting or overriding the camera stream. Set Teams’ background to None and let Windows Studio Effects handle blur — never run both.
Does background blur need good lighting?
Yes. The AI segmentation model needs to distinguish you from the background, and poor lighting or extreme clutter makes it fail or flicker. Face a light source for best results.
Why does blur flicker around my edges?
Edge flicker means the segmentation model is struggling — usually lighting, a busy background, or NPU strain. Improve light, simplify the background, and close other AI apps.
Is Windows background blur better than Teams' blur?
They use different pipelines. Windows’ version runs on the NPU with no app dependency; Teams’ is app-level. Use one, not both — stacking them breaks both.