---
title: "Sonos: which ports the Sonos app uses on a Mac, and what breaks if you block them · Kilobat"
url: "https://kilobat.app/processes/sonos"
description: "The Sonos app controls speakers on your network. Which ports and domains Sonos lists, and what stops working if a firewall blocks them."
---

# What is Sonos?

The Sonos app on a Mac controls speakers on your local network. Sonos publishes the ports that it needs, so a firewall rule can be exact.

**Fix this with your agent**Copies a prompt for Claude Code, Codex or any agent that can use Terminal.

I want to know what Sonos is doing on my Mac and whether its network use is normal. Read https://kilobat.app/processes/sonos.md and work through it with me. Install the Kilobat CLI if it’s missing: brew install seifip/kilobat/kilobat. Run the guide’s Terminal and kilobat checks yourself and tell me what you find. List the steps only I can do. Ask before you change any setting.

Process: `Sonos` · Also seen as: `Sonos S2`, `Sonos controller` · Made by Sonos · Applies to: The Sonos app on macOS 14 Sonoma and later. Checked on 7 November 2026 against Sonos Support. · Checked: 7 November 2026

## Short answer

The Sonos controller app. It finds and controls speakers on your local network, and talks to Sonos servers for content and your account.

Block with care

Blocking the Sonos app or its ports stops it from finding or controlling speakers. Playback that is already running may continue.

Path

`/Applications/Sonos.app/Contents/MacOS/Sonos`

## What it is

Sonos's firewall article lists TCP ports 80 and 443 for content services, radio and the Sonos account.

It lists TCP 1400, 1443, 1500, 1543, 1600, 1643, 1700, 1743, 1843, 1943, 2043, 2143, 3400, 3401 and 3500 for Sonos control.

It lists UDP 1900 and 1901 for Sonos app control, UDP 6969 for setup, and TCP 4444 for system updates.

It also lists TCP 4070 and UDP 5353 for Spotify Connect, and TCP 7000 to 7003 for AirPlay. The music library uses TCP 445 and 3445 and UDP 136 to 139.

Sonos says that the ports should be open to the IP addresses of your Sonos products. Inbound access must also be enabled for the Sonos app.

For full app function, Sonos lists these domains, among others. They are `logx.optimizely.com`, `cdn.optimizely.com`, `msmetrics.ws.sonos.com`, `e.crashlytics.com`, `device-api.urbanairship.com` and any `.sonos.com` subdomain.

## Why it uses the network

- **Speaker control.** The app sends commands to speakers on the local network on the control ports.
- **Finding speakers.** Sonos lists UDP 1900 and 1901 for app control. The article does not describe the discovery method in detail.
- **Content and account.** Radio, streaming services and your Sonos account use TCP 80 and 443.
- **Metrics and crash reports.** The domains that Sonos lists include a metrics host and a crash reporting host.

## How much is normal

Most of the app's traffic stays on your local network, between the Mac and the speakers.

Small exchanges with Sonos domains when you open the app are usual.

Sonos's article does not give traffic amounts, so this entry gives none.

## When it uses a lot, and why

- **A music library on this Mac.** Sonos lists the library ports. Playing from a shared folder sends the audio from the Mac or the file server to the speakers.
- **A system update.** Sonos lists TCP 4444 for system updates.
- **Many speakers.** Control traffic grows with the number of rooms that you control.

## Is it safe to block?

Block with care

Blocking the Sonos app or its ports stops it from finding or controlling speakers. Playback that is already running may continue.

What breaks if you block it

- The app cannot find or control speakers when the control ports are blocked.
- Setup fails when UDP 6969 is blocked.
- Account sign-in and music services fail when TCP 80 and 443 are blocked.
- Spotify Connect and AirPlay to Sonos stop when their ports are blocked.

Blocking means a firewall rule that refuses its connections. Don’t quit or disable a macOS process to save data: macOS starts it again, and other features depend on it.

## Reduce its use

1. Keep the Mac and the speakers on the same network. A guest network may block local traffic.
2. On a firewall, open the ports that Sonos lists to the speakers' IP addresses.
3. Run system updates of speakers on a network with room for them.

## See how much it uses

1. Open Activity Monitor and search for `Sonos`. The Network tab shows the bytes sent and received.

## With Kilobat

1. In the Kilobat app list, search for `Sonos`. Its row shows the local and internet hosts.
2. Ask the same question in Terminal.

   ```
   kilobat explain Sonos
   ```

The live view and the explanations are free. History in the app needs Kilobat Pro. Blocking needs Pro and the network filter: see the [network filter](https://kilobat.app/docs/blocking#filtering), [Protection](https://kilobat.app/docs/blocking#protection) and the [hotspot data saver](https://kilobat.app/save-hotspot-data).

## What isn’t documented

Sonos's article lists ports but does not say which of them the Mac app uses itself. Some belong to speakers or other services.

The article does not mention multicast, so this entry does not either.

## Questions

**Which ports does Spotify Connect use on Sonos?**

Sonos lists TCP 4070 and UDP 5353 for Spotify Connect.

**Why does the Sonos app need inbound access?**

Sonos says that inbound access must be enabled for the Sonos app, and that the ports must be open to your Sonos products.

## Sources

- [Sonos Support: Configure your firewall to work with Sonos](https://support.sonos.com/en-us/article/configure-your-firewall-to-work-with-sonos)
- [Kilobat docs: Connections](https://kilobat.app/docs)

Checked on 7 November 2026.

## Related

- [mDNSResponder](https://kilobat.app/processes/mdnsresponder): Part of macOS. It handles system DNS lookups for apps and runs Bonjour on the local network, so its traffic can include other apps' name lookups.
