Skip to content
bnb·explorer
EN

Guide · Developers

How to create a BEP-20 token, step by step

Deploying a token on BNB Smart Chain takes an hour and costs a fraction of a cent in gas. Doing it in a way that buyers, explorers and security scanners trust takes a little more care. This is the honest version: audited code, testnet first, verified source and no hidden tricks.

Regulated exchange partner · FinCEN-registered MSB · GFSC-authorised

OpenZeppelin + RemixTestnet first Updated · 12 min
Smartphone showing blockchain blocks, illustrating a BEP-20 token deployed on BNB Smart Chain

To create a BEP-20 token, write an ERC-20 contract based on OpenZeppelin, compile it in Remix, deploy it with MetaMask on BSC testnet (chain ID 97) to test, then deploy the same code on BNB Smart Chain mainnet (chain ID 56) and verify the source on BscScan. Gas for a simple token costs well under 0.0001 BNB.

That is the technical part, and it is genuinely easy. The hard part is everything around it: deciding what powers the contract should have, not shipping a token that scanners flag as a honeypot, and understanding what happens once other people hold it. We use the same tools and checks we apply when reviewing someone else’s token, from the other side.

Before you start: what a BEP-20 token is

A BEP-20 token is a smart contract on BNB Smart Chain that keeps a ledger of balances and implements the standard functions transfer, approve, transferFrom, balanceOf and totalSupply. The BEP-20 specification mirrors Ethereum’s ERC-20, which is why the same Solidity code works on both. Our BEP-20 token explorer explains how tokens appear on-chain once they exist.

What you need

Wallet
MetaMask (or any EVM wallet) with a fresh deployer account
Networks
BSC testnet (chain 97) and BSC mainnet (chain 56)
Test gas
Free tBNB from a testnet faucet
Mainnet gas
A small amount of real BNB
Tools
Remix IDE in the browser, OpenZeppelin Contracts
Time
About an hour the first time

How to create a BEP-20 token: the 8 steps

  1. 01

    Decide what the token must do

    Name, symbol, total supply and whether anyone should be able to mint, pause or charge fees later. Every extra power is a risk flag for buyers.

  2. 02

    Set up a wallet and BNB Smart Chain

    Use a fresh MetaMask account as the deployer, add BSC testnet (chain 97) and mainnet (chain 56), and get free tBNB from a faucet.

  3. 03

    Write the contract with OpenZeppelin

    Start from the audited OpenZeppelin ERC-20 implementation in Remix or the OpenZeppelin Wizard instead of copying code from a random tutorial.

  4. 04

    Compile and deploy on testnet

    Compile in Remix, deploy with the Injected Provider (MetaMask) on chain 97 and check the result in a testnet explorer.

  5. 05

    Test transfers and wallet display

    Send tokens between two test wallets, import the token in MetaMask and confirm name, symbol and decimals.

  6. 06

    Deploy on mainnet

    Switch MetaMask to chain 56, keep a little real BNB in the deployer, deploy the exact same code and save the contract address.

  7. 07

    Verify the source code

    Publish the source on BscScan (or Sourcify) with the same compiler version and settings. Verified code is the first thing careful buyers check.

  8. 08

    Add liquidity only if you mean it

    A DEX pool needs real capital on both sides and creates real obligations. Lock or burn LP tokens if you invite others to trade.

Step 1–3: write the contract with OpenZeppelin

Do not write token logic from scratch, and do not copy a contract from a video or a Telegram post. OpenZeppelin Contracts is the most widely used audited library for ERC-20 tokens, and its free Contracts Wizard generates a token from checkboxes — mintable, burnable, pausable, permit, ownable — and opens it in Remix in one click. Every box you tick adds a power that buyers and scanners will see, so start with none.

This is a complete fixed-supply token. It has no owner, no mint function after deployment and no transfer fees:

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.27;

import {ERC20} from "@openzeppelin/contracts/token/ERC20/ERC20.sol";

