---
title: "Brave: which Google services it proxies, what it disables, and whether to block it on a Mac · Kilobat"
url: "https://kilobat.app/processes/brave-browser"
description: "Brave is built on Chromium and proxies update and safety requests through its own servers. What it removes, which endpoints it proxies, and what breaks if blocked."
---

# What is Brave?

Brave is a web browser built on Chromium. Most traffic is the sites you open. Brave's help centre lists the services it removes and the ones it proxies.

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

I want to know what Brave is doing on my Mac and whether its network use is normal. Read https://kilobat.app/processes/brave-browser.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: `Brave` · Also seen as: `Brave Browser`, `Brave Browser Helper` · Made by Brave Software · Applies to: Brave for desktop on macOS 14 Sonoma and later. Checked on 8 November 2026 against Brave's help centre. · Checked: 8 November 2026

## Short answer

The Brave web browser. It is built on Chromium, removes many Google services, and sends some update and safety requests through Brave's servers.

Block with care

Blocking Brave stops browsing. Blocking only the update and safety endpoints leaves browsing working but stops those checks.

Path

`/Applications/Brave Browser.app`

## What it is

Brave's help centre says that Brave for desktop is built on the open-source Chromium project. It says that Chromium is not the same as Google Chrome.

The article lists services and features that Brave disables entirely. They include Google accounts integration, DNS prefetching, background sync, Google Cloud Messaging, Firebase Cloud Messaging, metrics reporting and Chrome's Privacy Sandbox.

It also lists services that Brave proxies through its own servers. Brave says that Google then does not receive any information about which client makes the request, not even the IP address.

The proxied requests are SafeBrowsing, geolocation, plugin updates, certificate revocation, CRLSets, component updates, spellcheck dictionaries, requests in devtools and, on Android, search engine favicons.

The article lists proxied endpoints. They include `safebrowsing.googleapis.com`, `sb-ssl.google.com`, `update.googleapis.com`, `*.gvt1.com` and `clients2.google.com`.

Brave notes that you may still see requests to Google domains. It says that `clients*.google.com` and `update.googleapis.com` are needed to check for updates to extensions that you installed.

The article says that Brave caps cookie lifetimes. JavaScript cookies last at most 7 days and HTTP cookies at most 6 months.

## Why it uses the network

- **Sites you open.** The browser fetches the pages and files that you ask for. This is most of its traffic.
- **Safe browsing checks.** Brave says that SafeBrowsing requests go through its own proxy.
- **Component and certificate updates.** Brave says that component updates, certificate revocation requests and CRLSet requests are proxied.
- **Spellcheck dictionaries and geolocation.** Brave says that requests for spellcheck dictionaries and geolocation are proxied.
- **Extension updates.** Brave says that requests to `clients*.google.com` and `update.googleapis.com` check for extension updates.

## How much is normal

Brave does not publish figures for idle traffic in this article. Most traffic follows the pages that you open.

Brave says that it disables metrics reporting and background sync.

## When it uses a lot, and why

- **Many open tabs.** Each tab loads its own page. Sites cause most of the traffic.
- **Extensions.** Brave says that update checks for installed extensions contact Google domains.
- **Downloads and streaming.** A large download or a video moves the data itself. Brave's article does not give sizes.

## Is it safe to block?

Block with care

Blocking Brave stops browsing. Blocking only the update and safety endpoints leaves browsing working but stops those checks.

What breaks if you block it

- Blocking the browser stops every website from loading.
- Blocking the SafeBrowsing endpoints stops those safety checks.
- Blocking the component update endpoints stops those updates.
- Blocking `update.googleapis.com` stops extension update checks.

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. Brave already disables metrics reporting. You do not need to turn it off.
2. Remove extensions that you do not use. Brave says that installed extensions are checked for updates.
3. Read the Brave article for the full list of what the browser disables and proxies.

## See how much it uses

1. Open Activity Monitor and search for Brave. Open the Network tab to see the bytes that the browser and its helpers moved.

## With Kilobat

1. In the Kilobat app list, search for `Brave`. The helper processes group under the app.
2. Ask the same question in Terminal.

   ```
   kilobat explain Brave
   ```

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

Brave's article does not give the bundle ID, the install path or the helper process names for the Mac app.

The article says that it is a work in progress. It does not give figures for idle traffic.

The article does not describe Brave's own services, such as its telemetry. Brave documents those elsewhere.

## Questions

**Does Brave send my requests to Google?**

Brave says that it proxies some Google requests through its own servers, so that Google does not see which client sends them. It lists the endpoints.

**What does Brave remove from Chromium?**

Brave lists Google accounts integration, DNS prefetching, background sync, metrics reporting and others. The full list is in its help centre.

**Why does Brave still contact Google domains?**

Brave says that `clients*.google.com` and `update.googleapis.com` are needed to check for extension updates.

## Sources

- [Brave Help Center: What does Brave remove from the Chromium engine?](https://support.brave.app/hc/en-us/articles/10742158329613-What-does-Brave-remove-from-the-Chromium-engine)
- [Kilobat docs: Connections](https://kilobat.app/docs)

Checked on 8 November 2026.

## Related

- [Google Chrome Helper](https://kilobat.app/processes/chrome-helper): Part of Google Chrome. Chrome runs its tabs, extensions and network service in helper processes, so your browsing shows under Google Chrome Helper.
