Guide

How to Make a Portfolio Website

Updated September 2026

How to Make a Portfolio Website

A portfolio website is a page you own — at your own link — that shows your work, your experience, and enough context for a visitor to decide whether they want to talk to you. It is not a résumé (too flat), not a LinkedIn profile (too crowded), and not a Behance gallery (too narrow). It is the one place online where you control what someone sees first.

Building one takes seven steps, and they always happen in the same order:

1. Decide what it is for — a job search, freelance clients, or a creative showcase each produce a different site.
2. Gather your material — résumé, best projects, proof, contact details — before you open any tool.
3. Choose the right tool — Squarespace, GitHub Pages, Skillfolio, a dozen others; the right one depends on what you are showing and who you are showing it to.
4. Write what goes on each section — About, Work, Proof, Contact — with real sentences, not placeholder text.
5. Build it and publish it — pick a domain or use a free subdomain, hit publish, and get a link you can share.
6. Run the launch checklist — mobile, load time, one clear call to action, the link on your résumé and LinkedIn.
7. Keep it alive — update it when your work changes, not on a calendar.

Those steps work whether you are a graphic designer with a hundred pieces to show, a nurse moving into administration, a recent graduate with two internships, a plumber starting to take direct clients, or someone returning to work after a decade away. The tool you pick matters less than the decisions you make before you pick it — what to include, what to cut, and who you expect to land on this page. Every section below walks through one step, with the specific choices inside it, so you can build the portfolio that fits your situation instead of copying a template that was made for someone else's.

Step 1: Decide What Your Portfolio Is For

Before you pick a color scheme or compare builders, answer one question: who is going to visit this portfolio, and what do they need to decide? Everything else — the sections you include, how visual the layout is, which tool you build it on — follows from that answer.

Most portfolio websites serve one of three purposes, and each one produces a different build:

Showing creative or visual work

If you are a photographer, designer, illustrator or architect, the images are the argument. Your visitor needs a gallery that loads fast, displays at full resolution, and gets out of the way. The writing matters less than the sequencing — which projects you lead with, how many you include, whether the progression tells a story about your range. A portfolio built for visual work lives or dies on presentation, which is why tools like Squarespace exist.

Supporting a job search

If you are applying for roles — marketing, operations, teaching, nursing, project management, anything where the work is not a photograph — your visitor is a recruiter or hiring manager who has already glanced at your résumé. They landed on your portfolio to answer a question the résumé could not: who is this person, and would they actually be good at this? They do not need a gallery. They need proof, context and enough personality to remember you after twenty other tabs. That means short project write-ups with outcomes, an About section that sounds like a human being, and a way to contact you — not a grid of thumbnails.

Attracting freelance clients

If you are selling your own services, the visitor is a potential buyer deciding whether to reach out. They need to see relevant past work, understand what you charge or how you work, and feel confident enough to send the first message. This build leans heavier on case studies and a clear call to action than either of the others.

Why this step gets skipped

Because every portfolio builder opens with a template gallery, not a question. You pick a layout that looks good, start filling it in, and realize three hours later that you have been arranging a design showcase when what you actually needed was a page that explains your ten years in logistics to someone who has never met you. That mismatch is the most common reason people abandon a portfolio halfway through — or finish one that does not do anything for them.

A quick self-test

If your work is visual and your visitor needs to see it to judge it, you need a gallery-first tool and strong images. If your work is not visual — if what you bring to a role is experience, judgment, problem-solving, leadership — you do not need a gallery. You need proof and story: what you did, what happened because of it, and enough of your own voice that the visitor walks away knowing something a résumé could never tell them.

Name your audience and your purpose now, before you gather a single file. The rest of this guide will keep pointing back to this choice, because it is the one that determines whether the portfolio you build actually works.

Step 2: Gather Your Material Before You Build Anything

The fastest way to abandon a portfolio is to open a builder with nothing to put in it. You stare at a blank template, realize you have not decided what to show, and close the tab. The fix is boring: collect everything first, then build. When you sit down to assemble the portfolio, every section should already have its content waiting in a folder or a document.

The material list

