Exchange listing announcement assets: the kit to have ready

A listing is confirmed with days of notice and announced by someone else, on their schedule. Everything that decides how it looks has to be finished while the date is still private.

August 29, 2026 · 10 min read

The confirmation arrives in a private channel on a Monday for a Thursday. It carries a ticker, a trading pair, a time in a timezone that is not yours, and a line about the embargo. Marketing finds out roughly when everyone else in the company does, which is late.

What follows is familiar. Someone opens a template and makes an announcement graphic in an afternoon. The exchange publishes its own post first, in its own house style, and the project reply looks thinner than the thing it is replying to. The community asks whether the pair is live yet, and the only answer is a screenshot. None of that is a design failure on the day. It is the result of starting on the day.

A listing is one of the few crypto moments with a real lead time attached, even if the notice is short. The date is private for a while before it is public, and that window is the entire opportunity. This post is the kit we prepare inside it, what the exchange itself will ask you for, and the parts that genuinely cannot exist until the pair is trading.

The announcement is not yours to make

The first thing to accept is that you are not the publisher of this news. The exchange is. It has a larger audience than you do, a fixed template, a legal review, and a schedule that serves its own listing calendar rather than your content plan.

That changes what your assets are for. You are not breaking the story, you are giving your own audience a version of it that looks like you, and giving the exchange something usable in its formats so its post carries your brand correctly rather than a logo pulled off a search result.

It also changes the timing. Your announcement lands in a window that opens when theirs does, and the window is short. Anything produced after the embargo lifts arrives into a conversation that already happened.

What can be finished while the date is still private

Almost all of it. This is the part teams underuse. A listing announcement has very few variables, and the variables are small: a date, a time, a pair, sometimes a region note. Everything around those fields is knowable in advance.

Build the assets with the variable fields isolated in the file, so the final step on announcement day is typing a pair and a time into a layer that was designed to receive them. That is a two minute job. Designing the frame is not.

The sequencing logic here is the same one behind our post on token launch marketing, which lays out the wider calendar around a launch date. This kit is the narrower case: not the campaign, just the announcement, for a project whose brand already exists.

The kit, file by file

What we hand over for a listing is short on purpose. A long list produced under pressure is how a kit ends up half finished and inconsistent.

1. 01One announcement frame, in every ratio you actually post. Square, portrait and the wide crop for the timeline. Not one image resized: three compositions that each read at their own size, because the crop that works in a feed loses the ticker in a story.
2. 02A pair lockup rule. Your mark beside a venue mark, with fixed spacing, fixed sizes and a decision about which backgrounds it survives on. This is the piece teams improvise, and improvised co-branding is the most visible sign that an announcement was rushed.
3. 03A short motion cut, ten to fifteen seconds. Silent, readable muted, ending on a static card that holds the pair and the time. This is what gets reposted. A still image rarely does.
4. 04Channel banners and avatars. Every surface you control should say the same thing on the same day. A profile header from last quarter under a listing announcement reads as an unattended project.
5. 05Two or three reply frames. Neutral backgrounds with room for a line of copy, so the follow up posts in the thread look designed rather than typed.
6. 06A docs and site component. Where a first time buyer lands after the announcement, with the pair, the contract address and the venue stated plainly.
7. 07The exchange submission pack. Their requested formats, kept separate from your own files.

That is the whole kit. Anything beyond it is usually a campaign, and a campaign has a different brief and a different budget. What the kit assumes is that a visual system already exists to build from. If it does not, the listing is the wrong moment to invent one, and the fix belongs upstream in the work described in our post on web3 branding.

What the exchange will ask you for

Most venues send a requirements sheet, and it is worth reading the day it arrives rather than the night before. The requests are mundane and they are the ones that stall an announcement.

• A vector mark, and a mono version of it. Their template will place your logo on backgrounds you did not choose. If only a full colour PNG exists, someone at the exchange will make the mono version for you, badly.
• A square token icon at small sizes. It has to survive at the size of a list row. Marks with fine detail or a wordmark inside them turn into a smudge there.
• Exact naming. Project name, token name and ticker, spelled and capitalised the way you want them to persist, because that string gets copied into interfaces for years.
• A short description with a character limit. Write it yourself, in advance. A description written under time pressure by someone who is not your writer becomes the boilerplate everyone quotes.
• Co-branding rules. Some venues will send theirs and expect you to follow it. Read it before you design the lockup, not after.

Keep these files in a separate folder from your own kit. They travel to a third party, they get reused without asking you, and mixing them with working files is how an unfinished draft ends up in someone else interface.

The listing hour is a reaction window

Once the embargo lifts, the useful work is fast and small: publishing on your own channels, replying under the venue post, correcting the wrong contract address that will circulate within minutes, and cutting one or two reactive pieces from material that already exists.

Staff that hour with capacity rather than with a longer file list. Someone who can edit, someone who can answer, and a short queue of pre approved copy. Our post on crypto community content covers how that queue is stocked so the answers do not have to be invented live.

There is one gap the kit does not close: the announcement is live, the feed wants motion, and the person who makes motion is asleep in another timezone. We would rather point at something of ours than at a competitor for that case. ShipTeaser comes from the same founder as this studio: you paste a product URL and it returns a 15 second 1080p motion graphics teaser built for muted feeds, with an optional music bed, and the first video is free without a card. It has no voice-over, no avatars, no screen recording and no timeline to edit, and it will not give you a visual system or a narrative spine, so it does not replace the cut in the kit above. For putting something moving into an hour that would otherwise be static, it is a fair trade.

What only exists after the pair goes live

A few things genuinely cannot be prepared, and it is worth being honest about which.

Anything referencing price or volume is in that category, and it is also the category we advise leaving alone. A chart posted by the project reads as a promise, it ages badly within a day, and in most jurisdictions it invites a conversation with a compliance team that nobody scheduled. The kit above deliberately contains no price surface.

What does belong after the event is quieter: a short recap once the week settles, the docs and support pages updated with what people actually asked, and the evergreen explainer that new holders will find weeks later. That last one is the highest value asset of the whole sequence and the one most often skipped, because by the time it matters the team has moved on to the next date.

The failures we see most often

• Announcing before the venue does. It breaks the embargo, it can cost the relationship, and it makes your post look like a rumour.
• A logo pulled from a search result. If you did not send the files, someone will find some. Send them early.
• Scam adjacent design. Countdowns, glowing coins, forced urgency and a wallet prompt in the first frame. Listings are among the most impersonated post types in crypto, so the visual distance between your real announcement and a fake one is a security feature, not a taste preference. The same argument applied to a distribution is in our post on airdrop announcement graphics.
• No contract address anywhere. The first fake token appears fast. State the address on your own surfaces and keep it one click from the announcement.
• One image for every channel. The crop that works on a timeline loses the pair in a story, and the channel where your holders actually talk gets the leftovers.
• Treating the listing as a campaign. It is an announcement. Spend the campaign budget on the explainer that keeps working in month two.

None of these are hard to avoid with a week of notice and a system to build from. All of them are close to unavoidable when the first design decision is made after the embargo lifts. You can see the kind of system layer this kit is cut from across the projects, and how the two week build and the monthly rhythm differ on the service cards.