1. LandOffer
  2. Blog
  3. All articles
  4. UXfolio Review: Case-Study Guidance, Paid Publishing, and Recruiter Access

Job search

UXfolio Review: Case-Study Guidance, Paid Publishing, and Recruiter Access

UXfolio's trial supports drafting, while publication requires paid access. A completed case rewrite and two hosting-cost decisions separate useful guidance from unsupported claims.

10 min readLandOffer team

UXfolio is worth considering when you want help structuring UX case studies and hosting the finished portfolio. Its free trial supports drafting; publishing requires paid access. Use its guidance to explain evidence you already have; do not treat a writing prompt as evidence that a project achieved a result. Section guidance, templates, and AI can help organize a case, but they cannot establish your individual contribution or prove a business result. Pay when the writing workflow fits and you need the public deliverable for a defined period.

LandOffer publishes this review and provides recent job discovery, so we have a commercial interest in job-search resources. We checked UXfolio's public pages on October 13, 2026. This is a documentation review, without an account, trial, generated case, purchase, or hosted-portfolio test. Rae and Tomas are fictional candidates; their project facts and buying decisions below are teaching examples, not testimonials or measured hiring outcomes.

A bookbinder aligns draft case-study pages before binding a portfolio, illustrating that writing a case and publishing it are separate tasks.

Use the trial to evaluate the writing workflow

The production pricing page lists a seven-day trial without a credit card, unlimited draft portfolios and case studies, and four AI actions: two case-study attempts and two Job Fit Checker attempts. Its FAQ excludes publishing, domain purchases, and review collection during the trial. “Free to start” therefore does not mean a free portfolio link ready for applications.

Use that boundary to choose a small evaluation. Bring one project you may share, with notes about the problem, your role, a decision, and the evidence available. Work through a representative case section before moving an entire archive. Judge whether the structure helps explain the decision in your project. A section you cannot support with facts does not need an invented answer.

For Rae, that representative section is a developer-console API-key setup flow. She already has permission to show the practice prototype and research summary in this fictional case. Her trial task would be to explain one confusing empty state and the resulting design decision. She does not need five finished case studies to judge whether this kind of writing support fits.

Do not schedule an application around an unpublished draft. If a recruiter needs a working link tomorrow, the trial's editing capability does not satisfy that requirement. You would need to decide on paid publication and inspect the actual public result, or keep an existing suitable portfolio. A new editor is useful only if the resulting deliverable can meet the application instructions.

Understand what case-study guidance can contribute

UXfolio's homepage describes guided sections with optional AI, customizable templates, thumbnail tools, prototype and media embedding, and hosting. It also advertises responsive presentation. These are vendor descriptions; we did not measure editor usability, output quality, mobile behavior, or recruiter preference.

Guidance can be valuable when you have the evidence but struggle to arrange it. A case that jumps from “we did research” to a polished screen needs the missing decision explained. Which problem did the research reveal? What alternatives did you consider? Why did this change follow? Answering those questions lets a reader connect the research observation to the design change, rather than guess why the final screen looks different.

It is less helpful when the missing piece is the project itself. A prompt asking for impact cannot supply a measurement nobody collected. A polished paragraph cannot turn a team result into your individual work. When a section does not fit the project's evidence, explain the limitation or leave out the unsupported claim rather than manufacturing a conventional success story.

For the same reason, a Job Fit Checker should be an aid to reviewing relevant work, not permission to rewrite your history. If a role needs design-system governance and your case concerns one API-key flow, the gap may be real. You can explain the relevant interaction decisions clearly while preserving the difference between that work and system-wide ownership.

Rae replaces an unsupported outcome with a defensible case

The following passage is an invented editing exercise, not output we obtained from UXfolio:

I led a complete developer-platform redesign that increased activation by 35% and transformed the onboarding experience.

Rae's fictional project notes support something narrower. A researcher moderated five sessions, Rae synthesized the notes and designed prototype changes, and an engineer reviewed technical constraints. Two of the five participants initially found the next setup step without help. The empty-state and next-step revisions have not been retested, and no production activation data was collected.

Draft claim Evidence in the fictional notes Completed correction
Led the complete platform redesign Rae owned synthesis and two prototype states Name that contribution and the collaborators
Activation increased 35% No production metric or post-change test Remove the percentage
Transformed onboarding Five sessions identify a specific next-step problem Explain the problem and proposed change
Improved the user experience Revised prototype not yet retested State the evaluation still needed

Rae's finished opening reads:

Making test-key setup understandable. I synthesized notes from five moderated sessions and redesigned the developer console's empty state and next-step guidance in a prototype. A researcher moderated the sessions, and an engineer reviewed the constraints around test credentials.

In the initial sessions, two participants found the next setup step without help. I proposed an inline example and a clearer distinction between creating a test key and making the first request. The revised prototype has not been retested, and we have no production activation result to report.

The correction preserves useful work. Rae can show the original confusion, the design alternatives, the selected prototype change, and the constraints raised by engineering. She can explain why she chose an inline example instead of adding another introductory screen. A missing outcome figure can feel like a weakness, but Rae can discuss the decisions she actually made without adding an invented percentage.