• Your résumé or work history. Even a rough one. If you do not have a résumé at all, write down every role, project, or responsibility you have held — paid or not — in the last five years. This is the spine of the portfolio.
• Three to five best projects or accomplishments. Not every project. The ones where something changed because of your work: a process improved, a problem solved, a thing shipped, a group helped. Pick the ones you can explain clearly, not the ones with the fanciest title.
• Metrics or outcomes, if you have them. Revenue, time saved, people served, error rates reduced, students passed — anything with a number. If you do not have hard numbers, a concrete before-and-after still counts: "The onboarding process took two weeks; I cut it to four days."
• A headshot — or not. A clear, recent photo helps a visitor feel like they are meeting a person. It does not need to be professional. But if you would rather not include one, that is a legitimate choice, and no builder requires it.
• Contact details. An email address you check. Your LinkedIn URL, if you use LinkedIn. Your city or region, if location matters for the kind of work you do. That is enough.

Where to find proof if you think you have none

Most people have more evidence than they realize — it is just scattered. Look in these places:

• Performance reviews. Pull out any line where a manager described a specific result or strength. That is third-party proof, and it is already written.
• Thank-you emails or messages. A client, a colleague, or a supervisor who wrote "this was exactly what we needed" gave you a usable quote. Screenshot it or copy the line.
• Project outcomes. Dig through old reports, presentations, or handoff documents. The summary slide from a finished project often contains the metric you forgot you had.
• Course certificates and credentials. A completed certification, a license, a relevant course — these are proof that does not require you to make a claim about yourself.

What to leave out

A portfolio is not a complete employment record. Leave out every job you have ever held — include only the roles and work that support the story you are telling now. Leave out personal details that do not serve the visitor: your marital status, your high school, your hobbies (unless a hobby directly demonstrates a skill you are selling). And leave out anything you cannot explain in a single sentence. If you need a paragraph of context before a project makes sense, it is not pulling its weight on this portfolio.

For career changers and students

If your paid work history does not match where you are headed, look sideways. A volunteer project where you managed a budget is a finance project. A class assignment where you built a working prototype is an engineering project. A student organization you led through a fundraiser is a leadership project. The work counts — it just was not on a payroll. Gather those the same way: what you did, what happened, and what it proves about how you operate. The portfolio does not care who signed your paycheck; it cares whether the visitor can see the skill in action.

Step 3: Choose the Right Tool (Comparison Table)

You know what the portfolio is for, and you have your material in a folder. Now you need a tool to put it together — and the honest answer is that the right one depends on what you decided in Step 1, not on which builder has the best marketing.

Here is what matters: cost, how fast you can get a real page live, whether you can use your own domain, and who the tool was actually designed for. Everything else — template count, animation libraries, plugin ecosystems — is noise until you have a published portfolio someone can visit.

Who should use what

If you are a photographer, a graphic designer, or an illustrator, your portfolio is the images. You need a tool that makes them look beautiful at full resolution, handles grid and lightbox layouts, and lets the work speak for itself. Squarespace does this better than anything else on the list. Wix is a close second if budget matters. Pick either one and spend your time curating the gallery, not wrestling with the builder.

If you are a developer, GitHub Pages is a genuine advantage: the portfolio itself is a repo, which means the site is proof of the skill it describes. You control every pixel, hosting is free, and anyone who visits your GitHub profile sees the source. The trade-off is time — you are building from scratch, so budget a few hours and know some HTML and CSS going in.

If you are a job seeker, a career changer, a teacher, a nurse, a project manager, or anyone else whose work is not a gallery of images but a body of experience — you do not need a blank canvas. You need a portfolio built for a hiring context: one that shows who you are, what you have done, and why it matters, in a format a recruiter can absorb quickly. Most general-purpose builders will get you there, but you will spend an hour or two deciding on layout, writing copy from scratch, and fiddling with fonts before you have anything live.

Where Skillfolio fits

Skillfolio starts from the résumé itself. Upload one and it rebuilds the wording and design, or, if you do not have one, it builds a résumé from scratch step by step. That résumé becomes a conversational portfolio — a page at your own link where an employer can ask questions about you and get real answers grounded in your actual experience, with citations showing where each answer came from. The whole setup takes about ten minutes, and you still get a clean PDF you can export and send the traditional way.

