An online hackathon is a build event run entirely over the internet, where teams form, mentors help and judges score through chat, video and submission platforms instead of a venue. This guide covers platforms, time zones and remote judging.
The format grew quickly during the pandemic, and the history of that period is told in the guide to the covid-19 hackathon movement. This page is an independent editorial guide to the practical side: what organisers and participants have to plan when everyone is in a different place.
What changes when a hackathon moves online
A remote event removes the venue, the catering and the hallway conversations, and each of those has to be replaced by something deliberate. The Major League Hacking organizer guide sets out the differences between digital and in-person events in a side-by-side comparison, summarised below.
| Part of the event | Digital format | In-person format |
|---|---|---|
| Check-in | Online form | Check-in desk at the venue |
| Opening ceremony | Pre-recorded or live-streamed, viewable anytime | Live presentation, seen once |
| Workshops | Live-streamed, viewable anytime | Live presentation, seen once |
| Meals and drinks | Participants provide their own | Organisers provide |
| Sponsor contact | Dedicated sponsor office hours | Visits to sponsor tables |
| Judging | Pre-recorded demos or live demos in channels | Live demos |
The table paraphrases the digital events page of the MLH Hackathon Organizer Guide, which also notes that a digital hackathon can cost a fraction of an in-person one because food, lodging and venue costs disappear.
One consequence is reach. The same guide observes that, because participants do not need to travel, sign-ups tend to rise closer to the event start, and that organisers can promote an event to hackers anywhere in the world, as described in the digital events section. Scale can be large: the European Commission’s EUvsVirus event reports that over 30,000 people submitted 2,164 projects, according to the EUvsVirus programme site.
Choosing platforms for streaming, chat and video
Most online events end up using four kinds of tool, and MLH’s guide names an example of each. A streaming service handles the opening and closing ceremonies, a video-calling service handles workshops and live demos, a chat platform keeps people connected, and a submission platform collects the finished projects.
- Streaming: the MLH guide recommends a browser-based tool that can send one broadcast to several video sites at once, and suggests pre-recording ceremonies so music and edited video make them more engaging.
- Video calls: for workshops, mini-events and live-demo judging the guide recommends a video-calling service and warns organisers to choose one that allows the right number of attendees. Its list of options notes that Google Meet allows up to 100 participants, per the MLH digital events page.
- Chat: Slack and Discord are named as the two most popular choices, with Discord preferred for its free voice chat, on the guide’s communication platform page.
- Submissions: projects are normally collected on a hackathon platform such as Devpost, which also publishes best-practice guidance for online hackathons.
The communication guide lists the channels an event needs at a minimum: team formation, introductions, questions for organisers, mentor help, an off-topic channel and a private channel for the organising team. It also reminds organisers that the code of conduct still applies in digital spaces, because people hidden behind a screen can behave worse than they would in a room.

