Devpost Guide (Markdown)
Devpost: hackutd-2025.devpost.com
Two deadlines, one platform. Register your team early, then polish your submission before judging — without getting disqualified on a technicality.
- Public repo only — link your code on Devpost; private repos can disqualify you.
- Max 2 sponsor tracks — you can still compete for general / MLH prizes.
- Invite every teammate on Devpost — one submission per team; everyone must be on it for prizes.
Final Pre-flight Check
- Public GitHub repo linked on Devpost (private = risk).
- At most 2 sponsor / company tracks selected.
- All teammates invited on the project (prize eligibility).
- Demo video is public (YouTube, etc.) — aim for about 2 minutes or less.
- You finished the final Submit flow — not just a saved draft.
Pick your path
- Saturday: Team Registration (2 mins)
- Sunday: Final Submission (10 mins)
Saturday 11:00 PM — your team must be registered on Devpost (complete the final Submit step).
1. Join the hackathon
Open the HackUTD Devpost page and sign up or log in. Complete your profile when prompted.
2. Create a project (blank is OK)
Go to My Projects → Create Project. For registration only, use your team name or “Team Registration” and placeholders where needed — you can edit before the final deadline.
3. Invite your whole team
Manage Team → invite everyone (the email tied to their Devpost account).
4. Project overview (registration)
Title can be your team name or “Team Registration”; elevator pitch can list teammates or a short idea.
5. Submit through the final screen
Pick sponsor tracks you’re considering (max two company/sponsor tracks). Placeholder video/repo is OK until Sunday.
You must complete the final Submit step or you are not registered.
Sunday 12:00 PM (noon) — final project due on Devpost.
1. Open your project for editing
My Projects → Edit Project. You can keep editing until the hack ends.
2. Project Overview
Title, pitch, thumbnail (recommended), technologies, links.
3. Project Details (Markdown)
Describe what you built, how to run it, demo-ready vs. prototype. Add screenshots or GIFs.
4. Additional information
Sponsor challenges (≤2 company tracks), public repo, demo video, schools for eligibility.
5. Agree and submit
Re-read Final Pre-flight Check at the top when you’re done.
Media requirements
| What | What to know |
|---|---|
| Demo video | Public link. About 2 minutes is ideal. |
| Thumbnails & screenshots | Show what actually works. |
| GitHub URL | Public repo only — private is a disqualification risk. |
- Never leave the repo private.
- School emails / profiles — match organiser rules for eligibility.
- One submission per team — no duplicate projects.
Prevent disqualification
- Submit early; keep editing until the Devpost cutoff.
- Invite issues → verify Devpost email, resend.
- Devpost bugs → another browser / cache clear → ask staff.
When do I register my team?
11:00 PM Saturday on Devpost. You can adjust tracks again before the final deadline.
Submit only once?
You can edit until Sunday 12:00 PM (noon).
Everyone submits separately?
One submission per team — invite every teammate for prizes.
Multiple projects?
One project per team.
How many sponsor tracks?
Up to two company/sponsor challenges. See the prize / sponsor guide for the rest.
Stuck? Ping a HackUTD officer or official event channels.
Happy hacking!