To make a portfolio, pick three to six pieces of your strongest, most relevant work, then present each one as a short case study that names the problem, your role, what you did, and the result. Write a plain about section that says who you are and what you want next, and put the whole thing on a website you control so a link, not a login, is all anyone needs to see it. The order matters more than the count: lead with the piece that best proves you can do the job you are applying for.
First principles
Decide what the portfolio is arguing before you build anything
The most common mistake is treating a portfolio as an archive: a place to park everything you have ever made, sorted by date. An archive answers the question "what has this person done?" A portfolio answers a sharper and more useful question: "can this person do the thing I need done?" Those are not the same question, and the second one is the only one a hiring manager or a client is actually asking. Everything that follows in this guide is downstream of that distinction, so it is worth settling first.
Start by naming the one job you want the portfolio to win. Not five jobs, one. A product designer applying to a fintech and a photographer pitching weddings need different proof, and a single page that tries to serve both ends up persuading neither. Write the target down in a sentence: "convince a design lead at a mid-size software company that I can own a feature end to end," or "convince a couple that I will document their day without getting in the way." That sentence becomes the filter for every later decision about what goes in and what stays out.
Once the argument is clear, the work sorts itself. A piece belongs in the portfolio if it moves that specific argument forward, and it does not if it merely proves you were busy. This is why a smaller portfolio usually beats a larger one: the reader judges you by the weakest thing they see, not the strongest, so every marginal piece you add lowers the average. Curation is not modesty. It is the single highest-leverage thing you can do.
The method
How to make a portfolio, step by step
Six steps, in order. Do them in sequence, because each one narrows the decisions in the next. The whole thing is a weekend of focused work, not a month.
Gather more than you will use, then cut hard.
List every finished piece of work you could plausibly show. Aim to collect two or three times what will make the final cut, so you are choosing from a real pool rather than settling for what you happen to have. Then keep only three to six pieces: the ones that best prove you can do the job you named. If you hesitate on a piece, that hesitation is your answer. Cut it.
Order by strength, not by date.
Put your single most persuasive, most relevant piece first. First impressions decide whether the reader keeps scrolling, and chronological order buries your best work behind whatever you happened to finish most recently. Lead with the strongest, follow with the second strongest, and let the rest support them. Nobody owes you a scroll to the bottom.
Turn each piece into a short case study.
A thumbnail shows what you made. A case study shows how you think, and thinking is what gets hired. For each piece, write the problem you were solving, your specific role, what you actually did, and what changed as a result. Keep it to a few tight paragraphs. The next section breaks down exactly what belongs in each one.
Write a plain about section.
Say who you are, what you do, who you do it for, and what you are looking for next. Resist the biography. A reader does not need your childhood, they need to know in ten seconds whether you are the kind of person they are hiring. Add a real photo if you have one and a single clear way to contact you.
Choose where it lives.
Decide between a website you own and a profile on someone else platform. For most people the answer is a site you control, for reasons the comparison below lays out. Whatever you pick, the goal is the same: a single link that opens your work with no login, no app install, and no algorithm deciding who sees it.
Publish, then make it findable.
A portfolio nobody can reach is a private diary. Put the link in your resume, your email signature, and every professional profile you keep. If it lives on your own site, give it a clear title, a short description, and a sensible page name so search engines and answer engines can read it. Then send it to three people whose judgment you trust and fix what they trip on.
Anatomy
What goes inside a case study that actually persuades
This is the part most portfolios skip, and it is the part that separates evidence from decoration. Each piece should answer these in order. You do not need headings for them, but the reader should be able to find every one.
Problem
The problem, stated plainly
One or two sentences on what needed solving and why it mattered. Without the problem, an image is just an image. With it, the same image becomes proof that you can take a brief and answer it. Skip the jargon and describe the situation the way you would to a smart friend outside your field.
Role
Your role, stated honestly
Say exactly what you did and what you did not. On team projects this is where trust is won or lost: claiming the whole thing reads as dishonest, while naming your slice reads as someone who knows how real work happens. "I owned the checkout flow" is stronger than a vague "I worked on the app."
Process
What you did, and why
A few sentences on the choices you made and the reasoning behind them. Reviewers are hiring judgment, not just output, so a single sentence on a tradeoff you weighed is worth more than three more polished screenshots. Show one dead end you backed out of and you look like someone who learns.
Result
What changed as a result
Close with the outcome. A number is ideal (a metric moved, time saved, a target hit), but an honest qualitative result beats an invented statistic every time. If you genuinely cannot measure it, say what shipped and who used it. Never fabricate a figure, because the one reader who checks will discard everything else you claimed.
Proof
The work itself, shown well
Real images, real screens, real pages, at a size someone can actually read. Compress them so they load fast, and caption anything that is not self-explanatory. The visual is the exhibit; the words around it are the argument. You need both, and a portfolio that is all pictures is missing half of itself.
Scope
Enough context, and no more
A case study is not a design document. Give the reader what they need to judge the work and stop. The failure mode on both sides is real: too little and the piece is decoration, too much and nobody finishes it. When in doubt, cut a paragraph and see if the argument still stands. It usually does.
The about section
Write an about section that positions, not one that narrates
The about section is where most portfolios go soft. The instinct is to write a biography, a warm, chronological account of how you got here, and it is almost always the wrong instinct. A reader on your portfolio is not deciding whether they like you. They are deciding whether you are the right person for a specific need, and a biography makes them do the work of figuring out the answer. Your job is to answer it for them.
A strong about section does four things in a few sentences. It says what you do, in the words your industry uses. It says who you do it for, so the right reader recognizes themselves. It gives one honest reason you are worth taking seriously, which might be experience, a specialty, or simply the quality visible in the work above. And it says what you want next, because a reader who cannot tell whether you are open to work has no reason to act. Everything else, the hobbies, the origin story, the manifesto, is optional and usually better cut.
Keep the tone plain and human. Write it the way you would introduce yourself to a respected peer: direct, specific, and free of the inflated language that makes everyone sound identical. Words like "passionate," "results-driven," and "innovative" are invisible from overuse; a concrete sentence about what you actually do lands harder than any adjective. Add a real photograph if you have one, because a face builds trust that a paragraph cannot, and make sure there is exactly one obvious way to reach you.
Where it lives
A website you own versus a profile you rent
This is the one structural decision that outlasts the content. You can rewrite a case study in an afternoon, but moving off a platform that changed its rules is a much larger tax. Choose deliberately.
| Capability | Folio | A rented profile |
|---|---|---|
| Who controls the layout | You do. The structure, the order, and the emphasis are yours to set, so the strongest work leads | The platform does. Everyone gets the same template, and your best piece sits in the same grid as everyone else |
| What the URL says | Your own name or domain, which reads as professional and is easy to remember | The platform name plus a handle, which advertises the platform more than you |
| What happens if the rules change | Nothing. Your site keeps working the way you built it, on your schedule | You adapt or you lose reach, on their schedule. A feed change can bury your work overnight |
| Who can see it | Anyone with the link, no account and no app required | Often only signed-in users, and only as far as the algorithm decides to show it |
| Time to a first version | A little longer, because you are making choices instead of filling a template | Fast. Filling in fields is quicker than designing, which is the real appeal |
| Best used as | The permanent home your resume and profiles all point back to | A distribution channel that drives people to the home, not the home itself |
The honest answer for most people is both: own the home, and use the rented profiles as signposts that point to it. The mistake is making a rented profile the only place your work exists.
Getting found
Publish it, keep it current, and give it a permanent address
A finished portfolio is worth nothing until it is reachable, and reachable means more than uploaded. Put the link in your resume header, your email signature, and the bio of every professional profile you keep, so that anyone who encounters your name has a one-click path to your work. If the portfolio lives on your own site, spend twenty minutes on the basics search engines and answer engines read: a clear page title, a one-sentence description, a sensible page name, and image captions. These are not growth hacks, they are the difference between a page a machine can summarize and one it skips.
Then treat it as a living thing. The single most common failure is not a bad portfolio, it is a stale one: a strong page that stopped at the work you did two years ago. Set a recurring reminder to revisit it every quarter. Add the piece you are proudest of, retire the one that has aged, and reread the about section against the job you want now rather than the one you wanted then. A portfolio that keeps pace with you always outperforms a more polished one that froze.
If you would rather not assemble the hosting, the layout, and the resume separately, Folio is a hosted platform that does the whole job from one account, and being straight about the free plan: it puts you on portfolio.wrxstack.com/yourname rather than a domain of your own, and it shows a small "Made with Folio" badge, with the full theme gallery on the paid tier. What is not gated is the resume: it exports to PDF and DOCX for free, with no watermark, so the document you attach to an application is clean whatever plan you are on. Whatever you build it with, the rules in this guide do not change. Curate hard, structure each piece as evidence, write a plain about section, own the address, and keep it current. The tool is a detail. The argument is the point.
Frequently asked questions
How many pieces should a portfolio have?
Three to six is the right range for most fields and most jobs. The reader judges you by the weakest piece they see, not the strongest, so every marginal addition lowers your average. If you have twenty pieces, your task is to find the three that best prove you can do the specific job you want, and to leave the rest out.
How do I make a portfolio if I have little or no professional experience?
Build the proof rather than wait for it. Real class projects, self-directed briefs, volunteer work, and honest personal projects all count, as long as each one is presented as a genuine case study with a real problem and a real result. What sinks an early portfolio is not thin experience, it is padding: three sincere projects beat ten filler thumbnails every time.
What should the about section of a portfolio say?
Say what you do in your industry words, who you do it for, one honest reason you are worth taking seriously, and what you are looking for next. Keep it to a few plain sentences and skip the biography, because a reader wants to know if you fit a specific need, not how you got here. Add a real photo and one clear way to be contacted.
Should I make a portfolio website or use a profile on an existing platform?
For most people, make a site you own and use platform profiles as signposts that point to it. A rented profile is fast to set up but the layout, the reach, and the rules belong to someone else, and a link to your own address is the version that keeps working when a platform changes. The common mistake is letting a rented profile be the only place your work exists.
How is a portfolio different from a resume?
A resume is a one-page summary of your history that a reader scans in seconds; a portfolio is the evidence behind it, where the work itself makes the case. Serious candidates keep both and link them: the resume states the claim, and the portfolio proves it. Neither replaces the other, and a strong application usually leans on both.
How often should I update my portfolio?
Revisit it about every quarter. Add your best recent work, retire pieces that have aged, and reread the about section against the job you want now rather than the one you wanted when you first built it. The most common weakness in an otherwise good portfolio is not quality, it is staleness, and a quarterly pass is enough to prevent it.