Choose a supported installation route
Playdate supports independently distributed games through Panic's documented sideloading features. Obtain the release from the developer, retain its readme and record the required system version. The compiled game is a PDX package. A downloaded archive may contain that package together with instructions or extras, so inspect the archive before copying anything to the device.
Keep a library folder on the computer with the original download, extracted package, version and source address. This gives you a local copy independent of a storefront listing. Record whether the game came from Catalog, a season or a separate developer release. The delivery channel and the saved progress are separate parts of the preservation record.
Wireless installation through your account
Register the device to your Playdate account, then upload a PDX or zipped PDX on the account's Sideload page. On the device, open Game Library and refresh the available games; earlier system versions use Settings and Games. Install the uploaded title and verify the displayed version. Keep the local package even when account delivery works.
USB installation
The SDK Simulator can open an unzipped PDX and send it to a connected, unlocked Playdate through Device, then Upload Game to Device. This is convenient when testing several builds. Use a data-capable USB cable and establish a working connection with a known package before diagnosing a particular game.
Without the SDK, connect USB and select Settings, System, Reboot to Data Disk. Copy the unzipped PDX into the mounted device's Games folder, then safely eject the volume. Limit manual file access to the documented operation; moving unrelated system folders can damage the software installation.
A useful installation acceptance test
- Launch the title and check that its version and controls match the developer's instructions.
- Use buttons and the crank as intended, then test an early save or settings change.
- Return to the game list, launch again and confirm that progress or settings persist.
- Record any error message in full, including whether it happens during installation, launch or later gameplay.
- Keep the last working package available when testing an update. Back up progress before replacing or removing a game.
Version changes and duplicate entries
A display name is not the same as a game's unique identifier. If two entries appear after an update, compare the developer's metadata and retain both data folders until you know which contains the valuable progress. Panic documents a historical identifier change affecting older website sideloads; follow that specific migration guidance only when it matches the situation.
Do not delete the older entry merely because the new one launches. Ask the developer whether its save format changed, and test with a copy of the data whenever a migration is involved. A downloaded package can be replaced, while an overwritten personal save may have no other source. Continue with backups and device care or SDK development for the next stage.
Sources and review
Reviewed October 11, 2026. The linked manufacturer and project documentation establishes supported behavior. The diagnosis checklists and preservation suggestions are original editorial guidance. Menus, services and project support can change; verify the linked instructions before an irreversible change.