/// Fixed supply, no owner, no fees: the simplest token buyers can trust.
contract MyToken is ERC20 {
    constructor() ERC20("My Token", "MTK") {
        // 1,000,000 tokens with 18 decimals, minted once to the deployer
        _mint(msg.sender, 1_000_000 * 10 ** decimals());
    }
}

Open Remix, create a file such as MyToken.sol, paste the code and change the name, symbol and supply. Remix fetches the OpenZeppelin import automatically. In the Solidity Compiler tab pick a compiler version that matches the pragma, compile, and note the exact version and optimisation settings — you will need them for verification. Decimals default to 18, the same as USDT and most tokens on BSC.

Step 4–5: deploy and test on BSC testnet

Add BSC testnet to MetaMask (chain ID 97, symbol tBNB) and claim free tBNB — both are explained in our BSC testnet explorer guide, which includes a one-click network button. In Remix, open Deploy & run transactions, choose Injected Provider – MetaMask as the environment, confirm that Remix shows chain 97, select your contract and click Deploy. MetaMask asks you to confirm the transaction.

Copy the new contract address from Remix and paste it into a testnet explorer. You should see a contract with your name, symbol, 18 decimals and the full supply in the deployer’s wallet. Then test the boring things: send tokens to a second account, import the token in MetaMask by contract address, and check that balances add up. If anything is off, fix the code and redeploy — testnet mistakes cost nothing.

Step 6: deploy on BNB Smart Chain mainnet

Switch MetaMask to BNB Smart Chain (chain ID 56) — our MetaMask guide has the settings — and make sure the deployer holds a little real BNB. In Remix, check that the environment now shows chain 56, deploy the identical compiled contract and confirm in MetaMask. Save the transaction hash and the contract address. Look the address up in our BNB explorer: it reads name, symbol, decimals and supply directly from the contract.

Use a deployer account that has never been used on random dApps and does not hold your savings. If your contract has any admin role, transfer it to a multisig such as Safe before anyone else holds the token.

Step 7: verify the source on BscScan

Unverified tokens look suspicious, and rightly so: nobody can see what the bytecode does. On BscScan, open your contract’s page, go to the Contract tab and choose Verify and Publish. Select the compiler type (single file, or Standard JSON input for multi-file projects), the exact compiler version, the licence and the optimisation settings you used in Remix. Because the OpenZeppelin import spans several files, the easiest route is Standard JSON input or flattening the contract with Remix’s Flatten command first.

When it succeeds, the Contract tab shows a green check, the source code and Read/Write tabs. Two alternatives: Sourcify verifies contracts on BNB Smart Chain without an API key, and Remix has a contract verification plugin. Command-line verification through Etherscan API V2 needs a plan that includes BNB Smart Chain, as covered in our BscScan review. Once verified, the BscScan token page can be updated with your logo and website through its token-info form.

Glowing network nodes symbolising a newly deployed and verified BEP-20 token contract on BNB Smart Chain
↳Verified source is the first thing explorers, scanners and careful buyers look for

What creating a BEP-20 token really costs

Gas on BNB Smart Chain sits at a 0.05 gwei floor, so the on-chain part is almost free. The table uses typical gas figures for a simple OpenZeppelin token; check live prices and run your own numbers in the BSC gas fee calculator.

Typical costs of a simple BEP-20 token (November 2026, 0.05 gwei)
ItemTypical gasCost in BNBNotes
Testnet deployment≈ 1–1.5M0 (free tBNB)Repeat as often as needed
Mainnet deployment≈ 1–1.5M≈ 0.00005–0.000075Depends on code size and features
Source verification—FreeBscScan web form or Sourcify
Token transfer≈ 35,000–55,000≈ 0.0000017–0.0000028Paid by whoever sends
DEX liquidity≈ 200,000+Gas is tiny; the capital is notYou supply both sides of the pair
Audit—Varies widely by scopeOnly needed for custom logic

The honest summary: creating the token costs cents; giving it a market costs real money, and the liquidity you deposit is at risk the moment others can trade against it.

