DevEx Math Breaks Down Once You Account for Roblox's Full Revenue Stack

The Number Everyone Cites Is the Wrong Number

The figure that circulates constantly in developer communities — that Roblox pays out roughly 25 cents per Robux at the Developer Exchange rate — is accurate as far as it goes. It just doesn't go very far. That 25% figure describes the cash-out conversion rate. It says nothing about what happened to your revenue before it ever reached DevEx. And that prior sequence of cuts, fees, and structural variances is where most of the real math lives. When you work through the full stack, the effective rate for a typical mid-tier developer — someone running a moderately successful experience, not a top-100 title — lands somewhere between 15% and 19% of gross Robux spent by players. Sometimes lower. The headline number is not a lie, exactly. It's just genuinely misleading in a way that matters for how developers plan their businesses.

Layer One: The Platform Cut You Already Knew About

Start with the known quantity. Roblox takes approximately 30% of every Robux transaction at the point of purchase — the cut that brings a 100-Robux item sale down to roughly 70 Robux credited to the developer. This is the number most DevEx explainers begin and end with. Then comes the DevEx conversion: as of 2026, the rate sits at $0.0035 per Robux for developers who meet the thresholds, which works out to that ~25% effective payout relative to what players originally paid in USD. Stack those two together and you get to approximately 17.5 cents on the dollar before you've accounted for anything else. That's the floor most people are working from. The problem is that the floor has a basement.

Layer Two: Marketplace Fees and the UGC Compounding Problem

If your revenue model involves the Avatar Shop or UGC items — and for a significant number of mid-tier games, it does, either through bundled passes or direct catalog items — you're dealing with a separate fee structure that compounds rather than replaces the platform cut. Roblox charges a 30% marketplace fee on avatar item sales, with an additional affiliate fee that kicks in when items are sold through experiences other than the creator's own. For developers who have built hybrid monetization models where in-game purchases link to catalog items, the compounding effect of the platform cut plus the marketplace fee applied at different stages of the transaction can push effective take rates down to the 14–16% range on those specific revenue streams. This isn't speculation — it follows directly from the published fee structures. What's underappreciated is how many mid-tier games have drifted into hybrid monetization without fully recalculating what that blend does to their blended margin.

Layer Three: Premium Payouts Don't Mean What You Think They Mean

The Premium Payout system is pitched as found money — passive revenue for engaging Premium subscribers. And for top-tier titles with massive Premium user bases, it can be meaningful. For most mid-tier developers, it's a volatile, opaque line item that inflates gross revenue numbers without translating predictably to DevEx-eligible Robux. Roblox calculates Premium Payouts based on a proprietary engagement weighting that the company has never fully disclosed. The result is that developers often see Premium revenue spike and drop in ways that don't correlate clearly with player counts or session time. The practical consequence: developers building financial projections who include Premium Payouts at historical average rates are frequently overestimating forward revenue. It's reasonable to treat Premium Payouts as a bonus rather than a baseline — which means the base revenue picture, stripped of that variance, often looks thinner than dashboard numbers suggest.

Layer Four: The Tax Treatment That Nobody Writes About

This is the layer that gets almost no coverage in developer communities, and it's the one with the most direct impact on what you actually keep. DevEx payments are self-employment income in the United States, subject to both income tax and self-employment tax (the combined Social Security and Medicare contribution that employees split with employers but self-employed individuals pay in full). That self-employment tax alone adds up to 15.3% on net earnings up to the Social Security wage base. A developer who converts $10,000 worth of Robux through DevEx doesn't take home $10,000 minus their income bracket — they take home $10,000 minus income tax minus self-employment tax minus any applicable state tax. Depending on the developer's total income and state of residence, the all-in effective take on gross player spend can fall below 10 cents on the dollar. I want to be careful here: tax situations are individual and this isn't tax advice. But the consistent absence of tax framing from DevEx discussions isn't just an oversight — it's the reason so many developers who hit what look like meaningful revenue milestones find the actual deposits disappointing.

What the Real Numbers Should Change About How You Operate

The corrected math doesn't necessarily mean Roblox is a bad platform to build on. It means the business case needs to be built on the corrected math, not the headline rate. A few things follow from this directly.

First, monetization model selection matters more than most developers treat it as. Pure in-experience purchases — game passes, developer products — generally sit at the better end of the effective rate range. Hybrid models involving the marketplace, affiliate sales, or heavy Premium dependency introduce more compounding fee exposure. If you haven't explicitly mapped your revenue mix against the fee structure that applies to each stream, you should. The difference between a 17% and a 14% effective rate on a game doing 50 million Robux in annual player spend is not trivial.

Second, Premium Payouts should be forecasted conservatively or not at all in any financial planning document. Track them, appreciate them when they arrive, but don't build expense structures against them.

Third — and this is the one developers most consistently resist — the tax layer needs to be in the conversation from the beginning, not at year-end when the 1099 arrives. If you're at a point where DevEx is generating real income, the gap between gross DevEx receipts and net after-tax income is large enough to affect decisions about reinvestment, pricing, and how you think about sustainable revenue targets.

The Roblox investor materials are useful here in a specific way: they describe the platform's own take from the economy in terms that make the margin structure legible if you're reading for it. The platform is designed to retain a substantial share of economic value at multiple points in the stack. That's not a criticism — it's a business model. But developers who understand the full structure of that model are better positioned to make decisions within it than developers who are working from the simplified version. Use RoWatcher to track your revenue trends over time and notice when the mix is shifting — because changes in your Premium Payout share or UGC revenue blend can move your effective rate without any visible change to your game.