Cisco IOS-XE: Why Converting from .bin to .pkg is "Better" In the world of Cisco IOS-XE, the debate between and Install Mode isn't just about file extensions; it's about how your hardware utilizes its resources. While most administrators are used to the monolithic .bin file, Cisco now strongly recommends Install Mode —which uses extracted .pkg files—for modern Catalyst 9000 series switches and routers. The Core Difference: .bin vs. .pkg
The conversion process typically involves cleaning existing files, expanding the files, and updating the boot variable. Cisco Community cisco convert bin to pkg better
| Aspect | Manual extraction | Cisco expand command | |--------|------------------|------------------------| | Preserves crypto signatures | ❌ No | ✅ Yes | | Creates packages.conf | ❌ No | ✅ Yes | | Supports ISSU later | ❌ No | ✅ Yes | | TAC-supported | ❌ No | ✅ Yes | | Speed | Slow (copy errors) | Optimized | Bundle Mode Cisco IOS-XE: Why Converting from
When conversion is “better” Converting a .bin to a .pkg can be better when it enables platform-native installation tools, supports modular upgrades or rollbacks, improves automation and auditing, or matches organizational deployment pipelines—provided the conversion preserves integrity and remains within vendor-supported paths. It is not better when conversion risks breaking signature checks, voids support, or introduces untestable changes. Preserve image integrity: never alter the binary payload
Better approach – use unzip (since many Cisco bins are ZIP-like internally):
Alex knew there was a better way: . By converting the monolithic .bin file into modular .pkg files, the switch would gain a "table of contents" called packages.conf , allowing it to boot instantly and run more efficiently. The Transformation Quest
switch# request platform software package expand file flash:cat9k_iosxe.17.09.01.SPA.bin to flash: