Extended Services for Data Stores is now available

Updates Announcements
1

[Update] April 9, 2026

Hello Creators,

Over the past year, we’ve been evolving Roblox Extended Services as an option for those with very large experiences or unique use cases to purchase and obtain additional service usage beyond the platform limit.

Last year, we also shared Data Stores Access & Storage limits along with tools to help creators manage their usage (Data Stores Manager, Storage notifications, Data Stores Batch Processor).

Today, we’re excited to share the next steps in that journey with more services and geographic expansion.

Data Stores Access & Storage limits

First, as previously announced back in April 2025, new Data Stores Access and Storage limits are launching.

We have talked to large experience Creators, analyzed scenarios (looking at 55M+ experiences), and designed these limits so that only a very small number of experiences are impacted (<30 experiences), while the vast majority remain well within the default platform limits.

Access Limits will be a staged rollout that consists of Test and Launch. The official launch rollout will start on April 9th and continue through April 23rd. Before then, we will hold a Test rollout starting March 16th (along with Notifications). If you are part of the Test rollout, you will receive a direct communication with details before the rollout.

Storage Limits will activate on April 9th.

Recommended Best Practice Actions

Data Stores Access
The primary change to Access is that the limit will be at the experience level instead of the server. However, we will preserve the ability to throttle per-server (with current server limits) for default backwards compatibility. Once the limits are rolled out for your experience, you may choose to change server limits on a per-experience level (e.g., adjust to rely on experience limits) with DataStoreService:SetRateLimitForRequestType(). Use Data Stores observability dashboards to understand your current usage pattern. We expect that the vast majority of experiences will not be impacted negatively by these changes - rather, most experiences will benefit from these increased limits. See FAQ for more details on the Access changes, and what you can do to prepare.

Data Stores Storage
For the vast majority (99.9999%+) of experiences, the Storage limit update will be seamless and require no additional action. However, it is recommended as a best practice for Creators to review your usage in the Data Stores observability dashboards and Data Stores Manager so you are aware of the rate at which your experience is growing and consuming usage.

For the large experiences that have been in overage these past two years - we appreciate your partnership in exploring how to improve your use of Storage over the past months. Seven large experiences have since cleaned up 10.4PB+ of data. This is resourcing that goes back to the broader community. If you have continued questions, please feel free to reach back out to us - we are here to help.

We heard feedback from large experience Creators that Data Stores Storage is a critical resource. If Storage limits throttle your experiences’ writes, your experience can break in ways that are hard to recover from, so we’re treating Data Stores Storage usage with extra care.

If your experience crosses the Data Stores Storage platform limit and is not on Extended Services:

  • Your experience will continue consuming storage as an overage and will not be throttled on storage writes.
  • Leading up to and once you have an overage, you will be notified of your overage costs, and after a grace period of 2 weeks, the overage will result in Robux deductions from the experience owner’s (or the owner of the Group owning the experience) Robux. Alternatively, you may onboard to Extended Services to repay dues using your Extended Service’s payment method (more details on Extended Services below).
  • If overage dues cannot be repaid, the experience will be unpublished in order to pause continued growth in overage dues and prevent players from experiencing a broken in-game scenario.
  • Robux spending and experience transfer abilities will also be temporarily paused until overage dues are repaid.

As a Creator, follow these steps to best prepare:

  • Watch for notifications - if you see high‑usage notifications (e.g., near 80–100% of your upcoming storage limit), review and optimize your usage patterns

image2
image2986×1346 129 KB

image3
image31530×516 45.5 KB

For both Data Stores Access and Storage, Extended Service will help futureproof your growth as you continue to scale without concern for disruption. Read on to learn more on what is new with Extended Services.

Extended Services for Data Stores is available today

Creators who need additional Data Stores Access or Storage beyond the platform limits have the option to opt in via Extended Services to enable your experience to grow above platform limits, so you may continue to scale.

For Data Stores Storage
Because Data Stores Storage is a critical resource, onboarding to Extended Services will automatically enable for Data Stores Storage. This way, instead of incurring an overage and having to deduct from Robux, you may simply pay for additional Storage resources with your Extended Services payment method.

For Data Stores Access
Data Stores Access still requires your manual enablement in order to obtain higher Access limits.

Note that early enablement is for ensuring business continuity. There is no purchasing for resources above platform limits until the Access and Storage limits are active.

As a Creator, you may:

What’s next

We’re continuing to invest in Extended Services and related tooling so you can confidently scale on Roblox:

  • More Geographic Expansion
    We recently expanded Extended Services eligibility to additional countries and will continue adding support - more information to share later this year.

  • Extended Services for Compute
    We’re actively exploring Extended Services for Compute and are targeting mid-2026 to share more details on how this will help you run more complex, server authority experiences on Roblox.

We’re excited to see what you build with these new options. Please share your questions and feedback below, especially if you’re running a large or data‑intensive experience. Your use cases help guide where we take Extended Services next.