The small session count also changes the interpretation. Two of five is a description of those sessions, not a population estimate of all developer behavior. Rae can use the observations to motivate a design hypothesis, but a case study should not turn five participants into a universal product conclusion. Further evaluation remains a concrete next step in the project.

This is where a structured editor could help: placing the observed problem, personal contribution, proposed change, and unresolved evaluation in a readable sequence. Whether UXfolio makes that work easier for Rae remains a trial question. The completed asset here is the corrected narrative, not a tested claim about the product's AI quality.

An editorial proof crosses out an unsupported 35% lift claim and replaces it with No retest yet, explicitly labeled as a fictional example.

Compare the charge with your hosting period

UXfolio's current pricing lists US$15 billed monthly or US$108 billed annually, equivalent to US$9 per month. The page says both paid plans have the same benefits, including public portfolios and cases, password protection, domain support, and removal of UXfolio branding. The annual figure is an upfront annual charge, not a US$9 monthly subscription.

Rae and Tomas make different completed choices under those base prices. These are hypothetical purchases; we did not enter checkout. The arithmetic excludes taxes, promotions, and domain charges that are not established for their accounts.

Candidate's stated need Monthly base cost Annual base cost Completed choice
Rae needs two months of public access while evaluating a new workflow 2×US$15=US$30 US$108 upfront Monthly; the shorter planned period costs US$78 less
Tomas expects to keep the portfolio hosted for twelve months and accepts the commitment 12×US$15=US$180 US$108 upfront Annual; US$72 less under the stated assumptions

The same features do not make the same billing period suitable for everyone. Rae values the smaller initial commitment while deciding whether to keep the workflow. Tomas has a longer stated hosting need. Neither decision assumes a subscription will produce interviews, and neither should be described as the cheapest choice without the period attached.

The period may extend beyond submitting applications. A link can remain in a recruiter conversation or an application record after your immediate search activity slows. Decide how long you intend to maintain it rather than treating the day you press Apply as the end of the hosting need. This is a planning consideration, not a measured claim about when recruiters open portfolios.

If you already maintain a clear, accessible portfolio elsewhere, changing tools may add little. UXfolio's case structure and hosting convenience need to solve a real problem for you. Compare the work required to move cases and maintain the new site with the specific help you need, rather than buying because the annual monthly equivalent looks small.

Read the terms around content, AI, and renewal

UXfolio's posted terms, whose standard section displays February 16, 2024 and AI section April 2, 2025, describe automatic subscription renewal and say cancellation does not automatically create a refund. They provide an initial three-day refund-request window; later requests are discretionary under stated service-problem conditions. Domain renewal is separate and can occur on another date. Record the actual charge and renewal dates before subscribing.

The same page grants UXfolio marketing-use rights for publicly displayed content, excluding drafts and password-protected projects, with a consent-withdrawal route. Its AI terms license inputs and outputs to operate, maintain, and improve the service and describe reasonable measures to remove direct identifiers. They also make accuracy review your responsibility and qualify paid “unlimited” AI use with reasonable-use limits.

Those are vendor terms, not a prediction about enforcing a refund or a certification of confidential-data handling. If you would be uncomfortable submitting a research note or client artifact under those terms, resolve that before using it as input. A password on a case page does not decide whether you may upload the underlying material or use it in an AI feature.

For Rae's teaching case, the input can stay small: permitted prototype details, her actual contribution, the five-session observation, and the absence of a retest. She does not need to submit an entire research archive to ask for a clearer paragraph. She would compare any generated wording with those facts before accepting it.

Make recruiter access a separate acceptance check

UXfolio's case-password instructions require a published case, then Portfolio editor, the thumbnail's Options menu, and Set password. They warn that a logged-in owner is not prompted and recommend an incognito check. An owner opening the case successfully is therefore insufficient evidence that a recipient encounters the intended access path.

Choose the public summary deliberately. It should identify the project, your role, and why the case matters without revealing material that belongs behind a permitted restriction. If a protected case is appropriate, follow the employer's instructions for supplying access. Do not include account credentials; a case password is a different item from your editor login.

For Rae, a public summary can describe the API-key setup problem and her synthesis/prototype contribution. The fuller case would contain only material she is permitted to share. If permission does not cover an artifact, she leaves it out rather than assuming a password cures the restriction. That decision comes before the hosting setting.

Then inspect the exact link from outside the owner session on a phone and desktop. Check whether the introduction, role, main visuals, and limitations are readable, and whether any embedded prototype has its own access requirement. These are proposed acceptance checks; we did not perform them on a UXfolio-hosted portfolio. The responsive marketing claim is a reason to evaluate the result, not proof that every chosen embed will work.

Choose it for a specific writing and hosting need

Consider UXfolio if guided case writing and integrated hosting address a problem you actually have. Use the trial for one representative case, keep unsupported outcomes out, and choose the paid period from the access you need. Keep an existing portfolio if it already communicates your work clearly and is easy for the intended reader to open.

For the next step, choose one relevant role and identify the contribution your lead case can demonstrate. You can browse recent roles on LandOffer.ai or use an opening already in your search. Finish one case opening that names your contribution and the evidence available. If the opening needs a claim you cannot support, revise it before adding more cases or paying to publish. LandOffer does not assess your portfolio, verify UXfolio's output, or guarantee a recruiter response.

Sources and Further Reading