Most event swag ends up in a drawer. Good hackathon apparel does the opposite – it becomes the T-shirt people wear to the next meetup, and the hoodie they code in all winter. Here is how to design swag participants actually keep.
Start with the design, not the sponsor list
The front of the T-shirt should be about the event – a strong graphic, the event name and year. Put sponsor logos together in one tidy block on the back. A front crowded with logos looks like a uniform and rarely gets worn again.
Ideas that work for tech crowds
- A code snippet, terminal prompt or inside joke from your community.
- Minimal line art of your city or campus with the event year.
- Dark colours – black, navy, charcoal – are the safest favourites.
- A small sleeve print with the edition number ("v5.0").
Use colour to show roles
Give organisers, mentors, volunteers and judges different T-shirt colours with the same design. Participants find help faster, and photos look organised.
Hoodies for overnight events and winners
Overnight hackathons get cold under office AC. A hoodie for every participant is a big upgrade; if budget is tight, keep hoodies for winners, mentors and the core team.
Sizing and timelines
Collect sizes in the registration form and order a small buffer of M and L for walk-ins. Printed T-shirts take about 10–15 working days after artwork approval; hoodies 15–20 working days. Lock artwork 3–4 weeks before the event.
See our hackathon & tech event apparel and event & volunteer T-shirts pages.
Frequently Asked Questions
Where should sponsor logos go on a hackathon T-shirt?
Group them in one block on the back, keeping the front for the event design.
How many extra T-shirts should we order?
A small buffer of common sizes (M and L) covers walk-ins and size swaps.
Can roles get different colours?
Yes, the same design can be produced in multiple colours.