Skip to main content
playfab file manages the files stored on a PlayFab entity, such as a player.
Every file command requires --entity-id and --entity-type. For a player, pass their title player account ID with --entity-type title_player_account, not their master player account ID; playfab player account get returns it as UserInfo.TitleInfo.TitlePlayerAccount.Id.

Output

playfab file list writes the files’ metadata to stdout as JSON, or as a table with --output table, which shows FILE NAME, LAST MODIFIED, and CHECKSUM. upload, download, and delete are file operations, like cp and rm. They write nothing to stdout, and report what they did on stderr: These messages might change between releases, so scripts should check the exit code: 0 when the operation succeeded, and nonzero when it failed, with the error on stderr. These three commands don’t accept --output table, and --data-only doesn’t change what they write.

playfab file list

playfab file download

download replaces a local file that’s already at the destination path.
When the entity has no file with that name, the error shows the file list command to run:

playfab file upload

If an upload fails

While an upload is in progress, PlayFab blocks every other upload to the entity’s files, including the game’s own, which fail with EntityFileOperationPending. So when an upload fails partway, or you press Ctrl+C, the CLI cancels it and says on stderr whether that worked. When the cancel works, the entity’s files are unchanged. When the CLI can’t cancel the upload, or can’t tell whether the upload or the cancel applied, it says so. It prints the command that cancels the pending upload and, when the file might have changed, the file list command to check. Run the cancel command only if later uploads fail with EntityFileOperationPending, because it also cancels an upload of that file that the game started.

playfab file delete

Last modified on November 18, 2026