Handling time zones across a global field
Time zones are the quiet problem of any online event. A deadline that looks generous in one city can land in the middle of the night in another, so every time that matters needs to be stated clearly.
Platforms bake in a default. On Devpost, hackathon times are set to Eastern Time unless the manager changes them, and the platform’s own help page says: “All hackathons are set to (GMT -05:00) Eastern Time by default.” The same page explains that a local time zone can be chosen instead, which then changes every time associated with the event, as described under setting up the essentials.
Devpost’s page on dates adds a practical rule: avoid midnight deadlines because they cause confusion, and stick to business hours, according to its dates guidance. A midnight cut-off is ambiguous in any case, since it could mean the start or the end of a day, and it is worse when participants span many zones.
A few habits follow from this for organisers:
- State the deadline in one named reference zone and show the same moment in at least one other widely used zone.
- Put the full schedule on the event page rather than only in chat, so late joiners see the same times.
- Record ceremonies and workshops. The MLH guide describes digital workshops as live-streamed and viewable anytime, which lets participants in awkward zones catch up.
- Spread mentor and sponsor office hours across the day so no region is left without help.
Submission timing matters too. Devpost reports that submissions almost always arrive in the final day or two of the submission period, so a deadline that falls overnight for many people tends to produce a rush at the worst possible hour, per its advice on getting more projects submitted.
Forming teams and keeping people connected
Online events lack the natural camaraderie of a shared room. Devpost’s guidance on community describes participants as likely sitting at their computer and learning about the event on their own, and tells managers to connect them with each other. Its tools for this include a Discord team-building channel, a discussion board for floating ideas, and a participants tab where registrants can see who else has joined, as set out in its page on community and forming teams.
For newcomers the practical steps are different from organisers’ concerns, and the guide on how to join a hackathon covers signing up, finding teammates and preparing before the start. This page assumes that groundwork is done and looks at what remote participation adds on top of it.
Moderation is part of keeping a remote event healthy. The MLH guide suggests that organisers stay active in chat, start conversations and moderate threads, which also makes the event more accessible to people who find large groups difficult.
Support is the other half. Devpost suggests checking the manager email, the discussion forum and any live chat, and replying within 24 hours on weekdays, as listed in its advice on getting more projects submitted. Quick answers keep participants building instead of waiting.
Judging remotely
Remote judging works best when it is planned before the event opens. Devpost’s judging guide lists the decisions to make early: who is judging, how much time they need, which criteria matter and how the projects will be assessed. The principles behind those criteria are covered in the separate guide to hackathon judging criteria; this section concerns the logistics of doing it at a distance.
Submission format
Without a room full of tables, the demo has to travel as a file or a link. MLH recommends that teams submit a 2 minute video through the submission platform, as stated in its judging plan page, and notes that the video should be a demo of the hack rather than a presentation. Devpost’s planning page suggests a 3-5 minute demonstration video in its hackathon planning guide. The two figures differ, which shows there is no single standard: organisers choose a length and publish it in the rules.
Panels, workload and scoring
Devpost advises managers to narrow the field before it reaches the judges. Its judging page says it often sends at most 30 projects to judges, expecting scoring to take about 5 hours. It suggests a window of 1-2 weeks for judges, at least three people on each panel, and between 2 and 4 panels when prizes are category-based, according to the judging and public voting page. Judges on the platform rate each criterion from 1-5 stars, and can recuse themselves from a project where they have a conflict of interest, as described in the guide on how to judge an online hackathon.
Live demos and public voting
Where live demos are wanted, MLH suggests giving each team its own voice channel so teams can wait, then share their screen or video as judges join, per the digital judging notes. Public voting can add excitement, but Devpost’s judging page warns of fraudulent votes and recommends small prize values and hiding live results until votes are reviewed.
Planning the schedule and communications
A remote event is easier to run when the dates are fixed early. Devpost recommends a registration and submission period of 6-8 weeks to allow time for marketing and building, followed by a judging period, as set out in its planning guidance. Other formats exist, and weekend events run on much shorter clocks, so the right length depends on the audience and the size of the project being asked for.
Communication should run through the whole event. Devpost’s platform has built-in reminders that can be edited, and its advice is to add relevant updates that point to resources, share an inspiring story or announce office hours. Participants also need to know what they must deliver. The platform’s testing guide explains how to ask for working links, builds or live demonstrations so judges can verify a project without paying for it, in the testing guide.
The MLH day-of checklist for digital events is a useful final pass: check-in ready, streaming platform ready, opening ceremony ready, sponsors assigned on the chat platform, an accurate schedule visible to attendees, relevant channels open, mentors and judges confirmed, and internal tasks assigned.
Frequently asked questions
What is an online hackathon?
It is a hackathon held over the internet, where teams collaborate remotely and submit projects through a platform. Opening ceremonies, workshops, mentoring and judging all happen through video, chat and submission tools.
Which platforms do online hackathons use?
MLH’s guide names a streaming service for ceremonies, a video-calling service for workshops and live demos, and Slack or Discord for chat. Devpost is a common platform for submissions and judging.
How do organisers cope with participants in different time zones?
They publish deadlines in a named reference zone, avoid midnight cut-offs, record sessions for later viewing and spread office hours across the day. Devpost lets managers set the event’s time zone, which changes every time on the event page.
How are online hackathon projects judged?
Typically through recorded demo videos and written submissions scored against published criteria, with live demos in video or voice channels when wanted. Platform tools such as Devpost let judges rate each criterion and recuse themselves where there is a conflict of interest.
