Epic Online Services Player Data Storage
- Free allowance
- 400 MB total storage per user, 200 MB maximum per file, 1,000 files per user.
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- anonymous?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- per-object-cap200 MB per file
- Evidence
- reported3 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | 400 MB total storage per user, 200 MB maximum per file, 1,000 files per user. No published product-level or title-level byte cap. unit MB; metered on stored-bytes |
|---|---|
| Price | none stated |
| Limits |
per-object-cap: 200 MB per file and 64-character filename limit; request-rate: ~1,000 read or write requests per minute per user, then EOS_PlayerDataStorage_UserThrottled; per-object-cap: 1,000 files per user. Retention: none stated — files persist until explicitly deleted; no expiry found. Data is encrypted at rest with a client-side key EOS never stores, so losing the key loses the bytes. |
| Identity | anonymous (inferred, not read) not published |
| Egress | No per-GB egress meter documented for Player Data Storage; access is metered as API requests. EOS itself is free for all developers. |
| Per-object cap | 200 MB maximum per file (200000000 bytes) |
| Retention | not stated |
| Interface | rest, rclone part of the text of Limits, above |
| Tooling | EOS SDK (C/C++), C# and Unreal plugins (PlayEveryWare/eos_plugin_for_unity). File ops are chunked read/write callbacks: EOS_PlayerDataStorage_WriteFile / ReadFile / QueryFileList. No rclone backend. |
| Composes with | 400 MB per ProductUserId x unlimited free player identities. EOS supports anonymous/device auth, so identities are mintable at will; each new ProductUserId is a fresh 400 MB bucket. 2,500 identities = 1 TB. |
| Reliability | Throttles writes (not errors) once the 400 MB per-user total is reached until files are deleted; quota is per-deployment so a busy title can hit service-level allocation failures. |
| Parsed numbers |
|
Evidence 3
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | dev.epicgames.com/docs/epic-online-services/player-and-game- | filename format, 64-char limit, encryption-key requirement, 'Data that you store through this interface is accessible to players (users) on any device' |
| 2026-10-21 | grokipedia.com/page/Player_Data_Storage_Epic_Online_Services | quotas table 'Maximum individual file size 200 MB / Total storage space per user 400 MB / Maximum files per user 1000' (secondary source, corroborates the SDK error codes EOS_Result_PlayerDataStorageFileSizeTooLarge and _UserThrottled) |
| 2026-10-21 | dev.epicgames.com/docs/epic-online-services/working-with-the | 'Each service applies usage quotas on a per-deployment basis' |
Unknown values 3
- per object cap notes: the field may be stated in a source that was not read
- retention notes: the field may be stated in a source that was not read
- retention stated: the field may be stated in a source that was not read