> For the complete documentation index, see [llms.txt](https://docs.pharos.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pharos.xyz/node-and-validator-guide/pharos-network-snapshots.md).

# Pharos Network Snapshots

Welcome to the official snapshot page for Pharos Network. Here you can find regularly updated data snapshots for each network environment — Atlantic Testnet and Mainnet — to help you quickly synchronize and bootstrap your nodes without performing a full sync from genesis.

Snapshots include the latest database state and can be used for fast setup, disaster recovery, or performance testing.

### 💡 Notes & Best Practices

* Snapshots do not contain full block history, only the latest validated state.
* Archival nodes should still sync from genesis.
* After applying a snapshot, the node will continue syncing from the latest height.
* Always ensure your snapshot corresponds to the correct network and version.

> ⚠️ Always verify the snapshot source and integrity before applying it to your node.\\

See [Rapid Node Initialization](/node-and-validator-guide/rapid-node-initialization.md) for detailed instructions.

***

### Atlantic Node Snapshot

| Latest Snapshot | atlantic-snapshot-2026-11-02-04.tar.gz                                                                                         |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| Type            | **FullHistory**                                                                                                                |
| Last Updated    | [atlantic-snapshot-2026-11-02-04.tar.gz](https://snapshot.dplabs-internal.com/atlantic/atlantic-snapshot-2026-11-02-04.tar.gz) |
| Format          | Compressed TAR archive                                                                                                         |
| Notes           | Only includes the ***public*** database                                                                                        |
| sha256 checksum | `59316d832ec96a68622d730776fbcbdf0cba8f562c17d9908f2bcbe1cda32f23`                                                             |

***

### Mainnet Node Snapshot

| Latest Snapshot | mainnet-snapshot-2026-11-01-03.tar.gz                                                                                       |
| --------------- | --------------------------------------------------------------------------------------------------------------------------- |
| Type            | **Archival**                                                                                                                |
| Last Updated    | [mainnet-snapshot-2026-11-01-03.tar.gz](https://snapshot.dplabs-internal.com/mainnet/mainnet-snapshot-2026-11-01-03.tar.gz) |
| Format          | Compressed TAR archive                                                                                                      |
| Notes           | Only includes the ***public*** database                                                                                     |
| sha256 checksum | `a8dc0a0888730285a7afcd2865b18e28dd73b098194ea682237034f50542b5a1`                                                          |

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pharos.xyz/node-and-validator-guide/pharos-network-snapshots.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.