Database Sizes


Full Node
Retains last 256 blocks
Size - 171.99 GiB
Last Updated - 11/14/2022 11:30:05 PM Block Height - 15,225,799
Size - 123.09 GiB
Last Updated - 11/29/2022 5:00:22 AM Block Height - 13,129,255
Pruned Node
Retains last 1,000 blocks
Size - 170.79 GiB
Last Updated - 11/29/2022 5:00:08 AM Block Height - 15,528,431
Size - 121.59 GiB
Last Updated - 11/28/2022 4:15:20 PM Block Height - 13,124,988
Archive Node
Retains all blocks
Size - 945.05 GiB
Last Updated - 11/16/2022 8:30:10 AM Block Height - 15,185,550
Size - 563.36 GiB
Last Updated - 11/16/2022 8:30:26 AM Block Height - 12,833,368
The data used to populate this table is freely available via and should be updated hourly at the 15 min mark, date format = UTC.

Full Node - A full node is a pruned node that retains the last 256 blocks. It can be initiated, in default, by starting a node and not specifying the --validator or any pruning flags.

You may use the following flags to initate a full node manually: --pruning=256 --unsafe-pruning

Pruned Node - A pruned node is one that retains only the last x blocks i.e. the database is pruned (trimmed). It can be used as a measure to reduce the storage footprint of a node's database, which is the usually the largest store of information for a node. Pruned databases can be used for validator nodes, the most popular configuration of which is to retain the last 1000 blocks.

A pruned database still requires a full download and processing of all blocks in the chain. To circumvent this you may use a database snapshot to restore or load a pruned database. The pruned settings of the snapshot must match those used in your config. While there's no reason to suspect mischievious behavior of current providers; one should approach use of snapshots with caution and on the basis of need.

You may use the following flags to initate a pruned node that retains the last 1000 blocks: --pruning=1000 --unsafe-pruning

Archive Node - An archive node retains all block history for the chain. This can be used by validators if storage requirements permit. It is best suited for those who desire to retain a copy of the chain for the purpose of redundancy and redistribution. An archive node may also be used for development purposes to fulfil historical queries.

You may use the following flags to initate an archive node manually: --pruning=archive

Methodology - Presented are the uncompressed size of the /home/{user}/.local/share/polkadot/chains/{chain}/db folder and all subcontents using the du -sh command. The output was then converted to JSON using code available here. This does not reflect the final size of a complete Polkadot installation, it only represents the size of the database. Please note and scale your estimates.

  • Growth charts coming SoonTM
  • For any suggestions, feel free to submit a PR for these relevant source files 1, 2