Pro free for a week: code NETMUTE
NetMute

Two ways to get NetMute

Both are free to download and contain the same features. They differ in how you buy Pro.

Mac App Store

The simple route

  • Pro is bought in the app with your Apple Account
  • No licence key to keep
  • Apple handles payment and refunds
Open the App Store

Direct download

Version 2.3.10 · 13 MB

  • Invoice with VAT ID, ready for expenses
  • 5- and 10-seat licences for teams
  • Unlocked with a licence key
Download the .dmg

The direct build is signed with a Developer ID, notarised by Apple and updates itself. Pro does not carry over between the two: a licence key works only in the direct build, an App Store purchase only in the App Store version.

What Is avconferenced on Mac? The FaceTime Firewall Prompt Explained

avconferenced is a legitimate macOS process from Apple that handles the audio and video of FaceTime calls on your Mac. It asks to accept incoming connections because FaceTime connects devices directly, so allow it if you make calls on this Mac. If you deny it, FaceTime calls fail to connect or drop, and nothing else is affected.

7 min readUpdated

What avconferenced is

avconferenced is the macOS service that carries the audio and video of FaceTime calls. The name comes from AV (audio and video) and conference, and the program is built on a private Apple framework called AVConference. It ships with macOS. On macOS 26 the binary is /usr/libexec/avconferenced, on the protected system volume, and it is code-signed by Apple.

When you start or accept a FaceTime call, the FaceTime app handles the window and the buttons. avconferenced does the real-time work underneath: it takes the camera and microphone, encodes and encrypts the streams, and sets up the network connection to the other participants. Phone calls relayed from your iPhone are also handled through the FaceTime app on the Mac, so they lean on the same calling stack.

During a call you will usually see two more Apple processes in Activity Monitor next to it. identityservicesd is Apple's identity service, which finds the devices registered to a phone number or Apple Account so a call can reach them. callservicesd manages the state of calls on the Mac. avconferenced is the one that moves the actual sound and picture.

You can see this role in what macOS allows the binary to do. Its code signature grants it access to the camera and microphone, screen capture (used when you share your screen in a call), and both network client and network server access. That last entitlement matters for this article: avconferenced opens connections and also accepts them.

launchd starts it as a LaunchAgent, defined in /System/Library/LaunchAgents/com.apple.avconferenced.plist under the label com.apple.videoconference.camera. It runs under your user account and is launched on demand when a calling feature needs it. It may then stay loaded for a long time. On the macOS 26 Mac we checked, avconferenced had been running for more than two weeks and had used about 12 seconds of CPU time in total.

Why your firewall asks about avconferenced

The dialog reads: "Do you want the application avconferenced to accept incoming network connections?" It comes from the built-in macOS firewall, which you find in System Settings > Network > Firewall.

That firewall filters incoming connections, and avconferenced is one of the few Apple services that genuinely needs them. A FaceTime call starts through Apple's push service and Apple's relay servers. Apple's security documentation then describes the devices using STUN and ICE to set up a direct peer-to-peer connection where possible. On a direct connection, the other person's device sends audio and video packets straight to your Mac, and to the firewall those look like incoming connections to avconferenced.

Normally you never see the question, because under Firewall > Options the setting "Automatically allow built-in software to receive incoming connections" lets Apple's own signed services through without asking. You are most likely to see the prompt if that option is switched off, or after a macOS update replaced the binary and the firewall treats it as a new program.

The opposite case is quieter and easier to miss. If you enable Block all incoming connections in the firewall options, macOS does not ask at all. Apple describes that mode as preventing incoming connections to nonessential services and apps, so the direct connections FaceTime prefers can be blocked without any dialog. If FaceTime stopped working right after you hardened your firewall settings, that option is the first thing to check.

The other place people meet avconferenced is a network monitor during a call. There you will typically see it talking to Apple servers while the call connects, followed by traffic to an unfamiliar IP address. That address usually belongs to the internet provider of the person you are talking to, because the call switched to a direct connection. As with any peer-to-peer call, the two devices learn each other's network address in the process. The traffic volume during a video call is far higher than for most background services, which is expected for live video.

