Ask what game UI/UX design costs and you get a range so wide it is useless. Published rates for hiring game UX designers run from roughly $25 an hour to well over $100, and plenty of engagements price above that.
That spread is not a quality gradient. It is a category gradient, and buyers who read it as quality make the most expensive mistake available in this market, which is buying cheap production to solve a problem that needed thinking.
What Each Tier Actually Buys
The rate spread makes sense the moment you stop treating it as one market.
Roughly $25 to $50 an hour. Art production, usually in a lower-cost region, and frequently very good art. You send a spec, they send back beautiful screens. Fast, scalable, and exactly right if you already know what your interface should contain. What you are not buying is anyone telling you the spec is wrong. That is not a knock, it is the deal.
Roughly $50 to $100 an hour. Experienced designers, often through a staffing or outsourcing arrangement, embedded into your team. You get capacity and craft. You manage the direction. This works well with strong internal design leadership and badly without it, because an embedded contractor has no standing to tell your VP the onboarding is the problem.
$100 and up. A team with product and research capability that starts with your problem rather than your spec. Fewer artefacts per week, because a meaningful share of the engagement is spent finding out what is actually wrong. Worth it when a number is bad and nobody knows why. Waste of money when you already know what you want built.
Comparing these on rate is comparing a printer to a publisher. Both make books. Only one of them will tell you the manuscript has a problem.
Why Per-Screen Pricing Is a Trap
It is the most common commercial model in this market and it is structurally misaligned with the work.
The core of good interface design is removal. The most valuable thing a designer can do for your game is talk you out of a screen. Under per-screen pricing, nobody gets paid for that. The incentive points at producing more screens, which is precisely how interfaces get worse.
It also prices the wrong unit. Two screens can differ in difficulty by an order of magnitude. An inventory screen supporting browsing, comparison, sorting, and action, on a controller, with variable-length items in nine languages, is not the same unit of work as a settings page, and any model that prices them alike is going to produce a great settings page and a terrible inventory.
What to look for instead: pricing tied to an engagement, a phase, or an outcome. It is harder to compare across vendors, which is exactly why buyers gravitate to per-screen, and it is the reason per-screen persists despite everyone knowing better.
The Cost Nobody Puts in the Budget
The fee is the small number. Here are the large ones.
Solving the wrong problem. A studio with a retention problem hires art production because it was cheaper. They get a beautiful version of the interface that was causing the retention problem. The vendor delivered perfectly. The problem is untouched, six months are gone, and the studio now believes design does not work. The fee was $40,000. The cost was the year.
Late rework. Every constraint that forces an interface rebuild is knowable in advance. Controller navigation. Text size at couch distance. Localisation inflating your strings 40% into German. Certification requirements. Teams that discover these at cert pay to redo work that is already approved, which is multiples of what designing inside them would have cost. None of it is a surprise. It is only ever a surprise to people who did not look.
The interface you already have. This is the one that never appears on any budget line. If your first-session drop-off is 60% and it should be 40%, you are paying for that every single day, in acquisition spend that buys installs who never activate. Against that meter, most design fees are rounding errors. The question is never what a redesign costs. It is what the current design costs per month.
Where Research Fits in the Number
Research is the line item that gets cut first and it is the cheapest insurance in the project.
Claudia Mérigo, a UX researcher on our team, put the case plainly on our podcast: if you skip research, you are designing entirely on assumptions, and the biggest risk is spending time and money building something that either already exists or does not solve a real user problem.
She described a gaming project where the interviews revealed the client had misunderstood their own audience. The product had been designed for casual gamers. The people who would actually use it were professional gamers, and the two groups have completely different behaviours, needs, and expectations. The research redirected the entire product. Consider the counterfactual cost of not running it: a full build for the wrong audience.
She also noted that a minimum study runs about a month, or two for something larger with twenty-plus participants. That is the honest schedule cost, and it is why it gets cut. It is also less than the time you will spend rebuilding.
One thing specific to this vertical makes the excuse weaker than usual. Mérigo pointed out that gamers are unusually easy to recruit and interview, because they enjoy talking about games so much that the hard part is ending the conversation. Compared to trying to book time with CTOs, this audience is cheap to reach. Most teams simply never go.
Eric Lee Smith, a game designer with award-winning titles behind him, was blunter about the underlying politics on our Visionaries podcast. He described testing as a job where doing it perfectly earns you a C and anything less earns you an F, which is exactly why it stays at the bottom of every priority list. Nobody is celebrated for the disaster that did not happen.
How Projects Actually Get Priced
Three models dominate, and the model tells you more about what you are buying than the number does.
Time and materials. An hourly or daily rate against an estimate. Honest, flexible, and it puts the overrun risk on you. Works when scope is genuinely unknown, which for a diagnostic engagement it usually is. The failure is a vendor who discovers scope indefinitely.
Fixed fee per phase. A number for discovery, a number for design, a number for handoff. This is the model most product partners run because it prices the thinking rather than the artefacts, and it forces both sides to define what "done" means at each gate. It is harder to compare across vendors than per-screen, which is the point.
Retainer. A monthly fee for ongoing capacity. Correct for live games, where the interface problem never finishes because every new system re-opens the sequencing question. The failure is a retainer with no defined outcome, which decays into a standing invoice for whatever the backlog contains.
Per-screen is the fourth and it is the one to avoid, for the reasons above. If a vendor will only price that way, you have learned what they sell.
What Drives the Number Up
If you want to estimate before you talk to anyone, these are the multipliers that actually matter.
Platform count. Mobile plus console plus PC is not one interface with three layouts. It is three interfaces sharing a design system, because a console layout scaled down is unusable on a phone and a mobile layout scaled up reads as cheap. This is close to the biggest single driver and buyers routinely assume it is a rounding error.
Input models. Controller support means focus order, wrap behaviour, and default selection specified for every screen. It is real design work, it is invisible in the mockup, and skipping it produces a console build that feels broken.
Localisation depth. Nine languages is not nine times the work but it is not free either, and it constrains every layout decision from the first sketch.
Regulatory scope. Real-money gaming carries interface requirements that vary by jurisdiction and reach into the layout. Session timers, deposit controls, responsible gambling messaging with required prominence. Designing these in from the start is normal cost. Bolting them on afterwards is expensive and produces an interface that visibly resents them.
Legacy. Redesigning inside an existing codebase where the interface is entangled with game logic costs more than a greenfield build, sometimes considerably. This surprises people every time.
The Constraints That Are Cheap Early and Brutal Late
Almost every expensive rebuild in this category traces to a constraint that was published, knowable, and skipped.
Microsoft's Xbox Accessibility Guidelines specify text size minimums by platform and resolution, and they are more demanding than most teams' intuitions. Discovering at certification that your entire type scale is undersized means re-laying-out every screen, after they have all been signed off, which is the most expensive moment in the project to change anything.
The Game Accessibility Guidelines basic tier is similar. Remappable controls, subtitle options, and never using colour as the sole carrier of meaning are cheap if designed in and structural if retrofitted. Colour-only state encoding in particular tends to be woven through a whole interface by the time anyone checks.
Localisation is the third. Designing every string container with headroom costs nothing. Discovering during translation that your layouts only fit English costs a re-approval cycle across every screen you shipped.
None of these are surprises. They are only surprises to teams who did not read the documentation, and the entire cost of reading it is an afternoon.
How to Compare Quotes Honestly
Two quotes for the same brief can differ 5x and both be reasonable, so the comparison has to be on what is inside them.
Does the proposal include research, or does it start at wireframes? If research is absent from the proposal it will be absent from the project, and you are buying assumptions rendered attractively.
Does it define an outcome or a deliverable list? A vendor committing to a number is exposed to whether the work succeeds. A vendor committing to fourteen screens is exposed to nothing.
Did they look at the product before quoting? A price given without looking is a price for a fixed quantity of output. Which is fine if that is what you want, and a warning if you thought you were buying diagnosis.
Mariana Lopez, a product strategist on our team, gave a test on leveraging metrics to improve user experiences that is worth applying to any proposal: a metric is measurable, movable, related to a specific goal, and not gameable. A vendor promising to improve engagement without defining it is promising to improve a number that also rises when your menus are confusing.
The rest of the vendor evaluation is in our guide to choosing a game UI/UX design company, and the build-versus-buy decision is in our guide to hiring game UI/UX designers.
What the Money Buys When It Works
Buildbox is a no-code game creation platform used by millions, backed by a former Riot Games CTO. Genuinely powerful product. The original interface presented all of that power the moment a user signed in, and people got lost and left before making anything. The value was completely real and completely invisible.
The redesign asked one question: what does a meaningful first success look like for a new user? Everything else moved later. First-success completion improved 41%.
That is worth pricing properly. A 41% improvement in users reaching value is not a design metric, it is a revenue metric, because users who find the value are the ones who convert from trial to paid. Against that, the design fee is not really the number under discussion.
The same held on MPL, one of the largest skill-based gaming platforms in the world, entering the US market. Their platform was not poorly designed. It treated credibility signals as supplementary content rather than core architecture, in a market where real-money users apply the scrutiny of a financial product. Restructuring where trust appeared, rather than refreshing how it looked, produced a 34% increase in perceived trust, a 28% lift in intent to download, and a 22% reduction in time to first action.
Neither of those was an art problem. Neither would have been solved by the cheapest quote.
Final Thoughts: Price the Problem, Not the Screens
The wide range in game UI/UX design cost is honest. It reflects a market selling genuinely different things under one label, and every tier is correctly priced for what it is.
The mistake is not paying too much or too little. It is buying the wrong category, which happens when a buyer with a product problem shops as though they have an art problem, because art problems are easier to write a brief for. "Redesign our onboarding screens" is a brief. "Find out why most installs never finish a match" is a question, and questions are harder to put out to tender.
So work out which you have before you compare quotes. If your interface is ugly and your numbers are fine, take the cheap quote and enjoy the value. If your numbers are bad and nobody knows why, the cheap quote is the most expensive thing on the table.
Get a Real Number for Your Situation
If you want an actual figure rather than a range, send us the product. Wandr has designed for game creation platforms, real-money gaming, esports tools, and character systems, and we will come back with the top friction points we would fix and what it would take, including the outcome where the honest answer is that you need a cheaper vendor than us. See how our game UI/UX design team works. Free, no pitch.
