> For the complete documentation index, see [llms.txt](https://d3fenders.gitbook.io/d3fenders/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://d3fenders.gitbook.io/d3fenders/11.-snapshot-tool.md).

# 11. Snapshot Tool

### Introduction

The **D3fenders Snapshot Tool** helps NFT founders and project teams clearly understand who holds their NFTs - and what those holders are doing with them -at the exact moment decisions need to be made.

Whether you are preparing an **airdrop**, building a **reward system**, creating an **allowlist**, or protecting your community from abuse, accurate holder data is essential. The Snapshot Tool provides a fast, reliable way to generate that data across multiple blockchains without requiring custom scripts or deep technical knowledge.

At a glance, teams can see:

* Who currently holds NFTs
* How many tokens each wallet owns
* Which NFTs are actively listed on marketplaces
* How ownership is distributed across the collection

***

### Why Accurate Snapshots Matter

In Web3, many issues around airdrops and rewards don’t come from bad intent — they come from incomplete or misleading data.

Without a reliable snapshot, teams risk:

* Rewarding wallets that are actively flipping NFTs
* Missing loyal holders due to indexing gaps
* Over-distributing tokens or rewards
* Creating confusion or distrust within the community

The D3fenders Snapshot Tool removes this uncertainty by combining **on-chain ownership data** with **real-time marketplace listing awareness**, giving teams a clearer and more actionable view of their community.

***

### Built for Real-World Conditions

Most snapshot tools assume ideal infrastructure: perfect indexers, single-chain collections, and marketplace-only visibility.

D3fenders Snapshot was built for real environments:

* Multi-chain collections
* Collections identified by contracts or update authorities
* Marketplaces with delayed or partial data
* Founders who need clarity, not black-box automation

Manual verification and explicit workflows are supported by design, not treated as failures.

***

### Designed for Founders and Community Teams

While the Snapshot Tool is production-grade under the hood, its purpose is simple:\
**give non-technical teams the same clarity developers rely on.**

You shouldn’t need to write scripts, manage APIs, or stitch together CSV files just to understand your holders. The Snapshot Tool is built to be:

* Easy to use
* Repeatable
* Transparent
* Export-friendly


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://d3fenders.gitbook.io/d3fenders/11.-snapshot-tool.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
