Define the distributable Robux first
Before a split method matters, you need a clean number for the pool you are actually dividing. In some cases that is already-available treasury Robux. In other cases it is an estimate based on gross sales minus the platform deduction.
That distinction matters because arguments often start when people think they are splitting different numbers. One person may be thinking about projected sales while another is thinking about already-received Robux. The payout plan only works when the pool is explicit.
- Use treasury Robux if the money is already available to split.
- Use a net estimate if you are planning from projected sales.
- Write down whether the pool is gross, net, or already-distributed Robux.
A worked pool estimate, start to finish
The estimate is only as good as the pool you start from, so derive it explicitly. Suppose a game pass priced at 200 Robux sells 100 times. Gross is 200 × 100 = 20,000 Robux, but that is not the distributable pool — Roblox keeps 30% at the point of sale, so the group actually receives 20,000 × 0.70 = 14,000 net Robux. That 14,000 is the number to split, not the 20,000 the buyers paid.
From there the split method takes over. Split 14,000 equally among four people and each gets 3,500. Split it 40/30/30 and the shares are 5,600, 4,200, and 4,200. The single most common group-payout mistake is dividing the gross 20,000 instead of the net 14,000, which promises everyone about 43% more than the team can actually pay. Always net the pool first, then choose the method.
- Gross: 200 Robux × 100 sales = 20,000 Robux.
- Net pool: 20,000 × 0.70 = 14,000 Robux (the 30% comes off before any split).
- Split 14,000: equally across 4 → 3,500 each; 40/30/30 → 5,600 / 4,200 / 4,200.
- Common mistake: splitting the gross 20,000 promises about 43% more than the group can pay.
Pick the simplest split method that matches the work
Equal splits are the easiest to explain and audit. They work well when collaborators contributed roughly the same amount and everyone agrees that a clean simple rule matters more than granular precision.
Percentage and weighted splits are more flexible. They help when one person handled programming, another handled assets, and a third handled community or publishing. The more custom the rule, the more important it becomes to keep the math and the justification visible.
- Equal splits are best for small teams with similar contributions.
- Percentage splits are best when roles already have agreed shares.
- Weighted splits are useful when you want contribution points instead of fixed percentages.
Watch the rounding leftovers before you finalize
Robux payouts usually end up in whole numbers, which means many group splits create small leftovers after rounding. That is normal, but it should never be a surprise discovered after the payout plan is announced.
A fair split process makes the leftover rule visible up front. You might assign leftover Robux by largest remainder, give it to a shared pool, or reserve it for a future balance adjustment. The important thing is consistency and transparency.
- Check whether percentages add up the way you expect.
- Review the final rounded amounts before you approve the split.
- Decide how leftovers will be handled before anyone is paid.
How to use this with our tools
Use the Roblox Group Revenue Split Calculator when you already have a pool to divide and want a clean per-person breakdown. If you still need to estimate the net creator-side Robux before the split, start one step earlier with the Roblox Tax Calculator or the Roblox Price After Tax Calculator.
That two-step approach keeps the workflow honest: first estimate what is actually available after deductions, then split only the amount the group can really distribute.
- Use the Tax Calculator if you still need a net revenue estimate.
- Use the Group Revenue Split Calculator once the distributable pool is clear.
- Re-run the split if a price, sales projection, or team weight changes.