Introduction

A portfolio is the part of a job or client application that a resume cannot replace. A resume says what you can do; a portfolio shows it. Hiring managers and clients routinely open the link before they read the resume closely, and a clear, working portfolio can move an application from the pile to the shortlist.
You do not need to write code to build one. No-code portfolio builders now handle the layout, hosting, and mobile display, so your job is the part no tool can do for you: choosing the right work, explaining it clearly, and making it easy for a stranger to contact you. This guide walks through that process in order — picking a platform, selecting work, writing project descriptions, adding proof and contact pages, and launching.

Step 1: Decide what the portfolio is for

Before you open any builder, answer one question: who will read this, and what should they do next? The answer shapes everything else.

• Applying for a job: the reader is a recruiter or hiring manager. They want to see relevant skills fast, so lead with work that matches the job description and make your resume easy to find.
• Finding freelance clients: the reader is a potential client. They want to see results and trust signals, so lead with finished work, a clear services list, and a simple way to start a project.
• Changing careers: the reader needs evidence that your new skills are real. Coursework and practice projects count here, as long as you present them honestly as learning work and explain what you did.
  Write the goal down in one sentence, for example: “A portfolio for entry-level UX design jobs that shows three case studies and a resume download.” If you cannot write that sentence yet, do it before you build anything — it stops the portfolio from becoming a random collection of everything you have ever made.

Step 2: Choose a no-code platform

There is no single best platform. The right choice depends on your field, your budget, and how much design control you want. These are the options that consistently appear in 2026 roundups of free and low-cost portfolio builders, with their trade-offs as reported by those roundups in October and November 2026. Pricing and plan limits change, so confirm the current terms on the platform’s own pricing page before you commit.

Wix: the most flexible free option

Wix is the best-known general website builder, and its free plan lets you publish a real portfolio site with a drag-and-drop editor and a large template library, including hundreds of portfolio and resume templates. The free plan shows Wix branding and ads, and it does not include a custom domain. That makes it a good starting point if you want full control over layout and are willing to upgrade later for a cleaner address. For a broader walkthrough of the same kind of builder, see our guide on how to create a website without coding.

Carrd: the simplest one-page portfolio

Carrd builds single-page sites, which is exactly what most portfolios need: a short introduction, a few projects, and a contact section on one scrolling page. Its paid plans are among the cheapest in this category — recent roundups list paid plans starting at $9 per year, with custom domains from $19 per year — and the free tier publishes a live page. Choose Carrd if you want something live today with almost no learning curve.

WordPress.com: the most expandable free option

WordPress.com’s free plan gives you a hosted site with a selection of themes and the block editor, which builds pages visually without code. The free plan includes limited storage (recent guides report 1 GB) and shows WordPress ads, and you cannot install plugins or custom themes until you pay. It is a strong choice if you may later add a blog, because the same site can grow into one.

Behance: the portfolio network for visual work

If you are a designer, illustrator, or photographer, Behance is less a website builder and more a portfolio community. A free profile lets you publish an unlimited number of projects with images, video, and written case studies, and other professionals can discover your work there. The trade-off is control: your work sits inside Behance’s design, not your own site. Many creatives use both — Behance for discovery and a personal site for applications.

Canva: the fastest start for non-designers

Canva’s free portfolio maker turns a template into a one-page portfolio site, and it is useful if you already use Canva for resumes or social posts. The design quality is high for the effort involved, but customization is shallower than Wix or WordPress.com, and Canva’s own help pages note that custom domains require a paid plan.

GitHub Pages: the free option for developers

If you are a developer or a student learning to code, GitHub Pages hosts a static site free from a repository. It does require some comfort with files and Markdown rather than a purely visual editor, so it is not truly no-code — but it is free, it never shows ads, and a GitHub profile with live projects is itself strong evidence for a technical role.

How to choose in five minutes

Your situation	Start with
You want maximum design freedom, free	Wix
You want one clean page, live today	Carrd
You may add a blog later	WordPress.com
You do visual work and want discovery	Behance, plus a personal site later
You already live in Canva	Canva’s portfolio templates
You are a developer	GitHub Pages
Pick one, and do not spend more than an afternoon comparing. The platform is not what gets you hired — the work on it is.

Step 3: Select your best work — quality beats quantity

Most beginners make the same mistake: they publish everything. A portfolio with twelve uneven pieces reads worse than one with four strong ones, because the reader judges you by your weakest piece.
Aim for four to six projects to start. If you have fewer than four strong pieces, three excellent ones beat four with a filler. Choose work that shows the skills the job or client actually needs, not the work you are most attached to. A simple test: for each piece, write one sentence explaining what skill it proves. If you cannot, leave it out.

What counts if you have no clients yet

Beginners often wait for permission — a first client, a first job — before building a portfolio. You do not need it. Honest, clearly labelled practice work is legitimate portfolio material:

• Coursework and bootcamp projects. A course project you completed yourself, presented with your own explanation of the problem and your decisions.
• Redesigns and spec work. A redesign of a real website or app, labelled clearly as an unsolicited concept, with before-and-after reasoning.
• Personal projects. A small tool, a writing sample, a photo series, a mock brand — anything finished and presentable.
• Volunteer work. A flyer for a community group, a website for a local nonprofit, a spreadsheet system for a small business. Real users, real constraints, real evidence.
  The rule is honesty: label learning work as learning work. Never present a class exercise as client work, and never invent results, clients, or testimonials. A hiring manager who discovers one invented claim will doubt everything else on the page.

Step 4: Turn each project into a short case study

A screenshot without context is decoration. A case study is evidence. For each project, write four short sections:

1. The problem. What needed to be done, and for whom? One or two sentences.
2. What you did. Your role, the tools you used, and the key decisions. Be specific: “designed a three-page site in Wix and wrote all the copy” is useful; “worked on a website” is not.
3. The result. What happened, in honest terms. If it was coursework, the result might be “completed the project and received instructor feedback” rather than a business metric. If a real project improved something measurable, give the number — but only if you can verify it.
4. What you would do next. One sentence showing you can evaluate your own work.
   Keep each case study to roughly 150–250 words plus images. The reader should understand the project in under a minute.

A project-description template you can reuse

Project: [Name of the project]
Type: [Coursework / personal project / volunteer work / client work]
Role: [What you personally did]
Tools: [The tools you used]
The problem: [One or two sentences]
What I did: [Three or four bullet points, most important first]
Result: [What happened, honestly stated]
Link: [Live link, code, or document — whatever the reader can open]
Fill in this template for every project before you touch the builder. Writing first and designing second keeps the portfolio focused on substance instead of decoration.

Step 5: Add the pages every portfolio needs

A portfolio is more than a gallery. These pages turn visitors into replies:

• Home. Your name, what you do, and your three best projects. A visitor should understand you in five seconds.
• About. Two or three short paragraphs: who you are, what you are looking for, and one human detail. Skip the life story.
• Work or projects. The case studies from Step 4, each opening onto its own page or section.
• Resume. A link to your resume as a PDF or a page. Pair it with our guide on how to write an ATS-friendly resume so the document and the portfolio tell the same story.
• Contact. An email address and one or two professional profiles, such as LinkedIn. A contact form is helpful, but an email link is enough to start — never publish a personal phone number on a public portfolio.

Step 6: Add proof without inventing it

Trust signals help, but only real ones. Use what you actually have:

• Testimonials from real people you worked with — a teacher, a volunteer coordinator, a client — quoted with their name and role, and only with their permission.
• Links to live work rather than screenshots alone, so the reader can verify it exists.
• Certificates from courses you completed, linked to the issuer’s verification page where one exists.
• A short “currently” note, such as “Currently open to entry-level design roles,” which tells the reader you are active.
  Do not add fake testimonials, invented client logos, or statistics you cannot support. One invented claim can cost you the opportunity the portfolio was built to win.

Step 7: Launch checklist

Run through this list before you share the link anywhere:

• Every link works. Click each project link, the resume link, and the contact email yourself.
• It works on a phone. Most recruiters open links on mobile first. Check that images load, text is readable, and nothing overlaps.
• Images are compressed. Large photos slow the page down. Export images at a reasonable size before uploading.
• Your name is on the page. The browser tab title and the homepage should both show your name and what you do.
• Spelling checked. Read the whole site once aloud, or paste the text into a spell checker.
• No placeholder text. Remove every “Lorem ipsum” and sample project the template came with.
• Contact information tested. Send yourself a test message through the form, or click the email link to confirm it opens correctly.
• Shared in the right places. Add the link to your resume, your LinkedIn profile, and your email signature — and to applications for legitimate remote jobs where a portfolio is requested.

Frequently asked questions

How many projects should a beginner portfolio have?
Four to six strong pieces is a good target, and three excellent ones are better than six uneven ones. You can add more as you finish new work.
Can I use coursework in my portfolio?
Yes, if you label it honestly as coursework or a personal project and explain what you did. Employers value the thinking behind the work, not only whether someone paid for it.
Do I need a custom domain?
Not to start. A free subdomain is fine while you are learning and applying. A custom domain looks more polished and is worth the small annual cost once the portfolio is earning you interviews or clients — and every paid plan above offers one.
How long does it take to build?
Most people can publish a solid first version in a weekend: a day to write the case studies, a few hours to build the pages. Expect to keep improving it — a portfolio is never finished, it is maintained.
Should my portfolio and resume say the same thing?
They should agree, not duplicate. The resume lists roles and skills; the portfolio proves them with examples. Keep dates, job titles, and skills consistent across both.

The bottom line

A professional portfolio without coding is a weekend project, not a technical one: pick one platform and stop comparing, choose four to six honest pieces of work, write a short case study for each, add an about page and a working contact method, and test everything on your phone before you share the link. The platform matters far less than the clarity of the work on it — so publish the simple version now and improve it as you finish new projects.