AirPods Microphone Not Working? Fixes in Order (Mesh, Mic Setting, Reset)

The fastest way to fix AirPods microphone not working is to stop guessing and test one thing at a time, starting with the bud that actually carries the call. A mic that sounds muffled, distant, or completely silent can come from a blocked mesh, a wrong mic setting, a stale pairing, or a permission that quietly changed after an update. Each of those causes leaves a different clue, and this guide follows the clues in the order that wastes the least time, so a simple cleaning or setting change is found before anyone considers a reset or a repair booking.

Two quick tests narrow the field more than any list of tips. Speaking into each bud on its own shows whether one side has failed, and recording a short voice memo shows whether the fault lives in the AirPods or only inside one calling app. With those two answers in hand, the rest of the sequence stops feeling like trial and error and starts feeling like a short investigation with a clear end.

What Usually Causes This

Before the steps, it helps to know that this fault rarely has a single cause, and the table below separates the likely causes by the sign you actually see, so you can start at the row that matches your situation rather than at the top of a generic list. Working out how to fix AirPods microphone not working starts with that match, because the right first step depends on the symptom in front of you.

Likely cause	Sign you will see	First check
Blocked mic mesh	Muffled or silent mic on calls	Clean the mic mesh gently
Wrong mic setting	Mic uses the quieter bud	Set Microphone to Automatic or one bud
Stale pairing	Mic fails after an update	Forget and re-pair the AirPods
One bud fault	Mic fails on one side only	Test each bud separately
System permission off	Mic fails in one app only	Check system microphone privacy
Firmware or hardware fault	Mic fails after all steps	Update firmware and seek service

Note what changed before the fault began, what still works, and what you have already tried, because those three facts turn a frustrating afternoon into a short sequence of tests. A short note on those points, written before you start, also makes any later conversation with support far shorter, since you can describe what you have ruled out instead of repeating the symptom.

Before You Touch a Setting

Read the whole guide once before changing anything, because the order matters, and a step skipped early often returns as a larger problem later. Where a price or a feature is given, check it on the vendor page before you commit, since pricing and features change, and the right choice depends on your situation and your existing setup.

When you approach fix AirPods microphone not working, keep a simple log of each test and its result, even a few lines on paper. Change one thing, test, and note the result before moving on, because changing three things at once and seeing an improvement leaves you unsure which change helped, and the fault returns when the unhelpful changes are undone.

Back up anything important before the later steps, even if you do not expect to reach them. A backup made while the device still works is worth far more than a backup attempted after a destructive step, and it removes the fear that keeps people from taking a legitimate last resort step. Check that the backup completed, rather than assuming it did, since a backup that never finished offers no protection at all.

AirPods microphone visual tied to the Before You Touch a Setting section of this guide

How to fix AirPods microphone not working in the Right Order

Working through fix AirPods microphone not working in this order keeps the least disruptive tests first, so a simple settings fault is found before anyone considers a reinstall, a replacement, or a repair booking, and each step below ends with what a success looks like, so you know when to stop.

