Presentation is typically 20% of your hackathon score, and it is the only 20% that does not depend on how much you managed to build. It is also the part first-time teams rush in the last thirty minutes. That is a lot of free marks to leave on the table.
What judges actually do with your video
Be realistic about this. A judge may have forty submissions to get through. Most of them will not clone your repository and run it. Your video is your project as far as scoring is concerned.
They are watching for three things: what does it do, does it work, and did you understand the problem you were solving. If your video answers those in the first sixty seconds, you are ahead of most of the field.
The structure that works
For a three-minute limit, this split is close to optimal:
0:00–0:20 — The problem, concretely
Name a specific person and a specific annoyance. "Students struggle with productivity" is noise. "If you live in a hostel, you find out the laundry pickup was moved only after you have missed it" is a problem a judge can picture.
0:20–0:40 — What you built, in one sentence
Say the thing plainly before you demo it, so the viewer knows what they are looking at. "So we built a tracker that pulls the hostel notice board into a phone reminder."
0:40–2:15 — The actual demo
Screen recording of the real thing working. This is the bulk of the video and it should be the bulk of your effort. Show the main flow start to finish, at a normal pace, with real data.
2:15–2:45 — How it works, briefly
Thirty seconds on the technical side. What is the stack, what was the hard part, what did you solve that was not obvious. This is where technical execution marks get reinforced.
2:45–3:00 — What is next
One or two sentences on what you would build with more time. This reads as ownership, and it also quietly explains what is missing without you having to apologise for it.
Rules that matter more than production quality
- Show the real thing running. Slides describing your project score significantly worse than thirty seconds of it actually working. If parts are broken, demo the parts that are not.
- Never demo with placeholder data. "Lorem ipsum" and "User 1, User 2" make a finished project look unfinished. Spend ten minutes putting realistic content in.
- Stay under the limit. Judges stop watching at the cutoff. If your best feature is at 3:20, it does not exist.
- Get the audio right. Bad audio hurts more than bad video. Record somewhere quiet, close to the mic. Phone earphones beat a laptop's built-in microphone.
- Do not spend time on a title animation. Nobody has ever scored higher for one.
A script template you can fill in
Hi, we're [team name].
If you're [specific person], [specific annoying situation].
[One sentence on why the current way is bad.]
So we built [name], which [does the one main thing].
[DEMO — screen recording, main flow, real data]
Under the hood it's [stack]. The tricky part was
[one real problem], which we solved by [approach].
With more time we'd add [one or two things].
Thanks for watching.Read it aloud once and time it before recording. Almost everyone's first draft runs long.
Free tools that are enough
- Recording: OBS Studio (free, all platforms). Or the built-in recorder — Game Bar on Windows, Shift-Command-5 on macOS.
- Quick trimming: your OS's default video app handles trimming the start and end, which is often all you need.
- Fuller editing: DaVinci Resolve or CapCut, both free. Only if you actually have spare time.
- Hosting: upload to YouTube as unlisted and submit that link. Do not put it behind a Google Drive permission wall — judges frequently cannot open those, and a video a judge cannot watch scores zero.
The timing mistake almost everyone makes
Recording, re-recording, exporting and uploading takes longer than anyone expects — an hour is a normal amount, and uploads on a shaky connection can take much longer.
Start your video with at least four hours left, not thirty minutes. If that means you stop building one feature early, stop building the feature. A finished project with a clear video beats a slightly bigger project with a rushed one, every time.
Before you submit, check
- The link opens in a private or logged-out browser window
- Audio is audible on phone speakers, not just headphones
- It is under the time limit
- Your project name is said out loud in the first fifteen seconds
- Nothing sensitive is visible on screen — no API keys, no personal messages, no unrelated browser tabs