Guides · Nov 17, 2026
Hackathon Demo Video Tips: A 3-Minute Video Judges Finish
For many hackathons, your demo video is the submission. Judges with a long list of projects may watch your video, skim your description and move on. If the video is clear, your project gets a fair hearing. If it starts with a minute of slides, it may not get one at all.
The good news: a strong hackathon video is not about production budget. It is about structure, clarity and avoiding a handful of common mistakes. Here is how to make one judges watch to the end.
Check the rules first
Before you plan anything, open the official rules and find the video requirements. Look for:
- Maximum length. Many hackathons set one, and some say judges may stop watching at the limit. Treat it as a hard ceiling.
- Where to host it. Rules often name YouTube, Vimeo or a similar platform.
- What must be shown. Some events require the project running on a specific device or platform, or the required tools visibly in use.
- Language and captions. Some events require English or ask for subtitles.
- Third-party material. Rules commonly ban copyrighted music or content you don’t have rights to.
If there is no stated limit, about two to three minutes is a common, safe target.
A structure that works
Here is a simple outline for a three-minute video. Shorten each part for a two-minute limit.
- 0:00–0:15, the problem. One or two sentences: who has the problem and why it hurts. No logo animation, no title slides.
- 0:15–1:45, the demo. Show the product doing the job, live, from the user’s point of view. Follow one realistic path from start to finish. Narrate what the user is doing and why it matters, not which button you are clicking.
- 1:45–2:30, how it works. A quick look at the architecture or the clever part, and a clear mention of the sponsor’s tools if they are required. One diagram is plenty.
- 2:30–3:00, why it matters. What makes it different, who could use it next, and one line on what you would build after the hackathon.
The single most important rule: get the working product on screen within the first 20 seconds or so. A judge who sees it working early relaxes and pays attention to the rest.
Write a script, then cut it
Unscripted demos ramble. Write the narration out word for word, read it aloud with a timer, then cut it by a quarter. Speaking pace is slower than you think, and pauses while the screen changes take time.
Good narration is specific. Compare “our platform leverages AI to optimize workflows” with “paste in a messy receipt photo, and it fills in the vendor, date and total for you”. The second one can be pictured instantly.
Use real-looking data. A demo full of “test test 123” makes the product feel unfinished. Realistic names, numbers and content make it feel ready.
Recording setup
- Screen: Record at a common resolution such as 1920×1080. Close notifications, extra tabs and anything personal. Increase your browser zoom so text is readable on a small window.
- Audio: Sound quality matters more than picture quality. Any headset or USB microphone in a quiet room with soft furnishings beats a laptop mic in an echoing kitchen.
- Software: Any screen recorder that captures your screen and microphone will do. Many operating systems include one.
- Takes: Record the demo in sections, not one long take. It is much easier to redo a 30-second clip than a three-minute one.
- Mobile apps: Record the device screen directly or use a simulator, and say which you are using if the rules care.
Editing for clarity
- Cut the waiting. Trim loading spinners and typing. If something takes time in real life, a quick cut with a note such as “about 20 seconds later” is honest and keeps the pace.
- Zoom where it matters. A short zoom on the important part of the screen helps judges watching on a laptop.
- Add captions. They help judges watching without sound, non-native speakers and anyone in a noisy room. Many platforms can auto-generate them; check and correct them.
- Keep music quiet or skip it. If you add music, use only tracks you have rights to, and keep it well under your voice.
Don’t fake it. If a feature is mocked up rather than working, say so. Judges and organizers take honesty seriously, and many rules require the project to function as shown.
Upload mistakes that cost entries
These are painful because they have nothing to do with the quality of your work:
- Private video. Judges can’t see a private video. Use public or unlisted, as the rules allow. YouTube explains the difference in its privacy settings help.
- Still processing. A large upload can take a while to process at full quality. Upload early.
- Blocked music. Copyrighted audio can get a video muted or blocked.
- Wrong link. Paste the link into a private browser window where you are not signed in, and watch the first few seconds.
- Over the limit. If the rules say three minutes, 3:20 is a risk you don’t need.
Put a reminder in your calendar a day before the deadline to do this check. Every hackathon on our site has an Add to calendar button for exactly this reason.
A quick checklist before you submit
- Within the length limit, with a few seconds to spare.
- Working product visible in the first 20 seconds or so.
- Problem, demo, how it works, why it matters, in that order.
- Required tools clearly shown and named.
- Clear audio, readable text, captions checked.
- Public or unlisted, link tested while signed out.
- Only music and content you have rights to.
Then put the same link on your project page, your repository README and the entry wall, so everyone who finds your project sees the same clear story. For the rest of the submission, see how to win a hackathon and how hackathons are judged. Looking for the next one to enter? Start with online hackathons open now.
FAQ
How long should a hackathon demo video be?
Follow the official rules first, since many hackathons set a maximum length and may stop watching or penalize videos that run over. If no limit is given, about two to three minutes is a common and sensible target.
What should a hackathon demo video include?
Open with the problem and who has it, show the working product solving it as early as possible, briefly explain how it works and which required tools it uses, and close with what makes it different. Keep the product on screen for most of the video.
Do I need to show my face in a hackathon video?
Usually not. Most rules ask for a demo of the project, and a screen recording with clear narration is enough. Showing yourself briefly can add a personal touch, but the product should take most of the time.
Where should I upload my hackathon video?
Use the platform the rules name, often YouTube, Vimeo or a similar site. Make sure the video is public or unlisted, not private, then test the link in a private browser window where you are not signed in.
Can I use music in my hackathon video?
Only music you have the rights to use. Copyrighted tracks can get a video blocked or muted on upload, which can break your submission. Royalty-free music or no music at all is safer.