A portfolio should have three to five projects, not a dozen. The person reviewing your work does not have time to read twelve case studies, and a long list actually reads as weaker because it hides your best work behind your average work. Pick three to five projects that are relevant to the job you want, show a real outcome, and give you a story you can tell in an interview. If you only have one project that is genuinely strong, a single flagship done well beats five that are padding.
The honest answer
Depth beats breadth, and it is not close
The instinct is to show everything. You worked hard on all of it, so a bigger portfolio must be a stronger portfolio. It is the opposite. The person reviewing your work is busy, skeptical, and forming an opinion in under a minute. A wall of twelve projects does not read as "look how much I have done." It reads as "I could not tell which of these was any good," and that is a judgment problem, not a volume win.
Three to five projects is the sweet spot for almost everyone. It is enough to show range without diluting your best work, and it is short enough that a reviewer will actually look at all of it. More than that and you are betting they will find your strongest piece before they lose interest. They will not. They will skim the first two, form a verdict, and move on. So the only projects that matter are the ones you put first, which means the padding at the bottom is not helping you, it is quietly lowering your average.
Depth is what a shorter list buys you. When you only carry a handful of projects, you have room to explain each one properly: the situation, what you decided, what you did, and what happened. That depth is the actual signal. Anyone can list twelve things they touched. The person who can walk through three things they owned, end to end, is the person who looks like they can be trusted with the next one.
The filter
How to choose which projects make the cut
Run every candidate project through these three tests. If it does not clearly pass all three, it belongs in your archive, not your portfolio.
Test it against the job you actually want.
Not the job you had, the job you want next. If you are aiming for design systems work, the marketing site you built three years ago is noise, even if it was good. Relevance is the first filter because a perfect project for the wrong role still fails to move you toward the right one.
Demand a real outcome, not just activity.
A project earns its place when you can name what changed because of it. "Cut checkout drop-off by a third" or "took the feature from prototype to ten thousand users" is an outcome. "Worked on the checkout flow" is activity. If the only thing you can say is that the project existed, it is not ready to be shown.
Keep only what you can tell a story about.
The best portfolio projects are the ones you would happily be asked about in an interview, because there is a decision, a tension, and a result inside them. If a project would leave you fumbling for what to say, it will read as thin on the page too. Depth on the page and a story you can tell are the same thing.
Cut anything that only survives out of loyalty.
You will be tempted to keep a project because it was hard, or early, or sentimental. None of that helps the reviewer. Be ruthless: if it does not pass the first three tests, it comes off. A smaller portfolio of things you are proud of always beats a bigger one you are apologizing for.
The anatomy
What a portfolio-worthy project actually contains
A strong project is not a screenshot and a paragraph. It is a small, complete argument that you are good at the work.
Context
The situation
One or two sentences on what the problem was and why it mattered. Without context, a result is just a number floating in space. The reviewer needs to know the starting line before your finish line means anything.
Role
What you owned
Be honest and specific about your part. "I led the redesign" and "I contributed to the redesign" are different claims, and a good interviewer will find the seam. Owning a clear slice reads as stronger than vaguely claiming the whole.
Decision
The judgment call
The most valuable thing in any project is the moment you chose one path over another and why. That is the part a reviewer cannot get from a resume, and it is the part that proves you think, not just execute.
Outcome
The result with a number
Whatever changed, quantify it where you honestly can. A real figure is what a skim-reader remembers, and it is the difference between a project that proves something and one that merely describes something.
Proof
The link or artifact
A live URL, a repo, a case study, a testimonial with a real name. Proof turns "trust me" into "verify it yourself." One verifiable artifact is worth more than three paragraphs of self-description.
Craft
The presentation
Consistent visuals, real copy instead of placeholder text, and no broken links. Sloppy presentation of good work quietly tells the reviewer how you will present their work. The frame is part of the picture.
The trade-off
Three deep projects versus a dozen shallow ones
Both take real effort. Only one of them actually helps the person deciding whether to hire you. Here is why the shorter list wins on every axis that matters.
| Capability | Folio | A dozen shallow projects |
|---|---|---|
| What the reviewer reads | All of it, because there is little enough to read | The first two, then they lose interest |
| What it signals | Judgment: you know which work is your best | Volume: you could not decide, so you showed everything |
| Your average quality | High, because every piece had to earn its place | Dragged down by the weakest thing on the page |
| Interview readiness | You can go deep on any project they point at | You half-remember half of them |
| Maintenance | Easy to keep current and correct | Stale links and outdated work you forgot was there |
The goal is not the biggest portfolio. It is the portfolio where your worst visible project is still one you are proud of.
The exception
When a single flagship is enough
Sometimes the right number is one. If you have a single project that is genuinely excellent, deeply relevant to the role, and rich enough to talk about for twenty minutes, a portfolio built around that one flagship can beat a portfolio of five average pieces. This is common for people early in a career, for career changers with one strong proof point, and for specialists whose entire pitch is one hard thing done extremely well.
The trick with a single flagship is to give it the room it deserves. Do not pad it out with three weak projects to hit an imaginary quota, because the weak ones will drag the reviewer's estimate of the strong one down with them. Instead, go deep: the full story, the decisions, the outcome, the artifacts. Let the one project carry the weight, and let a short about section and a resume fill in the rest of who you are.
The rule underneath both answers is the same. Never show a project you would not want to be judged on. Whether that leaves you with five projects or one, the standard does not move. Quantity is negotiable. The floor on quality is not.
The pruning
How to retire weak work without regret
Retiring a project feels like deleting effort, so people avoid it and let old work pile up. Reframe it. Every project a reviewer can see is a vote you are casting for your own standard. Leaving a weak one up does not add to your case, it lowers the bar you are asking to be measured against. Taking it down is not throwing work away, it is refusing to be averaged down by your past self.
Do it on a schedule so it never becomes a big emotional decision. After each new win, add the fresh project and ask whether it should push the weakest current one off the page. Portfolios that win are not the ones with the most history, they are the ones curated to the last big result. And nothing you remove is truly lost: keep an archive, keep the files, and know that your content is yours to export and bring back any time you want it. Retiring a project from the front page is a display choice, not a delete.
That is the whole discipline. Choose three to five projects that are relevant, prove an outcome, and give you a story. Give each one the depth it deserves. And keep pruning, so the portfolio always shows the best version of your judgment rather than the longest version of your history.
Frequently asked questions
How many projects should a portfolio have?
Three to five projects is right for most people. It is enough to show range without diluting your best work, and short enough that a reviewer will actually look at all of it. If you only have one genuinely strong, relevant project, a single flagship can beat five pieces of padding.
Is it better to have more or fewer projects in a portfolio?
Fewer, done deeply. A long list reads as weaker because it hides your best work behind your average work and drags your visible quality down to the weakest piece on the page. A short, curated set signals judgment, and judgment is what gets hired.
What makes a project good enough to include in a portfolio?
Three tests: it is relevant to the job you want next, it shows a real outcome you can name rather than just activity, and it gives you a story you could tell comfortably in an interview. If a project fails any of the three, it belongs in your archive, not your portfolio.
Can a portfolio have just one project?
Yes. If that one project is excellent, relevant, and rich enough to discuss in depth, a single flagship can outperform a portfolio of five average pieces. This is common for people early in a career, career changers, and specialists whose pitch is one hard thing done very well.
Should I remove old projects from my portfolio?
Yes, on purpose and on a schedule. Every project a reviewer can see is a vote for your own standard, so leaving weak work up lowers the bar you are measured against. Keep an archive and export your content any time, but keep the front page curated to your best.