We’re excited to share some powerful updates to the Data Stores Observability Dashboard!
Our redesigned dashboard now includes several new features aimed at giving you deeper insights and greater control over your Data Stores access and storage:
Near real-time storage usage and limit chart: View historical trends in your Data Stores storage usage at a glance.
Explore mode: Dive deep into any Data Stores metric with advanced filtering and breakdown.
Chart data export: Export data from any chart for your own analysis or reporting needs.
Improved navigation and user experience: A streamlined interface to make exploring your data easier than ever.
We hope these enhancements help you better monitor, understand, and optimize your Data Stores usage. As always, we’d love to hear your feedback or help with any issues you encounter.
This is really helpful! Unfortunately, I can’t use this feature because my game has a lot of old DataStores that I don’t use anymore. Will there be a way in the future to delete DataStores (not just keys)?
This is nice and all, but the 2026 DataStore cap ruins any experience where players can build freely at a large scale and having it save, at least without completely watering down what’s possible.
I’m a bit confused as to why this cap is being imposed if less than 1% of experiences will go beyond this cap? If that’s the case, this shouldn’t cause any issues.
At the very least, I would like the cap to increase by 4 MB per player rather than 1 MB.
So the max size per user is basically gonna go from 4MB per user to 1MB? That’s gonna become a challenge, especially for a game like mine, which allows players to have lots of items & data.
This really shouldn’t be a problem for most games. I don’t believe Roblox is wrong in their estimate. I just believe that Roblox has no reason to have this limit if only 30 experiences reach that limit currently. It basically kills or severally harms any future projects that would go above those limits.
If your data is over 1 MB, you should probably look into optimizing your data storage. This limit is really only a limit for games on the scale of Minecraft or similar, where a full chunk of completely unique non-storage blocks (65,536 blocks) may take up 327.68 KB.
(If anyone wants to see my math, you can read my full post)
There are hundreds of RPG-like games that give players hundreds of items at a time, as long as you put any effort into trying to optimise the data format you’ll never hit the limit.
All very, very good stuff, but I can’t help but notice that there is still no way to delete entire datastores. Words can not describe how important it is that we get this kind of tooling BEFORE the limits are instated in 2026. My game has 100s of old, unused datastores that are a holdover from bad habits, and it means that I cannot actually use any of the metrics to check my data usage. Furthermore, it means that my game is artificially and unintentionally closer to the limit than it should be.
You need to get this done, ROBLOX. We cannot make effective use of these tools without a way to efficiently and quickly delete old data.
Other than that, I’m looking forward to seeing how all these tools work and I think they will help us manage our data usage more effectively.
Thank you for giving us all these useful tools, but mass-management and cleanup of our datastores should be priority #1 now.
For the Minecraft versions 1.18+ a world would be 16x384×16 making for a total 98,304 blocks per chunk meaning a 66%~ increase in size per chunk which if a Roblox sandbox voxel game was to use a column chunk format rather than cubic chunks (which would also erase the height/depth limits for building/generation) making higher column chunks more taxing and less worthwhile.
Yeah, I went with 16x256x16 because the position can be stored with just 2 bytes (2 characters). Halving the height would, of course, reduce the amount of data each filled chunk would take. That would be 32,768 blocks at 163.84 KB of data. But, regardless of what optimizations you make, it’s still 1 MB per player. With 1 MB and half a chunk, you can still only store 6 chunks with 65.536 KB left over. That would also be for one user, for the entire experience and all worlds/servers, just 6 chunks.
If we got the full 4 MB of a DataStore per user, like we should, then each player could have 25 chunks with 98.304 KB left over. (Or 12 chunks with 262.144 KB left over, if we’re talking about the full 256 height.) While it can never compare to Minecraft, 25 savable chunks per player seems at least reasonable.
