Build a UX designer
portfolio from your resume.
The fastest way for a UX designer to build a portfolio website is to paste an existing resume into Folio, which reads your roles, skills, and tools and drafts a clean first version of the site in about a minute. You then give each project the arc a reviewer wants, the problem, the research, the iterations, and the measured outcome, choose a design with room for long-form narrative, and publish to your own domain. It is a better fit than a generic drag-and-drop builder because it starts from your resume and produces a matched, ATS-safe resume alongside the site, which is the document that still clears the first screen for most UX roles.
Three ways to build it.
A UX designer can build a portfolio by hand, in a generic website builder, or by pasting a resume into Folio. Here is how the three compare on the things that matter to a design applicant.
| What a UX designer needs | By hand | Generic site builder | Folio |
|---|---|---|---|
| Time to first draft | Hours to days | An evening of setup | About a minute |
| Built from your UX resume | No, you write it all | No, an empty canvas | Yes, paste and go |
| Room for long-form case studies | If you design it that way | Possible, but you build the layout | Custom pages built from blocks |
| Matched ATS-safe resume | Separate tool | No | 48 layouts, live scoring |
| Unfinished case kept private | If you build drafts | On some paid plans | Draft pages stay off the site |
| Custom domain with TLS | Manual hosting setup | On paid plans | On paid plans, TLS automatic |
| Coding needed | Often yes | No | No |
| Reads on the first crawl | Depends how you host | Often client-rendered | Server-rendered HTML |
A generic builder is the right call if you want to hand-craft a bespoke visual layout and enjoy building it. For a resume-driven case-study site done in a minute, that is what Folio is for.
From resume to site, for a UX designer.
The build is the same paste-and-edit flow, with the case-study structure a UX designer needs already in place. Here is the exact sequence.
Drop in your UX resume or a LinkedIn export. The draft picks up your headline, roles, key results, and links, and you review every field before it is saved.
You get a headline, an About section, your experience, draft key results, and links, each taken from what your resume actually says. Nothing is saved until you review it.
Add the problem, the research, the flows and wireframes, and the outcome to each project, then pick a design with room for the narrative.
Publish at portfolio.wrxstack.com/yourname, or on a paid plan connect your own domain and Folio issues TLS automatically. The pages ship as real HTML a recruiter or an AI answer engine can read.
The same paste also produces a matched resume with a live ATS score, which is the document most design teams screen first.
Words to keep in the resume.
The builder produces a resume as well as a site. Make sure the skills a design hiring manager searches are present in it, in the exact terms they use, and tailored to the posting.
Run the finished resume through the free ATS score checker against a real posting before you apply.
Designs that suit a UX designer.
Of the 74 designs and 48 resume layouts, these are the ones to reach for, and the ones to skip, for a case-study-led site.
A design that gives each project its own page and lets text and images alternate in reading order. It carries the problem, the process, and the outcome without the story running out of space.
A grid of thumbnails fronts the visuals and leaves your reasoning nowhere to live. It suits a visual portfolio, not a UX one, where the thinking is the thing being hired.
A two-column resume can parse into a scrambled order in an applicant tracking system. A single-column layout keeps your experience in reading order when it is screened.
A domain like yourname dot design reads as more established than a free subdomain and is easy to drop into an application, a portfolio field, or a message to a recruiter.
When the builder is the wrong tool.
Folio is a resume-to-website builder, not a fit for every UX situation. Here is where it helps and where a different route wins.
Use the builder if you
- +Already have a UX resume and want a case-study site from it without an evening of layout work.
- +Have projects with a problem, a process, and an outcome you can write up honestly.
- +Have NDA work and want a way to show your thinking without publishing the confidential parts.
- +Want the matched ATS-safe resume the same paste produces.
Choose another route if you
- −Want pixel-exact control of a bespoke, animated, or highly art-directed site. A code-first or design-first build suits that better.
- −Have no case studies you can show and no time to build one from a redesign or self-directed project.
- −Have no resume yet to draft from. Write one first, then paste it in.
- −Are on a deadline. Fix the resume for the ATS first, then build the site after.
Building a UX site.
The practical questions UX designers ask before they build.
What is the best portfolio builder for a UX designer?
The best builder for a UX designer is one that starts from your resume and gives each project a case-study page with room for research, iterations, and an outcome, because that is how a reviewer reads. Folio does this and produces a matched, ATS-safe resume alongside the site. A generic drag-and-drop builder can also work if you are willing to construct the case-study layout yourself and do not need the resume.
Do I need to know how to code to build a UX portfolio?
No. You paste your resume, write out each case study, choose a design, and publish. Folio handles hosting and the TLS certificate for your custom domain. There is no HTML or CSS to write, and no template to wrestle into shape, which leaves your time for the writing that actually gets you hired.
How do I show a confidential project?
Keep it off the public site. Folio does not offer password-protected pages, so publish an abstracted version that names no unreleased feature, internal metric, or real user, and walk a reviewer through the full case on a call or in a document you send on request. That keeps confidential work off the open web while still letting a hiring manager see your best thinking.
Can I connect my own domain?
Yes, on a paid plan, and Folio issues the TLS certificate automatically. On the free plan your site publishes at portfolio.wrxstack.com/yourname. A domain in your own name reads as more established than a free subdomain and is easy to add to an application, a portfolio field, or a message to a recruiter.
How long does it take to build a UX portfolio?
The first full draft appears in about a minute after you paste your resume. The real work is writing the case studies, and that is where a strong portfolio is won or lost, so budget a few evenings to do the problem, research, iterations, and outcome justice. On a paid plan, connecting a custom domain adds a few minutes while DNS propagates.
Keep going.
See what to include, test your resume, or read the full product.
Showing the thinking, not just the screens.
A UX designer is hired for judgement, and judgement is invisible in a final comp. The whole job of the portfolio is to make the reasoning visible: how you moved from a messy problem to a decision you can defend, and what happened when it shipped.
The mistake most UX portfolios make
They lead with the outcome and skip the argument. A grid of polished screens tells a reviewer you can operate a design tool, which is table stakes, and nothing about whether you can think. The screens that got cut, the research that redirected the work, the constraint you designed around, that is the part a hiring manager is reading for. Show the messy middle, not just the tidy end.
Start every case with the problem, not the solution
Open with the real problem and the business goal behind it, then the constraints you worked inside. A reviewer cannot judge a design decision until they know what boxed it in: the deadline, the platform, the legacy system, the users you could not reach. A smart decision under a hard constraint reads as smart. The same decision with no constraint stated reads as arbitrary.
Make the research do real work
Say what you did and what it changed. Five user interviews, a round of usability testing, a heuristic evaluation, a look at the analytics, then the one or two findings that redirected the design. A reviewer wants to see that your choices came from evidence, not taste alone. Even a small, honestly reported study beats a page that claims research happened but never shows it moving anything.
Show the iterations you rejected
The versions you discarded are more persuasive than the one you shipped, because they prove you explored the space and had reasons to choose. A before and after with a single line on what the change fixed does more than a gallery of final frames. Let a reviewer watch the design get better, and they will trust that the final version is considered rather than lucky.
Close with the outcome, and be honest about it
End each case with what changed after it shipped: task success, conversion, activation, retention, a drop in support tickets, a usability score. If the number is confidential, describe the direction and rough size without breaching the NDA. A case study with no result is a mockup. One with an honest result, even a modest one, is a project a hiring manager can weigh.
State your role without inflating it
On a team project, say exactly what you owned and what a colleague led. Research, information architecture, interaction design, the prototype, the design system contribution, the engineering hand-off. Reviewers interview around vague claims, and a role that does not hold up in the room costs you the offer. Precise ownership of a smaller slice reads better than fuzzy credit for the whole thing.
Protect confidential work, and let the fix show your judgement
Do not put unreleased features, internal metrics, or real user data on the open web. Keep the full case off the public site and share it privately on request, or abstract the work so nothing identifiable remains. Handling an NDA well is itself a signal: it tells a hiring manager you can be trusted with a company's confidential work, which is part of what they are deciding when they read your site.
Let the resume carry the keywords the site cannot
The portfolio persuades a human; the resume clears the applicant tracking system first. Keep the skills a design team searches in the resume in their exact terms, UX design, user research, usability testing, prototyping, Figma, design systems, tailored to each posting. The same paste that builds the site produces that resume, so the two stay in step and neither one carries the whole load alone.
Paste a resume.
Get a UX site.
Start free. Drop in your UX resume and get a case-study-led website plus a matched ATS-safe resume in about a minute. Add the research and outcomes, keep NDA work off the public page, and connect your own domain on a paid plan when you are ready.