01 — Differences in a table
| Aspect | Web Designer | Web Developer |
|---|---|---|
| What they decide | Layout, visual hierarchies, typography, palette, micro-interactions, user journey, visual identity. | Tech stack (framework, database, hosting), performance, security, integrations, code architecture. |
| Primary tools | Figma, Sketch, Adobe XD, browser DevTools, Lighthouse (visual side). | Code editor, terminal, Git, frameworks (React, Next.js, Vue), DevOps, monitoring. |
| Output | Figma files, design system, clickable prototype, exported assets, brand guidelines. | Working deployed code, Git repository, technical documentation, infrastructure. |
| Limit when working alone | Beautiful designs the dev cannot implement (exotic 4MB webfont, layout that scrolls badly on mobile, interactions requiring heavy libraries). | Site that works but looks like a hackathon demo. Times New Roman typography, default Tailwind colours, UI ignoring the brand, UX decided 'by gut feel'. |
| What it costs you | Gorgeous design the dev (in-house or separate freelance) must adapt, simplify or reimplement. Painful hand-off, fidelity lost, two invoices. | Technically clean site indistinguishable from 50 others. You must pay a separate designer for personality, or stay generic. |
02 — Where the separation comes from
The "designer designs, developer codes" separation is a leftover from 2000s agencies, when the two worlds spoke different languages and tools didn't overlap.
In 2026 this division no longer holds. Modern tools (Figma with Code Connect, Tailwind, React/Vue components, tokenised design systems) have made the design→code handoff much smoother. Serious people in the field know both sides: a designer who doesn't understand what a media query is draws layouts impossible to implement; a developer who doesn't understand typography and visual hierarchy writes unreadable interfaces.
The reality is that the two roles have merged in modern freelancers. Agencies keep them separate because that way they can bill them separately. It's business, not technique.
03 — What the Web Designer actually does
The Web Designer decides how the site looks, reads, navigates. It's not "making things pretty": it's applied visual engineering.
What they concretely do: wireframes and mockups in Figma, typographic hierarchies (display, body, mono, modular scales), colour palette with WCAG-compliant contrast, systematic spacing (8/16/24px or equivalent), reusable design system components, micro-interactions (hover, focus, transition), responsive breakpoints, clickable prototyping, brand consistency.
What they DON'T do (in theory): write code, deploy, configure hosting, optimise database queries, integrate APIs, backend performance. In practice, modern designers know just enough not to draw impossible things.
04 — What the Web Developer actually does
The Web Developer turns the design into something that works, scales, and is secure.
What they concretely do: implements the design in code (HTML/CSS/JS or modern framework), picks the stack (React, Next.js, Vue, vanilla, WordPress headless or classic), configures database and APIs, integrates third-parties (payments, CRM, analytics), handles technical SEO, Core Web Vitals performance, security, deploy, hosting, monitoring, backup, long-term maintenance.
What they DON'T do (in theory): visual design, branding, copywriting, UX flow. In practice, modern developers refuse to work with poor designs and often "fix them on the fly".
05 — Why both-in-one works better (for small and medium projects)
For 90% of projects — brochure site, small/medium e-commerce, landing page, blog, portfolio — having one person doing both is objectively better.
1. No painful hand-off. The design is already conceived to be implemented. No "ah, this gradient can't be done". No "this font costs 800€ in licensing". Decisions made knowing how they end up in code.
2. One invoice, one point of contact. No discussions like "this isn't my fault, it's the designer/developer's". One person who designs, builds, and maintains.
3. Fast iterations. Want to change a component? The same person updates the Figma design and the code in half an hour. With two separate roles it becomes two meetings, two extra quotes, two weeks.
4. Coherence. A single brain makes coherent choices between layout and technique: performance and beauty aren't in conflict, they're part of the same job.
06 — When to pick two separate roles
Intellectual honesty: there are cases where two separate specialists are the right call.
Large complex projects: multi-tenant SaaS platforms, e-commerce with 300,000 SKUs, enterprise systems with ISO 27001 security audit, corporate design systems with 200+ components. There a single freelance isn't enough — you need a team, and inside a team specialisations make sense.
Brand identity from scratch for large companies: full branding (naming, positioning, visual system, brand book) is its own job that justifies a specialised brand designer. For projects under 100k€ though, "essential" branding is well-handled by a Designer-Developer.
Complex custom backend: distributed microservices, ERP-SAP-Salesforce integrations, machine learning. There you need a pure developer, ideally with a DevOps team. The designer limits themselves to admin/dashboard UI.
For everything else — brochure site, portfolio, e-commerce, blog, small platform — a single competent person is almost always the rational choice. Lower cost, faster timeline, zero hand-offs.