Import Delta skins on iPhone and iPad

A skin is a control layout

Everything on screen wants room: the picture, the D-pad, the action buttons, the menu row. A skin decides where each of those lands. Pick by system and orientation first, and treat color as the last consideration.

• Check which system a package was drawn for before importing it.
• Portrait and landscape coverage depends on the layouts the skin actually includes.
• A readable package format says nothing about whether a third-party layout fits your device.

Import a .deltaskin package

Send the .deltaskin file to Retropa's skin import screen and pick it up from Files. Assign it to the matching system afterward. Then load a game and inspect the screen area, the directional controls and each action button before you commit to it.

• Import the whole .deltaskin package, not a screenshot of one.
• When a package refuses to load, recheck its format and target system before hunting for a replacement.
• Go back to a skin that works if the new one hides a control you need.

Touch controls and physical controllers

Retropa also works with compatible external controllers, with button mapping you can adjust. Pair the pad in iOS first, then look at how Retropa reads it. Artwork and button assignments are separate jobs, so a fresh skin will not correct a mismapped trigger.

Packages and purchase boundaries

PackHub is the catalog for browsing Retropa's skins. Premium packages require Retropa Plus, and importing a file from somewhere else does not get around that check. Requirements for a given package are listed in the app, so read them there before you commit. Delta compatibility describes a file format; it says nothing about any tie to the Delta project.