To build a portfolio website as a student, pick three or four projects that match the work you want next, write each one up as a short case study, and put them on a small site with a home page, project pages, an about page, your resume and a contact link. Class projects, side projects, volunteering and part-time jobs all count. What you lack in experience you make up for by explaining your thinking clearly.
What counts as portfolio work when you're still in school
Nobody reviewing a student portfolio expects client work for famous brands. They want evidence that you can take a problem, make decisions and finish. That evidence can come from more places than you might think:
- Class projects. The assignment brief is a client brief. Treat it like one.
- Capstones, theses and studio projects. Usually your longest and most complete work, so lead with them.
- Side projects. Anything you built, designed or wrote because you wanted to. These show initiative, which class work can't.
- Competitions, hackathons and design challenges. Useful because they come with a fixed deadline and outside judges.
- Volunteering. A poster series for a food bank, a website for a student society, the social accounts for a local sports club.
- Part-time and campus jobs. A café shift or a library desk job counts if you changed something: a new scheduling sheet, clearer signs, a process that saved time.
- Research or teaching assistant work. Show the method and your contribution, not just the paper title.
What works best depends on your field:
| Field | Strong work to show | Leave out |
|---|---|---|
| Computer science | A deployed side project, a capstone with a clear role, open source contributions | Tutorial clones you didn't extend |
| Design (graphic, UX, product) | Two or three case studies with process, one self-initiated project | Every exercise from an intro course |
| Architecture | Studio projects with drawings, models and a clear concept | Renders with no site, brief or explanation |
| Marketing and communications | Campaign plans, accounts you actually ran, writing samples | Group slide decks with no sign of your part |
| Writing and journalism | Published pieces (the student paper counts), a focused set of clips | Class essays on unrelated topics |
| Sciences and data | A reproducible analysis with a clear question and good charts | Lab reports copied straight from coursework |
If you want to see your material take shape while you gather it, the student portfolio starter opens FNJ's AI builder with a prompt written for students.
How many projects, and which ones
Three or four strong projects beat ten average ones. A reviewer will usually open one or two, so the first ones they see have to be your best.
Choose by the job you want, not by the grade you got. A B-graded project that matches the internship you're applying for is worth more than an A from an unrelated course. Aim for this mix:
- Your strongest piece, ideally a capstone or a long project.
- One project that matches the role or industry you're targeting.
- One self-initiated project that shows what you do when nobody assigns anything.
- Optionally, a piece that shows range or a second skill.
If you only have one strong project right now, that's fine. Publish it with one or two smaller pieces and add more each term. A short, honest portfolio beats no site at all.
Turn a class assignment into a case study
The difference between a course exercise and a portfolio piece is the write-up. Use the same structure for every project:
- The problem, in plain words. Rewrite the brief as a problem someone actually has.
- Your role. Especially for group work, say exactly what you did.
- Constraints. Time, tools, team size, budget, anything that shaped your decisions.
- Two or three key decisions. What you chose, what you rejected and why.
- The result. Images, a live link or a short demo video, plus any outside recognition: picked for the end-of-year show, won a hackathon track, adopted by the club you built it for.
- What you'd do differently. One or two honest sentences. Reviewers value this more than most students expect.
Here's what that change looks like in a project's title and summary:
- Before: "HCI 201, Group Project 2."
- After: "Showing which washing machines are free before residents walk downstairs: a booking flow for a campus dorm. Four-person team; I ran the interviews and built the prototype."
The second version says what the problem was, who it was for and what you did, in two lines. If you're a design student, this guide to writing a UX case study goes deeper on structure and visuals.
Group projects, permissions and honesty
Group work is normal in school, and you can show it. Just be precise about your part:
- Name your role in the summary, not in a footnote at the bottom.
- Credit teammates by role, for example "research with two classmates, visual design by a teammate".
- Show the pieces you made, and label the shared ones.
- If the project was for a real organization, ask before publishing anything that isn't already public, and leave out internal data.
- Check whether your school or program has rules about sharing coursework. Policies vary.
Overclaiming tends to surface in interviews, when someone asks you to explain a decision you didn't make.
The pages a student portfolio needs
Keep it small. Five pages are enough:
- Home. One line on what you study, the work you want and when you're available, then your featured projects. For example: "Third-year industrial design student, looking for a summer 2027 internship in consumer products."
- Projects. An index, plus one page per project using the case study structure above.
- About. A short bio, a friendly photo, your skills in plain sentences, and the profiles you keep up (LinkedIn, GitHub or Behance, depending on your field).
- Resume. A web page, a downloadable PDF, or both. Keep your expected graduation date visible.
- Contact. A personal email address, ideally on your own domain.
Optional extras: a page for awards and activities, or a short "now" line on the home page saying what you're working on this term.
Computer science students have a slightly different job, because reviewers often want live demos and repositories rather than images, so a student developer portfolio should put those links first.
Mistakes that make student portfolios look weaker than they are
- "Aspiring" in the headline. Say what you are: a design student, a junior developer, a writer. You don't need permission to describe your field.
- Skill bars and percentages. "Photoshop 80%" tells a reviewer nothing. Show the skill inside a project instead.
- A list of courses instead of work. Courses belong on the resume, briefly.
- No dates. Reviewers need to know when you graduate and when you can start.
- A school email address as the only contact. You'll lose access after graduation, and so will everyone who saved it.
- A site on university web space. Student hosting usually disappears when you leave. Put the site on your own domain from the start.
- Huge, uncompressed images. Resize and compress them before uploading, or your pages will crawl on a phone.
- Dead links to group repositories, class tools or shared drives that were deleted after the term ended.
Keep it current without making it a chore
Two habits make the biggest difference:
- Capture as you go. Screenshot your work, export final files, and write three sentences about each project while it's fresh. Course platforms and shared folders often close when the term ends, and you won't remember why you made a decision six months later.
- Review the site at the end of every term. Swap in a stronger project, drop the weakest one, and update the availability line on the home page.
Start the site before you need it, ideally a term or two before applications open. The first version is the hard part; updating it each term takes an evening.
Building your student portfolio with FNJ
FNJ's portfolio builder for students opens the AI builder with a starter prompt for a student portfolio. You add a short description of yourself and a reference (a screenshot or the link of a site whose look you like), watch it build the pages, and refine them in plain words. FNJ isn't free: a one-time Site Pack covers about three complete sites, and you host the exported site yourself, for example on Cloudflare Pages' free plan, so it keeps working long after you've stopped using FNJ.
Frequently asked questions
What should a student put in a portfolio with no work experience?
Class projects, capstones, side projects, competitions, volunteering, and part-time jobs where you changed something. Write each one up as a short case study that explains the problem, your role, your decisions and the result.
How many projects should a student portfolio have?
Three or four strong projects are enough. Lead with your best one, and make sure at least one matches the job or internship you're applying for.
Can I include group projects in my portfolio?
Yes, as long as you state your role clearly, credit your teammates, and show only what you made or label shared work. Ask before publishing anything from a real organization that isn't already public.
Should I use my university email on my portfolio?
Use a personal address instead, ideally on your own domain. University accounts are often closed after graduation, which breaks the contact link on everything you've shared.
When should a student start a portfolio website?
Earlier than feels comfortable, ideally a term or two before internship or job applications open. Publish a small first version and improve it at the end of each term.