Modern Xcode: One 1024×1024 Universal Icon
Generates one opaque Default appearance PNG and a universal iOS manifest entry. Xcode creates the smaller device representations.
Turn one icon into a complete AppIcon.appiconset with matching PNGs and Contents.json.
Choose the modern 1024×1024 Single Size workflow or export the classic iPhone, iPad, and App Store compatibility slots. Every image is flattened to an opaque square and packaged locally in your browser.
Start with a finished square master. A 1024px or larger raster image avoids upscaling; SVG also renders cleanly into every compatibility slot.
PNG · JPG · WEBP · SVG / MAX 10 MB / 1024×1024 RECOMMENDED
Choose the Xcode contract
Modern Xcode can derive iPhone and iPad variants from one 1024×1024 image. The compatibility mode is for projects that retain explicit point-and-scale slots or teams that tune artwork at smaller sizes.
The 18 compatibility outputs are catalog slots, not 18 required designs. Current Xcode All Sizes catalogs can leave slots unassigned, and Single Size is the simpler default for most new iOS projects.
Generates one opaque Default appearance PNG and a universal iOS manifest entry. Xcode creates the smaller device representations.
Generates the complete classic 18-slot matrix so every idiom, point size, and scale has a named PNG.
| Decision | Modern Single Size | All Sizes compatibility |
|---|---|---|
| Best for | New iOS and iPadOS projects with one finished 1024px master | Older catalogs, handoff packages, or deliberate small-size tuning |
| PNG output | 1 universal 1024×1024 PNG | 18 slot files across 13 unique pixel dimensions |
| Manifest mapping | universal + platform iOS + 1024 size | iPhone, iPad, and iOS marketing idioms with point size and scale |
| Artwork control | One appearance stays identical at every derived size | Files can be replaced later when a small slot needs custom detail |
From ZIP to asset catalog
The download opens directly to the asset set folder. Keep the PNG files and Contents.json together so Xcode can resolve every manifest entry.
Generate the chosen mode, download AppIcon.appiconset.zip, and expand it without renaming or separating its files.
In the project navigator, open the asset catalog assigned to your application target and locate the existing AppIcon set.
Quit any active file rename, then drag the generated folder into the asset catalog or replace the matching folder in the project.
Confirm the target's App Icons Source points to AppIcon, then build and review the icon on the devices and appearances you support.
Manifest anatomy
Xcode reads the manifest rather than guessing from filenames. Each images entry identifies the intended catalog slot; the filename then connects that slot to the PNG beside Contents.json.
{
"images": [{
"filename": "AppIcon-1024.png",
"idiom": "universal",
"platform": "ios",
"size": "1024x1024"
}],
"info": { "author": "xcode", "version": 1 }
}References a PNG inside the same AppIcon.appiconset directory. Every generated reference is checked before packaging.
Modern output uses the universal idiom with the iOS platform. Compatibility output identifies iPhone, iPad, or iOS marketing.
Compatibility slots express points and @1x, @2x, or @3x scale; multiplying them gives the required PNG pixel dimension.
The catalog metadata declares author xcode and format version 1, matching the asset catalog convention.
Before the first build
Generation solves the file and manifest work. A short visual review still protects the final icon across system masks, devices, and App Store presentation.
Avoid transparent edges. The selected background is flattened behind every PNG so no alpha remains in the Xcode output.
Keep the exported canvas square. iOS applies its own mask; pre-rounded artwork can create visible borders or double rounding.
This first release generates only the Default appearance. It never duplicates that image into fake Dark or Tinted variants.
Check target settings, catalog warnings, device previews, and a real build. Automated package checks do not replace project-level validation.
Appearance variants
When custom variants are absent, the system can derive them. A proper Dark asset may use transparency and a Tinted asset should be grayscale, so neither can be reconstructed honestly from every flat source.
Layered Apple icons
Apple Icon Composer preserves layers and Liquid Glass adjustments. A flat upload cannot recover that structure, so this tool deliberately exports a traditional AppIcon.appiconset.
Different output jobs
Use this page for a focused Xcode asset catalog. Choose the cross-platform generator for iOS plus Android resources, or the resizer for loose PNG size files without catalog metadata.
The modes, terminology, and cautions on this page were reviewed against Apple guidance. The final project build remains the authoritative validation for your Xcode version and target.
Answers about 1024×1024 source files, Single Size, compatibility slots, transparency, Contents.json, Icon Composer, and local processing.
Use a square 1024×1024 PNG, JPG, or WebP, or upload an SVG that can render cleanly at that size. A smaller raster file can be enlarged, but the generated 1024px App Store image cannot recover missing detail.
No. Modern Xcode supports a Single Size workflow that starts from one 1024×1024 icon and derives smaller representations. Use All Sizes compatibility only when your project or handoff needs explicit point-and-scale slots.
No. They represent the complete classic iPhone, iPad, and App Store slot matrix, not 18 universally required designs. Current Xcode All Sizes catalogs can leave slots unassigned; this tool fills the matrix to make a self-contained compatibility package.
The Default app icon should not rely on transparency, so this generator flattens every PNG onto the selected opaque color. Custom Dark appearance artwork follows different guidance and is not generated in this first release.
No. Every exported PNG remains a full square. The rounded outline in the preview shows how a system mask may frame the artwork; iOS applies the real mask at display time.
It maps each PNG filename to an asset catalog slot. Modern output uses a universal iOS 1024 entry; compatibility output records idiom, point size, and scale for each iPhone, iPad, and App Store slot.
No. It creates the Default appearance in a traditional AppIcon.appiconset. It does not copy artwork into misleading Dark or Tinted variants, and it cannot create the layered .icon file produced by Apple Icon Composer.
No. Image reading, SVG sanitization, resizing, PNG encoding, manifest creation, preview, and ZIP packaging all happen in your browser. LogoFoundry does not receive or store the selected artwork.