This debate never dies but I feel like 2026 is a different landscape with AI coding tools everywhere. Does it still make sense for designers to learn HTML/CSS/JS, or has the calculus changed? Curious what people think.
As someone who codes and designs, my answer is a qualified yes, but the reasons have shifted. Learning to code used to be about self-sufficiency, being able to build what you design without waiting on a developer. That’s still valuable, but now it’s more about understanding the medium you’re designing for.
When you understand how CSS flexbox actually works, you design layouts that are feasible and elegant to implement. When you know what JavaScript can and can’t do efficiently, you make better decisions about interactions and animations. That knowledge doesn’t require you to become a full-stack engineer. It just requires literacy.
The AI coding tools are actually an argument in favor of learning, not against it. Tools like Cursor and Copilot are most useful when you understand enough to guide them and evaluate their output. A designer who can look at AI-generated code and say ‘this CSS is going to break at smaller viewports’ is far more effective than one who has to accept whatever the tool produces.
That said, I don’t think every designer needs to write production code. But understanding how the web works at a fundamental level makes you a better collaborator with engineers and a more thoughtful designer. The question isn’t really ‘should you learn to code’ but ‘how deeply should you understand the technical medium you design for.’
I lean toward yes for web and product designers, and no for brand and print designers. The investment has to make sense for your specific practice. If you’re designing SaaS interfaces every day, understanding front-end code will make you more effective and more employable. If you’re designing packaging or book covers, that time is better spent elsewhere.
One thing I will say is that even a basic understanding of HTML and CSS changes how you think about responsive design. Before I learned to code, I designed static mockups at three breakpoints and called it a day. After understanding how the browser actually reflows content, I started designing systems that work at any width. That mental shift was worth the learning curve on its own.
I’m going to offer the contrarian take here. I think the pressure on designers to code has always been slightly overblown, and with AI tools in the picture it’s even less necessary than before. Your time as a designer is finite. Every hour you spend learning React is an hour you’re not spending improving your visual design skills, studying color theory, or learning about user psychology.
The designers I admire most are the ones who went deep on design, not the ones who spread themselves thin trying to also be developers. That said, I agree with @Thunderblossom that understanding the basics of how the web works is valuable. I just think there’s a big difference between ‘understanding CSS’ and ‘learning to code.’
The answer really depends on what you want to create. For me, learning JavaScript and working with libraries like GSAP and Three.js unlocked creative possibilities that I simply couldn’t access through design tools alone. Interactive motion, generative art, real-time visual experiments. These are things that live at the intersection of code and design, and they’ve become a core part of my practice.
But I came to coding because I was drawn to it creatively, not because someone told me I had to learn it for career reasons. And I think that distinction matters. If you’re learning to code because you genuinely want to expand your creative toolkit, go for it. If you’re doing it out of obligation or job market anxiety, you’ll probably burn out and resent the process.
The AI coding tools have lowered the barrier significantly. I can now prototype interactive ideas in a fraction of the time it used to take because I use AI to handle the boilerplate while I focus on the creative logic. So in a weird way, AI makes coding more accessible for designers while also making it less essential for basic implementation tasks. Both things are true simultaneously.
My suggestion: try building one small project that excites you. If you enjoy the process, keep going. If it feels like pulling teeth, that energy is better directed at what you’re already great at.
for web designers specifically, I think knowing HTML and CSS is almost non-negotiable at this point. Not because you’ll be writing production code, but because clients expect you to understand the environment you’re designing for. When a client asks ‘can we do this on our WordPress site?’ you need to be able to give an informed answer.
I use Webflow and WordPress daily, and my CSS knowledge saves me hours compared to designers who have to Google every layout question. But @pixelrage47 makes a fair point about not stretching too thin. I’d say learn CSS deeply, understand HTML structure, and maybe pick up enough JavaScript to customize existing components. Beyond that, it’s diminishing returns for most design roles.
Twenty-five years in design and I’ve never written a line of production code. Still have a successful career. Knowing the basics helps, but the idea that you need to code to be a good designer is a myth that mostly benefits employers who want to hire one person to do two jobs.
This thread perfectly illustrates why the answer is ‘it depends,’ and that’s not a cop-out. The designer-coder question sits at the intersection of several different factors: your design discipline, your career goals, your working context, and genuinely, your personal interests.
I learned to code specifically because I wanted to build interactive prototypes that felt real, not just clickable mockups in Figma. Being able to hand a developer a working prototype with real data flowing through it changed the way my design work was received. Developers trusted my designs more because they could see I understood the constraints, and product managers loved that the prototypes were testable before development even started.
But here’s what I think people miss in this debate: the goal shouldn’t be to replace developers. It should be to expand your vocabulary. When I learned enough React to build prototypes, I didn’t become a front-end engineer. I became a designer who could think in components, understand state management at a basic level, and communicate with engineers using their language. That’s an enormous professional advantage, especially in product design roles.
The AI angle is interesting too. I agree with @Velnix92 that AI tools make coding more accessible. I use Claude and Cursor regularly to scaffold prototype code that I then customize. Having foundational knowledge helps me steer those tools effectively. Someone with zero coding knowledge can also use them, but they’ll struggle to debug issues or evaluate whether the output actually makes sense.
My practical recommendation: if you’re a product or web designer, invest 3-6 months learning HTML, CSS, and basic JavaScript. Not to become a developer, but to develop technical literacy that makes you better at your actual job. Use that knowledge alongside AI coding tools and you’ll be able to prototype and experiment at a speed that would have been impossible even two years ago.
If you’re a brand designer, illustrator, or print specialist, skip it. Your growth is better served by deepening your core craft. There’s no universal answer here, and that’s perfectly fine.