Building Consistent Icon Sets with AI Bundle Generation
How to use IcoGenie's bundle feature to generate cohesive icon sets for your app, with consistent style across every icon.
The consistency problem
Individual AI-generated icons look great on their own. The challenge is making 10 or 20 icons look like they belong together — same stroke weight, same level of detail, same visual language.
IcoGenie's bundle generation solves this by generating icons as a coordinated set rather than one at a time.
How bundles work

Instead of sending each icon through the pipeline separately, bundles use a grid-based approach:
- You list your icons — names and optional descriptions for 2-20 icons
- AI normalizes descriptions — ensures consistent language and detail level across all icons
- Grid generation — icons are generated in 2x2 batches, sharing the same visual context
- Individual extraction — each icon is split from the grid and stored separately
The grid approach is key. When four icons are generated together, they naturally share visual characteristics — stroke weight, level of detail, and spatial composition stay consistent.
Step by step: Building a dashboard icon set
Let's build an icon set for an analytics dashboard. On the web, switch to the "icon bundle" tab and list your icons:
1. bar-chart — vertical bar chart with three bars
2. line-graph — trending line graph going up
3. pie-chart — pie chart with three segments
4. metrics — speedometer or gauge
5. calendar — calendar with a date highlighted
6. export — download arrow into a document
Click "Normalize" to let AI refine the descriptions for consistency. The normalizer ensures each description follows the same pattern and detail level.
Then generate. At 1 credit for the entire bundle preview, it's the most cost-effective way to create a set.
Tips for better bundles
Be specific about the style upfront. Choose solid or outline before generating. Mixing styles in a bundle breaks consistency.
Keep descriptions at the same detail level. If one icon is "simple arrow" and another is "detailed ornate compass with cardinal directions and decorative border," they won't match.
Use the normalizer. It's free and it catches inconsistencies you might miss. The AI rewrites all descriptions to the same level of specificity.
Regenerate outliers. After generating, if one icon doesn't match the set, regenerate just that one. The regeneration prompt includes style guidance from the rest of the bundle.
Bundle pricing
Bundles use a tiered credit system for downloads:
| Bundle size | Cost per icon | Total example |
|---|---|---|
| 2-4 icons | 5 credits | 10-20 credits |
| 5-9 icons | 4 credits | 20-36 credits |
| 10+ icons | 3.5 credits | 35+ credits |
Preview generation is always 1 credit flat, regardless of bundle size. So you can preview a 20-icon set for 1 credit before committing to download.
Using bundles from the CLI

The CLI supports bundle generation too:
npx @icogenie/cli bundle \
--icons "home,settings,profile,notifications,search" \
--style outline
Or describe a theme and let AI suggest the icons:
npx @icogenie/cli bundle \
--description "icons for a fitness tracking app" \
--style solid
The CLI uses the same grid-based pipeline as the web, so consistency is identical.
Download contents
Each icon in a downloaded bundle includes:
icon-name.svg— production-ready vectorIconName.jsx— React component with TypeScript typespng/icon-name-{16,32,192,512}.png— raster assets at standard sizesmeta.html— favicon HTML snippet
Plus a shared AGENTS.md with API examples and CI/CD integration patterns for the entire set.
When to use bundles vs. single icons
Use bundles when you need 3+ icons that should look like a family — navigation sets, feature icons, dashboard widgets.
Use single icons for one-off needs — a hero illustration, a specific action icon, or when you want maximum control over individual prompts.
The bundle approach trades per-icon control for set-wide consistency. For most app icon needs, that's exactly the right trade-off.
Try bundle generation and build your first icon set.