What should a freelancer's portfolio website have?
The short answer
Six or eight pieces of work with a sentence each explaining the problem you solved, a clear statement of what you do and who for, some indication of price or how you work, and one obvious way to get in touch. Most freelance portfolios show everything and explain nothing, which makes the visitor do the work of deciding whether you are right for them.
On this page
Show fewer things, explain each one
The instinct is to show everything you have ever made. It is the wrong instinct, for two reasons.
A portfolio is judged on its average, not its best. A visitor forms an impression from the first few pieces. If three of the first six are merely fine, that is what they conclude about you — the excellent one further down does not undo it.
Everything with no context is a mood board. A grid of nice-looking images tells somebody you have taste. It does not tell them you can solve their problem, which is the thing they are actually trying to establish.
Six to eight pieces, each with two or three lines: what the client needed, what you did, what happened. That last part is the one almost nobody includes, and it is the one that converts — "traffic doubled", "they still use it three years later", "it shipped in five weeks".
Say what you do and who for
The most common freelance positioning is a job title. "Designer." "Developer." "Copywriter." That describes the skill, not the service, and it leaves the visitor to work out whether you do their kind of thing.
Better is one sentence naming the work and the client: "I build websites for small hospitality businesses." "I write copy for B2B software companies." "I do brand identity for independent food producers."
The fear is that narrowing loses work. In practice the opposite happens — a specific statement makes the right client feel understood immediately, and the wrong client self-selects out, which saves you the calls you were never going to win. You can always take the adjacent job when it comes; you just do not have to advertise for it.
The two things freelancers leave off
Price, in any form. Most freelance sites say nothing, so every enquiry starts with a mutual guess and a meaningful share end at the number. A day rate, a project starting point, or "most projects fall between X and Y" filters before the call rather than during it. It is the single change that saves the most time — see should I put prices on my website.
How you work. Availability, typical lead time, how many rounds of revisions, whether you work alone or bring people in, how you invoice. Clients who have been burned by a freelancer before are checking for professionalism, and a short "how I work" section signals it more convincingly than any adjective on your homepage.
About, contact, and the boring parts
Put your face on it. Freelance is bought from a person. A real photograph and a real name do more than a logo, and a freelance site with neither reads as a shell — see how to write an about page.
One way to get in touch, prominent. Not five. Email or a short form, on every page.
Say when you are available. "Taking projects from September" is genuinely useful and almost nobody publishes it. It also does something subtle: being visibly booked is a stronger signal than being visibly free.
Personal site or portfolio site?
Worth deciding deliberately, because the two get conflated and they behave differently.
A portfolio is for winning work. It is organised around the client's decision, and everything on it serves that.
A personal site is for being findable and known — writing, projects, whatever you are interested in. It builds slowly and compounds, and it often produces better work than a portfolio does, because it attracts people who already agree with how you think.
You can have both on one domain, and most people should. Just be clear which page is doing which job, because a homepage trying to do both usually does neither.
Own the domain
The one structural point. Publish on your own domain, not on a portfolio platform's subdomain.
Everything you post to a platform builds that platform's authority, and the day you leave — or it changes its terms, or shuts down — the links people saved point at nothing. A domain in your name is cheap, permanent, and the only version of this you actually own. See what is a domain name.
What this looks like in Helm
The freelance-specific problem is that a portfolio is only as good as its most recent entry, and updating it always loses to billable work.
Every freelancer knows their site is two projects out of date. The reason is never that they did not know — it is that adding a case study means opening a code editor or a CMS they set up two years ago and have forgotten, on a Sunday, for free.
On Helm a project is structured content: images, a title, the client, the category, the description, all fields you fill in and press Go Live on, with a live preview. Adding the job that wrapped last week takes about ten minutes rather than an afternoon of remembering how the site works. That is the whole difference between a portfolio that stays current and one that quietly ages.
And if you build sites for clients yourself, the other half of this is worth knowing about — Helm Partners is how freelancers hand clients a branded dashboard without building one.
The short version
Six to eight pieces, each with what the client needed and what happened. One sentence saying what you do and who for. Something about price. Your face, your name, and one way to contact you. On your own domain. And keep it current, because in freelance the last piece on the page is the one being judged.