How to Run an Airdrop Eligibility Checker (Free CSV Snapshot Guide)

If your project is running a token claim or airdrop against an existing snapshot, the way you let people check their status matters. A public spreadsheet or a flood of "am I eligible?" messages doesn't scale — and it gives every visitor the same unverified list to screenshot and share, eligible or not.

What is an airdrop eligibility checker?

It's a way for respondents to find out, instantly and privately, whether their specific wallet qualifies for a claim — checked against a snapshot you control, not a list they have to trust on their own. Instead of messaging your team or scrolling a shared sheet, they connect their wallet and get a definitive answer.

Why a public spreadsheet doesn't work

Posting a Google Sheet or CSV publicly has three real problems. First, it leaks — anyone can copy, scrape, or screenshot the full list, including addresses that were never meant to be public. Second, it doesn't verify anything — reading your own address in a spreadsheet row proves nothing about who's actually connecting to claim it. Third, it doesn't scale — every ambiguous case turns into a DM or support ticket asking your team to manually confirm a row.

The fix: a private snapshot + wallet-verified check

Formz's Airdrop Checker block keeps your snapshot private and ties every check to a real connected wallet. You upload the CSV once; respondents connect their wallet and get an immediate Eligible or Not eligible result, with your custom claim instructions shown automatically if they qualify.

Respondents connect their wallet and see their status instantly.

Building your eligibility checker in Formz

1. Start from a new form and add an Airdrop Checker block — see Getting started if this is your first form.
2. Upload your snapshot CSV of eligible addresses. It's parsed and normalized automatically, and the block shows how many addresses were loaded.
3. Add your claim instructions — what an eligible respondent should do next (claim link, deadline, contract address). This is shown automatically the moment someone checks in as eligible.
4. If a respondent already connected a wallet earlier in the form — for example, from a gate or a separate Wallet Connect field — the checker reuses that connection automatically instead of asking again.
5. Hit Go Live and share the link. Every check is logged to your responses dashboard — address, eligible/not eligible, and timestamp — exportable to CSV.

Optional: pair it with an allowlist or wallet gate

Checking eligibility for an existing snapshot and collecting a new allowlist are two different jobs — see how to create an NFT allowlist form if you're building the pre-launch side instead. You can also gate the entire form behind existing NFT or token ownership before respondents ever see the checker — see NFT & token gating.

Combine the checker with a gate so only qualifying wallets see the form at all.

Questions