GlitchMod tutorials
Playdate modding wiki
Official Playdate sideloading, game storage and save backups, Lua and C SDK development, Simulator testing, updates and hardware care.
Browse topics
Tutorials & referencePlaydate modding and preservation wiki
Playdate supports independent games through official sideloading and development tools. This directory connects PDX installation, Lua and C SDK work, Simulator testing, game-data backups, system recovery and practical care for the handheld.
Start with a practical guide
- Sideloading and storage
Install independently distributed Playdate games through official routes, organize PDX packages and protect progress while changing versions.
- SDK development
Build Playdate software with the official Lua or C SDK, test in Simulator and on hardware, and package releases with stable metadata and save behavior.
- Backups, updates and care
Copy Playdate game data before resets or migrations, apply official system updates and use documented recovery and maintenance practices.
Working record
Keep the exact hardware model, installed software, tested accessories and backup date together. Record the last working setup before a change and verify important saves after maintenance.
Keep software and progress separate
Store original game downloads with their release notes, developer address and minimum system requirement. A compiled PDX package is the software you install; your personal game data is a different preservation target. Plan a backup of both before deleting an older build, transferring devices or changing a save format.
Record how a title was delivered: a season, Catalog or an independent release. Keep enough information to identify the exact build, rather than relying only on the displayed name. Stable game identifiers matter when comparing versions or investigating duplicate entries. Do not remove an older data folder before locating the progress it contains.
Choose the installation route that fits the task
The installation guide covers account delivery, SDK Simulator upload and the documented USB Data Disk route. Use one method for the first test so a failed launch has a clear context. Confirm that a USB cable carries data, then check the known package before diagnosing the game itself.
Manual filesystem access should remain limited to the intended copy operation. Keep a full backup before migration experiments and safely eject the mounted device when copying finishes. A successful transfer does not prove that the game supports the installed system version, so read its own documentation and retain any error text.
Develop in small, measurable stages
The SDK guide starts with a minimal Lua program, explains the role of the compiler and then builds a hardware acceptance routine. Keep the SDK version with the source project. Test the actual compiled package on the device as well as in Simulator, especially when performance, crank interaction or save handling matters.
Use real play situations for testing. A busy scene, a long session and an update from an older save reveal problems that a fresh empty project cannot. Record controls and accessible alternatives in the release notes. Test the archive users will download rather than only the files in the development directory.
Maintain a usable device record
Keep the system version, last update date, known working cable and dated Data-folder backups together. Read Panic's official recovery instructions when the device cannot boot normally. A reset is a separate destructive decision; preserve what remains readable before choosing it.
Schedule battery checks for a stored collection and protect the crank, ports and buttons during transport. Record unusual charging behavior or mechanical resistance for support. These guides provide the practical workflow around the manufacturer's documentation, while the linked sources establish the supported menus and tools.
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.