How to add a custom network or RPC in Rabby

Quick steps

1. Check the built-in list. Make sure the chain is not already supported by Rabby before adding it yourself.
2. Collect network details. Get the chain ID, network name, RPC URL, currency symbol and optional explorer from the chain's documentation and cross-check the chain ID.
3. Add the custom network. Open Rabby's settings, choose the option to add a custom network, fill in or search the details and confirm.
4. Optionally change an RPC. To use your own node for a built-in chain, use the extension's option to modify the RPC URL, pick the chain, paste the URL and save.
5. Test with a small amount. Switch to the network, confirm balances and gas load, and send a small test transaction.

Rabby already includes a long list of EVM chains and switches to the right one automatically when a dapp asks. See supported chains first; you may not need a custom network at all. Custom settings are useful for new chains, testnets, app-specific chains and private or paid RPC endpoints.

Two different things

These option names come from a September 2026 Chainstack tutorial. Older guides place them under a "More" menu instead of "Settings", so the location depends on your Rabby version. Look for them in Rabby's settings or more menu.

Step 1: get trustworthy network details

You need four values, plus one optional value:

• Chain ID: the number that identifies the chain. This is what protects you from signing for the wrong network.
• Network name: any label you like.
• RPC URL: the node Rabby will talk to.
• Currency symbol: the gas token (for example ETH).
• Block explorer URL: optional, used for transaction links.

Take these from the chain's own documentation, and cross-check the chain ID with a second source such as Chainlist (chainlist.org). A 2026 review notes that Rabby's custom network screen can search Chainlist data to fill the fields for you (Bytwork, 2026). Be careful with RPC URLs from random posts or DMs.

Step 2: add the custom network

1. Open Rabby's settings and choose the option to add a custom network.
2. Search for the chain, or enter chain ID, network name, RPC URL and currency symbol by hand. Add the explorer if you have one.
3. Confirm. Rabby warns that it cannot verify the security of custom networks (Chainstack, 2026).

The network now appears among your chains. Chainstack reports that custom networks are listed under a separate custom network tab in the portfolio, and that you can add tokens there by contract address.

Step 3 (optional): change the RPC of a built-in chain

1. In the extension's settings, open the option to modify an RPC URL.
2. Pick the built-in chain from the list.
3. Paste your RPC URL and save.

The endpoint must belong to the same chain. A mismatched or broken endpoint can stop balances and gas estimates from loading. To undo it, delete the custom entry from the same screen (Chainstack, 2026).

What custom networks do not get

Rabby gives full support, including portfolio values and security features, only to integrated chains. For custom networks, Chainstack reports that Rabby shows token amounts only, with no price data or transaction history, and CryptoSlate describes them as having basic transfers and dapp connections. Rabby's built-in swap does not work on custom networks (Rabby source code, 2026). Expect transaction previews and risk checks to be more limited too, so be extra careful when signing on a custom chain.

Custom networks and RPC changes are stored locally. After reinstalling Rabby or moving to another browser, add them again.

Security risks of untrusted RPCs

• Privacy. The RPC operator sees your addresses, IP address and the transactions you send.
• Wrong data. A malicious RPC can show fake balances or fake confirmations, which some scams use to make a "deposit" look real.
• Wrong chain. A wrong chain ID can lead to signing for a network you did not intend. Always verify it.

An RPC cannot take your funds by itself; it cannot sign for you. The danger comes from what it makes you believe and sign. Rabby will never ask for your seed phrase to "activate" a network, and neither will any chain team.

Common mistakes

• Adding a chain that Rabby already supports. You lose prices, history and some security checks. Use the built-in chain and, if needed, change only its RPC.
• Using a websocket or dashboard link. Rabby needs the HTTPS RPC endpoint that your provider gives for wallets, not a web page or a websocket address.
• Testnet and mainnet mix-ups. Many chains have a testnet with a similar name. The chain ID tells them apart.
• Expecting tokens to appear by themselves. On a custom network, add tokens by contract address, taken from the project's official documentation.

Check it works

Switch to the network, check that your balance and gas estimates load, and send a small test transaction before moving larger amounts. If transactions hang, see transaction stuck pending. To estimate costs on a new chain, try the gas cost estimator.

Frequently asked questions