PPSA21402 / Roguelike
Balatro
Balatro on AnyPS5: In-game · Local patches. Compare PS5 test reports, build versions, hardware, FPS and known issues. Official game images are separate from runtime evidence.
About the game

A poker-inspired deckbuilder using hands, jokers and evolving scoring combinations. Record an actual round and score calculation separately from a functioning main menu.
Check the edition before testing
This page covers the PS5 release. A PS4 edition, native PC release or console performance mode is not an AnyPS5 test. Confirm the title ID and version before comparing reports.
Official game informationCommunity report · Windows
In-game
Gameplay and sound reportedly work at 60 FPS after the listed PRs and local flip/depth fixes. The patched stack matters; this does not establish compatibility for the published release.
- AnyPS5 build
- PRs #1020 / #1038 + local flip/depth fixes
- Platform
- Windows 11 Pro
- Game version
- 1.0.1o-FULL
- CPU
- AMD Ryzen 7 7800X3D
- GPU
- NVIDIA RTX 5070
- Driver
- Not specified
- Test date
- Not specified
Performance observations
NVIDIA RTX 5070
AMD Ryzen 7 7800X3D
Scope of this result
Gameplay and sound reportedly work at 60 FPS after the listed PRs and local flip/depth fixes. The patched stack matters; this does not establish compatibility for the published release.
Source reports; no benchmark by this site. Experimental reports may use forks or local changes. Read the build details before reproducing.
Game identity
- Game
- Balatro
- Title ID
- PPSA21402
- Edition / region
- Not specified
Screenshots and video
Official game images
Promotional images from the publisher’s game page. These are not screenshots of the game running in AnyPS5. Images are hosted on this site; rights remain with their owners.
Official game informationSource reports; no benchmark by this site.
Source policy · Read more
Prepare an AnyPS5 test
Record the PS5 title ID, game version, AnyPS5 commit and operating system. Note any local changes, then test startup, menus, gameplay, audio and saves separately. Attach the first relevant error and a short capture of the same build.

