How to Connect a Dapp to Brave Wallet

You can connect a website or dapp to Brave Wallet from the Brave browser by selecting its connect-wallet option and approving the connection in Brave Wallet. The connection lets the site interact with your public wallet address; it does not, by itself, move crypto or give the site your recovery phrase.

Before you begin, make sure you are using Brave and can unlock the wallet. Keep the site open in the same browser where Brave Wallet is available. If you are on a phone, open the site in Brave rather than a different browser or an in-app web view.

Have these ready:

• Brave Wallet set up and unlocked.
• The account you intend to use, especially if your wallet has more than one.
• The network the dapp supports, plus its native token if you expect to make a transaction.

Connecting is generally free. Later actions can cost network fees, and a dapp may charge additional fees for swaps or other services. You do not need to enter your recovery phrase into a website to connect.

1. Open the dapp in Brave and check the address carefully. Use the site’s official address that you already trust; ads, copied names and lookalike domains can lead to fakes.
2. Select Connect wallet, Connect, or a similar control on the dapp.
3. Choose Brave Wallet from the wallet options. If the site offers several wallet choices, do not pick one simply because it appears first.
4. Review the request in the Brave Wallet window or panel. Check which account is being connected and what permissions the prompt describes.
5. Approve only if the site and account are correct. Return to the dapp and confirm that it shows the expected public address or connected state.

Some dapps use different button names, and Brave’s menus can vary by version or device. If no Brave Wallet option appears, do not type your recovery phrase into the page or install an unfamiliar wallet extension just to make the connection work. First check that you are in Brave, that the wallet is enabled and unlocked, and that the dapp supports browser wallets.

A dapp may work only on particular networks. Before continuing, compare the network selected in Brave Wallet with the network the site says it supports. A wallet can hold accounts across multiple networks, but an asset or transaction on one network is not automatically available on another.

Check these details before using the dapp:

• Account: Is the displayed address the one you meant to connect? If you have separate accounts, choose deliberately.
• Network: Does the wallet show the chain the dapp expects? Changing networks can affect which assets and features the site can access.
• Funds for fees: If you plan to send a transaction, you may need that network’s native token to pay its fee.
• Transaction destination: For any later transaction, verify the asset, amount, recipient or contract, and network in the wallet prompt.

Do not bridge or transfer funds just because the dapp reports a network mismatch. First confirm that the dapp genuinely supports the destination network and that you understand the cost and risks of moving assets. If the wallet and site disagree, pause rather than approving a transaction to “fix” the connection.

A wallet connection is not the same as approving a payment. Connecting normally lets a site read your public address and request certain wallet actions. A separate prompt is generally needed for a signature or transaction. Read each prompt as a new decision, even if you already connected to the site.

Before approving anything, check:

• What action is being requested: a message signature, a token approval, or a transaction.
• Which account and network the request uses.
• The amount and asset, if funds are involved.
• Whether an approval gives a contract permission to use tokens, and whether the requested scope makes sense for what you are doing.

A signature can have consequences even when it does not look like a conventional payment. If the wallet prompt is unclear, unexpected, or unrelated to the task, reject it and leave the site. Never share your recovery phrase or private key with a dapp, support agent, or pop-up. Brave Wallet cannot make a malicious site safe simply because the wallet is built into the browser.

If the connection does not appear, work through these checks in order:

1. Confirm the site is open in Brave and reload it once. Make sure you did not open it in another browser or an embedded app window.
2. Open Brave Wallet from the browser toolbar or menu and unlock it. If the wallet is unavailable, check Brave’s wallet settings and browser version.
3. Return to the dapp and choose its connect option again. Select Brave Wallet if the site asks you to choose a provider.
4. Check whether the dapp supports the selected account type and network. Try the site’s documented supported network rather than switching blindly.
5. If a wallet prompt opened behind another window, bring Brave to the foreground and look for it. Reject any prompt you did not initiate.

If the wallet connects but the dapp still shows “not connected,” reload only after confirming there is no pending request. You can also disconnect the site and start over. Avoid installing unknown add-ons, sharing screen access with strangers, or entering recovery details into troubleshooting forms. If the issue persists, wait and try later or contact the dapp through a channel you independently verify.

To end a connection, first look for a disconnect control in the dapp’s wallet menu or account panel. If it does not offer one, open Brave Wallet and look for connected sites, site permissions or a similar control; remove the specific site there. The exact label and location can vary between Brave versions.

Then consider whether you approved anything beyond connecting. Disconnecting prevents the site from using that wallet connection, but it does not reverse an on-chain transaction or necessarily cancel a token allowance. If you approved a token allowance and no longer want it active, review and revoke it using a trusted wallet or blockchain tool for the relevant network. Revocation itself may require a transaction fee, and you should verify the network and contract before proceeding.

If you suspect a fake site or exposed recovery phrase, disconnecting alone is not enough. Do not use the suspicious site again. If a recovery phrase may have been compromised, move remaining assets to a newly created, secure wallet as soon as you can do so safely; never reuse the exposed phrase. For an ordinary connection you no longer need, removing the site is a sensible cleanup step.

Most problems come from choosing the wrong wallet, network or site—or from treating a connection as harmless permission to approve every later prompt. Use this short checklist before you proceed:

• Wrong website: Check the full domain and make sure it is the one you intended to visit.
• Wrong account: Confirm the address shown in Brave Wallet before connecting. Do not assume the first account is the right one.
• Wrong network: Match the chain shown in the dapp and wallet. Do not send assets across networks without understanding the transfer route.
• Unexpected signature: Reject it if you cannot explain why the dapp needs it.
• Unclear token approval: Check what token and permission the contract is asking for; do not grant broad access just to dismiss a warning.
• Recovery phrase request: Stop. A website does not need your seed phrase to connect to Brave Wallet.
• Urgent support message: Do not share wallet details or let someone control your device to “fix” the issue.

When uncertain, cancel the request and verify the dapp independently before trying again. It is safer to miss a transaction than to approve one you do not understand.