**Test each AirPod separately.** Put one AirPod in the case, make a test call with the other, then swap. A mic that works on one bud but not the other points at the failing bud, its mesh, or its mic setting, while failure on both buds points at pairing, permission, or firmware. Note which bud fails, since every later step depends on that answer. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Clean the microphone mesh gently.** Wipe the mic mesh areas with a dry soft cloth, and use a dry soft brush for debris, without pushing anything into the mesh and without liquids. A blocked mesh muffles the mic or silences it entirely, and it is the commonest physical cause. Test a call after cleaning, since a clear mesh often restores the mic immediately. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Check the microphone setting.** On iPhone, open Settings, Bluetooth, tap the info icon beside your AirPods, and check Microphone. Automatic lets the AirPods choose a mic, while Always Left or Always Right forces one bud. Try Automatic first, then force the working bud if one bud is clearly better, and test a call after each change. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Check mute and app settings.** Check the mute control in the calling app, and check that the app uses the AirPods as its input device where it offers a choice. A muted call or a wrong input device silences the mic while the AirPods themselves work perfectly. Test with a second app, such as a voice recorder, to separate app settings from AirPods faults. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Test the mic outside calls.** Open Voice Memos on iPhone, or a voice recorder on another device, and record with the AirPods connected. A mic that records clearly but fails on calls points at the calling app, while a mic that fails everywhere points at the AirPods. This test prevents a reset for an app level fault. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Check system microphone privacy.** On iPhone, open Settings, Privacy and Security, Microphone, and confirm the calling app is allowed. On Mac, open System Settings, Privacy and Security, Microphone, and confirm the app is allowed. A system block overrides app settings, so the app cannot receive mic audio until the system allows it. At this stage of fix AirPods microphone not working, a success here is especially valuable, because it proves the fault sat in the middle of the sequence rather than at either end. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Restart the phone and reconnect.** Disconnect the AirPods, restart the phone, then reconnect the AirPods and test a call. A restart clears a stuck Bluetooth audio route and releases a mic session held by a crashed app. Test before opening other audio apps, so a fresh app cannot seize the mic first. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Forget and re-pair the AirPods.** On iPhone, open Settings, Bluetooth, tap the info icon beside your AirPods, and choose Forget This Device. Then put both AirPods in the case, open the lid, press and hold the setup button until the light flashes amber then white, and pair again. A fresh pairing clears a stale audio route that a simple reconnect cannot fix. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Check firmware and update through the phone.** Keep the AirPods connected to the iPhone, with the case nearby and charging, and check Settings, Bluetooth, AirPods, Version for the firmware version. AirPods update automatically when connected and charging, so leave them connected for a while rather than forcing an update. Test a call after the AirPods have had time to update. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Test with another device.** Pair the AirPods with a second phone, tablet, or computer, and test the mic there. A mic that works on a second device points at the first device and its settings, while failure on every device points at the AirPods. This test decides whether to keep troubleshooting the phone or to focus on the AirPods. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Reset the AirPods fully.** Put both AirPods in the case, open the lid, press and hold the setup button for about fifteen seconds until the light flashes amber then white, then pair again from the start. A full reset clears pairing and settings that a simple forget may leave behind. Test a call immediately after reset, before restoring custom settings. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.
**Stop and book service for a hardware pattern.** Stop when one bud mic stays silent after cleaning, a mic setting change, a reset, and a second device test, or when both mics fail after a full reset and a firmware update. Further resets cannot repair a failed mic mesh or internal mic fault. Take your notes on which bud fails and which tests you ran. If this step restores normal behaviour, stop here and note what worked, because continuing past a working fix only adds risk.

AirPods microphone visual tied to the How to fix AirPods microphone not working in the Right Order section of this guide

Details People Often Miss

AirPods mic faults confuse people because the mic you hear through and the mic others hear are not the same thing. The AirPods choose a microphone automatically, and they may choose the quieter bud, the bud in the case, or a bud with a blocked mesh. Testing each bud separately exposes that choice, while testing only in a call leaves it hidden. This distinction shapes how you should approach fix AirPods microphone not working.

The microphone setting is the most powerful and most overlooked control. Automatic sounds like the safe choice, yet it can switch mics mid call when a bud moves or loses contact. Forcing the working bud removes that switching entirely, and for many owners that single change ends a fault that looked like a hardware failure.

Mesh blockage deserves a gentle approach, because the mesh is delicate and the mic sits behind it. A dry cloth and a soft brush clear surface debris safely, while a pin, a wet cloth, or compressed air at close range can push debris deeper or damage the mesh. Cleaning gently, then testing, is the right order, and aggressive cleaning is a mistake that creates a new fault.

The checks that matter most, in brief, are the first five steps of the sequence, and they deserve a second pass if the fault survives them.

Test each AirPod separately
Clean the microphone mesh gently
Check the microphone setting
Check mute and app settings
Test the mic outside calls

Apple publishes AirPods microphone and reset guidance through its official support pages, and the Settings paths in this guide follow those pages. See Apple Support for the current AirPods steps for your model.

Testing one change at a time is the habit that separates a quick repair from a long afternoon of guessing. Change a single setting, run the same test you ran at the start, and write down the result before you touch anything else. When a later step appears to work, that note tells you whether the improvement came from the latest change or from an earlier one that only needed time to take effect. Support teams ask for the same log, so the habit pays twice.

A short note made before you start will save time later, especially if the fault returns or if someone else has to finish the job. Record what changed just before the fault appeared, which tests you have already run, and what each test showed. A fault that began after an update, a new accessory, or a move points in a different direction from a fault that appeared out of nowhere, and that single detail often narrows the search more than any single setting.