Thank you,
Roblox Creator Services Teams

FAQ

How can I prepare for Access limit changes (with further details)?

There are a number of changes coming with Access Limits. These changes will not affect the vast majority of experiences; however, please review the following, especially if your experience is hitting the current server-level access limits or your usage is above the forecasted experience-level limit:

  • Experience-Level Limits: New global limits now apply across your entire experience.
  • Modern DataStoreRequestTypes: Simplified DataStoreRequestTypes now align with experience-level limits.
  • Modified Server-level Limits: Server-level limits are now overridable to a higher amount using the new DataStoreService:SetRateLimitForRequestType() API. Each request is now subject to the new modern request type limits.
  • New Error Code Handling: Throttled requests will now return new error codes <RequestType>GameServerThrottled and <RequestType>ExperienceThrottled. Ensure your DataStore calls catch these errors and retry using exponential backoff (e.g., progressively increasing delays with jitter) rather than retrying immediately to avoid repeated throttling.

As a Creator, here is how you may prepare for the upcoming limits:

  • Monitor Usage: Check the Data Stores Observability Dashboard. If your experience exceeds the forecasted limits, optimize your code’s Data Stores usage.
  • Update Budget Checks: Transition GetRequestBudgetForRequestType to the modern request types early. Throttling will switch to these new types in April.
  • Pre-configure Limits: Use SetRateLimitForRequestType now to ensure higher server-level limits are active when the rollout completes in April.
  • Update Error Handling: If you manually parse Data Stores throttling error messages in your experience code, please update your logic to detect the new error codes. E.g. if you parse an error message for GetAsyncThrottle, please change the code to instead parse for StandardReadGameServerThrottled or StandardReadExperienceThrottled.

Can I set a limit on Storage usage that will not be crossed?

Setting a limit on Storage equates to writes throttling, which leads to experience breaking. In this scenario, it is recommended to manually unpublish the experience so that users are not affected by a broken experience.

Can I pay directly with Robux as the official payment method for Extended Services?

We have plans for Extended Services to support additional payments to make it easier to pay - we will share more later this year.

54 Likes
2

This topic was automatically opened after 12 minutes.

3

TEN POINT FOUR PETABYTES??? HOW???

41 Likes
4

that’s insane, considering 2b2t, the oldest anarchy server in Minecraft has a world file size of 80 terabytes and it’s 15+ years old at this point

10 Likes
5

that almost doesnt sound real lmao, 10.4PB is an absurd amount of data, especially for SEVEN experiences

9 Likes
6

huh?

image
image872×187 37.3 KB

I have some test games that use data stores. What if I spam some goofy thing, I don’t wanna lose Robux out of the blue for it.

Just error the calls and let me delete the entire store.

12 Likes
7

how does this overage thing work in more detail and is overage even the correct term for it?

i remember everyone getting outraged over this back when it was announced, but it seems much more lenient than some other recently imposed requirements and restrictions

5 Likes
8

Yeah, I can understand why Data Store limits and extended services had to be introduced. Optimization is very important when it comes to data storing, if you want your game to scale.

10 Likes
9

If I spam Text-to-speech, would I trigger such a thing?

Does anyone know? Can I try it out right now.

:sob:
Wait so if data store makes mistake and I request 5 seconds faster, it’s gg?

4 Likes
10

And those “seven large experiences” totally weren’t made by Roblox to inflate the numbers. /s

4 Likes
11

I understand numPlayers

But how do you calculate concurrentUsers oh wait I think it’s over all experiences, compared to per experience.

I pressed CTRL + F and the docs didn’t tell me nothing…

1 Like
12

Hi Roblox staff! Can you please tell me when this update will be released?

	["Feature.BiometricChallenge.Action.Cancel"] = "Cancel";
	["Feature.BiometricChallenge.Action.Continue"] = "Continue";
	["Feature.BiometricChallenge.Content.LivenessHostedPrompt"] = "Open your external browser and take a quick selfie to confirm you're human.";
	["Feature.BiometricChallenge.Content.Loading"] = "Loading...";
	["Feature.BiometricChallenge.Title.ConfirmHuman"] = "Confirm you're human";
8 Likes
13

where did you find that dawg :sob:

3 Likes
14

oops (might need a little help here)

image
image1953×461 43.7 KB

1 Like
15

Are you storing the entirety of the internet in your game, what is this

12 Likes
16

Let me guess, DataStore2?

17

I wrote more about it here.:

Details

char limit

3 Likes
18

As I’ve said before, because this impacts so little games, this update never should’ve happened. At worst, the limit should’ve never have been this strict. We don’t even get the full 4 MB per DataStore. This kills any form of survival game with terrain destruction that saves. Anyway, I’ve talked about this many times already.

2 Likes
19

four one and six seven? really guys

8 Likes
20

numPlayers is the number of unique players that join your game once. concurrentUsers is the amount of players actively playing your game at a given time.

5 Likes