Resume website vs. portfolio site vs. personal website: what's the difference?

Type "portfolio website" into Google and you'll get design agencies, WordPress themes, a Wikipedia page about art portfolios, and roughly nine different tools all claiming to be the one you need. Nobody agrees on the words. A designer calls it a portfolio. A recruiter calls it a personal site. Your uncle, who worked in sales for 30 years, calls it "the website thing" and asks if you need one now that you're job hunting.

You do, probably. But which kind depends on what you're applying for, and the three terms aren't interchangeable, even though most articles online treat them like they are.

TL;DR#

• Resume website: your resume, reformatted for a URL instead of a page. Same content, browsable instead of printable.
• Portfolio site: work samples front and center. Built for roles where the output matters more than the job title (design, writing, photography, dev).
• Personal website: the broadest of the three. Can include a resume, a portfolio, a blog, whatever. Built around you as a person, not you as an applicant.

Most job seekers actually want a resume website with a light portfolio section bolted on. Full personal websites are usually overkill unless you're already building a public reputation. Skip to the decision framework if you just want the answer.

Resume website#

A resume website takes the content of your resume, the same jobs, dates, and bullet points, and puts it on a page instead of a PDF. The structure barely changes. What changes is the format: scrollable instead of paginated, clickable instead of static, alive instead of a file sitting in someone's downloads folder.

This is the right call for most job seekers. If your resume already tells the story you want to tell (you're not pivoting industries, you're not primarily selling creative output), a resume website gets you the most payoff for the least effort. It's "having a link," solved.

What it typically includes:

• Name, title, one-line summary
• Work history with the same content as your PDF, formatted for scanning
• Skills or tools section
• Contact info or a contact form
• A downloadable PDF version, for when someone actually needs to upload one

What it usually skips: deep case studies, a blog, personal essays. A resume website is not trying to be interesting. It's trying to be findable and credible. If you want to see what one actually looks like across different fields, browse real example sites built from real resumes rather than starting from a blank template.

Portfolio site#

A portfolio site leads with output. The homepage isn't your name and title, it's the work: three to six projects, thumbnails first, details on click. Text about your career history exists, but it's secondary. The visitor is there to see what you can do, not to read what you've done.

This matters most for roles where a resume genuinely can't prove competence. A software engineer can list "built a payments pipeline" on a PDF, but a link to the actual repo or a live demo does more work than the sentence ever could. Same for a photographer, a UX designer, a copywriter, an illustrator. If your value is visible and specific, showing beats telling.

What it typically includes:

• 3-6 project case studies (problem, approach, result, not just a screenshot)
• A short bio, usually below the fold
• Contact info, often gated behind a form to filter serious inquiries
• Sometimes: a resume link, tucked in the nav, for the recruiter who wants the traditional format too

The trap with portfolio sites is scope creep. I've talked to designers who spent three weekends on case study layouts and never actually applied anywhere. A portfolio site is a tool for getting hired, not a design project with a deadline of "someday." If you want the case-study structure without the weekend build, start from a template built for exactly this and swap in your own projects.

Personal website#

A personal website is the umbrella. It can contain a resume section, a portfolio section, a blog, a newsletter signup, photos from a trip, whatever you want. The organizing principle isn't "get me a job," it's "this is a page about me," and the job-search content is one piece of a bigger picture.

This is the right build for people who already have, or want, a public presence beyond any single job search: writers building an audience, consultants establishing expertise, freelancers whose next client might find them through a Google search rather than an application. It's also right for anyone early enough in a niche that "having opinions in public" is part of the career strategy (think: a data scientist writing about a specific modeling technique, building credibility one post at a time).

What it typically includes:

• Whatever the owner wants. That's the whole point.
• Usually a resume or "about" page nested inside
• Often a blog or writing section
• A more personal, less applicant-facing tone throughout

The tradeoff: personal websites take longer to build well, and a half-finished one (a blog with two posts from 2023, an "About" page that says "coming soon") can read worse than no site at all. If you're not going to maintain it, don't start it.

The overlap, and why the terms get confused#

Here's the thing nobody says clearly: these aren't three separate categories. They're three points on one spectrum, and most real sites people build sit somewhere in between.

A UX researcher I mentioned in an earlier post wanted her site to prove she could think strategically, not just take notes in user interviews. That's a resume-website job with one portfolio-style case study grafted on, not a full portfolio site, and definitely not a personal website with a blog she'd abandon in six weeks. Most people land somewhere in that same middle zone. The mistake is picking a category label first and building to match it, instead of starting from what the reader on the other end actually needs to see.

