Platform Configuration
Zapicon lets you control where exported icons are saved and which sizes are generated. You can also create custom platforms for frameworks or internal tools that are not in the default list.
Default platforms
Each built-in platform has a default set of sizes and file names:
| Platform | Default sizes | Default output |
|---|---|---|
| iOS | 20–1024 px | AppIcon.appiconset |
| Android | 48–192 px | mipmap-.../ic_launcher.png |
| macOS | 16–1024 px @1x/@2x | icon_...png + icon.icns |
| Windows | 16–256 px | icon.ico |
| Web | 16–512 px | favicon.ico, apple-touch-icon.png, etc. |
| Tauri | 32–512 px | Mixed PNG/ICO/ICNS |
| Flutter | 48–192 px + iOS set | Android + iOS folders |
Modifying built-in platforms
Pro users can edit the output paths and size lists for any built-in platform:
- Open Platform Settings from the export panel or settings.
- Select a platform.
- Add, remove, or edit paths and sizes.
- Save the configuration.
Free users can use the built-in platforms with their default settings but cannot modify them.
Custom platforms
Custom platforms are useful when you need a non-standard folder structure, such as a company design system or a game engine.
Create a custom platform
- Open Platform Settings.
- Click Add Custom Platform.
- Name the platform.
- Add output paths. Each path can specify:
- File name
- Width and height
- Whether to generate ICO or ICNS
- Save and enable the platform in the export list.
Limits
| Plan | Custom platforms | Paths per platform |
|---|---|---|
| Free | 1 | 10 |
| Pro | Unlimited | Unlimited |
Import and export configuration
Zapicon can import and export platform configurations as JSON files. This is useful for:
- Sharing settings across a team.
- Backing up your custom platform definitions.
- Replicating a setup on a second machine.
Note: Platform configuration is stored locally in your app data and persists between sessions.
Last updated