Do not judge a fix by the first few seconds after you apply it. Some settings need a restart, some connections need a fresh pairing attempt, and some apps need a full close before a change takes effect. Run the same real world test you used at the start, such as opening the feature, making a test call, or playing a short clip, and give the result a full minute before you declare the step a failure and move on.

If the same fault has appeared before, look for the pattern rather than treating each occurrence as new. A fault that returns after every update, every long trip, or every period of heavy use usually has a trigger that the ordered steps can expose. Fixing the trigger, such as a worn cable, a full storage, or an app that hogs resources, prevents the next occurrence far better than repeating the same quick fix.

Keep the accessories you use for testing in a known good state. A spare cable, a charged spare remote battery, or a second pair of earbuds turns a vague suspicion into a clear answer in under a minute. When the fault follows the accessory to another device, the accessory is the problem. When the fault stays with the original device, the device or its settings deserve the attention.

Before any step that erases data or resets settings, confirm where your important content lives. Photos, messages, and documents that sync to a cloud account usually return after a reinstall, while local downloads and unsaved work may not. A quick backup takes a few minutes and turns a last resort step from a risk into a routine procedure.

When a fault may end in a warranty claim, preserve evidence as you go rather than reconstructing it later. Keep dated notes, keep the original accessory that failed, and avoid opening a sealed device, since an opened device can complicate a claim even when the fault is genuine. A repair centre that receives a clear timeline and untouched hardware can usually decide faster than one that receives only a description.

After any system or app update, retest the feature that previously failed, even if the update notes do not mention it. Updates change drivers, permissions, and background behaviour in ways that release notes rarely capture fully, and a fault that an update quietly fixed can return with the next update just as quietly. A two minute retest after each update turns that uncertainty into a known result.

A second device is the cheapest diagnostic tool you can own for this kind of fault, because it answers the device versus environment question in a single test. Borrow a second phone, headset, remote, or monitor for ten minutes, and run the same test on both. When the fault follows the accessory, replace the accessory. When it stays with the original device, focus the repair there and stop buying accessories.

AirPods microphone visual tied to the Details People Often Miss section of this guide

Mistakes That Make It Worse

The following errors do not cause the original fault, but they regularly turn a short repair into a long one, and they are worth naming before you start.

Pushing a pin into the mic mesh, which can damage the mesh and push debris deeper.
Resetting the AirPods before testing each bud, which erases pairing for a one bud fault.
Testing only on calls, which leaves an app mute disguised as a mic fault.
Assuming both mics have failed when only the automatic selection is choosing the wrong bud.
Ignoring a blocked mesh and replacing the AirPods, which discards a repairable pair.

Avoiding those errors keeps fix AirPods microphone not working short and calm, because every wasted reset or repeated test adds frustration without adding evidence, and a calm repair is a faster repair.

AirPods microphone visual tied to the Mistakes That Make It Worse section of this guide

When to Stop and Get Help

Book an Apple service check when one bud mic stays silent after cleaning, a mic setting change, a reset, and a second device test, or when both mics fail after a full reset. Take notes on which bud fails, the mic setting you tested, and the second device result. Stop if the AirPods or case show swelling, heat, or liquid damage.

Take your notes with you when you seek help, including which tests passed and which failed, and the exact conditions where the fault appears. Support moves faster with ruled out causes than with a repeated symptom description, and a clear log often leads to a faster repair or a correct replacement part on the first visit.

AirPods microphone visual tied to the When to Stop and Get Help section of this guide

How to Prevent a Repeat

Clean the mic mesh gently and regularly, keep the AirPods firmware current through normal connected charging, and review the microphone setting after any iOS update. Test the mic with a voice recording before an important call, and store the AirPods in their case rather than loose in a pocket. A short monthly check of mesh, setting, and firmware prevents most mic faults.

A ten minute monthly check of updates, storage, cables, and permissions catches most problems while they are still small, and it builds a baseline so a future change stands out immediately. Prevention is not extra work on top of the repair, it is the same discipline applied before the fault appears, and it pays for itself the first time it saves a repeat repair.

AirPods microphone visual tied to the How to Prevent a Repeat section of this guide

A Second Round When the First Round Misses

