Managing Assets

Platform Packs

This guide covers how to create and use platform packs in iISU.

Platform packs are built to allow users to seamlessly customize the appearance of their console icons, title images, and hero backgrounds. These must be made manually outside of the app, and imported in using the designated file structure. This table details each compatible folder name per console.

Current supported platform asset types per platform:

  • icon

  • title

  • background

All three are optional on a per-platform basis. A pack can contain:

  • only icons

  • only titles

  • only backgrounds

  • any mix of the above

Multiple imported packs can be layered. Higher layers win only for the asset types they actually provide.

Example:

  • Pack A contains snes/icon.png

  • Pack B contains snes/background.png and snes/icon.png

Result:

  • snes icon comes from Pack A

  • snes background comes from Pack B

ZIP Schema

Platform pack ZIPs are folder-based.

This is the valid format:

My Cool Pack.zip
└── monkeyicons/
    ├── snes/
    │   ├── icon.png
    │   ├── title.png
    │   └── hero.png
    ├── nds/
    │   ├── icon.webp
    │   └── hero.jpg
    └── genesis/
        └── title.png

The importer is generous and also accepts hero images as background.png/webp/jpg, and you can name files like nds_title.png , though maintaining the shown format is recommended. A note that the folder name beneath the zip, such as monkeyicons will be seen in the app.

Valid per-platform folder names are taken from the platform IDs iiSU already knows through emuladores.json or bundled emuladores_default.json.

Current matching sources:

  • shortName

  • alternativeNames

The full list of folder names can be found here.

Supported File Names

Inside each platform folder, the importer currently recognizes:

Icons

  • icon.

  • custom.

  • dark_icon.

  • dark_custom.

Titles

  • title.

  • customtitle.

Heros

  • background.

  • custombackground.

  • hero.

  • hero_1.

background, hero, and hero_1 are treated as the same platform background slot during import.

custombackground maps to the custom-background slot.

The importer also accepts explicit flat runtime-style names anywhere in the ZIP, including:

  • .

  • _icon.

  • _custom.

  • dark_.

  • dark__custom.

  • _title.

  • _customtitle.

  • _background.

  • _hero.

  • _hero_1.

  • _custombackground.

Examples:

  • nds/title.png

  • nds/background.png

  • nds/custombackground.png

  • nds_title.png

  • nds_custombackground.png

Supported File Extensions

Current accepted image extensions:

  • png

  • jpg

  • jpeg

  • webp

  • gif

  • json

That matches the launcher’s platform image pipeline, including animated formats like GIF and Lottie JSON.

Import Normalization

Imported packs are extracted into the active asset root under:

iiSULauncher/assets/platform_packs/<pack_id>/platforms/

The importer normalizes inputs into the file name structure.

  • icon.png -> .png

  • custom.png -> _custom.png

  • dark_icon.png -> dark_.png

  • dark_custom.png -> dark__custom.png

  • title.png -> _title.png

  • customtitle.png -> _customtitle.png

  • background.png -> _hero_1.png

  • custombackground.png -> _custombackground.png

  • hero.png -> _hero.png

You don't need to worry about this for creating packs, but just note it in case you ever wish to manually manipulate files.

Layering Rules

Layering is as follows:

  1. manual platform overrides in iiSULauncher/assets/platforms using _custom*
  2. imported platform packs, in your layer order
  3. bundled/default platform assets in iiSULauncher/assets/platforms
  4. launcher fallback UI

Theme Dialog UI

Platform packs are managed in-app from:

Appearance > iiSU Themes