Blockchain snapshots
This section is for node operators who are bootstrapping or recovering NEAR infrastructure. It is not an application-data surface. If the job is reading balances, history, blocks, or contract state, use the API and RPC docs instead of snapshot workflows.
Free snapshots are deprecated
The free nearcore data snapshots were deprecated on June 1, 2025.
The NEAR Infrastructure Committee and Near One recommend Epoch Sync plus decentralized state sync. Use NEAR Nodes for the current operator guidance and recommended bootstrap posture.
Current status
- FastNear does not currently publish a working public self-serve snapshot download flow from this docs site.
- For regular RPC nodes and validators, follow NEAR Nodes and use the current Epoch Sync plus decentralized state sync guidance.
- For archival snapshot access, visit fastnear.com/snapshots or email snapshots@fastnear.com.
- The legacy scripts in fastnear/static still exist, but the old public
latest.txtdiscovery flow is no longer the supported public path here.
Useful operator references
- NEAR Nodes: Epoch Sync for the current boot-node refresh step before first start.
- NEAR Nodes: State Sync for the current non-snapshot bootstrap recommendation.
- NEAR Nodes: Run an Archival Node for archival node configuration and data-directory expectations.
- NEAR Nodes: Split Storage for NEAR Archival Nodes if you are planning hot/cold storage for modern archival setups.
What to have ready before you request archival access
- the network:
mainnetortestnet - the node role: validator, RPC node, or archival node
- whether you expect a single
~/.near/datarestore or a split hot/cold layout - the target
NEAR_HOMEpath and the storage layout you plan to use - any time sensitivity, bandwidth constraints, or recovery deadline that affects the transfer plan
Use this section when
- you are confirming the current FastNear snapshot posture for mainnet or testnet
- you need the right request path for archival snapshot access
- you are deciding whether to use snapshots or the standard NEAR node bootstrap guidance
Do not use this section when
- you are trying to query chain data for an application
- you need recent blocks, balances, history, or contract state
- you are looking for general product API guidance rather than operator setup
In those cases, use RPC Reference, FastNear API, Transactions API, or NEAR Data API.
Choose a network
Use the network pages below for the current status and escalation path. They no longer assume a public self-serve download URL.