Last updated: March 15, 2026

To disable Brave’s crypto features, go to brave://settings, toggle off Brave Rewards and Brave Wallet, then visit brave://flags and set IPFS, Brave Wallet, Native Wallet, and Solana Wallet to “Disabled.” For persistent enforcement on managed devices, deploy registry policies (Windows), plist configurations (macOS), or JSON policies (Linux) that set BraveWalletAllowed and BraveRewardsAllowed to false. This guide covers five methods from simple GUI toggles to custom compiled builds, each with different tradeoffs between ease and permanence.

Prerequisites

Before you begin, make sure you have the following ready:

Step 1 - Understand Brave’s Crypto Features

Brave includes the following crypto-related components by default:

Each of these can be disabled individually through configuration. The level of control depends on your technical access and deployment scenario.

Step 2 - Method 1: Disable via Brave Settings (GUI)

The easiest approach uses Brave’s internal settings panel without requiring administrative access:

  1. Open Brave and navigate to brave://settings
  2. Scroll to Additional Settings → Brave Rewards and Tips
  3. Toggle off all reward-related options
  4. Navigate to Wallet section and disable Brave Wallet completely
  5. Return to settings and disable any remaining crypto-related toggles

This handles basic disabling but leaves residual code in the browser executable. Features may reappear after browser updates or can be re-enabled by users with access to the settings panel.

Step 3 - Method 2: Disable via Configuration Flags

For granular control beyond the standard settings, Brave provides experimental flags accessible at brave://flags. These offer deeper control over individual features:

These flags apply immediately and persist across sessions. However, they may reset with major browser updates and require re-application.

Step 4 - Method 3: Disable via Command Line Arguments

For deployment scenarios, automated setups, or enterprise deployments, use launch arguments applied at runtime:

macOS
/Applications/Brave\ Browser.app/Contents/MacOS/Brave\ Browser \
  --disable-features=BraveWallet,BraveRewards,IPFS,Solana

Linux
brave-browser --disable-features=BraveWallet,BraveRewards,IPFS,Solana

Windows
"C:\Program Files\BraveSoftware\Brave Browser\Application\brave.exe" ^
  --disable-features=BraveWallet,BraveRewards,IPFS,Solana

The --disable-features flag accepts comma-separated feature names from Brave’s Chromium implementation. For permanent application on Linux systems, create a wrapper script or desktop entry that includes these arguments automatically.

Method 4 - Configure via Policies (Enterprise/IT)

System administrators managing multiple workstations can deploy registry or plist configurations that override user settings and prevent re-enabling through the UI:

Windows Registry (per-user):

[HKEY_CURRENT_USER\Software\Policies\BraveSoftware\Brave]
"BraveWalletAllowed"=dword:00000000
"BraveRewardsAllowed"=dword:00000000

Windows Registry (machine-wide):

[HKEY_LOCAL_MACHINE\Software\Policies\BraveSoftware\Brave]
"BraveWalletAllowed"=dword:00000000
"BraveRewardsAllowed"=dword:00000000

macOS plist (com.brave.Browser.plist in /Library/LaunchDaemons):

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN">
<plist version="1.0">
<dict>
    <key>BraveWalletAllowed</key>
    <false/>
    <key>BraveRewardsAllowed</key>
    <false/>
    <key>IPFSEnabled</key>
    <false/>
</dict>
</plist>

Linux (distributed via /etc/chromium/policies/managed/brave.json):

{
  "BraveWalletAllowed": false,
  "BraveRewardsAllowed": false,
  "IPFSEnabled": false
}

These policies override user settings and prevent re-enabling through the UI. The machine-wide configurations take precedence over per-user settings and require administrative privileges to modify.

Step 5 - Method 5: Compile Custom Build

For maximum control and minimal attack surface, build Brave from source with crypto features disabled entirely:

  1. Clone the Brave repository: 
    git clone https://github.com/brave/brave-browser.git
cd brave-browser
npm install
  2. Modify component build configurations to disable features by default:
