How to Fix Krisp Not Working: Mic Not Detected, Devices Not Showing, Bluetooth/Permission Issues, and Better Fallbacks

Quick Answer: the 5 fastest fixes

If Krisp is not working, the fastest fixes are usually:

1. Make sure you’re troubleshooting the right product. Discord’s built-in Krisp is not the same thing as the standalone Krisp desktop app.
2. Check mic permissions first. On Windows, confirm microphone privacy access is enabled. On Mac, go to System Settings > Privacy & Security > Microphone and allow Krisp.
3. Verify routing. In Zoom, Teams, Meet, OBS, or Discord, select Krisp Microphone as input only if you are using the desktop app’s virtual device.
4. Turn off double processing. Disable extra noise suppression in Zoom, Teams, Discord, OBS, headset software, and vendor audio effects before blaming Krisp for robotic or muffled sound.
5. Restart, sign back in, or reinstall. Krisp’s own help docs say missing devices can come from sign-out state, error-state devices, or needing a restart or reinstall.

If the live chain still keeps failing, the practical fallback is to record first and clean podcast audio with SimpleClean afterward instead of stacking more real-time filters.

Is it the Krisp desktop app or Discord’s built-in Krisp?

This is one of the biggest sources of confusion.

• Krisp desktop app: creates Krisp virtual devices that other apps can use.
• Discord Krisp: Discord also offers Krisp-based noise suppression inside Discord itself.

If Krisp seems to work in Discord but not in OBS, Zoom, or Teams, that often means you are only using Discord’s built-in noise suppression, not the standalone desktop routing.

So before changing settings everywhere, answer this first:

• If you need Krisp across multiple apps, troubleshoot the desktop app.
• If the problem only happens inside Discord, check Discord’s own voice settings separately.

Symptoms table: what to check first

Why Krisp microphone or speaker is not showing up

According to Krisp’s official troubleshooting, missing Krisp devices in other apps usually comes down to a few repeat causes:

• Microphone permission is not granted
• You are signed out of Krisp
• The device is in an error state
• The app needs a restart or reinstall

That means you should avoid random tweaking and check the basics in order.

Windows fixes

If you’re on Windows, work through these in order:

1. Check microphone privacy settings. Microsoft recommends confirming microphone access is enabled for the device and for apps.
2. Confirm Windows detects the real microphone. If Windows itself does not see the mic, Krisp cannot process it correctly.
3. Check the default input device. Make sure your intended mic is selected before Krisp enters the chain.
4. Run a mic test in Windows. If the raw mic fails there, this is not a Krisp-only problem.
5. Update or reinstall audio drivers if needed. Microsoft’s mic troubleshooting guidance includes driver-level checks when the microphone is not detected properly.
6. Restart Krisp and the target app. Close Zoom, OBS, Teams, or Discord fully before reopening.
7. Reinstall Krisp if devices are still missing. Krisp’s Windows install/update help recommends redownloading the latest version when updates fail or behave inconsistently.

Mac fixes

On Mac, the most common blockers are privacy permissions and install restrictions.

1. Allow microphone access. Apple’s path is System Settings > Privacy & Security > Microphone.
2. Reopen Krisp after granting access. Some apps do not refresh permissions until restarted.
3. If install fails, redownload the installer. Krisp’s Mac help specifically addresses Gatekeeper restrictions and the “damaged installer” style message.
4. Install from a local Downloads or Desktop folder. Krisp’s Mac article recommends reinstalling from a local location rather than launching from a mounted or unusual path.
5. Restart the Mac if virtual devices still do not appear.

If Krisp was installed before microphone access was granted, uninstalling and reinstalling can help clear up a broken setup state.

How to fix Krisp devices not showing in Zoom, Teams, Meet, OBS, or Discord

Once Krisp is installed and permitted, the next failure point is routing. In many cases, Krisp is fine but the meeting or recording app is still listening to the wrong device.

Zoom

• Open Zoom audio settings.
• For Microphone, choose Krisp Microphone if you want the standalone Krisp app to process your mic.
• If Zoom’s own suppression is also enabled aggressively, test with lower or disabled built-in noise suppression to avoid stacked processing.

Microsoft Teams

• Open Teams device settings.
• Select Krisp Microphone as the input only if you are using Krisp desktop routing.
• Turn off or reduce extra Teams audio effects if your voice starts sounding unnatural.

Google Meet

• Open Meet settings before or during a call.
• Choose the Krisp virtual mic as your input if that is your intended chain.
• If Meet was already open during install, close the browser tab or browser and reopen it.

OBS

• Open your Mic/Aux source properties.
• Select the correct source explicitly; do not assume OBS auto-switches.
• If OBS already has its own RNNoise or other suppression filters on the mic, disable them while testing Krisp.
• If Krisp works in Discord but not OBS, this is usually a routing mismatch, not proof that Krisp is broken.

If you need a related walkthrough, our Krisp vs OBS RNNoise guide covers how these chains differ.

Discord

