For standard data stores: read, write and remove are 60 + 40 x players per minute, and list is 5 + 2 x players. For ordered data stores: read is 60 + 40 x players, write and remove are 30 + 5 x players, and list is 5 + 2 x players.
Check the DataStore request budget of a server and the size of your data against the per-key limit.
Roblox gives every game server a default DataStore request budget per minute that grows with the number of players. For a standard data store, reads and writes get 60 plus 40 per player and list requests get 5 plus 2 per player. Ordered data stores write and remove at 30 plus 5 per player. This tool applies those formulas to your player count and compares them with the requests your autosave makes. It also measures a JSON or text value against the 4,194,304 limit per key. The size is an estimate based on compact JSON, so confirm critical values with HttpService:JSONEncode in Studio.
Paste the code into your HTML and the tool shows up on your page, without J-Kit's navigation and ads. It still runs in the browser of whoever visits your site.
<iframe
src="https://jkit.tools/embed/en-US/roblox-datastore-limits-calculator"
width="100%"
height="600"
style="border:0"
loading="lazy"
title="Roblox DataStore Limits Calculator"
></iframe>These references help contextualize formulas, standards, APIs and limitations used on this page. They do not replace professional validation when a result has legal, financial, medical or operational impact.
For standard data stores: read, write and remove are 60 + 40 x players per minute, and list is 5 + 2 x players. For ordered data stores: read is 60 + 40 x players, write and remove are 30 + 5 x players, and list is 5 + 2 x players.
| Method | Per min |
|---|---|
| GetAsync | 860 |
| SetAsync | 860 |
| IncrementAsync | 860 |
| UpdateAsync | 860 |
| RemoveAsync | 860 |
| ListKeysAsync | 45 |