// In src/brave/common/brave_switches.cc
// Disable wallet features by default
const char kDisableBraveWalletFeature[] = "disable-brave-wallet";
const char kDisableIPFSFeature[] = "disable-ipfs";
const char kDisableSolanaFeature[] = "disable-solana";
  1. Configure build arguments in src/brave/DEPS or via GN args: ```bash gn args out/Default Add the following lines: brave_wallet = false brave_rewards = false ipfs = false brave_solana = false

Then build ninja -C out/Default brave


This approach requires significant build infrastructure including approximately 100GB of disk space and build dependencies. The resulting binary contains no crypto functionality, making it ideal for security research or high-security deployments.

Step 6 - Verification: Confirming Disabled Status

After applying your chosen method, verify the features are properly disabled:

Check Brave Wallet availability:
```javascript
// Open browser console (F12) on any page
console.log(window.ethereum?.isMetaMask);
// Should return: undefined (wallet not present)
console.log(window.solana?.isPhantom);
// Should return: undefined (Solana wallet not present)

Check IPFS functionality:

Attempt to resolve an IPNS domain
curl -I https://ipfs.io/ipfs/QmT5NvUtoM5nWFfrQdVrFtvGfKFmG7AHE8P34isapyhCxX
Should fail or timeout if IPFS integration disabled

Check Rewards status:

Navigate to brave://rewards-internals
Should show "Rewards are disabled" or similar message

Check brave://settings:

Security Considerations

Disabling crypto features provides several tangible benefits for security-conscious users:

Fewer code paths mean fewer potential vulnerabilities. wallet implementations frequently contain security flaws that attackers target. Disabling these features eliminates blockchain-related metadata leakage including wallet addresses, transaction patterns, and IPFS content hashes that could be correlated with user activity. Removing them also eliminates background crypto operations, wallet processes, and IPFS node resource consumption. This configuration can meet corporate or regulatory requirements that prohibit cryptocurrency software or require controlled browsing environments. Fewer features also means fewer updates required and less exposure to browser update-related vulnerabilities.

However, consider the tradeoffs before disabling everything. IPFS, for instance, has legitimate non-crypto uses for decentralized content delivery that can improve resilience against content censorship. Evaluate your specific security requirements and threat model before disabling everything.

Troubleshooting Common Issues

Settings revert after restart - User-level configurations may not persist. Use policy enforcement (Method 4) for persistent configuration or command line arguments (Method 3) for scripted deployments.

Features re-enable after update - Brave updates frequently reset feature flags and may re-enable components. Maintain deployment scripts that reapply settings after each update cycle.

Cannot access brave://flags: Enterprise installations may have flags locked via group policy. Contact your system administrator for access or use policy-based configuration instead.

Performance degradation persists: Background processes may continue even after UI disabling. Use process monitoring tools to verify crypto-related processes terminate completely.

Frequently Asked Questions

How long does it take to complete this setup?

For a straightforward setup, expect 30 minutes to 2 hours depending on your familiarity with the tools involved. Complex configurations with custom requirements may take longer. Having your credentials and environment ready before starting saves significant time.

What are the most common mistakes to avoid?

The most frequent issues are skipping prerequisite steps, using outdated package versions, and not reading error messages carefully. Follow the steps in order, verify each one works before moving on, and check the official documentation if something behaves unexpectedly.

Do I need prior experience to follow this guide?

Basic familiarity with the relevant tools and command line is helpful but not strictly required. Each step is explained with context. If you get stuck, the official documentation for each tool covers fundamentals that may fill in knowledge gaps.

Is this approach secure enough for production?

The patterns shown here follow standard practices, but production deployments need additional hardening. Add rate limiting, input validation, proper secret management, and monitoring before going live. Consider a security review if your application handles sensitive user data.

Where can I get help if I run into issues?

Start with the official documentation for each tool mentioned. Stack Overflow and GitHub Issues are good next steps for specific error messages. Community forums and Discord servers for the relevant tools often have active members who can help with setup problems.

Related Articles

Built by theluckystrike. More at zovo.one