Hello Creators,
Building expansive worlds requires good data management, and we’re here to support you in that process. As a part of this focus, we provide resources, including cloud services that scale based on your usage.
Going forward, we’re updating our limits for DataStores access and storage to ensure Roblox services can continue to scale as the community grows. We are building a fair system that gives every creator control over their DataStore usage and lets you focus on building your experiences. Here are the top takeaways:
-
We’re moving DataStore access limits from per-server to per-experience and increasing these limits substantially; updated limits will take effect in early 2026.
-
We’re introducing a total storage limit for DataStores, that scales with lifetime experience users and is dramatically higher than most per-user usage today; new limits will take effect in early 2026.
-
Out of the top 55 million experiences, there is a very small number of experiences, less than 30 total, that are currently over the limit. These limits will not impact the vast majority of experiences.
-
If your experience is over the limit, you will have a DevForum inbox message with more details on how to prep for early 2026.
-
We know many creators have expressed the desire to go above these limits, and we are exploring options to make this scalable. More information will come in the next few weeks.
-
-
Today, we’re also launching Data Store Manager to help you measure your DataStores storage usage and show your current usage vs the limit. We are also updating DataStores Access dashboard with a view based around the updated limits.
- Documentation can be found here.
Limit impact & next steps
For DataStores Access, there will be a net positive experience across the creator community – many previously throttled experiences will now have higher limits. There will be a few scenarios where some experiences in specific situations will now hit a limit.
For DataStores Storage, only a small handful of experiences will be over the limits. We defined a limit where less than 30 experiences (<0.0001%) are impacted out of the top 55 million. For the few experiences that will be impacted on Storage, the respective creators have been contacted via a private DevForum message in their inbox.
For the few creators above the limits, we will support you with guides and tools (such as observability dashboards, Data Stores Manager, and the ability to conduct batch processing). These tools are available for anyone who wants to optimize, and we will release them throughout the year.
Lastly, we have heard many creators ask for the ability to go beyond the established service usage limits. As such, we are looking into ways to allow creators who want to use even more resources and build more expansive worlds. We recognize that your experience may be unique and may require additional resources. More information on this will be shared in the coming weeks.
Timeline for Rollout
Today, we launch our first solutions:
-
New DataStores Access Observability Dashboard – allows you to measure how your usage compares to the upcoming Access limits. You will still have visibility to the current Access dashboard for existing operational needs.
-
Data Stores Manager - a new way to view, filter, browse, and understand how your DataStores are being used along with storage usage insights.
Upcoming limits updates for DataStores
Access
We are changing today’s limits to one where limits are now per-experience instead of per-server, enabling greater flexibility. We have also adjusted the request typing and updated the request with more generous ceilings.
| Request Type | Functions | Requests per Minute per Universe |
|---|---|---|
| Standard | ||
| Get |
GetAsync()GetVersionAsync()
|
250 + CCU × 40 |
| Set |
SetAsync()IncrementAsync()UpdateAsync()
|
250 + CCU × 20 |
| List |
ListDataStoresAsync()ListKeysAsync()ListVersionAsync()
|
10 + CCU × 2 |
| Remove | RemoveAsync() |
100 + CCU × 40 |
| Ordered DataStores | ||
|---|---|---|
| Get | GetAsync() |
250 + CCU × 40 |
| Set |
SetAsync()IncrementAsync()UpdateAsync()
|
250 + CCU × 20 |
| Get Sorted | GetSortedAsync() |
100 + CCU × 2 |
| Remove | RemoveAsync() |
100 + CCU × 40 |
Note: RemoveVersionAsync() will now be in the deprecated state.
| Storage | |
|---|---|
| Limit Type | Limit Allotted |
| Standard Storage | 100 MB + 1 MB * (Lifetime Players) |
Please share questions and comments below.
Thank you,
Roblox Services team
FAQs
How will I know if I’m at risk of hitting the limits of DataStores?
-
If you are forecasted to be at risk of impact with the new limit definitions, you will have received direct communication and guidance on what actions you can take. You have approximately one year of lead time before the limits are enforced in early 2026.
-
You may use tools like the Observability Dashboard and Data Stores Manager to track the quota limits and the usage for your experience.
After the new limits go live, what if my experience has a quick growth in users and usage consumption?
- We are working towards a throttling grace policy to help account for burst scenarios. More information on this will be shared later this year.
What should I do if I hit the limits?
- We have designed a comprehensive framework for you to identify root causes and take action to optimize. This includes email alerts, highlights and tips on the insights dashboard, error logs, and optimization guides (such as Memory Stores). For those who want to save time or still need more, we are exploring ways to offer this in a scalable way.
What about Ordered DataStores Storage?
- We do not have any changes to announce for Ordered DataStores Storage at this time, but we are exploring it and will share as soon as we have something concrete.
