What is Slack?
Slack is a messaging app. On a Mac, its network use is one long-lived connection for live messages. Slack documents that connection for network administrators.
I want to know what Slack is doing on my Mac and whether its network use is normal. Read https://kilobat.app/processes/slack.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.
Short answer
The Slack desktop app. It keeps a persistent WebSocket connection to Slack's messaging servers over port 443, plus HTTPS for everything else.
Block with care
Blocking Slack's hosts stops live messages in the app. Block them only on a network where you do not use Slack.
- Path
/Applications/Slack.app/Contents/MacOS/Slack- Signing identifier
com.tinyspeck.slackmacgap
What it is
Slack's connectivity article is for IT and network administrators. It says that Slack needs a persistent connection between its messaging server and members' apps or browsers.
Slack says that it uses WebSockets over port 443 for this connection. Proxies and firewalls can sometimes interrupt it.
The article tells administrators to allowlist every URL on my.slack.com/help/urls. You must sign in to a workspace to see that page. Each workspace or org shows its own list.
If a proxy decrypts SSL, Slack says that the proxy must support WebSockets. Otherwise you must exempt wss-primary.slack.com, wss-backup.slack.com and wss-mobile.slack.com from decryption.
Slack also says that administrators can limit access to chosen workspaces by injecting a header at a proxy. The network requirements are the same.
On this Mac, the app is Slack.app with the bundle ID com.tinyspeck.slackmacgap.
Why it uses the network
- Live messages. The WebSocket connection delivers new messages and other updates to the app as they happen.
- Everything else over HTTPS. Slack's article lists the URLs that a workspace needs. It does not say which URL serves which feature.
- Connection tests. Slack's page
my.slack.com/help/testchecks your network. It shows WebSocket results for the primary and backup hosts.
How much is normal
Slack does not publish figures for idle traffic. You should expect small, steady traffic from the open connection when nobody posts.
Traffic grows with what you read and share. Opening a busy channel, previewing links and loading files all use the network.
Slack's article says that an out-of-date desktop app can cause connection problems and broken features. It advises you to keep the app current.
When it uses a lot, and why
- Large files. Uploading or opening big files in channels moves the file over the network.
- Many workspaces. Slack's article says that each workspace or org has its own URL list. Several signed-in workspaces mean several sets of connections.
- A blocked WebSocket. If the WebSocket fails, the app may retry. Slack's test page shows primary and backup results.
Is it safe to block?
Block with care
Blocking Slack's hosts stops live messages in the app. Block them only on a network where you do not use Slack.
What breaks if you block it
- The app cannot keep its WebSocket connection, so new messages stop arriving.
- Sign-in and workspace loading fail when the URLs on Slack's list are blocked.
- A proxy that decrypts SSL without WebSocket support breaks the connection.
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
Keep the app current. Slack says that old versions can cause connection problems and broken features.
Sign out of workspaces that you do not use on this Mac.
On a company network, ask the administrator to allow the URLs on
my.slack.com/help/urls.
See how much it uses
Open Activity Monitor and search for Slack. Open the Network tab to see the bytes that the app and its helpers moved.
With Kilobat
In the Kilobat app list, search for
Slack. Its helper processes group under the app.Ask the same question in Terminal.
kilobat explain Slack
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, Protection and the hotspot data saver.
Hosts it contacts
Apple and the maker document these hosts for this feature. A process can also contact others; Kilobat’s Connections tab shows what it actually opens on your Mac.
What isn’t documented
Slack's article does not list the macOS process names. It does not say how much data an idle connection uses.
Slack does not say in this article which features, such as calls or huddles, use extra ports. Use the URL list in your workspace for exact needs.
Slack names some antivirus and ad-blocking products that can interfere. It gives no detail on how.
Questions
Which port does Slack use?
Slack says that it uses WebSockets over port 443 for its persistent connection.
How do I test my network for Slack?
Sign in to a workspace and open my.slack.com/help/test. Check the WebSocket results for the primary and backup hosts.
Sources
Checked on 8 November 2026.