Windows Studio Effects — automatic framing, eye contact correction, background blur, and portrait lighting — are among the best reasons to own a Copilot+ PC. They work beautifully in Teams and Zoom. Then you join a Google Meet call in Chrome, open the effects panel, and… nothing. The toggles are missing, grayed out, or simply do nothing to your video.

The frustration is real because the feature clearly works — your NPU is fine, the camera is fine, Teams proves it. The problem is specific to how browsers handle the camera. Chrome and Edge access your webcam through a sandboxed media pipeline that can bypass, conflict with, or simply not expose the driver-level Studio Effects that native apps see cleanly.

This guide covers every angle: the browser settings that break effects, the Windows camera settings to verify, driver fixes, and the pragmatic fallback of Meet’s own built-in effects. If your Studio Effects fail in Teams too, the problem is system-wide — see our Studio Effects not working in Teams guide instead. For Zoom-specific issues, there’s Studio Effects in Zoom meetings . Related AI audio quirks on Dell machines are covered in Dell Optimizer AI audio issues , and if Windows Hello is blocking camera-adjacent features, check Recall PIN and Windows Hello requirements .

Why this happens

  • Browser camera sandboxing: Chrome and Edge access the camera through a restricted media pipeline that may not enumerate driver-level effects the way native apps do.
  • Hardware acceleration conflicts: Browser GPU acceleration can take over video processing and bypass the NPU effects chain.
  • Camera permission layering: Meet requests camera access through the browser’s permission system, adding a layer where effects metadata can get lost.
  • Multiple camera devices: Virtual cameras, phone-link cameras, or external webcams can become the active device, and Studio Effects only apply to the built-in camera.
  • Outdated camera or NPU drivers: The effects chain depends on the camera driver exposing effect nodes and the NPU driver processing them — either can break it.
  • Meet’s own effects overriding: If Meet’s built-in background effects are active, they can conflict with or mask Windows Studio Effects.

How to fix it

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

Fix 1: Verify Studio Effects work outside the browser

Before touching browser settings, confirm the effects chain is healthy. Open the Windows Camera app and check whether Studio Effects toggles appear and function there.

  1. Open the Windows Camera app and test each Studio Effect.
  2. Check Settings > Bluetooth & devices > Cameras for effect toggles.
  3. Test in Teams if available to compare native vs browser behavior.
  4. If effects work outside Meet, the issue is browser-specific.
  5. Note which effects work natively to guide browser testing.

Fix 2: Use Meet’s built-in effects as the reliable path

Google Meet ships its own background blur, background replacement, and lighting effects that run entirely in the browser — no NPU, no Windows effects chain required. Before a call, click the effects icon (the sparkle/three-star button) in the Meet preview screen; during a call, open the More menu and choose “Apply visual effects.” These are the most reliable effects for Meet because they’re designed for its pipeline.

  1. In the Meet preview screen, click the visual effects icon.
  2. Choose background blur, replacement, or lighting adjustment.
  3. During calls, access effects via More > Apply visual effects.
  4. Turn Windows Studio Effects off to avoid double-processing.
  5. Test lighting effects too, since they need no NPU at all.

Fix 3: Toggle Chrome’s hardware acceleration and camera flags

Chrome’s hardware acceleration can hijack the video pipeline and bypass Studio Effects. Open Chrome Settings > System and try toggling “Use hardware acceleration when available” off, then restart Chrome and test Meet.

  1. Open Chrome Settings > System and toggle hardware acceleration.
  2. Restart Chrome and test your video in a Meet preview.
  3. Visit chrome://flags and reset any modified media flags.
  4. Try the same Meet preview in Microsoft Edge for comparison.
  5. Clear Chrome’s cache if flag changes don’t take effect.

Fix 4: Fix camera selection and permissions

Meet may simply be using the wrong camera. In the Meet preview, click the camera settings and verify the built-in laptop camera is selected — not a virtual camera, not your phone via Phone Link, not an external webcam you forgot was plugged in.

  1. In the Meet preview, confirm the built-in camera is selected.
  2. Check the address-bar camera icon for Meet’s site permission.
  3. Verify Settings > Privacy & security > Camera allows browser access.
  4. Remove any virtual camera apps from the device list if unused.
  5. Re-grant permission if the browser asks again after restart.

Fix 5: Update camera, NPU, and chipset drivers

The Studio Effects chain needs three healthy drivers: the camera driver exposing effect nodes, the NPU driver processing them, and the chipset driver tying it together. Open Device Manager, expand Cameras and Neural processors, and check for warnings. Intel-based laptops can pull the latest bundle via the Intel driver support assistant .

  1. Check Device Manager under Cameras and Neural processors.
  2. Download the latest AI camera driver bundle from your maker.
  3. Install, reboot, and test effects in the Camera app.
  4. Check manufacturer utilities for overriding camera effect toggles.

Fix 6: Reset the browser profile and Windows camera stack

When nothing else works, corruption in the browser profile or Windows camera stack may be the cause. In Chrome, create a fresh profile (or test in an incognito window, which disables extensions) and try Meet there — a misbehaving camera-related extension is a surprisingly common culprit.

  1. Test Meet in a Chrome incognito window or fresh profile.
  2. Disable camera-related extensions one by one if that works.
  3. In Device Manager, uninstall the camera device and reboot.
  4. Install all pending Windows updates.

Closing

Studio Effects failing specifically in Google Meet is a browser-pipeline problem, not a broken NPU — your effects work, Chrome just isn’t picking them up. The pragmatic fix most people settle on is Meet’s own built-in effects, which are reliable and need no troubleshooting.

Frequently asked questions

Do Windows Studio Effects work in browser-based video calls?
Only partially. Studio Effects apply at the camera driver level, so they should affect any app using the camera — but browser sandboxing, hardware acceleration settings, and camera permission quirks in Chrome and Edge often break them in Google Meet specifically.
Why do Studio Effects work in Teams but not in Google Meet?
Teams is a native app with direct camera access, while Meet runs inside a browser sandbox. Chrome’s camera pipeline can bypass or conflict with the driver-level effects that Teams picks up cleanly.
Can I use Google Meet's own background effects instead?
Yes. Meet has built-in background blur, replacement, and lighting adjustment that run in the browser. They don’t need Studio Effects or an NPU, and they’re the most reliable option for Meet calls.
Do I need a Copilot+ PC for Studio Effects in Meet?
Studio Effects themselves require a Copilot+ PC with an NPU. But the browser-specific failures in Meet happen on Copilot+ machines too — the NPU being present doesn’t fix the browser pipeline problem.