This one started with a genuinely small annoyance: while putting together the icon set for one of our own apps, we couldn't tell — just by looking at the file — whether our multi-resolution .ico actually had a 256px image baked into it, or whether it silently topped out at 48px like an older export sometimes does.
Windows doesn't make this obvious. An .ico file can look like a single icon and actually be a bundle of anywhere from one to eight embedded resolutions, and there's no built-in way to just open one and see a clean list of what's inside. We ended up writing a small script to parse the ICONDIR headers ourselves just to check — and then realized that if we needed this, other developers building Windows apps probably run into the same wall.
What it turned into
Icon Commander started as that one inspection script and grew into a proper library manager: import a folder of icons, see exactly what's embedded in each .ico, organize everything by project instead of one flat folder, and batch-convert between ICO, PNG, and SVG when a format doesn't match what you need.
Catching problems before they ship
The feature we keep reaching for ourselves is the size-gap check: point it at an icon and it tells you, plainly, which of the sizes Windows usually asks for aren't actually in there. It's the same question that started this whole thing — "does this icon actually have a 256px entry" — just generalized to every size instead of the one we happened to be missing that day.
Where things stand
The inspector, the library organization, and batch conversion are all working well in our own daily use. Export presets — generating the exact size set a specific target (a Windows Store listing, a favicon set, an installer) expects in one step — are the last piece we're finishing before it's ready for anyone outside the team to install.
No download yet, but it's close. If you've ever shipped an icon and hoped it looked right at every size Windows might request, this is one to keep an eye on.