Ux design portfolio examples

Most look like a short project index on the home page, then a dedicated page per case study. Three to five projects is the common range. The index carries a thumbnail, a project name, and a one-line framing of the problem. The case study pages run long and mix screens, diagrams, and written reasoning. Browse the live examples on this page to see the pattern across different specialisms.

Case studies with a stated problem and a stated outcome, a short About section that says what kind of work you want next, and contact details reachable from every page. Product design portfolios usually add more on constraints: what the business needed, what shipped, and what got cut. Process artefacts such as personas and journey maps are optional and rarely the reason someone gets hired.

Three to five, told properly, beats ten summarised. A reviewer scanning six candidates will open one or two case studies per portfolio, so the depth of the first project matters more than the total count. Cut anything you would not want to be asked about in an interview.

Speed to the argument. A good UX portfolio states the problem in the first screen of a case study, shows the constraint that made it hard, and names what changed. Weak portfolios open with a hero animation and put the reasoning four scrolls down. The strongest examples on this page share that pattern regardless of which template they started from.

A UI portfolio is judged on craft: type, spacing, colour, component systems, and how the screens hold together. It can carry more weight visually and less in writing. A UX portfolio is judged on reasoning and needs the written case study to work. Many designers ship one site that does both, leading with visual work and linking through to full case studies.

The framing shifts from user problem to business problem. Product design portfolio examples tend to lead with the metric that moved, the trade-off that was made, and the scope that got cut to ship. UX portfolios lean harder on research method. The site structure is usually identical: a short index, then long case study pages.

Most research roles ask for one, and it is usually harder to build than a designer's. Research portfolios carry method, sampling, synthesis, and the decision the work changed, with far fewer screens to show. Password protection helps here, because raw study material often cannot be published.

Yes. Pixpa includes password protection on whole sites or on individual pages, on every plan, so a case study can sit behind a password you share with a recruiter while the rest of the portfolio stays public. Designers also anonymise the client, blur real data, and describe the problem without naming the account.

Yes. Pixpa has a drag-in HTML, JS, CSS block plus page-level code injection on every plan, so a Figma embed code, a Framer prototype, a Loom walkthrough, or a CodePen drops straight into a case study page. Custom CSS is included on every plan too, so the template is a starting point rather than a fixed layout.