Sync Options
A new node has to acquire the chain's state before it can validate. Syncing from genesis block by block is slow; in practice operators use a snapshot or state sync, and choose a pruning setting that matches what the node is for. This page covers the options and how to choose; for the install itself see Install osmosisd.
Snapshot contents and state-sync RPC servers change frequently. The snapshot providers below are current; always take the latest snapshot height from the provider's page, and confirm state-sync RPC servers before relying on them.
The options
| Option | What it does | Good for |
|---|---|---|
| Snapshot restore | Download a recent compressed copy of the chain data and extract it | Fastest way to a working node; the common choice |
| State sync | Fetch a recent state snapshot from RPC peers and verify it against trusted block hashes | Minimal data transfer, no third-party archive needed |
| Genesis sync | Replay every block from genesis | Building an archive node, or when you need full history |
The get.osmosis.zone installer can set up a node from a snapshot; see Install osmosisd.
Pruning vs archive
app.toml controls how much historical state the node keeps (pruning). This is the single biggest determinant of disk usage:
- Default / pruned: keeps only recent state. Smallest disk footprint. Correct for a validator and most RPC nodes.
- Archive (
pruning = "nothing"): keeps all historical state. Required for serving historical queries or taking a state export at an old height (for example, an airdrop snapshot). Large and growing disk footprint.
Choose pruned unless you specifically need history. Switching a node from pruned to archive later means re-syncing.
Choosing for your use case
- Validator: snapshot restore + default pruning. You want to be synced and current, not serving history.
- Public RPC / indexer: snapshot restore, pruning sized to the queries you serve.
- Archive (historical queries, old-height exports): genesis sync or an archive snapshot,
pruning = "nothing".
Snapshot providers
- snapshots.osmosis.zone — the official Osmosis snapshots.
- Polkachu — community-maintained snapshots with restore instructions.
Each provider's page lists the current snapshot height, download URL, and the extract command for the latest data. Match the snapshot's pruning profile to your node's role (a pruned snapshot for a validator, an archive snapshot only if you need full history).
Reference
- Hardware specs and installation: Install osmosisd.
- Running a node: Running a Node on Mainnet / Testnet.