PlayStation Classic modding wiki

Choose the change you actually need

PlayStation Classic supports several community modification paths, including USB launchers and optional internal kernel changes. Treat them as different operations. Identify the console's existing modification state and retain the original backups before changing projects. A prepared USB package may contain components that a launcher source repository does not build by itself.

Establish working stock power, HDMI and controllers first. Test a small supported storage device and one appropriate disc-image set before expanding a library. Do not assume every filesystem or OTG arrangement works on an unchanged stock console. Match those features to the installed kernel and exact project documentation.

Keep a restorable library

The media guide separates disc descriptors and tracks, ordinary memory-card saves and emulator states. Preserve game edition and region, multi-disc order and the expected card layout. A launcher's cover art or metadata cannot repair a missing audio track. Test a meaningful later stage and a save reload rather than counting an opening screen as complete compatibility.

When migrating between launchers or emulator versions, use copied data first and retain the previous known-good setup. States can depend on the implementation and version; ordinary game saves are important alongside them. Preserve paths and configuration so apparent missing progress can be checked before files are overwritten.

Read project status

ModMyClassic's current homepage says Eris and Lunar development is on indefinite hold and directs readers to archived guides. AutoBleem lineages have separate source and release documentation. Cite the project actually tested rather than presenting an old tutorial as a current universal procedure. Kernel changes require the chosen project's own original-state and restore prerequisites.

Use this directory

Choose a guide by the work you intend to do, then record the hardware model, installed software and existing condition. Preserve data before a reset, storage change or firmware write. Each guide links primary documentation and separates documented requirements from editorial checklists. Keep a known-good baseline, change one variable at a time and verify a restore where saved progress matters. When contributing, include the exact tested configuration and source revision so another reader can reproduce the result and understand its limits.

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.

• Sony: PlayStation Classic instruction manual
• AutoBleem: original project and USB setup documentation
• AutoBleem-NG: original project and distribution documentation
• ModMyClassic: current project status and archived Eris instructions