Be clear about what it does not do: there are no image galleries, no custom CSS, no drag-and-drop layout editor. If visual presentation is the work — if someone needs to see your photographs or your UI designs at full size — Skillfolio is the wrong tool, and you should use Squarespace or Wix. But if the problem is that your résumé says what you did without showing who you are, and you need something a hiring manager can explore in more depth than a PDF allows, that is the specific gap it was built to close.

Step 4: Write What Goes on Each Page

You have your material in a folder and your builder open. The cursor is blinking. This is where most portfolio builds die — not because the tool is hard, but because nobody told you what the words should actually say. Here is what goes in each section, in the order a visitor will read it.

About

Two to three sentences, first person, present tense. Answer three questions and stop: who you are, what you do, and who you do it for. That is the entire section.

A good About section for a middle-school science teacher moving districts might read: "I teach sixth- and seventh-grade life science, and I have spent six years building labs that work on a tight budget. I am looking for a district that values hands-on learning and will let me keep building." A project manager's might read: "I run software launches for mid-size SaaS companies — scoping, scheduling, and keeping twelve-person teams honest about deadlines. I have shipped nine products in four years, all on time."

Do not start with where you were born, where you went to school, or the phrase "I am a passionate." Start with the work. If you cannot describe what you do in two sentences, that is a sign you are trying to cover too many roles at once — pick the one this portfolio is for.

Work or Projects

Each entry needs exactly three things:

• A headline that names the work — not a job title, but what you actually did. "Rebuilt onboarding for a 200-person sales team" is a headline. "Sales Enablement Specialist" is a job title.
• A short paragraph explaining what the situation was, what you did, and why it was hard. One paragraph. If you need two, the project is too big — split it or pick the part that matters most.
• A result — a number, an outcome, a change. "Ramp time dropped from fourteen weeks to nine." "The grant was funded." "The client renewed for a second year." If you do not have a number, a concrete outcome still works: "The district adopted the curriculum for all four middle schools."

Three to five entries is enough. You are not documenting your career — you are giving the visitor three to five reasons to keep reading. Put the strongest one first, not the most recent one.

Proof

This is anything that is not your own claim about yourself. It might be a certification, a link to a live project, a published article, a metric from a tool you can screenshot, or a real testimonial from a real person who gave you permission to use their name. If you have none of those, skip this section rather than fill it with self-assessments. A portfolio with no proof section is better than a portfolio with a proof section that proves nothing.

Do not fabricate a testimonial. Do not write one and attribute it to a former manager. If you want a quote, ask someone — most people will say yes if you draft it for them and let them edit.

Contact

Include your email address (a professional one, not the handle you made in high school), a link to your LinkedIn profile, and your city or metro area if location matters for the role. That is all.

Leave out your phone number — this is a public page, and you do not control who finds it. Leave out your full mailing address. Leave out a contact form if your builder makes it clunky; a plain email link is faster and more reliable.

What to Leave Out Everywhere

Cut any jargon the visitor would need your industry to decode. Cut the full list of every skill you have ever touched — a wall of twenty-eight skills tells the reader you could not decide which ones matter. Cut the objective statement; your About section already does that job in a sentence that sounds like a person wrote it.

The tone test: read each section out loud as if you are explaining your work to a smart person at dinner — someone who is interested but does not share your job title. If a sentence sounds like it belongs on a corporate slide deck, rewrite it until it sounds like something you would actually say. The person visiting your portfolio is deciding whether to talk to you. Write like someone worth talking to.

Step 5: Build It and Publish It

You have your material written and your tool chosen. The build itself should be the shortest part of this process — assembly, not invention. Log in, drop your sections in order (About, Work, Proof, Contact), and resist the urge to redesign anything before the first version is live. A published portfolio you can improve tomorrow beats an unpublished one you are still tweaking next month.

The Domain Decision

Every builder gives you a subdomain for free — something like yourname.squarespace.com, yourname.carrd.co, or yourname.skillfolio.studio. A custom domain (yourname.com) costs roughly $10–15 per year through a registrar like Namecheap, Porkbun, or Google Domains, and most builders let you connect one in their settings panel.

The honest question is whether a custom domain matters for you right now. If you are freelancing and sending proposals to clients, it does — it signals permanence and professionalism. If you are a job seeker sharing a link on your résumé, a clean subdomain is perfectly fine. No recruiter has ever rejected a candidate because the portfolio lived at a subdomain instead of a .com. Spend the money on a custom domain when the portfolio is earning you work, not before.

