I charged $40/hr for the first year I freelanced, then found out a designer with a thinner portfolio was charging $85/hr for comparable work. The difference wasn't skill. It was that their case studies stated a specific number: "reduced signup friction, conversion up 22%." Mine just showed pretty screens. I raised my rate the following month and lost exactly zero clients over it.
That's the real lesson buried under all the rate-guide numbers: the number matters less than what backs it up.
TL;DR: Junior UI/UX designers charge $35-60/hr in 2026, mid-level $60-120/hr, senior $120-200+/hr (goLance, 2026). Designers with outcome-based case studies charge 30-80% more than portfolio-only competitors at the same experience level.
What Are Realistic 2026 Rate Ranges?
Three tiers, and I'd trust these ranges over any single "average" number, since averages hide how wide the real spread is:
- Junior (0-2 years): $35-60/hr. Some markets show $30/hr at the floor.
- Mid-level: $60-120/hr, averaging around $78/hr.
- Senior (5+ years, strong specialization): $120-200+/hr, averaging around $138/hr, with top specialists reaching $230/hr or more (goLance, 2026).
Mid-range rates, roughly $55-100/hr, deliver the best value-to-quality ratio for most client budgets, which is exactly why that band is the most competitive one to price into. Under-price into that range and you're leaving money on the table; over-price without the case studies to back it and proposals go quiet.
| Tier | Experience | Rate range | Average |
|---|---|---|---|
| Junior | 0-2 years | $35-60/hr | n/a |
| Mid-level | 2-5 years | $60-120/hr | ~$78/hr |
| Senior | 5+ years, strong specialization | $120-200+/hr | ~$138/hr (top specialists $230+/hr) |
Why Do Two Designers With Similar Skill Charge Wildly Different Rates?
The single biggest lever isn't experience, it's whether your portfolio states an outcome. A designer with detailed case studies showing measurable results, a specific conversion lift, a specific drop in support tickets, charges 30-80% more than a portfolio-only competitor at a comparable skill level (Ruul, 2026).
I rewrote my own portfolio around this exact insight, using the same case-study structure I recommend for any design portfolio. Every project got one sentence stating what changed and by how much. Landed clients started referencing that sentence back to me in the first call, which never happened when the case study was just before/after screenshots with no number attached.
Hourly or Project-Based, Which Should You Actually Use?
Hourly while you're still calibrating how long your own work takes; project-based once you can scope reliably. Hourly protects you from scope creep, every extra ask costs the client more, which is valuable early on when your estimates are still shaky. Project-based protects your income from micromanagement over hours and rewards you for getting faster, which hourly actively punishes.
My actual practice: charge hourly for the first engagement with any new client, so I collect real data on how long their specific type of work takes. Every project after that gets a flat-rate proposal, informed by that data instead of a guess.
What Actually Moves You Up a Rate Tier?
Not years alone. If you're still on the first climb, focus on the skills that actually move that needle. The designers I've watched jump from mid to senior rates all did the same two things: they started documenting outcomes instead of just deliverables, and they got comfortable making tradeoffs under ambiguity without needing a client to approve every micro-decision. Clients paying senior rates expect less hand-holding, that's a real part of what they're buying, not just more polished pixels.
If you're pricing your next project, do the case-study rewrite before you touch the rate card. It's the move that pays off fastest, and it's the one thing on this list that costs you an afternoon instead of a client relationship.
One more number worth tracking: your effective hourly rate on flat-rate projects, actual hours worked divided into what you billed. Revisit it every quarter. If a project type consistently pays out below your target hourly, that's a scoping problem, not a rate problem, and no amount of raising your headline number fixes a proposal that under-counts revision rounds.
What the Rate Ranges Hide About Geography and Client Type
The tier table is useful and slightly misleading, because two designers with identical skill can sit 60% apart on rate purely based on who they're billing. A funded startup in Berlin or Amsterdam pays a mid-level designer somewhere around 70 to 90 euro an hour without much negotiation. A small agency subcontracting the same work will push for 45 to 55, because they're marking you up to their own client and the margin has to come from somewhere. A local business owner paying out of operating cash often genuinely cannot go past 40, and that isn't them lowballing you, it's arithmetic.
So the useful question isn't "what should I charge," it's "which of those three rooms am I standing in." I stopped bidding on agency subcontract work entirely in 2024 after running the numbers, and my income went up while my hours went down. That's an opinionated call and plenty of designers make good money the other way, but the agency rate ceiling is real and it doesn't move much no matter how good your case studies get.
A Worked Example: Pricing an Actual Project
Say a client asks for a five-screen mobile onboarding flow, with a design system starter and a clickable prototype. I'd scope that at roughly 40 hours: 6 for discovery and audit, 18 for the screens across two rounds, 8 for the token and component setup, 5 for the prototype, and 3 for handoff documentation. At an 80 euro target rate that's 3,200 euro. I'd quote 3,600 and state two revision rounds explicitly, because that spare 400 is what covers the third round that always appears.
Now the part I got wrong for years: if the client comes back and cuts scope to three screens, do not cut the price proportionally. Discovery, tokens, and handoff barely shrink. Three screens is maybe 32 hours, not 24. Price the work, not the deliverable count, and say that out loud in the proposal so the conversation happens before the invoice does.
I keep a simple spreadsheet for this, one row per project: quoted price, actual hours logged, effective hourly rate, and one line on what went over. Six months in, patterns show up that memory alone never surfaces. My "quick logo refresh" line item was quietly the worst-paying work I did all year, clients kept asking for "just one more variation" that never showed up in the original scope, and I only caught it because the spreadsheet made the pattern impossible to ignore. Raise your rate on the work that's actually earning it, not on everything uniformly, and you'll keep the clients worth keeping.