Which one do you actually need?#

Answer honestly, not aspirationally:

You're applying to jobs where the resume format already does the job (most roles: ops, sales, marketing management, healthcare, trades, admin, finance). → Build a resume website. Add one or two proof points if you have them (a project you led, a metric you moved), but don't force a portfolio structure onto content that doesn't need it.

You're applying to jobs where the work itself is the evidence (design, engineering, writing, photography, video, illustration). → Build a portfolio site. Lead with 3-6 strong examples. A thin resume section at the bottom is enough; nobody's judging your portfolio site by its "About" page.

You're building toward something bigger than the current job search (a personal brand, a consulting practice, a body of public writing). → Build a personal website, but be honest about the maintenance cost before you start. A resume website you finish beats a personal website you abandon.

You're not sure, and the job search feels urgent. → Start with a resume website. It's the fastest to finish, the easiest to keep current, and the one that never looks unfinished. You can always add a portfolio section later once you know which projects are worth featuring. (Still in school or just graduated? The same logic applies, just with a thinner work history to work with.)

What employers actually do with these#

This part is where the terminology stops mattering and the actual behavior takes over. A CareerBuilder/Harris Poll survey of 2,380 hiring managers and HR professionals found that 69% use search engines like Google to research candidates, and 57% said they're less likely to call someone in for an interview if they can't find them online at all. That's not a portfolio-specific stat, it applies to anyone with any kind of personal link. Not having one is a bigger risk than picking the "wrong" category of site.

For roles where a portfolio is the norm, the numbers get more specific. A 2017 survey of 121 hiring professionals by Hover found 86% will visit a portfolio site when a candidate provides one, and 71% said the quality of that portfolio influences their hiring decision. Small sample, but the direction is consistent with everything else in this space: given a link, they click it.

What they're actually looking for, in their own words, from a Muse interview with hiring managers across different industries: Deniz Gültekin at Eventbrite wants "a great two- to five-line bio that sums up who you are and what your value proposition is." Ed Fry, formerly of Inbound.org, said he loves "a list of projects, along with explanations as to what those projects were about." Appcues' Ty Magnin put it more bluntly: "If there's a lack of personalization, I'd worry that the person isn't creative."

None of them said "impressive design." All three wanted specificity. That's the actual bar, regardless of which of the three categories your site falls into.

What every version needs, no matter the label#

Whichever one you build, a few things hold across all three:

1. A URL you're not embarrassed to share. yourname.com or a clean subdirectory beats a randomly generated string of characters every time. ResumeHowl gives you P1 automatically, no domain purchase required.
2. Fast load, especially on mobile. Recruiters are often clicking your link from their phone between meetings, not settling in at a desktop.
3. One clear next step. Contact form, email, or a calendar link. Don't make someone hunt for how to reach you.
4. Something specific. A number, a project name, a real result. "Passionate about growth" tells a hiring manager nothing. "Grew organic signups 34% in six months by rebuilding onboarding" tells them everything.
5. A downloadable PDF version. Job boards and ATS portals still want an upload. Your site is for the human who follows up after; the PDF is still what gets you into the pipeline in the first place. (See the case for why that PDF should be a boring, ATS-safe one, not the beautifully designed one you're tempted to attach.)

So which should you actually build this week?#

If you've read this far because you're mid-search and the decision has been sitting on your to-do list for two weeks: build the resume website. It's the one that's never wrong, it's the fastest to finish, and it's the one every hiring manager already knows what to do with when they click it. Add a portfolio section if you have 2-3 things worth showing. Skip the blog. Skip the "coming soon" pages. Ship something this weekend that's complete, even if it's small, rather than something ambitious that stays half-built through three more application cycles.

Because the sites that actually help are the finished ones. Which one were you about to overbuild?

More on this topic: browse every portfolio & personal site post.

Sources#

• CareerBuilder, "Number of Employers Using Social Media to Screen Candidates at All-Time High" — Harris Poll survey of 2,380 hiring managers and HR professionals, conducted Feb 16–Mar 9, 2017 (link)
• Hover, "Will Quality of Portfolio Site Influence Hiring Decisions?" — survey of 121 hiring professionals, Feb 2017 (link)
• The Muse, "Can a Personal Website Help Your Job Search? What 6 Hiring Managers Really Think" (link)