4.7/5 on Capterra
A UX portfolio website that shows the thinking, not just the screens
Case study pages, password protection for NDA work, and full CSS control. On your own domain.
15 days free trial · No card required
Case study pages, password protection for NDA work, and full CSS control. On your own domain.
15 days free trial · No card required
The basics
A UX portfolio website is a site on your own domain where each project is a case study rather than an image: the brief, the research, the decisions you rejected, and the screens you shipped. Hiring managers read it to work out how you think, not what you can render.
Most portfolio tools handle that badly. Gallery-first builders hand you a grid and a lightbox, which is the right tool for a photographer and the wrong one for a designer who needs a thousand words of process under each project.
Why Pixpa
Pages, not just galleries
A full page builder with content blocks for text, images, video and embeds, plus custom CSS and HTML on every plan for when the editor runs out.
Password protection on any page
Lock an NDA case study and give the password to one recruiter. Available on all plans, on individual pages or the whole site.
Your own domain
A free custom domain for the first year on annual billing, or connect one you already own.
Support answered by a person
Live chat, 24/7, staffed by people who use the editor.
“Almost non-existent learning curve. Learning how to build your own website was almost instant.”
Case studies
Every project gets its own page and its own layout. Stack a hero frame, three paragraphs on the research, a wireframe sequence, an annotated before and after, then the metric that moved. Reorder any of it by dragging.
Custom CSS ships on every plan and custom HTML is available in the editor, so a Figma prototype, a Loom walkthrough or a scroll-triggered interaction goes in as an embed rather than a screenshot of one.
When the case study runs long, split it across pages and link them.
Honest answer
Designers ask this one first. Custom CSS ships on every plan, so you override a template rule instead of working around it, and the HTML is editable in the editor. Type scale, spacing, grid and block order all change without touching code, and desktop and mobile can be styled separately. A template is a starting point you can switch later without losing content, not a container you’re locked into.
Under NDA
Most senior UX work is under NDA, and the usual workaround is to describe it vaguely and hope the reader fills the gap. They don’t.
Pixpa supports password protection on individual pages and on whole sites, on every plan. Put two open case studies on the public site, keep the fintech redesign behind a password, and send that password to the hiring manager who asked for it. When the process ends, change it.
For work you’re delivering rather than showing, client galleries add access controls, activity tracking and auto-expiry on a set date.
Why not Dribbble
Behance and Dribbble get you seen. They don’t get you a domain, a case study longer than a caption, or a password on the work under NDA. They also rank for their own name, not yours.
Most designers run both: the shots go on Dribbble, the case studies live on a site they own, and the profile links out.
Examples
Live sites from UX designers, UI designers and product designers. Open any of them and check the thing that matters: how the case study reads on a phone.
Design
Pixpa has 200+ templates in the library and 18 filtered for UI and UX work. They’re built around long-form project pages with a lot of white space, not around image density.
Nothing about a template is fixed. Move any block, change the type scale, write custom CSS, edit the HTML. Switch templates after the site is live without losing content.
If you sell UI kits, icon sets or design courses, the store handles digital downloads on the same site, and Pixpa’s commission on every sale is zero.
“Wonderful design templates, easy to use and manage content, flexibility to alter default template settings.”
Step by step
Six steps. Roughly a weekend if the case studies are already written.
Pick three projects.
Three deep case studies beat nine thin ones. If you can’t explain a decision you made on a project, it isn’t ready to go on the site.
Write the case studies before you touch a builder.
Problem, constraint, what you tried, what you shipped, what it changed. The writing is the hard part and no template fixes weak writing.
Choose a template.
Filter to UI and UX work, then judge it on how a long text block reads, not on the homepage hero.
Build one case study page end to end.
Get one right, then duplicate it. Consistent structure across projects is what makes a portfolio scannable.
Lock the NDA work.
Set a password on those pages, and write a one-line public summary that says the study exists and how to request access.
Connect your domain and set the metadata.
Use the SEO Manager to write page titles and descriptions before you share the link, then send it.
15 days free trial · No card required
Standards
Six things separate a portfolio that gets a callback from one that gets a scroll. None of them are about visual polish.
Lead each case study with the outcome.
Someone working through a stack of applications decides whether to read your project from its first line, not its third paragraph. Put what changed there: the metric, the launch, the decision that got reversed. The research narrative earns its read after that, not before.
Three case studies, not nine.
Volume reads as an archive. Three projects you can defend in an interview reads as judgement, and judgement is the thing being hired. Anything you would not want to be questioned on for twenty minutes should come off the site.
Show the work you rejected.
The rejected direction is the only part of a portfolio that proves a decision was made rather than stumbled into. A UI gallery shows the final screen. A UX portfolio shows the two you killed and why. This is the single clearest separator between the two, and most portfolios skip it because the rejected work is ugly.
Write it so a non-designer can follow it.
The first screen is often a recruiter or a hiring manager from another function. Jargon that signals competence to another designer reads as noise to them. Define the constraint in plain language before you name the method.
Don’t make the prototype the load-bearing element.
Embedded Figma prototypes are slow on mobile, break when a file moves, and fail entirely behind some corporate firewalls. Lead with static frames that carry the argument on their own, and put the live prototype below as a bonus rather than the proof.
Say what role you want and how to reach you.
“Open to senior product design roles, UK or remote” removes the one question that stops people getting in touch. Ambiguity reads as unavailability.
The rejected-work point is where most UX portfolios lose the callback, and it costs nothing to fix.
FAQs
Everything else you might want to know before you start. Still curious? Live chat is open 24/7.
Three is the working standard for most roles, four at the top end. Each one needs a defined problem, your actual contribution named separately from the team's, and an outcome. A fourth thin case study weakens the three strong ones next to it.
Put the case study on a password-protected page and give the password only to the people who ask for it. On Pixpa, password protection works on individual pages and on whole sites, on every plan. On the public site, leave a one-line summary saying the study exists and how to request access.
Pixpa has a 15-day free trial with no credit card required and a 30-day money-back guarantee after that. There's no permanent free plan. Free portfolio hosts exist, but they put their own branding on your work and keep the domain, which means the site you spent a weekend on is advertising someone else.
No. You start from a template and change what you want to change. Custom CSS ships on every plan and the HTML is editable if you want it, but a full case-study site can be built without touching either.
A UI portfolio shows finished interface work and is judged on craft. A UX portfolio shows the reasoning that produced it and is judged on decision-making. Most designers need one site that does both: the screens carry the craft, the case study carries the reasoning.
Long enough to show the decisions, short enough that someone reads it. The strongest ones carry the argument through annotated images and captions rather than long paragraphs, so the reader can follow the reasoning by scrolling. If a section doesn't change what the reader thinks of your judgement, cut it.
It depends on what else the site has to do. UXfolio is the tightest fit if a portfolio is the only site you'll ever need. Framer and Webflow give the most control and cost the most setup time. Pixpa is the faster route if you want case studies, a blog and a store on one domain, with password protection on any page.