Sync a Filecoin node in minutes, not weeks.
Validating the Filecoin chain from genesis takes about a month. A snapshot is a pre-validated collection of chain state you import to skip straight to a recent head. Stax serves fresh mainnet snapshots every day.
Snapshot hierarchy
Three depths, one format.
Pick the lightest snapshot that covers your use case. Most operators want lightweight; explorers and indexers want full; researchers reach for archival.
Lightweight
Recent state without full history. The right choice for syncing a fresh node fast. Smaller, faster, sufficient for most operators.
- End height
- Recent head
- Messages from
- head − 2,000
- State from
- head − 2,000
- Cadence
- Daily
Full
Recent head with deeper message and state history for explorers, indexers and anything querying older state.
- End height
- Recent head
- Messages from
- deep history
- State from
- deep history
- Cadence
- On request
Archival
Sparse checkpoints at fixed epoch intervals back to early 2026, for replay and point-in-time state reconstruction.
- End height
- fixed epochs
- Spacing
- ~30,000 epochs
- Oldest
- epoch 5,700,000
- Cadence
- rolling
Naming
Stax-branded, drop-in compatible.
Snapshots follow a predictable scheme: network, production date, and chain height at the snapshot head. The format is the standard Filecoin .car.zst — only the prefix is ours.
- mainnet — the Filecoin network
- 2026-06-04 — UTC date produced
- height_6075840 — chain epoch at head
# Stax snapshot filenamestax_snapshot_<network>_<YYYY-MM-DD>_height_<epoch>.car.zststax_snapshot_<network>_<YYYY-MM-DD>_height_<epoch>.car.zst.sha256 # Today's mainnet lightweight snapshotstax_snapshot_mainnet_2026-06-04_height_6075840.car.zst # Always-latest redirecthttps://snapshots.stax-infra.com/latest/mainnet/Quick start
Download, verify, import.
Three steps from a cold box to a syncing node. The latest snapshot is always at the /latest/mainnet/ path.
Download the latest snapshot
# aria2c, parallel + resumablearia2c -x5 https://snapshots.stax-infra.com/latest/mainnet/ # or curl with resumecurl -C - -O \ https://snapshots.stax-infra.com/latest/mainnet/stax_snapshot_mainnet_2026-06-04_height_6075840.car.zstVerify the checksum
# fetch the checksum file alongside itcurl -O \ https://snapshots.stax-infra.com/latest/mainnet/stax_snapshot_mainnet_2026-06-04_height_6075840.car.zst.sha256 # verify — should print: OKsha256sum -c stax_snapshot_mainnet_2026-06-04_height_6075840.car.zst.sha256Import into Lotus
# import + start syncinglotus daemon --import-snapshot stax_snapshot_mainnet_2026-06-04_height_6075840.car.zst # import only, don't start the daemonlotus daemon --halt-after-import \ --import-snapshot stax_snapshot_mainnet_2026-06-04_height_6075840.car.zst…or into Forest
# Forest imports the same fileforest --import-snapshot stax_snapshot_mainnet_2026-06-04_height_6075840.car.zst # check sync progressforest-cli sync waitWatch the sync
After import, the node fetches headers down to your snapshot height, then validates forward to the live head.
$ lotus sync waitWorker: 0; Base: 0; Target: 6075840 (diff: 2031)State: header sync; Current Epoch: 6073809; Todo: 2031Validated 0 messages (0 per second)...# check the last synced block timedate -d @$(lotus chain getblock \$ (lotus chain head | sed 1q) | jq .Timestamp)Create your own
Already running a node? Export a lightweight snapshot in the same shape we serve.
# Lotus: lightweight, recent stateroots onlylotus chain export \ --recent-stateroots=2000 \ --skip-old-msgs \ stax_snapshot_mainnet_2026-06-04_height_6075840.car.zst # Forest equivalentforest-cli snapshot export \ --output-path stax_snapshot_mainnet_2026-06-04_height_6075840.car.zstQuestions operators ask.
Can't find it here? The team answers directly — no ticket queue.
Ask us anythingFresh snapshot, verified, today.
Daily mainnet · resumable · sha-256 verified