Free Hosting vs. Paid

Some tools cost nothing to host. Google Sites and GitHub Pages are completely free. Skillfolio is free at skillfolio.studio. Carrd has a free tier with limits. Squarespace and Wix charge a monthly fee — typically $14–16/month on an annual plan — which makes sense if you need their design tools but is hard to justify if all you need is a place to hold your work and a way to be contacted.

What the URL Should Look Like

Your portfolio link will appear on your résumé, in your LinkedIn About section, and in every email signature you send during a job search. It needs to be short, readable, and clean. Good examples:

• janedoe.skillfolio.studio
• janedoe.carrd.co
• janedoe.com

Bad examples: anything with a trailing slash followed by a random string, a URL that includes the word "site" or "page1," or a link so long it wraps to a second line on a résumé. If the builder gives you a default URL full of numbers, change it in settings before you publish. On your résumé, place the link directly under your name and contact information — not buried in a footer. On LinkedIn, add it in the website field and in the first few lines of your About section, where it is visible without clicking "see more."

Publishing: The Ten-Second Test

Hit publish. Then do three things in this order:

• Open it on your phone. Not a phone simulator — your actual phone, in a browser. If any section is cut off, overlapping, or unreadable, fix it now. Most of the people who click your link will be on a phone or a laptop with a small window, not a wide desktop monitor.
• Send the link to one person — a friend, a former colleague, a family member who will be honest. Ask them one question: What did you understand about me in ten seconds? If the answer is vague ("it looks nice") or wrong ("I thought you were a graphic designer" when you are an operations manager), your About section needs another pass.
• Click every link on the page. A dead link to a project, a broken email mailto, or a LinkedIn button that goes to a 404 makes the whole portfolio look unfinished. This takes sixty seconds and catches the mistake that costs you a reply.

Your portfolio is now live. It does not need to be perfect — it needs to be accurate, readable, and reachable at a link you can hand to anyone. The next section covers the checklist that makes it look finished before you start sharing it widely.

Step 6: The Launch Checklist Before You Share It

A portfolio with a broken mobile layout or a missing contact link does not look unfinished — it looks abandoned. The difference between the two is about ten minutes of checking. Run through every item below before you put the link on your résumé, in an email, or anywhere a hiring manager might click it.

Mobile test

Open your portfolio on your phone. Not a phone-sized browser window on your laptop — your actual phone. Tap every link. Scroll every section. If text runs off the screen, if buttons overlap, if an image pushes the layout sideways, fix it now. More than half the people who click your link will be on a phone, and a recruiter who sees a broken layout will close the tab before they read a word.

Load time

If the page takes more than three seconds to load, you are losing visitors before they arrive. The usual culprit is images: a 4MB headshot or a full-resolution project screenshot that could be a quarter of the size. Compress them. If an image does not directly support a point you are making about your work, remove it entirely — it is costing you speed and giving you nothing back.

One clear call to action

Decide what you want the visitor to do: email you, book a call, read a specific project. Then check whether that action is obvious within five seconds of landing on the page. If your portfolio ends with three buttons, two social links, and a contact form, the visitor has to make a decision you should have made for them. Pick one. Make it visible.

A real way to contact you

An email link or a simple contact form — not just a LinkedIn button. LinkedIn requires a login, sometimes a connection request, and adds friction at the exact moment someone wants to reach you. Give them a way to write to you directly, right from your portfolio.

The link on your résumé

Add your portfolio URL directly under your name and contact information, at the top of your résumé. Not in a footnote, not buried in a skills section at the bottom. It should be as visible as your email address and your phone number. Keep the URL short and readable — no trailing slashes, no random query strings, nothing a human cannot type from memory if they had to.

The link on LinkedIn

Put it in two places: the website field in your contact info (where LinkedIn makes it clickable) and in the first few lines of your About section (where people actually read). A link only in the website field gets overlooked because most visitors never open the contact-info panel.

Favicon and page title

These are small, and they are the difference between polished and half-finished. The favicon is the tiny icon that appears in the browser tab — if yours still shows the builder's default logo, change it to your initials or a simple mark. The page title is what appears in that same tab and in search results. "Home" or "Untitled" tells a visitor you did not care enough to name the thing. Set it to your name and what you do: Jordan Reyes — Operations Manager. It takes thirty seconds and it signals that every other detail on the page was intentional, too.