• Decide whether you want Discord’s built-in Krisp or the Krisp desktop app.
• If using Discord’s built-in Krisp, you may not need Krisp virtual devices at all.
• If using Krisp desktop, pick the Krisp virtual mic in Discord and disable overlapping Discord processing during testing.

Bluetooth and AirPods caveats: why users think Krisp is broken

Krisp’s Bluetooth help documentation explains a common trap: when you use a Bluetooth headset for both microphone input and speaker output, the connection may switch into a hands-free mode. That can reduce quality and force mono behavior.

To users, this often looks like:

• Krisp ruined the sound
• The mic suddenly got narrow or phone-like
• Audio output quality dropped when the mic turned on

But the root cause may be Bluetooth profile limitations, not Krisp itself.

Best tests:

• Try a wired headset
• Use a separate USB mic plus Bluetooth headphones only for listening
• Compare raw mic vs Krisp with the same hardware chain

If quality improves immediately with wired gear, the issue is likely Bluetooth hands-free behavior rather than a failed Krisp install.

Turn off double processing before you judge the sound

Krisp’s headset guidance warns that extra processing from apps, headsets, or other audio tools can degrade quality. This is one of the biggest reasons voices become robotic, watery, clipped, or muffled.

Before you decide Krisp sounds bad, disable:

• Zoom noise suppression
• Teams noise suppression or audio effects
• Discord Krisp if you are already using Krisp desktop
• OBS noise suppression filters
• Headset software enhancements
• Vendor AI filters from audio drivers or companion apps
• Operating system effects that alter mic sound

Use one processing layer at a time, then test again.

If you are comparing options, you may also want our Krisp vs Nvidia Broadcast and NVIDIA Broadcast not working guides.

System requirements and unsupported OS note

Per Krisp’s official system requirements, the desktop app is not supported on Linux or Chrome OS. If you are trying to make the desktop app work there, the problem is not a hidden setting; it is an OS support limitation.

If you are on a supported Windows or Mac system and still seeing missing devices, continue with permissions, routing, restart, and reinstall steps instead.

How to test whether Krisp is actually processing your mic

Use this simple check:

1. Record a short sample with your raw microphone.
2. Record the same sample with Krisp enabled.
3. Use the same app and same hardware both times.
4. Turn off every other suppression tool.
5. Compare keyboard noise, fan noise, and voice tone.

If there is no difference at all, Krisp may not be in the signal chain. If the background noise is lower but the voice sounds worse, you may be overprocessing or using a Bluetooth hands-free path.

When Krisp is the wrong tool

Live suppression is useful, but it is not always the best choice.

Krisp may be the wrong fit when:

• You are already in a quiet room and suppression makes the voice less natural
• You are recording singing, emotional delivery, or high-dynamics speech where artifacts are more obvious
• Your live routing is unstable across apps
• You care more about final recording quality than live-call convenience

In those cases, it is often better to capture the cleanest raw recording you can and fix the file afterward.

Best fallback workflow: record first, then clean the file

If Krisp keeps failing live, skip the fragile virtual-device chain.

1. Record or export your WAV, MP4, or MOV file from Zoom, OBS, your editor, or your recorder.
2. Upload it to SimpleClean for file-level cleanup.
3. If you are publishing video, add subtitles with Best AI Captions.
4. If you need multilingual versions, use Translate Dub to translate, dub, and caption the video.
5. When the cleaned version is ready to promote, distribute clips and posts across channels with Mallary.ai.

This workflow is often better for podcasters, creators, and support teams who care about the final asset more than live filtering during the call.

If your problem is really “I just need the exported recording to sound better,” it is usually faster to remove background noise from recorded audio after export than to keep stacking live suppressors.

Best for: which path should you choose?

• Best for live meetings: Krisp desktop, if permissions and routing are stable and you avoid double processing.
• Best for Discord-only use: Discord’s built-in Krisp, if you do not need system-wide routing.
• Best for Bluetooth trouble: Test wired audio or separate input/output devices first.
• Best for final content quality: Record first, then clean the exported file.
• Best for publishing polished content: Clean audio first, then add captions, translations, and distribution tools.

How to reinstall Krisp on Mac or Windows

Windows

1. Quit Krisp completely.
2. Download the latest installer again from the official source.
3. Run the installer.
4. Restart your communication or recording apps.
5. Recheck that Krisp devices appear in app settings.

Mac

1. Quit Krisp.
2. Redownload the latest installer.
3. Move it to a local Downloads or Desktop folder if needed.
4. Run the installer and approve any required system prompts.
5. Re-enable microphone access in Privacy & Security if prompted.

Final takeaway

Most “Krisp not working” cases are not mysterious. They usually fall into one of five buckets: wrong product confusion, blocked permissions, missing virtual-device routing, Bluetooth hands-free limitations, or too many suppression layers at once.

Fix those in order, and Krisp often comes back quickly. But if your live chain still feels fragile, the smart fallback is simple: record first, then clean recorded voice audio after the fact.