A second pass is not a repeat of the first pass, it is a different kind of test. The first pass rules out the common causes in order, while the second pass looks for a cause that was masked during the first, such as a second device interfering, a setting that reverted after a restart, or a fault that only appears under load. Work the second pass slowly, and change only one variable at a time, since a second pass done hastily produces the same confusion as the first pass done at random.

During the second pass, test under the exact conditions where the fault originally appeared, with the same app, the same accessory, and the same network or location. A fault that cannot be reproduced under test conditions has not necessarily been fixed, it may simply be waiting for its trigger. If the second pass still fails, the notes from both passes together give support a far stronger starting point than either pass alone, and they often reveal a pattern that a single pass hides.

Testing the Mic Before You Call It Done

Return to the first step and confirm it properly before moving on, because a step that was rushed the first time often looks like a failure when it was really an incomplete test. Give it the full time it needs, watch for the result described in the main sequence, and only then move to the next step. This habit of retesting the early steps, rather than jumping to the later and more disruptive ones, saves most of the time that troubleshooting usually wastes.

The diagnosis table at the start deserves a second look once the main steps are done, because a cause that seemed unlikely at the start can become the leading explanation once the obvious ones are ruled out. Compare what you observed with the sign described for each row, and if your observation matches a row you dismissed earlier, work that row again with fresh attention. Diagnosis improves when the table is treated as a checklist to revisit, not as an introduction to skip.

Test again the next day under normal use, not just in the moment after the fix. Some faults return when the device warms up, when a background app updates, or when the original trigger recurs, and a next day test catches those returns while the repair is still fresh in your mind. If the fault returns, note exactly what changed since the fix, since that change is the most likely trigger.

Frequently Asked Questions

Why did this problem start suddenly?

The commonest trigger is a change just before the fault, such as an update, a new accessory, a move, or a period without use. Tracing that change usually points at the cause faster than testing parts at random. Note the last change first, then work through the ordered steps, because a fault with a clear trigger often has a short fix and a fault without one needs the full sequence. Retest the exact action that failed before, not an easier one.

How long should each fix take before I move on?

Give each simple step a proper test rather than a glance, because a restart, a cable swap, or a permission change needs a minute or two to show its result, while a reinstall or a restore needs longer. If a step shows no change after a fair test, move on and note the result, because the log of failed steps is what narrows the remaining causes for the steps that follow. Retest the exact action that failed before, not an easier one.

Will clearing data or resetting settings delete my content?

Clearing a cache removes temporary files only, while clearing data or storage signs you out and removes local settings, so check where your content lives before the stronger step. Content that syncs to a cloud account usually returns after a reinstall, while local downloads and unsaved work need a backup first. Never take a destructive step on a device that holds the only copy of something important. Retest the exact action that failed before, not an easier one.

What if the fault affects only one app, one device, or one connection?

That pattern is useful evidence, because a fault tied to one app points at that app and its permissions, while a fault that follows the device points at the device itself. The ordered guide for fix AirPods microphone not working helps separate those two cases before you change settings everywhere, and testing with a second app, a second device, or a second connection is the fastest way to draw that line. Retest the exact action that failed before, not an easier one.

When should I contact support instead of trying more fixes?

Contact support after the ordered steps fail, or immediately if you see danger signs such as heat, swelling, liquid damage, or a burning smell, and take your notes on what you tried. Support moves faster when you can list the causes you have ruled out, and continuing to guess after that point risks making a repairable fault worse or turning a warranty claim into a dispute. Retest the exact action that failed before, not an easier one.

How do I stop this happening again?

Keep updates current, keep comfortable free storage, check cables and permissions monthly, and note any change before a fault appears, because most repeats come from the same neglected basics. A ten minute monthly check is cheaper than another afternoon of troubleshooting, and it builds a baseline that makes future changes obvious before they become faults. Retest the exact action that failed before, not an easier one.

A Steady Finish

Work through fix AirPods microphone not working in order, stop at the step that works, and keep the notes on what you tried, because that discipline turns a frustrating fault into a short sequence of tests, and it also means the next fault starts from a known baseline instead of from scratch.

Start with the first step today, test one change at a time, and let the result of each test decide the next move, because a calm ordered approach beats a fast random one, and the time saved by not repeating failed steps is time you get back for the work itself.