Reviewed guide | 2026-10-15
Using Bybit Sub-Accounts to Keep Deposits for Different Purposes Apart
Bybit lets you create sub-accounts with their own deposit addresses and permissions. How to set one up for a bot or a savings pot, move funds between them and limit what each can withdraw.
Bybit | the reader's region | the reader's funding currency | deposits, networks and withdrawal controls
Most people deposit everything into one Bybit account: the coins they plan to hold for years, the money they trade with each week and the capital a bot is allowed to touch. When everything sits together, one mistake or one leaked API key affects all of it. Bybit's sub-account feature lets you split funds into separate compartments under the same login, each with its own deposit addresses, balances and API keys. Setting it up is quick, and it changes how much damage a single error can do.
Create a sub-account
On the Bybit website, open the account menu and choose Sub-Account. Select create, give it a descriptive name such as bot capital or long-term holdings, and choose the account type offered. Bybit creates it under your main account, so you do not need a separate email unless you choose that option. The sub-account appears in a list with its own balance and settings.
Deposit and transfer between accounts
Each sub-account has its own deposit addresses, which you can view by switching into it and opening the deposit page. Many users deposit everything to the main account and then use the internal transfer function in the Sub-Account page to move funds across. Internal transfers between your own accounts are recorded in the asset history of both sides and do not go on chain. Label each transfer clearly in your own notes so you can reconcile later.
Limit what each compartment can do
The real benefit comes from permissions. Create API keys only inside the sub-account a bot uses, so a leaked key cannot reach your main holdings. For the long-term holdings compartment, avoid creating any API key at all. Withdrawal rights and the withdrawal address whitelist are managed from the main account security settings; keep the whitelist on so funds can only leave to addresses you saved.
Review the structure regularly
Once a month, open the Sub-Account page and check the balance of each compartment, the API keys attached and any recent transfers. Delete sub-accounts you no longer use after moving their balance back. If you stop running a bot, remove its key and transfer its capital to the main account the same day.
Risk boundary: Bybit Deposit Guide
Digital assets are volatile and derivatives can amplify losses. This website has no login, wallet connection, deposit form or customer-support chat. A referral link only records attribution; it does not guarantee access, pricing, rewards, approval or investment results. Availability can differ by residence, legal entity and product, so no regional access is assumed from language or branding alone.
Scenario checkpoint
- Create a named sub-account for each purpose, such as bot capital or long-term holdings.
- Use the internal transfer function to move funds and note the purpose of each transfer.
- Create API keys only inside the sub-account a bot uses and never in the holdings account.
- Review balances, keys and transfers of every sub-account during a monthly check.
Digital assets are volatile and derivatives can amplify losses. This website has no login, wallet connection, deposit form or customer-support chat.