Airdrop announcement graphics: announcing a distribution without looking like a scam

The visual language of an airdrop post was taken over by impersonators years ago. Announcing a real distribution now means designing against that resemblance, on purpose.

August 30, 2026 · 10 min read

A team finishes the eligibility logic, agrees a claim window, and then makes the announcement graphic in an afternoon. It comes out looking the way airdrop posts have always looked: a coin with a glow behind it, a countdown, a gradient nobody uses anywhere else in the product, and the words claim now in a heavy typeface.

Within the hour, four other accounts publish something almost identical, with a different link. Some of them have more followers than the project does. The holders who have been around a while do the sensible thing and assume all five are fake, including the real one. The support channel fills with the same question for two days: is this actually you?

That is the specific problem this post is about. An airdrop is one of the few announcements where the design brief includes a threat model. The assets have to communicate a distribution, and they also have to be hard to counterfeit and easy to tell apart from the counterfeits that will exist by lunchtime.

The look everyone copies is the scam look

Impersonators do not invent a visual language. They copy the one that already converts, which means the generic airdrop aesthetic belongs to them now by sheer volume. Every convention in it, the glow, the coins, the countdown, the urgency, has been used against holders more often than it has been used honestly.

So a real project that reaches for those conventions is competing on the exact ground where it has no advantage. A fake account can produce that frame faster, publish it more often, and pay to put it in front of more people. The only ground where the real project wins is the ground the fake cannot occupy: your actual brand system, used consistently for months before this post existed.

This is the practical argument for spending on a visual system before there is a distribution to announce. A project with a distinct type treatment, a fixed palette and a motion grammar has something to be recognised by. A project whose assets are assembled per event has nothing to compare a fake against, which is the position described in our post on web3 branding.

What one frame has to answer

The announcement frame is read in about two seconds by someone who wants to know whether it concerns them. It has to answer that question and it has to survive being screenshotted out of context, because it will be.

• Who is eligible, in plain terms. A snapshot date, or an activity, or a role. Not a formula. The detail belongs in the docs the frame points to.
• When the window opens and closes. Real dates with a timezone written out. A relative countdown is the single most impersonated element in the category, and it stops being true the moment the image is reposted.
• Where the claim happens. One surface you control, named the same way every time. Never a link that only exists in a graphic.
• What it costs. If there is a gas cost, say so. Free is the word every fake uses, so specificity reads as real.
• What it is not. No wallet connection required to check eligibility, no purchase, no direct message from the team. Stating the negatives makes the fakes easier to spot.

Everything else is decoration and most of it is working against you. A frame that answers those five things in your own type and colour is a better announcement than a rendered coin, and it takes less time to build.

The kit, file by file

A distribution runs over days, not one post, and the assets follow the same phases the eligibility does. What we prepare is short and each piece has a job.

1. 01The eligibility frame, in every ratio you post in. Square, portrait and the wide crop, each composed at its own size rather than resized from one master, so the dates never fall outside a story crop.
2. 02A checker card. The asset that sends people to the one surface where they find out if they qualify. This one gets reposted most and forged most, so it carries the strongest brand signal you have.
3. 03A short silent motion cut, ten to fifteen seconds. Readable muted, ending on a static card that holds the window and the official domain. Motion is harder to counterfeit convincingly than a still, which is a security argument as much as a reach argument.
4. 04Window open and window closing frames. Two variants of the same layout, designed together, so the reminder posts do not look like a different project made them.
5. 05Channel banners and avatars for the period. Every surface you control saying the same thing on the same day, which is also how a visitor tells your account from a copy of it.
6. 06Reply frames. Two or three neutral backgrounds with room for a line of copy, for answering in threads without typing into the void.
7. 07A docs and site component. Eligibility, dates, the claim surface and the contract address, stated plainly on a page you own and can update.

The sequencing is close to what we described for exchange listing announcement assets, with one difference that matters. A listing date is usually private before it is public, so the kit is built under embargo. An airdrop date is normally yours to set, which means there is no excuse for the assets to be late, and the whole kit should exist before the first teaser goes out.

Real announcement, fake announcement

The table below is the working checklist we run a distribution kit against. The left column is not a style preference, it is the set of choices a forger has trouble reproducing quickly.

Read down the right column and notice how much of it is standard practice in crypto marketing. That is the trap. Several of those habits were normal before they were adopted by people impersonating projects, and they have not been normal for a while.

The claim window is an operation, not a post

Once the window opens, the work changes shape. It stops being production and becomes response: confirming the real link under a fake reply, correcting an address that is circulating, publishing a reminder that fits the day rather than the plan, answering the same eligibility question in a form people can screenshot.

Staff that period with capacity and a queue of pre approved copy rather than with a longer file list. Our post on crypto community content covers how that queue is stocked so nothing has to be invented while a thread is moving.

One gap the kit does not close: the window is open, a moment worth posting appears, and the person who makes motion is offline in another timezone. For that narrow case we would rather point at something of ours than at a competitor. ShipTeaser is built by the same founder as this studio: it takes a product URL and returns a 15 second 1080p motion graphics teaser designed for muted feeds, with an optional music bed and the first video free without a card. It has no voice-over, no avatars, no timeline and no stock footage, and it inherits none of the brand distinctness this whole post argues for, so it belongs nowhere near the eligibility or claim frames. As a way to put something moving into an hour that would otherwise pass in text, it is a fair trade.

When the window closes

Two assets are worth making after the distribution, and both are usually skipped because the team has already moved on.

The first is a plain close notice. A window that ends without an announcement leaves the old graphics circulating as live offers, and every fake claim page that survives the event feeds on that ambiguity. Publishing the end of the window is part of protecting the people who missed it.

The second is the explainer that outlives the event: what the token is for, what holders can now do, why the distribution was shaped the way it was. Recipients arrive weeks later with none of the context that was obvious in the thread. That asset keeps working long after the announcement frames stop, and it is the one place where the campaign budget compounds. The wider calendar this sits inside is laid out in our post on token launch marketing.

The failures we see most often

• Announcing before the checker exists. The gap between the post and the working page is exactly the window a fake page fills.
• A different look for every phase. Teaser, eligibility, reminder and close made by different hands over three weeks reads as three projects, and it teaches holders that your announcements do not have a consistent look to verify against.
• Countdowns in the artwork. They expire, they get reposted anyway, and they are the most reliable marker of a fake.
• Putting the claim flow in the image. Any asset that asks for a wallet action directly is training your audience to do the thing you spend the rest of the year telling them not to do.
• No contract address on a surface you own. Fakes appear fast. The correction has to be one click from every asset.
• Treating the distribution as the campaign. It is a moment inside one. The explainer afterwards is what new holders actually read.

None of this is difficult with a system to build from and a week of preparation. Nearly all of it is unavoidable when the first design decision happens the morning of the announcement. You can see the kind of system layer these kits are cut from across the projects, and how the two week build differs from the monthly rhythm on the service cards.