What happens if you deny it

If you click Deny, or later set avconferenced to block incoming connections, FaceTime on that Mac becomes unreliable. The symptoms people report:

  • Calls ring but never connect, or hang while connecting.
  • Calls connect and then drop.

A call can still ring because the notification arrives through Apple's push service, a separate path that the firewall does not touch. The media connection that avconferenced needs is the part that fails. How badly calls break depends on your network: Apple's own firewall guidance notes that, depending on your router's NAT configuration, additional ports may be used for video, so the media path differs from one network to the next. One user report on Apple's support forum describes FaceTime failing in both directions after declining the prompt.

Denying it does not affect anything outside calling. Web browsing, iCloud, iMessage text messages, mail and your apps work as before.

Undoing a denial. Open System Settings > Network > Firewall, click Options, find avconferenced in the list and set it to Allow incoming connections. In Terminal, the firewall's command-line tool can do the same: sudo /usr/libexec/ApplicationFirewall/socketfilterfw --unblockapp /usr/libexec/avconferenced. Then try the call again.

If you manage a network firewall or router rules, Apple lists the ports FaceTime uses in its support article on using FaceTime and iMessage behind a firewall. They include TCP 80, 443 and 5223 and several UDP ranges for the media streams.

Should you allow avconferenced?

The decision follows from one question: do you make FaceTime calls on this Mac, or take iPhone calls on it?

If you do, allow it. There is no meaningful security benefit in blocking a signed Apple service from receiving the call traffic it exists to receive. Apple's security documentation states that FaceTime audio and video are end-to-end encrypted with SRTP, and that Apple cannot decrypt the content. Accepting incoming connections here means accepting packets for a call you started or answered.

The rule is also narrow. Allowing avconferenced lets that one program receive connections. It does not open your Mac to the internet in general, and every other program stays subject to the firewall as before. On most home networks your router sits in front of the Mac as well and only lets call traffic through once your side has started the connection setup.

If you never call from this Mac, denying it costs you nothing you would notice. The cleaner route is to switch calling off at its source: sign out of FaceTime in the FaceTime app's settings, and turn off calls from iPhone if you do not want your Mac to ring when your phone does. Then nothing asks avconferenced to do its job, and a firewall rule becomes unnecessary.

Avoid half states. A Mac that is signed in to FaceTime but blocks avconferenced can keep ringing for calls it cannot complete, which looks like a FaceTime bug and is tedious to trace back to a firewall decision made months earlier.

Sustained high CPU or heavy network use from avconferenced outside a call is unusual. Check that no call is still active, for example in the FaceTime app, then restart the Mac. A process that stays loaded but idle, as described above, is normal.

How to check it is the real avconferenced

avconferenced is Apple's code, so the genuine one is safe. It is still worth knowing how to confirm that, because malware sometimes uses familiar system names.

Check the path. In Activity Monitor, double-click avconferenced and open Open Files and Ports. The executable should be /usr/libexec/avconferenced. That directory is on the read-only system volume and protected by System Integrity Protection, so ordinary software cannot place a replacement there. A process with the same name running from your home folder, Downloads or an app bundle is not Apple's.

Check the signature. In Terminal, run codesign -dvv /usr/libexec/avconferenced. The real binary reports the identifier com.apple.avconferenced and a signing chain of macOS Software Signing, Apple Code Signing Certification Authority and Apple Root CA. A developer name you do not recognise, an ad-hoc signature or no signature means it is not the Apple service.

Check the behaviour. The real avconferenced is busy during calls and nearly idle the rest of the time.

The firewall dialog only ever shows you the processes that listen for incoming connections. Most of what your Mac sends out never triggers a prompt. NetMute lists every app and system process with live traffic, including avconferenced, and shows which domains and addresses each one contacted. If you decide a process should stay offline, one switch blocks it.

Frequently asked questions about avconferenced

See which processes on your Mac go online

NetMute lists every app and system process with live traffic, shows the domains each one contacted and blocks any of them with one switch. Free on the Mac App Store. Pro is a one-time purchase, no subscription.

Free on the Mac App Store

Free with no time limit · Pro $12.99 one-time

Download free