Where a Conversational Portfolio Fits (and Where It Doesn't)

Most portfolio websites are built to be looked at. A conversational portfolio is built to be asked. When you set one up on Skillfolio, the platform learns about you from two sources — your résumé and a short interview it walks you through — and uses that material to answer an employer's questions directly on your portfolio. Every answer cites the specific line from your résumé or interview it drew from, so nothing is invented and everything can be checked.

How It Actually Works

An employer lands on your portfolio and sees your story, your work, your proof — the same sections you would build on any tool. The difference is a conversation layer: they can type a question and get a real answer grounded in what you actually wrote. If someone asks "Has he managed people before?" and your résumé describes leading a five-person warehouse team for three years, the portfolio says so and points to that line. If you have never managed anyone, it says that too. It does not guess, and it does not pad.

There is also fit analysis. An employer pastes in their job description and gets an honest read of how you match — including the gaps. That honesty is the point: when the analysis says you are strong somewhere, the employer trusts it, because it did not hide the places where you are not.

You can see this in action with three real personas — Sales, Operations, and Product — on the live demo. Ask the portfolios anything and watch the citations appear.

Where It Does Not Fit

If your work is visual — photography, graphic design, illustration, architecture — the images are the argument. An employer hiring a photographer needs to see the photographs, not ask an AI about them. You need a gallery tool like Squarespace, and a conversational layer adds nothing that a strong image grid does not already say.

Where It Fits

If your career is a body of experience rather than a portfolio of images — you are a project manager, a nurse, a teacher, an operations lead, a career changer whose best proof lives in outcomes and stories, not visuals — then a traditional portfolio site gives you a blank canvas and asks you to become a designer. A conversational portfolio starts from your résumé. Skillfolio rebuilds the wording and design of that résumé (or builds one from scratch if you do not have one), then turns it into a portfolio that can speak for you when you are not in the room. The résumé and the portfolio come from the same source, so they never contradict each other, and when you update one the other follows.

That is the gap it closes: your résumé says what you did, but it cannot say who you are. The short interview Skillfolio runs — questions about how you work, what drives you, how you handle hard situations — gives the portfolio material a résumé never carries. When an employer asks a question that goes beyond job titles and dates, the portfolio has something real to draw from.

Keeping Your Portfolio Alive: What to Update and How Often

The most common failure mode for a portfolio website is not a bad design or weak copy — it is neglect. Someone builds it during a job search, lands a role, and never touches it again. Two years later they need it, and the page still lists a title they left eighteen months ago. The fix is not a maintenance schedule. It is a habit tied to the moments that actually change what the portfolio should say.

What to Update

Three things trigger an edit:

• A new project worth showing. You finished something that demonstrates a skill better than what is already on the page. Add it, and consider removing the weakest entry so the portfolio stays tight — five strong projects beat eight mediocre ones.
• A new role or responsibility. Your title changed, you moved companies, or your scope expanded. Update the About section and your résumé so both tell the same story.
• Something no longer represents you. Work from an early career stage, a skill you have moved away from, a project for a client you would rather not highlight. Remove it. A portfolio is not an archive — it is a curated argument for what you do next.

How Often

Not on a calendar. On a trigger. Every time you ship a project, change jobs, or earn a credential, open the portfolio and ask whether it still matches the person you would describe in an interview. If it does, close it. If it does not, spend fifteen minutes making it current. That rhythm keeps the page honest without turning maintenance into a recurring task you ignore.

How to Know Whether Anyone Is Looking

Most builders — Squarespace, Wix, WordPress, Skillfolio — include basic analytics: page views, visitor location, traffic source. Check them when you are actively sharing the link. If you sent the portfolio to five hiring managers and see zero visits, the link may be broken or buried. If you see visits but no responses, the content may need work. The other signal is simpler: when a recruiter or interviewer mentions something specific from your portfolio, you know the page is doing its job.

The Single-Link Advantage

Every place you have shared your portfolio link — your résumé header, your LinkedIn profile, an email signature — points to the same URL. When you update the portfolio, every one of those surfaces reflects the change immediately. No re-sending files, no version confusion, no "here is my updated résumé" follow-up email. One edit, everywhere at once.

When to Let It Sit

If you are not actively job-seeking or freelancing, a quiet portfolio is fine. You do not need to manufacture updates. Just make sure the page is not actively misleading: remove a job title you no longer hold, fix any broken links to external work, and confirm the contact email still reaches you. A portfolio that is accurate but unchanged for a year is far better than one that is current but full of dead links and a role you left in 2023.

Start With What You Have

If you have a résumé — even an old one, even one you are embarrassed by — you have enough material to build a portfolio today. You do not need a finished project list, a professional headshot, or a design eye. You need the facts that are already sitting in that document: where you worked, what you did there, and what came of it. That is the starting line.

If you do not have a résumé at all, open a blank document and write down three things you have done that someone would pay you for or thank you for. A semester-long research project. A volunteer event you organized. A process you fixed at work that nobody asked you to fix. Those three things are your material, and they are enough to fill an About section, a Projects section, and a reason for someone to reach out.

The point was never to build a perfect site. The point is to have something at your own link — a URL you control, that you can put on a résumé and a LinkedIn profile — that says more about you than a one-page PDF can. Something that shows how you think, not just where you have been. Something that is still working after you close your laptop and go to bed.

Pick the tool that fits your situation, write the four sections, publish it, and send the link to one person today. If you want a conversational portfolio that starts from your résumé and lets employers ask questions about you directly, Skillfolio will get you there in about ten minutes. If another tool fits better, use that one. Either way, start with what you have.

Common questions

How do I make a portfolio website for free?

Use a platform with a free tier: Carrd, Wix, or Google Sites all work. You'll get a subdomain instead of your own URL, and some features are locked, but it's enough to show your work. If you need something employers can question directly, Skillfolio builds a conversational portfolio from your résumé in about ten minutes.

What should I put on my portfolio website?

Start with an About section that says who you are and what you do. Add 3–5 examples of your best work, each with context: what the project was, what you contributed, what happened because of it. Include contact information and a way to download your résumé. If you want employers to explore on their own, a conversational portfolio lets them ask questions about your experience directly.

Do I need coding skills to make a portfolio website?

No. Platforms like Squarespace, Wix, Webflow, and Carrd are built for people who don't code. You pick a template, drop in your content, and publish. If you want full control over the design, learning basic HTML and CSS helps, but it's not required.

How long does it take to build a portfolio website?

An hour if you're using a no-code platform and already have your work organised. A day or two if you're writing the About section from scratch or choosing between twenty templates. Skillfolio takes about ten minutes because it builds the portfolio from your résumé and a short interview.

What's the best platform for a portfolio website?

It depends what you need. Squarespace and Webflow are strong for visual work like design or photography. Carrd is fast and minimal. Wix has the most templates. If you want a portfolio that answers questions about your experience on its own, Skillfolio is built for that.

Should I use a portfolio website or LinkedIn?

Use both. LinkedIn is where recruiters search; a portfolio website is where you show the work itself and tell the story LinkedIn's format doesn't hold. A conversational portfolio goes further: employers can ask it questions about your experience instead of skimming a profile.

How do I choose a domain name for my portfolio?

Use your name if it's available: firstnamelastname.com is clear and professional. If that's taken, try firstnamemiddleinitial.com or firstname-lastname.com. Avoid clever wordplay—you want something an employer can type from memory after meeting you.

Can I make a portfolio website without any work samples?

Yes, but call it a professional website instead of a portfolio. Focus on your About section, your skills, and what you're looking for. If you're a student or career changer, describe class projects, volunteer work, or anything that shows how you operate. A conversational portfolio built from your résumé can surface that experience even when you don't have a traditional body of work to display.

How often should I update my portfolio website?

Every time you finish something worth showing, or every few months if your work doesn't produce discrete projects. The portfolio should reflect what you can do now, not what you did three years ago. A conversational portfolio updates everywhere the moment you change something, so you're never sending outdated links.

Do employers actually look at portfolio websites?

Yes, when the work matters to the role. A designer without a portfolio is invisible; a marketer with one has an edge. The problem is most portfolios are static—employers have to read the whole thing to find what they care about. A conversational portfolio solves that by letting them ask questions and get answers grounded in your actual experience.