What this article is about
UX design vs web design — what each discipline actually covers, where they overlap, where they diverge, what each is good for, and how to know which one your business needs at a given stage. Even-handed and practical. Written for owners who want to commission the right work for the problem they actually have, rather than the work the word “designer” happens to suggest.
Most business owners, when they say they need “a designer for the website,” mean something slightly different from what whichever designer they hire will deliver. The conversation gets tangled because UX design and web design are often used interchangeably — by clients, by recruiters, sometimes even by practitioners themselves. The result is a recurring pattern of mild disappointment: a website that looks beautiful but does not quite work, or a website that works well but lacks the visual presence the brand needed.
The two disciplines are related, overlapping, and both genuinely valuable. They are not the same. Understanding where they diverge is one of the most practical things an owner can do before commissioning any digital work, because the difference between hiring the right discipline and the wrong one is usually the difference between a satisfying outcome and a frustrating one.
Why the Terms Get Confused
Part of the confusion is historical. Twenty years ago, “web design” was a single role that covered most of what now gets split between several disciplines. The web designer chose the layout, drew the visuals, often wrote the code, and tried to make the site usable along the way. As the web grew more complex, the role specialised. Visual craft remained with web design. Research, structure, and interaction logic gathered into UX design. UI design emerged as its own thing. Front-end development separated from design entirely.
Each of these specialities is now its own profession, with its own training, its own portfolio conventions, and its own pricing. The trouble is that the language has not kept up. Many small studios still describe themselves as “web designers” while doing UX work; many freelancers describe themselves as “UX designers” while doing mostly visual design. The titles, in practice, are unreliable. What matters is the actual work, and being able to recognise which kind you are commissioning.
What Web Design Actually Covers
Web design, properly defined, is the visual and compositional design of a website. It encompasses the look and feel — typography, colour, imagery, layout, hierarchy of visual elements, page composition, the texture and personality of the brand expressed on screen. It is the discipline that turns a structure into a designed surface.
A web designer’s strengths are visual: a sense of proportion, an eye for typography, an instinct for how images and white space carry a brand, the craft of moving between aesthetic references and a finished page. Their working materials are colour palettes, type systems, photography direction, illustration style, layout grids, and the dozens of small visual decisions that combine into the impression a website makes.
A good web designer can take a content structure they did not invent and produce a website that looks confident, distinctive, and aligned with the brand. They can adapt a visual system across many pages and devices. They can solve the kinds of problems where the answer is “this layout is not working” or “the typography feels generic” or “the visual hierarchy is competing with itself.”
What web design does not typically cover, in the modern definition, is the structure underneath the visuals, the research into who the visitors are, or the testing of whether the design works for the people using it. Those belong to the adjacent discipline.
What UX Design Actually Covers
UX design — user experience design — is the design of the experience a person has when interacting with a product, service, or website. Its scope is wider than the visible interface. It begins before the visible work and continues after launch.
A UX designer’s work includes research into who the users are and what they need, definition of the structure and flows that will serve those needs, design of the interactions and screens that make the structure usable, and testing of whether the design works for real people. It is concerned with the journey, not just the page — what happens before the user arrives, what they are trying to do once there, what happens after they leave.
The materials of UX design are different from those of web design. Research transcripts, journey maps, personas, sitemaps, wireframes, interaction specifications, usability test reports. The output is often not visual in the polished sense — it is structural. A UX designer who never touches a colour palette has still done UX design.
A good UX designer can take a vague business problem and turn it into a clear, tested experience. They can identify why a website is failing and what kind of failure it is. They can solve problems where the answer is “users do not understand what this section does,” “the flow has too many steps,” or “we are designing for an audience we have never spoken to.”
What UX design does not typically cover, on its own, is the visual finish that gives the experience its character. A UX deliverable handed to a developer without a visual designer involved tends to produce a site that functions but does not particularly feel like anything.
Where the Two Overlap
The overlap between web design and UX design is, in practice, the visible website itself. A finished website is the product of both disciplines working — knowingly or not. The structure that UX defines becomes the layout that web design composes. The interactions that UX specifies become the visual cues and components that web design renders. The site cannot exist without both contributions.
This overlap is part of why the disciplines get conflated. The user, encountering a website, has no way of knowing which design decisions came from which discipline. The owner, looking at the finished product, sees a single thing. The conflation is forgivable. It is just expensive when it leads to commissioning the wrong work for the problem.
A well-built website project usually involves both: a designer or team who attends to the structure, flows, and usability (UX), and a designer or team who attends to the visual character and composition (web/visual design). Sometimes one person does both, especially at small scale. Sometimes the two are entirely separate roles. Either model works. Neither role missing entirely tends to work.
Where They Diverge
The diverging edges of the two disciplines are where the differences become clearest.
UX extends backwards into research and forwards into measurement. A UX designer is interested in who the user is and what success looks like long after the site launches. They will design for behaviour change over months. A web designer’s involvement typically ends much closer to launch — once the visual system is delivered and applied, the work is done.
UX extends across non-visual channels. Mobile apps, internal tools, hardware interfaces, customer service flows, voice interfaces — all are UX domains. The web is one surface for UX, not its defining one. Web design, by definition, is concerned with the web specifically.
Web design extends deeper into visual craft. The level of attention to typography, colour, imagery, motion, and visual identity that a strong web designer brings is a specialised practice in its own right. A UX designer who is competent at visual work is rare; a UX designer who is excellent at visual work is unusual enough that the role usually becomes a hybrid one.
These divergences matter because they tell you what each discipline gets paid to do. A team without UX produces visually polished sites that may misalign with what users need. A team without strong web/visual design produces functionally sound sites that may lack character or distinction.
What Each Is Good For
Choosing which discipline a project needs is, in practice, a question of what problem the project is solving.
You need web design when: you have a clear sense of what your site needs to be and do, the structure is settled or simple, and what you need is for that structure to be expressed in a way that is visually confident and aligned with your brand. A brochure site for an established business. A relaunch of a clear product page. A visual refresh of an existing site whose structure works.
You need UX design when: you are not sure what your site should be or how it should be structured, you have an existing site that is underperforming and you are not sure why, you are launching a new product or service whose user journey has not been mapped, or you are scaling a digital product across new features and audiences. A complex service site where the flow matters. An e-commerce experience whose conversion is flat. A new app or interactive product.
You need both when: you are building a significant new website from scratch, or rebuilding one whose structural and visual problems are entangled. Most major web projects fall into this category, even if owners did not realise it when they commissioned the work.
You can sometimes get by with one when: the project is genuinely small and constrained, and one practitioner can responsibly handle both. This is more common at the smaller end of the market and rarer than its frequency suggests.
Why Hiring the Wrong One Produces Predictable Disappointment
The predictable failure modes are the things owners describe at the end of disappointing projects.
When UX is missing: the site looks great but customers do not behave the way the business hoped. Conversions are flat. The navigation does not quite work. The content lives in the wrong places. The owner is left wondering why “such a beautiful website” is not producing results. The answer is usually that nobody designed for what the user was actually trying to do.
When web/visual design is missing: the site works but feels generic. It does not stand apart from competitors. The brand does not come through. Visitors register the site as functional but unmemorable. The owner is left wondering why a site that “ticks all the boxes” feels flat. The answer is usually that nobody designed the surface with enough care.
In both cases, the project is not a failure of effort — it is a failure of scope. The wrong discipline was commissioned for the problem. Knowing what each one is responsible for is the simplest way to avoid that.
How to Know Which One You Need
A practical sequence for an owner uncertain about which discipline to engage.
First, name the problem. Is your concern about what the site should be and how it should work — its structure, flow, audience fit? That is UX territory. Is your concern about how the site should look and feel — its visual character, brand expression, polish? That is web design territory. If both, you need both.
Second, look at the practitioner’s actual portfolio, not their title. A “web designer” whose portfolio includes user research, sitemaps, and usability findings is doing UX work, whatever they call themselves. A “UX designer” whose portfolio is mostly polished visuals is leaning web design. The work is more honest than the label.
Third, brief for the discipline, not the deliverable. Telling a designer “I need a website” is brief enough to get you any kind of designer. Telling them “I need help understanding why our current site is underperforming, and then designing the structure of a better one” is a UX brief. Telling them “I have a defined site structure and need it expressed in a visual system aligned with our brand” is a web design brief. The right discipline often makes itself obvious from the brief.
The honest summary is that owners who can articulate which discipline they need tend to commission better work from both. Owners who cannot tend to receive work that solves the problem the designer found easiest to solve, which is not always the problem the business had.
Key Takeaways
- UX design and web design are related but distinct disciplines, often confused in practice.
- Web design covers visual craft — typography, colour, layout, imagery, the surface of the website.
- UX design covers experience — research, structure, flows, interaction, usability, the journey before and after the visible interface.
- The two overlap at the visible website itself; both contribute to a finished site.
- They diverge where UX extends into research and measurement, and where web design extends into visual craft and brand expression.
- Web design is the right choice when structure is settled and what you need is visual expression; UX is the right choice when the structure, audience, or flow is unsettled.
- Most significant projects need both; small projects can sometimes be handled by one practitioner.
- The wrong discipline for the problem produces predictable disappointment — beautiful sites that underperform, or functional sites that feel generic.
A note from SWL
Knowing the difference between UX design and web design is not academic — it is how owners commission the right work and avoid spending budget on the wrong solution to the right problem. If you are thinking about a new website or wondering why the current one is not quite landing, working out which discipline your situation actually calls for is a useful first step. We are happy to help you think through that whenever it would be useful.