Do you actually know who controls the Robux your team earned last week? If your experience is published under a Roblox group, the answer is almost never "everyone who worked on it."
Group funds are the default treasury for collaborative Roblox development, and they run on rules most teams only discover after a payout fails or a balance freezes. The mechanics are all documented — they're just scattered across a dozen help pages and a decade of forum threads that contradict each other.
What follows is the whole system in one place: where group revenue comes from, why your spendable balance is smaller than your earnings, who is actually allowed to move the money, and the handful of behaviors that get a group locked with everyone's split still sitting inside it.
What are Roblox group funds?
Group funds are a shared Robux balance owned by a Roblox group rather than a person. Revenue from group-owned experiences and marketplace items lands there automatically, and only members holding spend permission can pay any of it out.
Where Group Revenue Actually Comes From
A group treasury fills from four separate pipes, and they clear on different schedules. Knowing which pipe a given deposit came through is the difference between an accurate forecast and a promise you can't keep.
The sources that feed a group-owned balance include:
- In-experience purchases. Game Passes, developer products, and experience subscriptions sold inside a group-owned place return 70% of the Robux spent to the group balance. The remaining 30% is the platform's cut, taken before anything reaches you.
- Marketplace and UGC sales. Clothing, accessories, and other avatar items published under the group deposit at whatever the current marketplace split is — a figure Roblox has restructured more than once in the UGC economy, and one you should re-check rather than assume.
- Engagement-based payouts. Roblox distributes a share of Premium subscription revenue based on time spent, and for a group-owned experience that money lands in the group, not in the owner's personal wallet.
- Direct member deposits. Any member can send Robux into the group, which is how most teams pool an advertising budget or pre-fund a commission without routing it through someone's personal account.
Note that none of these arrive at the same rate per dollar spent by the player. A purchase made in a market with cheaper Robux pricing produces the same Robux for you at a different real-world cost to the buyer, which is why Robux regional pricing quietly reshapes what a "1,000 sales" month is actually worth.
Pending Robux, Or Why Your Balance Lies To You
Newly earned Robux does not land as spendable money. It sits in a pending state first, and during that window it appears in your revenue summary while being completely untouchable by the payout system.
The commonly documented hold runs roughly three days for in-experience sales, and it can stretch longer for some marketplace transactions. That delay exists because Roblox needs a window to reverse fraudulent purchases and chargebacks before the Robux becomes real.
Why can't I pay out my group's Robux yet?
Newly earned Robux stays pending for roughly three days before it becomes spendable. Payouts draw only from the available balance, so revenue you can see in your analytics may still be days away from being payable.
The practical consequence catches nearly every new team. If you promise contributors a Friday payout based on Thursday's revenue dashboard, you're promising money that hasn't cleared — and you'll cover the shortfall out of the standing balance or break the promise.
Keep in mind that reversals claw back from pending funds first. A refunded purchase that already cleared into available balance becomes a negative adjustment against future earnings, which is a nasty surprise on a month you'd already distributed in full.
The Permission Tiers That Decide Who Can Touch The Money
Roblox groups run on ranks, with 256 slots available from 0 through 255, and permissions attach to the rank rather than the person. Promote someone into a rank and they inherit every permission that rank carries, instantly and silently.
What matters here is that revenue permissions are separated from everything else. A rank can approve join requests, moderate the group wall, and rewrite the description without the ability to move a single Robux — and that separation is the entire basis of a safe group structure.
| Tier | What it can do with funds | Where teams get burned |
|---|---|---|
| Owner (rank 255) | Everything — one-time payouts, recurring splits, ad spend, ownership transfer | Single point of failure; if this account is compromised or moderated, the treasury stops with it |
| Rank with spend permission | Issue payouts to members from the available balance | Granted casually to an early collaborator and never revoked when they drift away |
| Rank with payout-view only | Read the payout ledger, move nothing | Underused — this is the correct default for most contributors |
| Member, no revenue permissions | Receive payouts only | Cannot independently verify their own split is being honored |
| Non-member | Nothing; cannot receive a payout at all | A contractor leaves the group and their recurring split silently stops |
Who can pay out Roblox group funds?
Only the group owner and members in a rank granted spend permission can issue payouts. Recipients must be current members of the group, and the paying account is generally required to have two-step verification enabled.
That last requirement is worth internalizing before you need it. Two-step verification on the account that moves money is not a nice-to-have — it's the gate standing between a phished password and an emptied treasury.
Be aware that the platform does not arbitrate revenue disputes between members. There is no escrow, no contract enforcement, and no appeal process for "we agreed on 40% and he paid me 10%" — whoever holds the spend permission holds the outcome.
One-Time Payouts Versus Recurring Payouts
Roblox gives you two distribution mechanisms, and teams routinely pick the wrong one. A one-time payout sends a fixed Robux amount from the balance sitting in the treasury right now, which suits bounties, milestone bonuses, and one-off commission work.
A recurring payout is a standing percentage instruction, routing a defined share of incoming revenue to a member automatically as it clears. Across all members those percentages cannot total more than 100%, which is the only real guardrail in the system.
| Dimension | One-time payout | Recurring payout |
|---|---|---|
| Source of funds | Existing available balance | Incoming revenue as it clears |
| Amount | Fixed Robux figure you enter manually | Percentage of each qualifying deposit |
| Applies to past earnings | Yes — that's the point | No; existing balance is untouched |
| Stops when | You stop sending them | The member leaves the group or you edit the split |
| Best for | Bounties, bonuses, contractor invoices | Ongoing revenue share with the core team |
Do recurring payouts split the Robux already in the group?
No. Recurring payouts apply only to revenue that arrives after the split is configured, so the balance already sitting in the treasury stays put until someone issues a one-time payout against it.
This is the single most expensive misunderstanding in group revenue sharing. A team that ships, earns for two months, then sets up a 30/30/40 recurring split has just agreed on a rule that ignores every Robux already banked — and the argument that follows is entirely avoidable by configuring splits on day one.
Getting Group Funds Out To Real Money
Group funds cannot be converted to currency directly. The Developer Exchange operates on individual accounts, so the path always runs group balance → payout to a member's personal balance → that member submits a DevEx request.
Eligibility has a stack of requirements: the cashing-out member must be at least 13, hold an active Roblox Premium subscription, have a verified email, keep an account in good standing, and clear a minimum earned-Robux threshold that has long sat at 30,000 Robux. The published developer rate has held at $0.0035 per Robux for years, putting that 30,000 minimum at roughly $105 before tax — verify the current rate on Roblox's DevEx page before you build a revenue model on it.
Can you DevEx directly from a Roblox group?
No. Group funds must first be paid out to an individual member's balance, and that member then submits their own DevEx request once they meet the Premium, verified-email, and minimum earned-Robux requirements.
There's a tax consequence buried in that sequence that nobody mentions to teenage dev teams. Whoever submits the DevEx request is the person the payment is reported to, so a single member cashing out for four people carries the reported income for all of it in most jurisdictions.
What's more, settling the difference by trading Robux for cash outside the Developer Exchange violates the Terms of Use. If your split relies on off-platform Robux sales to work, your split is a moderation incident waiting for a trigger — a pattern that shows up constantly in how top Roblox developers actually make money.
Why Groups Get Locked
A locked group is the failure mode that ends teams, because the funds stay frozen while the dispute plays out. The causes are more mundane than most developers expect.
Groups and their treasuries typically get locked or frozen for reasons including:
- Owner account moderation. A group is downstream of the account that owns it, so a termination or extended ban on the owner takes the group's funds with it — and no other member can unlock them.
- Group buying or selling. Trading groups or accounts for Robux or currency violates the Terms of Use, and a funded group changing hands is one of the easier patterns for the platform to detect.
- Automated payout-pattern flags. A burst of large payouts to accounts that joined the group hours earlier is indistinguishable from a compromised account being drained, and the system freezes first and reviews later.
- Moderation on group surfaces. The group name, description, icon, shout, and wall are all moderated content, and violations there can restrict the group regardless of how clean the experience itself is.
- Ownership disputes after a compromise. When a group changes owner during a hijacking, restoring it means proving original ownership through support — a slow process with no guaranteed outcome.
- Abandonment. A group whose owner deletes their account or lapses into an ownerless state enters a limbo where the accumulated funds are effectively stranded.
What happens to group funds if the owner gets banned?
The group and its Robux balance are tied to the owner's account, so a termination generally freezes the funds. Other members cannot pay themselves out, and recovery depends entirely on a support appeal from the owner.
The control worth more than all the others: two-step verification on the account that owns the treasury, backed by a recovery email someone on the team can still access in a year. Almost every horror story in this category starts with a compromised owner account, not a dishonest partner.
The Structural Decision You Only Get To Make Once
Publishing an experience under a group is close to irreversible. Moving a place out of a group means re-uploading it, which mints a new place ID and abandons your visit count, favorites, ratings, and every Game Pass players already purchased against the old ID.
In other words, the ownership choice you make in week one is the one you live with through your best month. Teams that publish under a personal account "just for now" and try to move it after traction discover that the discoverability they built is not portable.
Decide deliberately. If more than one person will ever have a revenue claim on the experience, publish it under a group from the start — the alternative is renegotiating trust at exactly the moment there's real money on the table, which is one of the quieter reasons behind the retention numbers on games that fail.
What A Sane Group Revenue Setup Looks Like
None of this requires legal sophistication, and most of it takes twenty minutes. Here's the setup that survives contact with an actual hit:
- Write the split down before launch. Percentages, named accounts, and what happens when someone stops contributing — a note in a shared doc beats a memory of a Discord conversation from March.
- Configure recurring payouts the day revenue starts. Since they never apply retroactively, every day you delay is a day of revenue that has to be distributed manually or argued about later.
- Grant view access freely, spend access almost never. Contributors want to verify the ledger, not move money, and payout-view permission satisfies that completely.
- Keep the owner account on the most secure, most stable person on the team. Two-step verification, a real recovery email, and no shared credentials.
- Never quote a payout date against pending Robux. Quote against available balance only, and build in the clearing window.
- Re-audit ranks whenever someone leaves. Departed collaborators who kept spend permission are the second most common source of missing funds after account compromise.
All of this adds up to a simple posture: treat the group treasury as shared infrastructure with real security requirements, rather than as a convenient wallet. The teams that survive their first successful month are the ones who set the rules while the balance was still boring.
Common Questions About Roblox Group Funds
How long does it take for group Robux to become available?
Newly earned Robux typically clears from pending to available in about three days for in-experience sales, with some marketplace transactions taking longer. Payouts can only draw from the cleared, available balance.
Can a group member pay themselves without the owner's approval?
Only if their rank carries spend permission. Roblox enforces permissions at the rank level, so any member in a rank with fund-spending rights can issue payouts without asking the owner first.
Do you need Roblox Premium to receive a group payout?
No. Premium is required to submit a Developer Exchange request and convert Robux to currency, but any current group member can receive a payout into their personal balance without it.
What happens to a recurring payout if someone leaves the group?
Payouts require active membership, so the split stops when the member exits. Their percentage does not automatically redistribute to anyone else, and you have to reconfigure the remaining shares yourself.
Can you transfer Robux directly between two Roblox groups?
Not directly. Funds have to be paid out to an individual member's balance first, and that member then deposits into the second group — which creates a taxable-looking paper trail worth documenting.
Is buying an established Roblox group with funds allowed?
No. Buying or selling groups and accounts violates the Roblox Terms of Use, and a funded group changing ownership is a common trigger for a freeze on both the group and the accounts involved.
If you're building with a team, get the ownership and permission structure settled before the first Game Pass goes live — it's far cheaper than renegotiating with a balance in dispute. For more on how money actually moves through the platform, start with our breakdown of the Roblox creator economy, then work through the rest of the Roblox guides library.