Crypto conference booth content: built for a loud room

A booth is not a landing page on a stand. It is three seconds of peripheral vision in a room with two hundred competing screens, and almost nobody designs for that.

August 27, 2026 · 9 min read

The booth gets booked in January and designed the week before the event. Someone exports the pitch deck to a video, someone else orders a backdrop with the tagline on it, and the whole thing is signed off on a laptop screen in a quiet office by four people who already know what the product does.

Then it goes into a hall. Two hundred stands, a DJ somewhere, the sound off on every screen, and a person walking past at normal speed with a coffee in one hand. That person gives the booth about three seconds of peripheral attention, from six metres away, at an angle. Nothing that was approved on the laptop survives that.

The teams that do well at conferences are not the ones with the biggest stand. They are the ones who accepted the actual viewing conditions early and built for them, which turns out to be a small amount of work done in the right order.

The room is the brief, not the stand

Every design decision at a booth is settled by the physical conditions, and those conditions are known months in advance. The screen will be at head height or above. The sound will be off, or drowned. The light will be flat and bright, so contrast collapses. Your neighbours will be running motion too, competing for the same peripheral vision.

That gives you a spec before anyone opens a design file. Type has to be readable at six metres, which in practice means very few words, very large. Motion has to work without audio and without a beginning, because people arrive mid loop. Colour has to hold against washed out hall lighting, not against the black background of a presentation.

All of that assumes a hall you do not control. An evening in your own venue is the opposite situation, with a dark room, a fixed audience and a surface you can design against, which is why projection mapping for a launch event follows completely different rules from a stand.

The five assets a booth actually needs

Booth content sprawls because nobody wrote the list. Someone asks for a video, someone asks for a banner, someone prints stickers, and there is no shared idea of what each piece is for. Five pieces cover it, and each one has a different job.

Notice what is not on the list: a long product film, a demo video with a voice-over, a slide deck on loop. Those are follow up material. They belong in the email that goes out afterwards, where someone is sitting down, alone, with sound, and has chosen to watch.

How to build the loop

The loop is the piece that carries the booth, and it is the one most often taken from somewhere else. A launch film cut down, a product demo with the pace unchanged, a montage of screenshots. All three fail the same way: they assume a viewer who started at the beginning.

1. 01Assume every second is the first second. Someone can walk up at any frame. There is no cold open, no build. The mark, the category line and the visual signature should be legible within any three second window.
2. 02Cut the word count by three quarters. Whatever the script says, a booth loop holds about one short line per beat. Read it aloud while walking past a screen: if you cannot finish the line in the time it takes to pass, it is too long.
3. 03Design for a bright room. Test on a screen at full brightness in daylight, not in a dark suite. Thin type, low contrast pairings and soft gradients all disappear under hall lighting.
4. 04Loop without a seam. The last frame should hand over to the first without a cut that reads as an ending, otherwise the loop looks like a video that keeps restarting.
5. 05Make one vertical cut at the same time. The same build, reframed, is your story content for the three days. Ask for it in the brief and it costs almost nothing extra. Ask for it after the event and it is a new job.

There is a fast lane worth naming honestly, because the tool is ours: ShipTeaser, built by the same founder as this studio, turns a product URL into a 15 second 1080p motion graphics teaser aimed at muted feeds, with an optional music bed and the first one free without a card. Muted is exactly the booth condition, so as a stopgap on the day before a smaller event it can hold a screen. It has no voice-over and no timeline to edit, and it will not carry a visual system you are trying to establish in a hall full of competitors, which is the whole point of a flagship booth.

The one line on the backdrop

Most crypto backdrops carry a phrase that could belong to forty other projects at the same event. The infrastructure layer for something. Building the future of something else. It reads as filler because it is filler, and it forces every passerby to walk closer to find out what you do, which is exactly the step they are not going to take.

The rule we use is blunt: the line must be false if pasted onto a competitor stand. If a rival could put your headline on their backdrop without lying, it is not a headline, it is decoration. Name the category, name who it is for, and let the loop and the staff carry the rest.

The same discipline applies to the scannable action. One code, at eye height, with a line under it saying what happens after the scan. Not the app store, not a link tree, not four codes for four things. This is the same reduction we describe for launch pages in our post on teaser video for app launch: one message, one action, everything else removed.

Order the work in the right sequence

The failure mode at conferences is not bad design, it is late design. Print deadlines and shipping dates are fixed by suppliers, so anything that has to be physical is decided first, which means the visual decisions underneath it were made under time pressure or not at all.

• Four weeks out, settle the headline and the visual direction, because the backdrop is a print job with a real deadline.
• Three weeks out, lock the loop concept and the copy on every physical piece, then send everything printed to production.
• Two weeks out, build the loop and the vertical cut from the same project, and export the team assets.
• One week out, test on a real screen at full brightness, from six metres, and fix what fails.
• On site, shoot deliberately: the stand full, the talks, faces. That footage is the recap, and nobody remembers to get it.

That last point is worth more than most of the booth budget. Three days of footage shot on purpose gives you weeks of content afterwards, and the difference between usable and unusable is decided by whoever is holding the phone on day one. Give someone that job in writing before the event starts.

What happens after the doors close

A booth is a spike of attention, and the spike is worth very little if nothing is ready to catch it. The follow up email goes out while people still remember the room, which means it has to be written and designed before the event, not composed on the flight home when the momentum has already gone.

Prepare the follow up as part of the booth build: the longer film that was too slow for the hall, one page that answers the questions your staff got asked most, and a short recap cut from the footage. It is the same visual system, so it is assembly rather than a new production, and it lands in the week where a reply is still likely. What to shoot and how to assemble it is its own exercise, set out in our post on the conference recap video.

This is also where a conference stops being a one off cost and starts feeding the ongoing rhythm, the same way a launch feeds the weeks after it. We cover that cadence in our post on crypto community content, and you can see how the visual systems behind this kind of work hold up across the work.