7-Zip at a glance: what it ships, which archives it masters, and how licensing reads for normal users

Reasons teams keep it installed

• 7z pipelines routinely return smaller payloads than vanilla ZIP for the same source tree—handy when VPNs throttle uploads or cold storage bills climb.
• You can both author and consume several ubiquitous formats without chaining extra plug-ins, which reduces support tickets for “mystery” attachments.
• Explorer shell entries mirror what the internal File Manager exposes, so casual users stay productive while power users still get toolbar automation.
• Binaries track a wide span of still-supported Windows versions, from aging classroom PCs to Arm laptops running current channel builds.

Containers you can author versus read-only

Author and reopen locally: 7z, XZ, BZIP2, GZIP, TAR, ZIP, and WIM remain the headline bidirectional formats.

Unpack-first examples: expect read paths for RAR payloads, optical ISO layouts, Microsoft CAB cabinets, Apple-style disk images, NSIS-based installers, numerous Linux tar derivatives, and assorted virtual-disk shells. When a workflow hinges on a rare codec, smoke-test a representative file before promising parity to stakeholders.

Release notes—not this marketing summary—remain the authoritative record whenever maintainers extend parsers or tighten compatibility.

Licensing without the legalese wall

Upstream ships the program as gratis software with readable sources. Core libraries sit under the GNU LGPL while helper modules lean on the three-clause BSD text. Anything touching RAR unpacking inherits extra language from the unRAR notice—consult the license folder inside your deployed MSI or EXE before you fork, embed, or redistribute bundles downstream.

Standard office rollouts, classroom imaging, and personal laptops do not trigger a retail SKU: compliance simply means honoring the bundled texts and not stripping attribution.