Every studio game has a hub at /studio/<universe id>, opened from the Studio games page. It has a header and eight tabs, each at its own address. Every signed-in member can open every hub; only the Feedback and Developer tabs are kept to the game's crew and owners. A game that is not in the studio has no hub (its address is "not found"); look it up in Explore instead.
The tabs
| Tab | Address | Shows |
|---|---|---|
| Overview | /studio/<id> | Key stats, public numbers, players over time, where it stands, players by hour, releases |
| Players | /studio/<id>/players | Active users, stickiness, playtime, retention, the acquisition funnel, the audience |
| Money | /studio/<id>/money | Revenue by day and source, payers, revenue per user, ad revenue, products and passes |
| Performance | /studio/<id>/performance | Frame rates, crash rate, server crashes, abuse reports, bans |
| Feedback | /studio/<id>/feedback | What players sent through the game's servers; crew and owners only |
| Developer | /studio/<id>/developer | The game's API key, its usage, how to connect a game and every endpoint |
| Contract | /studio/<id>/contract | Where the contract stands, its signers, the split, its terms, versions and the document |
| Shares | /studio/<id>/shares | The pool of shares, who owns the game, Buy a share |
The tabs are a row of pills under the header; on a phone the row scrolls sideways instead of wrapping. The old /studio/<id>/analytics address opens Players. There is no Updates & details tab any more: the release log is the Overview's Releases card, and the details are in the Manage game sheet; /studio/<id>/updates and /studio/<id>/details are "not found".
Read and triage what players sent: filters, statuses, pages.
Create, rotate and revoke the game's API key, and read its usage.
Who is the game's crew
The crew of a game is the developers named on its project and the game's lead. Organization owners can do everything the crew can, on every game. Everyone else is a member, who reads every tab except Feedback and Developer. See Roles and Members, developers and leads.
The game hub's header
The header shows the game's artwork and name, the project's description (or the game's pitch), its release state, where its contract stands ("Awaiting signatures · 1 of 2 signed"), its developers, its lead and target release date when they are set ("Lead: Sam · Target release Dec 1, 2026"), and its genre. On the right: Manage game for owners and the game's lead, a link to its GitHub repository when one is chosen, and Open on Roblox.
The Manage game sheet
Manage game opens a sheet from the right (the whole screen on a phone) with the game's release state, for owners, and its details. Only owners and the game's lead see the button; everyone else reads the lead and the target date in the header, and the repository from its link.
How an owner sets a game's release state or removes it
The sheet's Release state part is for owners only.
Open the sheet
Choose Manage game in the game's header.
Pick the state
In Release state, choose In development, Coming soon, Released, Paused or Archived.
Save it
Choose Save state. Coming soon and Released show the game on the public website.
Releasing needs the project's approved contract and public Roblox details. Remove from studio takes the game off the studio's games and the website and revokes its API key; what was recorded stays, and it can be registered again. See Games and releases.
The game's details: lead, repository, pitch and notes
The sheet's Details part holds the game's Lead, Repository (one the GitHub collection has seen), Target release date, Pitch (up to 160 characters) and Notes (up to 4,000 characters), with when and by whom they were last saved. Owners and the lead change them and choose Save details.
Refresh from Roblox
Refresh from Roblox, beside the details in the sheet, reads the game again with its group's key: its name, description and whether it is public. It works only for a game a registered group owns.
A project without a Roblox game
A project registered before its game exists lives at /studio/<project id> with only three tabs: Overview (where it stands, and "Players, money and the release log arrive once the project has a Roblox game"), Contract and Shares. Its developers and owners see Link a Roblox game in the header. Once a game is linked, the old address moves to /studio/<universe id>. See Projects.
Overview tab
The game at a glance.
Key stats on the Overview tab
Nine tiles in the order the studio reads them: CCU (playing now, with when it was read), DAU (latest day), D1, D7 and D30 (day-1, day-7 and day-30 retention), ARPDAU (Robux per daily active user), Payer conversion (the share of daily users who paid), Revenue, 24 hours (the latest full UTC day) and Revenue, 30 days. A line under them says "Roblox's numbers through" the last day stored; CCU is live.
A tile without a number says why: "Needs the group's key", "Not reported by Roblox" (Roblox declined that metric for this game, such as ad revenue for a game without ads), "Not reported by Roblox yet", or the analytics status. CCU says "Not tracked: private or unreleased" for a game the collector does not track.
Public numbers on the Overview tab
What Roblox shows anyone, from the collector: Visits (with the change in 24 hours), Favorites, Liked (the share of up votes, with the up and down counts) and Score, the breakout score out of 100, which needs eight hours of history.
Players over time chart
Concurrent players over 6 hours, 24 hours, 7 days (the default), 30 days or all time (?range=30d). Each release in the log is a dashed line on the chart, and a table under it lists them. A game the collector does not track shows "Not tracked" instead.
Where it stands card
Where the release stands in one sentence (for example "Not approved yet: every developer signs the contract first", or the day it was released and its week), the contract status, and the latest Playtime per active user, Session length and Paying users. Developers and contract opens the Contract tab.
Players by hour of the week heatmap
When the game is played: a grid of days by hours, in UTC, averaged over the last four weeks of the collector's readings. The footer names the busiest hour, for example "Busiest: Saturday at 18:00 UTC, about 240 playing".
Releases card: the release log
Launches, updates, hotfixes and live events, newest first, each with its kind, title, date and time, place version, who recorded it and its notes; each is marked on the game's charts. The five newest show; Show N earlier releases unfolds the rest below them. Owners and the game's lead see Record a release and a Remove button on each entry; everyone else reads the log. A link to /studio/<id>#releases lands on this card.
Open the game's Overview
Open the game's hub; the Releases card is on its Overview.
Start a release
Choose Record a release.
Fill it in
Pick the kind (Launch, Update, Hotfix or Live event), write a title (up to 120 characters), set released at, and add the place version and notes (up to 2,000 characters) if you have them.
Save it
Save. The release joins the log and appears as a dashed line on the game's charts.
A custom page can also hold a game's Latest releases card: its four newest releases, with Every release opening this card.
Players tab
Who plays the game and how, from owned analytics. The note at the top says where the analytics read stands ("Owned analytics read from Roblox 5 hours ago", or what is wrong and, for owners, Open groups).
Range on the Players, Money and Performance tabs
These three tabs read 30 days (the default), 90 days or 365 days (?range=90d), chosen with the tabs at the top right. Every chart marks each release with a dashed line. Metrics Roblox declined for the game are listed at the bottom in plain words.
Players tab tiles
Daily active users, Monthly active users, Stickiness, Day 1 retention and Playtime per active user, each its latest stored day with a small line of the range.
Players tab charts
Players by day: daily active users, players who started a session, and peak concurrent players.
Stickiness: daily over monthly active users.
Monthly and daily active users: players in the 30 days to each day, beside that day's.
Time played: minutes per active user in a day, against the length of a single session.
Retention: day 1, 7 and 30 together.
Hours played: every player's time added up, per day.
Conversion by day: shown to page opened, page opened to played, and shown to played.
Acquisition funnel: players shown the game, who opened its page, and who played, added up over the range, each step with its share of the one before.
Players by platform (stacked), Countries (the top ten), Where players come from (acquisition sources), Age groups, and Day-1 retention by platform, one line per platform.
Money tab
What the game earns as Roblox reports it, in Robux. Reported, not received.
Money tab tiles
Revenue over the range, Paying users, Per active user (ARPDAU), Per paying user (ARPPU) and Share who pay.
Money tab charts
Revenue by day: stacked by source (game passes, developer products and the other sources Roblox names), with By source splitting the whole range.
Paying users, Share of players who pay, Revenue per player (per daily active user and per paying user) and Ad revenue.
Revenue by platform, stacked by day, with Share by platform on an average day.
Developer products and game passes on the Money tab
Two tables, as the group's key last read them: each item's Name (marked "Off sale" or "No longer listed"), today's Price, and Changes ("2 changes, last 3 days ago", or "Unchanged since" the day it was first seen). The Money tab appears even without owned analytics, so the store can still show. The studio-wide list is on the Studio revenue page.
Performance tab
How well the game runs and how safe it is. Roblox keeps performance numbers for 28 days, so older days are only those the daily read stored.
Performance tab tiles
Client frame rate, Server frame rate, Client crash rate, Server crashes, Abuse reports and Active bans (on the last read).
Performance tab charts
Frame rate: average frames per second on players' devices and on the game's servers.
Client crash rate: the share of 15-minute stretches of play that ended in a crash.
Server crashes and Abuse reports (reports players filed against others in the game), per day.
Active bans: how many bans were in force on each day's read.
Who sees each ban and its reason
The Bans card lists each banned Roblox user, the private reason and the reason shown to the player, and from and until when, newest first, with "Lifted" on a ban no longer in force.
The whole list, private reasons included. It is read once a day with the group's key, which
needs universe.user-restriction:read.
Contract tab
The same tab for a game and for a project with no game yet (/studio/<project id>/contract):
Contract: three steps (Draft, Awaiting signatures with how many have signed, Approved), the studio week, version, when it was submitted and approved, and where the release stands. Under them, your next action comes first and filled in: Sign if you have not signed this version, Submit for signatures, Edit names and parts, Download signed contract or Download PDF; whatever else you may do follows in outline. The signed contract says whether it carries the studio's digital seal.
Signers: a table of everyone the contract names, with their part and when they signed or Waiting; anyone removed by another member is marked Leaving at 0% and must sign to consent. Under it, who is still waiting. There is no reminder button: everyone is notified when the contract is submitted and again with each signature, which the card tells a signer who has signed.
The split: a donut of each developer's part and the pool of shares.
The terms in plain language: six numbered cards with this game's numbers: parts, the pool and the share sale, points, release, what locks, and how to leave. Show the exact terms opens the contract itself in a sheet: a table of contents, numbered sections with their icons, the key numbers highlighted, tables, the split, worked examples and notes, defined terms in bold, every legal detail not set yet marked in brackets, the signers, and in Schedule A the exact terms with the SHA-256 hashes a signature is for. Until it is submitted, it is a preview.
Version history: every submitted version, newest first, with its date, the start of its PDF's SHA-256, whether everyone signed it, what changed from the version before, and Download version N for owners, the developers and leavers.
Edit names and parts opens a sheet from the right with each developer's part. Each part is checked as you type (at least 10%), a bar shows the developers, the pool and anything not given to anyone yet, and a line says whether the split makes 100%; Save names and parts waits until it does. After submitting, the sheet warns that saving makes a new version and clears every signature. The contract locks once approved. See Contracts and Signing a contract.
Signers, the split and the version history are widgets: Add to a page puts them on a page of your own.
Shares tab
Tiles for Left (shares not bought yet), Shares in the pool (each 10%), Bought, and On sale (Not yet, Open or Closed, with the release week and the two after, until the closing day). A member who may buy sees Buy a share, which spends their oldest point; anyone else sees why not. Who owns the game shows every developer's part, each shareholder's 10% with the day they bought, and the shares not sold yet; after the sale closes, unsold shares go back to the developers in proportion to their parts. See Shares.
Who can change a game's details, releases, key and contract
- Every signed-in member
Reads every tab except Feedback, and the Developer tab without the key or its usage.
- Owners and the game's lead
Open Manage game to edit the details and use Refresh from Roblox, record or remove releases, and see each ban's private reason.
- Owners
Set the release state and remove a game from the studio.
- Owners and the game's crew
Manage the API key and triage feedback.
- The project's developers and owners
Edit the contract draft and submit it; every signer signs.
- Members who did not work on the game
Buy a share during the sale.
The API checks these itself; a hidden button is never the only guard. A member who asks for a game's key or feedback is refused (403), and the ban list is left out of the answer for anyone but owners and the lead.
How fresh a game hub is
- CCU, visits, favorites, likes, score and players over time
From the collector, on the game's tier's schedule.
- Players, Money and Performance
Roblox's daily numbers, read once a day. The latest day is the last one Roblox finished; each read re-reads the last 7 days.
- Products, passes and bans
Read once a day with the same key.
- The release log, details, contract, shares, feedback and key
The platform's own records, current when the page opens.
The hub never asks Roblox or GitHub itself, except Refresh from Roblox, which reads the game's details once with its group's key. Where each source comes from, drawn: Where the Studio numbers come from. Every number is defined on Studio game stats.
A game hub on a phone
The tabs scroll sideways, and the Manage game sheet fills the screen. Key stats sit two across on a phone, three from 640 px and all nine in a row from 1536 px; the Players and Money tiles reach five in a row, Performance six, from 1280 px. Cards are one per row below 1280 px. Tables hide their less needed columns on a phone (a product's changes, a ban's dates) and scroll sideways.
Related: Studio pages, Projects, Getting a game's API key.
Updated