Currently, there are 3 sources of BSC snapshot could be used, if you are unclear about their differences, you may refer Clarification of the snapshots first, to decide which snapshot suit you the most.
Usage: usage/legacyfullnode_usage.md
Currently, snapshots are provided as block history data divided by year. Each list includes world states, historical block files, URL, MD5, file size. Users can use the provided tools to quickly download.
The Pruned Snapshot is intended for internal/private nodes that do not need older block history. Use the BSC client version required in the tables below, and see Starting from a pruned snapshot for runtime history retention settings.
| Snapshot Type | Snapshot File | Total Size | Remark |
|---|---|---|---|
| Full Snapshot | mainnet-geth-pbss-20261009 | ~7.4TB | BSC >= v1.7.2 |
| Pruned Snapshot | mainnet-geth-pbss-20261009-pruneancient | ~1.9TB | BSC >= v1.7.2 |
| Snapshot Type | Snapshot File | Total Size | Remark |
|---|---|---|---|
| Full Snapshot | testnet-geth-pbss-20260917 | ~520GB | BSC >= v1.7.2 |
| Pruned Snapshot | testnet-geth-pbss-20260917-pruneancient | ~180GB | BSC >= v1.7.2 |
You can download the mainnet or testnet files separately in the list and unzip them in a same directory. Or you can use the following script:
# install aria2 on your os
yum install aria2
wget https://raw.githubusercontent.com/bnb-chain/bsc-snapshots/main/dist/fetch-snapshot.shParameters:
-ddownload,-eextract,-cverify MD5 checksum,-puse pruned snapshot-D <dir>directory to store downloaded archives-E <dir>extraction target, should be the node's--datadir(e.g./data/bsc), files will be extracted to<dir>/geth/chaindata/...--auto-deletedelete each archive immediately after extraction to save disk space-pauto-appends-pruneancientto the snapshot name, do NOT use with a name that already has the suffix
Quick start (download, verify, extract, auto-delete in one step):
# full snapshot (~7.4TB compressed; allow extra disk space for extraction)
bash fetch-snapshot.sh -d -e -c --auto-delete -D /data/snapshot -E /data/bsc mainnet-geth-pbss-20261009
# pruned snapshot (~1.9TB compressed; allow extra disk space for extraction)
bash fetch-snapshot.sh -d -e -c -p --auto-delete -D /data/snapshot -E /data/bsc mainnet-geth-pbss-20261009After extraction, files will be at /data/bsc/geth/chaindata/..., start geth with --datadir /data/bsc.
Step by step (download first, extract later):
# step 1: download & checksum
bash fetch-snapshot.sh -d -c -D /data/snapshot mainnet-geth-pbss-20261009
# step 2: extract to datadir
bash fetch-snapshot.sh -e -D /data/snapshot -E /data/bsc mainnet-geth-pbss-20261009You can remove the -c option to skip MD5 checking. Run bash fetch-snapshot.sh --help for all options.
Please keep
fetch-snapshot.shthe latest version.
To keep pruning block history and transaction/log indexes, add these flags to your existing geth startup command:
--syncmode=full \
--history.transactions=600000 \
--history.blocks=600000 \
--history.logs=600000 \
--tries-verify-mode=localThe old --pruneancient flag is deprecated and is not required to use this snapshot.
- mainnet:
- mainnet-geth-pbss-20260805, mainnet-geth-pbss-20260805-pruneancient
- mainnet-geth-pbss-20260525, mainnet-geth-pbss-20260525-pruneancient
- mainnet-geth-pbss-20260408, mainnet-geth-pbss-20260408-pruneancient
- mainnet-geth-pbss-20260306, mainnet-geth-pbss-20260306-pruneancient
- mainnet-geth-pbss-20260202, mainnet-geth-pbss-20260202-pruneancient
- mainnet-geth-pbss-20260104, mainnet-geth-pbss-20260104-pruneancient
- mainnet-geth-pbss-20251205, mainnet-geth-pbss-20251205-pruneancient
- mainnet-geth-pbss-20251114, mainnet-geth-pbss-20251114-pruneancient
- mainnet-geth-pbss-20251013, mainnet-geth-pbss-20251013-pruneancient
- mainnet-geth-pbss-20250906, mainnet-geth-pbss-20250906-pruneancient
- mainnet-geth-pbss-20250806, mainnet-geth-pbss-20250806-pruneancient
- mainnet-geth-pbss-20250715, mainnet-geth-pbss-20250715-pruneancient
- mainnet-geth-pbss-20250605, mainnet-geth-pbss-20250605-pruneancient
- mainnet-geth-pbss-20250520, mainnet-geth-pbss-20250520-pruneancient
- mainnet-geth-pbss-20250501, mainnet-geth-pbss-20250501-pruneancient
- mainnet-geth-pbss-20250404, mainnet-geth-pbss-20250404-pruneancient
- mainnet-geth-pbss-20250310, mainnet-geth-pbss-20250310-pruneancient
- testnet:
- testnet-geth-pbss-20260407, testnet-geth-pbss-20260407-pruneancient
- testnet-geth-pbss-20251013, testnet-geth-pbss-20251013-pruneancient
- testnet-geth-pbss-20250610, testnet-geth-pbss-20250610-pruneancient
- testnet-geth-pbss-20250407, testnet-geth-pbss-20250407-pruneancient
- testnet-geth-pbss-20240711.tar.lz4(md5: 64626987189d739bd1a3ee743387f8a6)
Usage: https://github.com/BNB48Club/bsc-snapshots
Special thanks to BNB48Club on contributing another dump of snapshot.
Usage: reth-bsc snapshot usage
| Type | Network | File | Size | Special Parameters |
|---|---|---|---|---|
| Archive MDBX | BSC-MainNet | 8 files - see below | 7789.76 GB | --db.max-size=12TB --db.page-size=8KB |
| Archive MDBX | BSC-TestNet | 20261102_testnet_reth_mdbx_archive_node_v2.tar.zst | 491.65 GB | - |
| Full MDBX | BSC-TestNet | 20261102_testnet_reth_mdbx_full_node_v2.tar.zst | 303.45 GB | - |
| Full MDBX | BSC-MainNet | 20261102_mainnet_reth_mdbx_full_node_v2.tar.zst | 3621.42 GB | - |
| FastNode MDBX | BSC-MainNet | 20261104_mainnet_reth_mdbx_fast_node_v2.tar.zst | 840.42 GB | --minimal(required) --engine.skip-state-root-validation(required) |
NOTICE: FastNode snapshots (minimal mode) retain the current state required for transaction execution and recent block headers, while pruning older block history and blob sidecars to reduce snapshot size. State-root validation is skipped. Suitable for workloads that do not require full historical data or state proofs. If you use --minimal flag, you should remove --full flag.
All 8 files are required. The six static_files segments extract into the same static_files directory.
| Content | File | Size |
|---|---|---|
| static_files / headers | 20261102_mainnet_reth_mdbx_static_files_headers_archive_node_v2.tar.zst | 67.77 GB |
| static_files / transactions | 20261102_mainnet_reth_mdbx_static_files_transactions_archive_node_v2.tar.zst | 2363.10 GB |
| static_files / transaction-senders | 20261102_mainnet_reth_mdbx_static_files_transaction-senders_archive_node_v2.tar.zst | 132.08 GB |
| static_files / receipts | 20261102_mainnet_reth_mdbx_static_files_receipts_archive_node_v2.tar.zst | 1601.95 GB |
| static_files / account-change-sets | 20261102_mainnet_reth_mdbx_static_files_account-change-sets_archive_node_v2.tar.zst | 334.47 GB |
| static_files / storage-change-sets | 20261102_mainnet_reth_mdbx_static_files_storage-change-sets_archive_node_v2.tar.zst | 1760.65 GB |
| db | 20261102_mainnet_reth_mdbx_db_archive_node_v2.tar.zst | 556.27 GB |
| rocksdb | 20261102_mainnet_reth_mdbx_rocksdb_archive_node_v2.tar.zst | 973.47 GB |
| Total | 7789.76 GB |
As the node snapshot of bsc becomes larger and larger, backup, upload and download will become increasingly unmaintainable, and it will occupy more disk space and take up more upload and download time.
At the same time, in order to support the history expiry and state expiry of bsc later, it is planned to split the node snapshot according to historical data and active data, and the following advantages can be obtained:
- When updating the snapshot, only the changed part can be updated to reduce the difficulty of operation and maintenance;
- Support annual backup of historical data, which also helps with the subsequent historical data pruning;
- Support archiving multiple snapshot versions, avoiding wasting disk space;
- Support downloading and decompressing a single part immediately, and snapshot download and decompression can be completed on a smaller disk;