Resume vs. portfolio: what each one is for

A resume and a portfolio both describe your work, so it's easy to treat them as two versions of the same thing. They aren't. Each answers a different question for the person reading it, and knowing the difference helps you write both better.

This guide explains what each one is for, when to send which, and how to connect them so they strengthen each other.

The short version

A resume answers "is this person qualified?" It's a structured summary of your history, built to be scanned quickly and compared against a list of requirements.

A portfolio answers "is this person good, and how do they work?" It's a curated set of examples with enough explanation that a reader can judge the quality of your work directly.

One is a list of claims. The other is evidence for the most important of those claims.

What a resume is for

A resume has a narrow, practical job: get you past the first filter. That filter might be an applicant tracking system, a recruiter with dozens of applications to review, or a hiring manager skimming between meetings.

To do that job well, a resume should be:

• Short. One page for most people early in their career, two for those with longer histories.
• Conventional. Readers expect contact details, a summary, experience in reverse order, education and skills. Unusual structures slow them down.
• Matched to the role. The language should echo the job description where it honestly fits, so both people and software can see the match.
• Dense with results. Each bullet should say what you did and what changed because of it.

What a resume can't do well is explain. A bullet like "Rebuilt onboarding flow, reducing support tickets" raises questions the resume has no room to answer. What was wrong with the old flow? What did you change? How do you know it worked?

What a portfolio is for

A portfolio picks up exactly where the resume stops. It takes your strongest two to five pieces of work and explains them properly.

A good portfolio:

• Shows rather than tells. Screenshots, writing samples, links to live work, code, before and after examples.
• Gives context. The problem, your role, the constraints and the outcome.
• Reveals how you think. How you approached a problem says more than the fact that you solved it.
• Carries your voice. Your bio and project descriptions show how you communicate, which matters for almost any job.

A portfolio is also more forgiving about format. You can lead with your best project instead of your most recent job, which helps a lot if you're changing careers or don't have a long work history.

Side by side

Here's how the two compare on the things that matter most:

• Length: a resume is one or two pages; a portfolio can be longer but should still be selective.
• Order: a resume usually follows time; a portfolio follows strength and relevance.
• Detail per item: a resume gets one to three lines per achievement; a portfolio gets several paragraphs per project.
• Evidence: a resume asks the reader to trust you; a portfolio lets them check.
• Tailoring: a resume is often adjusted for each application; a portfolio usually stays the same, with perhaps a different project featured first.
• Where it lives: a resume is a file you attach; a portfolio is a link you share.

When to send which

Send the resume when the process asks for it

If an application form requires a resume, send one. Don't replace it with a portfolio link, even in creative fields. Many hiring pipelines need the structured document to log and compare candidates.

Add the portfolio whenever there's room

Put your portfolio link in the header of your resume, next to your email. Add it to the application form if there's a field for websites. Mention it in your cover letter, ideally pointing to a specific project: "The checkout redesign on my portfolio is the closest match to what you described."

Lead with the portfolio for freelance and client work

Clients hiring a freelancer rarely ask for a resume. They want to see similar work, understand your process and get in touch. Your portfolio is the main document here, and a resume is something you send only if asked. See the freelancer portfolio guide for more.

Lead with the portfolio when networking

When someone says "send me something," a link is easier to forward than an attachment. It also opens on a phone without downloads, and you can update it without resending anything.

A simple rule: the resume goes where a form asks for it, and the portfolio link goes everywhere else.

How to make them work together

The most common mistake is making your portfolio a copy of your resume with nicer fonts. If a reader clicks through and sees the same bullet points, the portfolio has added nothing.

Instead, think of the resume as an index and the portfolio as the chapters.

Pick the achievements worth expanding

Look at your resume and highlight the two to four bullets you'd most want to talk about in an interview. Those are your portfolio projects. Each one should get its own section with a proper explanation. The guide on how to write a case study walks through a structure for this.

Keep the facts consistent

Job titles, dates and numbers must match across both documents. If your resume says you led a team of four and your portfolio says six, a careful reader will notice, and it undermines both.

Let each document do its own job

Here's a worked example. Say you're an operations coordinator with a resume bullet that reads:

"Redesigned inventory tracking process, cutting monthly stock discrepancies roughly in half."

That's a good resume bullet. On your portfolio, the same achievement becomes a short project write-up:

"Our warehouse tracked stock in three separate spreadsheets that were updated by different shifts. Every month-end count turned up discrepancies that took two people most of a day to reconcile. I mapped where each spreadsheet was updated, merged them into a single shared sheet with locked columns for each shift, and wrote a one-page guide for the team. Over the next quarter, discrepancies at month-end dropped by about half, and reconciliation went from a full day to a couple of hours."

The resume version earns a click. The portfolio version earns trust.

Use the portfolio to show things the resume can't hold

Some things don't fit on a resume at all: a side project, a talk you gave, writing samples, a volunteer role that taught you a lot, a short statement about the kind of work you want next. Your portfolio has room for these. Keep them secondary to your main projects, but don't leave them out if they support the story.

Do you need both?

Almost everyone benefits from having both, but the balance varies.

• Applying for salaried roles in traditional industries: the resume is essential, and a portfolio is a strong bonus that sets you apart.
• Applying for design, writing, development or other visible craft roles: both are expected, and the portfolio may carry more weight.
• Freelancing: the portfolio is essential, and the resume is optional.
• Changing careers or starting out: both matter, but the portfolio does the heavier lifting because it lets you lead with relevant projects instead of unrelated job titles.

If you only have time for one this week, write the resume first, since most applications require it. Then build the portfolio from it. Your resume already contains the raw material; the portfolio is where you expand it. For a broader view of what a portfolio site is, see what is a portfolio website.

Putting it together

Your resume summarizes; your portfolio proves. The resume follows convention so it can be scanned quickly. The portfolio picks your best work and explains it in enough depth that a reader can judge it directly.

Keep the facts identical across both, link the portfolio from the top of your resume, and expand your strongest resume bullets into full project write-ups instead of repeating them. Send the resume when a process asks for it and share the portfolio link everywhere else. If you already have a resume and want a head start, Folitox AI can turn it into a draft portfolio that you then edit and expand.