Guides · Nov 17, 2026
How to Write a Winning Devpost Submission, Field by Field
The project page is the one part of a hackathon entry every judge sees. Some will watch your whole video. Some will open your repository. Nearly all of them will land on the write-up first, often between dozens of other entries. A clear page will not save a broken project, but a muddled page can sink a good one.
This guide walks through a Devpost submission field by field. The advice works on other platforms too, because the questions judges ask are the same everywhere. For the bigger picture, read how to win a hackathon and how hackathons are judged.
Before you write: open the rules
Every hackathon’s official rules list what the submission must contain. Read that section before you write a word, and copy its requirements into a checklist. The WebMCP Challenge rules are a good example of how specific these can be. They require a text description that explains four named points, a demo video under three minutes, access to a working project for testing, a public code repository with instructions and an open source license, and materials in English or with an English translation.
Then find the judging criteria. Your write-up should answer each criterion directly, ideally in the same order and with the same words. If “Potential impact” is a criterion, a section called “Impact” makes the judge’s job easy.
Start a draft early
Devpost’s own tips for planning your project recommend starting your submission about two weeks out, recording the video about a week before the deadline, and aiming to submit at least a week early. It also notes that you can edit a draft as often as you like before the deadline.
That last part matters. Many rules lock the entry once the submission period ends. The WebMCP rules, for instance, say you may not change your submission after that point. So the version that exists at the deadline is the version that gets judged. A rough but complete draft on day one beats a perfect page that is still half-written an hour before close.
Title and tagline
The title is how judges refer to you in their notes. Keep it short and easy to say. The tagline is your one-line pitch and appears in project galleries, so it needs to work alone.
- Say what it does and for whom: “Turns support tickets into a ranked fix list for small teams.”
- Skip hype words like “revolutionary” and “next-gen.” They take up space without telling the judge anything.
- Name the sponsor technology here only if it is central to the idea.
The project story
This is the main description. Many Devpost entries follow a familiar set of headings: Inspiration, What it does, How we built it, Challenges we ran into, Accomplishments, What we learned and What’s next. Those headings are a fine skeleton. Adjust them to fit the rules, and make sure each required point has its own clearly labeled section.
A structure that reads well:
- One-sentence summary. Put it at the very top, in bold if the editor allows. If a judge reads only this, they should know what you built.
- The problem. Two or three sentences about one real user and one real pain. Specific beats sweeping.
- What it does. Walk through the core flow in the order a user would experience it. A screenshot for each key step helps more than another paragraph.
- How it works. The architecture in plain language. Name the frameworks, models, APIs and sponsor tools you used, and say what each one does in the project.
- What is real and what is not. Say clearly which parts work end to end and which are mocked or hard-coded. Judges notice, and honesty builds trust.
- Challenges and what you learned. One or two concrete problems you solved. This is where your engineering judgment shows.
- What’s next. A few sentences, not a roadmap. It shows you have thought beyond the deadline.
Formatting tips: use headings, short paragraphs and bullet lists. Bold the phrases that map to the judging criteria. Avoid walls of text. If you used AI tools to build or write, check the rules for any disclosure requirement and follow it.
Built With
The Built With field is a list of tags for the languages, frameworks, platforms and APIs you used. Fill it in accurately. Organizers and sponsors often scan these tags to find entries that used their tools, and a missing tag can mean a missed look from a sponsor-prize judge. Do not add tools you did not really use.
Links, media and testing instructions
These fields are where entries quietly fail. Treat each one as a requirement, not decoration.
- Demo video. Check the length limit and visibility. The WebMCP rules say judges are not required to watch beyond three minutes, which is common. Our demo video guide covers structure and upload mistakes.
- Live demo link. If you have one, test it in a private browser window, signed out, on the day you submit.
- Code repository. If the rules ask for a public repository, make sure it is public, has a README with setup steps, and includes a license if one is required.
- Testing instructions. Spell out exactly how a judge can try the project: the link, a demo login if needed, sample data, and the two or three things to try first. If something needs an API key or special setup, say how to get around it.
- Image gallery. Clean screenshots of real screens. Crop out browser clutter and personal details.
Team and track details
Make sure every teammate has joined the project if the event requires it, and that names match the people who registered. Select every track or sponsor prize you are eligible for and want to be considered for. Then answer any extra questions the organizer added to the form. Those questions often feed directly into judging or eligibility checks.
Final checks before you submit
- Every requirement in the rules is checked off, in writing.
- The summary line makes sense on its own.
- Each judging criterion has a section or a clear answer.
- The video plays, is within the limit and is not private.
- The demo link and repository open while signed out.
- Testing instructions work for someone who has never seen the project.
- The entry shows as submitted, not as a draft.
Give yourself a buffer. Put the deadline in your calendar a day early with the deadline calendar, or use the Add to calendar button on any event page. When you are done, send your project for the entry wall so more people can see it, and look for your next event on the online hackathons list.
FAQ
What should a Devpost project story include?
Cover the problem, what the project does, how you built it, what is working and what is not, and what you would build next. Many submissions use the familiar headings Inspiration, What it does, How we built it, Challenges, Accomplishments, What we learned and What's next. Always add anything the official rules ask the description to explain.
How long should a Devpost description be?
Long enough to answer every question in the rules and the judging criteria, and short enough to skim. A one-line summary at the top, short sections with headings, and a few screenshots usually work better than long paragraphs.
Can I edit my Devpost submission after the deadline?
Usually not. Many Devpost-hosted rules say that once the submission period ends you may not change your submission, though you can keep updating the project in your portfolio. You can normally edit freely before the deadline, so start a draft early.
Do judges read the Devpost write-up or just watch the video?
It varies by event, and judges often have many entries to review. Rules commonly say judges are not required to watch beyond the video time limit, so the written page has to stand on its own. Write it so a judge can understand the project without the video.
What are testing instructions on Devpost?
Testing instructions tell judges how to try your project: a live link, demo login details, steps to run it, and anything that needs setup. Some rules require access to a working project for judging, so missing or broken testing instructions can cost you the entry.