Skip to main content

HackUTD Devpost Guide

Submission & Devpost

HackUTD Devpost Guide

Two deadlines, one platform. Register your team early, then polish your submission before judging — without getting disqualified on a technicality.

Register TeamSubmit Project

TL;DR — read these three

  • Public repo only — link your code; 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.
Deadline: Saturday 11:00 PM — team registered on Devpost

The workflow

  1. Join the hackathon

    Open the HackUTD Devpost page and create an account 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 placeholder text where needed — you will edit before the final deadline.

  3. Invite your whole team

    Open Manage Team and invite every teammate using the email tied to their Devpost account. Missing invites = prize problems.

  4. Submit through the final screen

    Choose sponsor tracks you are considering (max two company/sponsor tracks). Use placeholder video/repo if you must — replace them before Sunday. You must complete the final Submit step or you are not registered.

Media requirements (what judges expect)

Demo video

Public link (YouTube, Drive, etc.). Keep it tight — about 2 minutes is ideal.

Required link

Thumbnails & screenshots

Project thumbnail + in-page images or GIFs that show what actually works.

Highly recommended

GitHub URL

Must be a public repository with your hack code. Private repos are a disqualification risk.

Public only

Don't forget (safety net)

  • Never leave the repo private — judges need to verify your work.
  • School emails / profiles — match organizer requirements for eligibility; fix mismatches before the deadline.
  • One submission per team — coordinate so nobody spins up a duplicate project.

Prevent disqualification

  • Submit early; you can keep editing until the posted cutoff on Devpost.
  • If an invite fails, verify your teammate's Devpost email and resend.
  • Try another browser or clear cache if Devpost glitches — then ping staff.

FAQ — open only if you need it

When do I have to register my team?
By 11:00 PM Saturday on Devpost. Pick the companies/tracks you care about; you can adjust before the final submission deadline.
Can I only submit my project once?
No — edit as many times as you want before Sunday 12:00 PM (noon). Earlier drafts = less panic.
Does everyone need their own Devpost submission?
No. One submission per team — but invite every teammate so they stay prize-eligible.
More than one project?
Only one project per team is allowed at HackUTD.
How many sponsor tracks?
Up to two sponsor/company challenges. General and MLH tracks are separate — read the prize guide for details.

Stuck? Flag a HackUTD officer or post in official event channels — we'd rather fix Devpost drama at 3 PM than 3 AM.