How to make a portfolio website that doesn't waste your best work

To make a portfolio website, pick 3–5 of your strongest projects, show the process behind each one (not just the finished screenshot), organize them so a stranger can find the right one in under a minute, and pick a free plan only after you've checked what it actually restricts.

Most portfolio sites fail before anyone reads a word of copy. Someone finishes a project, exports a final image, drops it into a generic grid, and moves on. Six months later the grid has twelve thumbnails, no context, and a visitor who bounces in nine seconds because nothing tells them which one is worth opening.

The fix isn't a better template. It's deciding, before you touch a builder, what belongs on the page and what doesn't.

What actually gets looked at

Nielsen Norman Group surveyed 204 UX hiring professionals about what they look for in a candidate's portfolio, and the answer wasn't "more projects." It was process. Reviewers said they want to see "the messy process and all the work and research that was put in to land on that shiny polished design," not just the final screenshot.

That finding generalizes past UX. A photographer's client wants to know you can handle a difficult shoot, not just that you own a nice camera. A writer's prospect wants to see how you structure an argument, not a wall of bylines. The final artifact is proof you finished. The process is proof you can be trusted with the next project.

Practically, that means every portfolio project needs at least three things: the constraint you were working under, the decision you made because of it, and the result. Skip any of the three and the project reads as a screenshot with a caption.

How many projects, and what goes in each

NN/G's guidance, echoed across most design-hiring advice, lands on 3 to 5 detailed case studies over a longer list of thumbnails. Their recommended structure per project has seven parts: the problem you were solving, your specific role, how you got to the solution, why it addressed the problem, what you rejected along the way, the measurable impact, and what you'd do differently now.

You don't need all seven for every field. A photographer's "impact" section might just be where the shoot ran. A musician's "role" section might be one line if it was solo work. But the shape holds: problem, your part in it, the result is the minimum a visitor needs to judge the work instead of just looking at it.

Cut anything that doesn't clear that bar. A portfolio with four strong, complete case studies beats one with fourteen bare thumbnails every time. The fourteen just make the visitor do the filtering you should have done yourself.

Structuring it without a "project" block

Here's something that surprised us when we built ours: most portfolio tools, including Nameplate, don't have a dedicated "Project" block. Ours ships with thirteen block types (link, image, file, text, media embed, email signup, form, FAQ, resume, testimonial, divider, page link, and folder), and none of them is called "project."

That's not a gap. A folder block groups related pieces into an expandable section, and inside it you stack an image or two, a short text block for the context paragraph, and a link out to the live thing if one exists. That combination is the case study: the folder gives it a boundary, the text gives it the problem-and-result framing NN/G describes, and the image carries the proof. You get full template examples across roughly a dozen professions, from a photography-focused layout to one built for musicians, and each one arranges the same handful of blocks differently depending on what that field's visitors expect to see first.

If your work is genuinely singular (one long documentary project, one ongoing brand), skip the folder and just run text and image blocks in sequence down a dedicated page, linked from your home page with a page-link block. The block-based approach is more setup work than a rigid "add project" button, but it means a photographer's page and a developer's page don't have to look identical, and they shouldn't. Browsing portfolio examples across professions is a faster way to see the difference than reading about it.

Where you put your strongest project matters more than the tool you use to build it. Visitors decide whether to keep scrolling in the first few seconds, so lead with your best work, not your most recent. Those aren't always the same project.

What a free plan actually gets you

Worth saying plainly, because "free portfolio website" is one of the most-searched phrases in this space and most builders bury the details: on our free plan you get one published profile, and the page carries a small "Made with Nameplate" badge. That's the honest tradeoff, not a hidden one: free plans on any builder pay for themselves somehow, and here it's a visible credit line, not a project cap or a locked template.

If you only need one page and don't mind the badge, free is a complete answer, not a trial. If you're managing multiple pages (a personal site plus a client-facing one, say) or want the badge gone, that's when a paid tier becomes the honest recommendation rather than an upsell.

Common mistakes we keep seeing

Alt text left as the filename. Every image block needs real alt text, not "IMG_4021." MDN's guidance is the right bar to clear: alt text should describe what the image shows, read naturally alongside the caption before it, not just satisfy a form field. This isn't only about accessibility, though it is that. It's also what search engines and AI answer tools read when they can't see the image.

No route back to the work that matters. A folder full of six projects with no differentiation forces the visitor to guess. Put your strongest project first, and say why it's there in one sentence.

Copying a template's placeholder copy. "Explore featured projects, commissions, and downloadable resources" reads fine in a preview and terrible on a live page with your name attached. Every template ships with placeholder text; none of it should survive to publish.

One giant page, no structure. If you work across more than two or three distinct areas, a single scrolling page turns into scroll fatigue. A page-link block routing to a dedicated page per area, or per client type, keeps each visitor looking at only what they came for.

Common questions

How do I create an online portfolio?

Pick your 3–5 strongest projects, write a short problem-and-result paragraph for each, and put them behind a builder or a page-link structure that lets a visitor reach the right one quickly. The platform matters less than having those paragraphs written before you start building — most of the time people spend "building a portfolio" is actually time spent deciding what to leave out.

Is there a free way to make a portfolio website?

Yes. Most builders, including ours, offer a free tier that publishes a real page — the tradeoff is usually a small branding badge and a limit on how many profiles or pages you get, not a cap on how many projects you can show within one page.

Do I need to know how to code to make a portfolio website?

No. Block-based builders (link, image, text, folder, and similar components) cover almost everything a portfolio needs without touching HTML. Code helps if you want a fully custom layout, but it's not required to publish something that works.

How many projects should I put on my portfolio?

Three to five detailed ones, based on hiring-manager research from Nielsen Norman Group. More than that and visitors start skimming instead of reading; fewer than three makes it hard to show range.

Should my portfolio be one page or several?

One page works if your work is narrow enough that everything belongs in the same scroll. If you cover more than two or three distinct areas, a short home page linking out to a dedicated page per area (through something like a page-link block) keeps each visitor focused on what they came for.

What's the difference between a portfolio builder and a portfolio template?

A template is a fixed starting layout you fill in. A builder is the underlying tool that lets you rearrange blocks, add pages, and swap templates later without starting over. Most people searching for one actually need the other: a template to start fast, on a builder flexible enough that the template isn't a ceiling.