No-code BEP-20 token generators: the caveats

Many websites promise “create a BEP-20 token in one minute, no coding”. They fill in a template, deploy it from your wallet and usually charge a service fee in BNB on top of gas. Some are fine. Others are a problem in ways that only show up later:

  • Hidden powers. The template may include mint, blacklist, fee-change or “anti-bot” switches you did not ask for — exactly what makes scanners label a token risky.
  • Unverified or shared code. If the source is not verified, buyers cannot check it, and Token Sniffer-style tools may match it against known scam templates.
  • Proxies and backdoors. A generator that deploys an upgradeable proxy or keeps an admin role for itself can change your token after launch.
  • Fees and approvals. Some ask for approvals or payments beyond the deployment. Never approve spending of your other tokens to create a new one.

If you use a generator, deploy to testnet first, verify the source and run the result through the same scanners buyers use — GoPlus, honeypot.is, Token Sniffer — as described in our BSC honeypot checker guide. In most cases the OpenZeppelin Wizard plus Remix gives you the same result for free and with code you can read.

Risks and responsibilities

Security. A bug in custom token logic is permanent unless you built an upgrade path, and an upgrade path is itself a trust problem. Keep the token simple; put complex logic in separate, audited contracts. Keys. Whoever controls an admin key controls the token. Use a hardware wallet or multisig for anything that matters.

Reputation. BNB Smart Chain hosts countless scam tokens, so buyers start from suspicion. Verified code, no owner powers, locked liquidity and a public team are what separate a project from noise. Law and tax. Selling a token to others, promising profits or running a presale can bring securities, consumer-protection and tax rules into play depending on your country. Get local legal advice before you raise money. Nothing on this page is legal or financial advice.

And if what you actually want is exposure to BNB or a stablecoin rather than a token of your own, you do not need a contract at all — see our USDT BEP20 guide for moving Tether on BSC safely.

Code ready

Testnet passed? Mainnet needs real BNB.

Buy BNB on a regulated exchange and withdraw it to your deployer address on BNB Smart Chain — a few dollars covers deployment, verification and hundreds of test transfers.

Open account Partner link. Crypto assets are volatile; only invest what you can afford to lose.
  • Operating since 2013
  • FinCEN-registered MSB (USA)
  • GFSC-authorised DLT provider (Gibraltar)
  • Card, bank transfer and BNB withdrawals to your own wallet

Keep exploring

FAQ

Frequently asked questions

01

How much does it cost to create a BEP-20 token?

The deployment itself is cheap. A simple OpenZeppelin ERC-20 uses roughly 1–1.5 million gas, which at the 0.05 gwei floor is about 0.00005–0.000075 BNB. Verification on BscScan is free. The real costs come later: liquidity for a trading pair, audits for anything complex, and any fees a no-code generator charges.
02

Can I create a BEP-20 token without coding?

Yes, no-code token generators deploy a contract from a form. The catch is that you often cannot see or control exactly what they deploy: some add owner privileges, hidden fees or unverified code that security scanners flag. If you use one, insist on verified source code and read it, or use the free OpenZeppelin Wizard and deploy it yourself in Remix.
03

Is a BEP-20 token the same as an ERC-20 token?

Technically almost. BEP-20 is BNB Smart Chain’s version of ERC-20 and uses the same functions and events, so the same Solidity code compiles and deploys on both chains. The difference is the network: a BEP-20 token lives on BNB Smart Chain and pays gas in BNB.
04

How do I get my token logo on BscScan and wallets?

First verify the contract. BscScan then lets the contract owner or deployer submit token information, including the logo and website, through its token update form, which is reviewed manually. Wallets and price sites such as CoinGecko have their own listing processes and requirements.
05

Is creating a token legal?

Deploying a contract is a technical act, but selling a token to the public, promising returns or raising money with it can fall under securities, consumer-protection or tax rules in your country. If other people will buy it, get advice from a lawyer who knows crypto in your jurisdiction. This guide is not legal advice.