ERC-721 Holder Snapshot
Arc NFT Snapshot
Export the current holder addresses of an Arc ERC-721 collection to CSV. Addresses only, and you connect a wallet to pay the flat USDC fee.
Taking the Snapshot costs 62.5 USDC flat, whatever the size of the collection, plus the network gas the transaction spends.
Both parts are dollar figures, because USDC is what Arc charges for gas as well as what the fee is quoted in.
The export contains addresses only. There are no token IDs, no ownership counts and no contract labels.
How to snapshot NFT holders on Arc
- Connect a wallet to Arc
- Paste the ERC-721 collection address
- Click Take Snapshot and pay the flat fee
- Wait for the read to complete
- Download the addresses-only CSV
Benefits of NFT Snapshot
Addresses only
one row for each current holder returned by the snapshot
Connect a wallet
required to run and pay for the read
Any ERC-721 collection on Arc
ownership data is public
Flat fee in USDC
the same number before and after payment
Point-in-time result
the list reflects the block read by the tool
If you need more help contact our team
Got questions?
If you need more help contact our team
One current holder address per row. The CSV contains addresses only; it does not include token IDs or the number of NFTs held by each address.
Yes. You connect a wallet to Arc to pay the snapshot fee before the export runs.
62.5 USDC, flat, whether the collection has a hundred pieces or ten thousand.
Yes, after reviewing the file. Because the export contains addresses only, it supports an equal-per-wallet recipient list; there is no ownership-count column for weighting rewards.
What an Arc NFT holders snapshot is usually for
Most collection snapshots are taken with the next thing in mind rather than the last one. An allowlist for a second drop, a role or a gated channel that only holders should reach, a reward before a reveal, or a migration that has to pay the owners of a v1 collection when a v2 replaces it. In each case the question is the same, which is who owns a piece right now, and the answer stops being true the moment somebody sells.
That last part bites harder with NFTs than with tokens, because a collection turns over on marketplaces in bursts rather than steadily. A snapshot taken while a listing spree is running can differ from one taken an hour later by a noticeable share of the holders, so it is worth deciding the cut-off first and reading the chain after it.
One row per wallet, not per piece
The list is deduplicated by owner. A wallet holding forty pieces appears once, exactly like a wallet holding one, and there is no column saying which of the two it is.
For an allowlist that is the shape you want, since one entry per person is the point and a whale should not occupy forty places. For anything weighted by how much of a collection somebody owns it is a limit worth knowing before you plan the reward, and the same is true of token IDs, which the file does not carry either.
Contracts hold NFTs too
A holder is whatever address the contract says owns a piece, and that is not always a person. Where a marketplace escrows a listing, the escrow contract is the owner for as long as the listing stands, and it lands in the export like any other row. Vaults, staking contracts and lending pools do the same.
Since the file carries no labels, those rows look identical to everything else in it. Read the list before you pay from it, because sending a reward to an escrow contract is not a transaction anyone can undo.
What the Arc NFT snapshot exports
What comes back is a plain file, one line per owner, built to be pasted into whatever you are running next rather than admired on screen. There is no token ID beside a row, no count of how many pieces sit behind it and no label saying what kind of address it is, so the file answers who and nothing else.
Watch how it works