A .CB7 file is a comic bundle stored in a 7-Zip container, consisting of sequentially named JPG/PNG/WebP pages plus possible metadata files, and comic apps use the naming to determine page order; unsupported apps may need the archive converted to CBZ, and legitimate CB7 files should simply unpack like a typical 7z containing cleanly ordered images.
The “reading order” matters since an archive stores files without sequencing, leaving it to apps to sort alphabetically, which is why zero-padding (`001`, `002`, `010`) prevents misordering like `10` being placed before `2`; in short a CB7 is just images wrapped in 7z compression under a comic-friendly extension, making distribution cleaner, avoiding loose-file problems, enabling comic-reader features like zoom and library tracking, carrying metadata files together, protecting structure, and sometimes compressing mixed assets more efficiently.
For more info in regards to CB7 file support look into our own web page. Inside a .CB7 file you’ll usually find a simple “images as pages” layout, mostly JPG/PNG/WebP files named in zero-padded order (`001.jpg`, `002.jpg`, etc.), sometimes arranged into chapter folders, plus optional extras like `cover.jpg` and metadata such as `ComicInfo.xml`, with occasional harmless clutter like `Thumbs.db`; anything unusual like `.exe` or `.bat` is a red flag, and to open the file you either load it in a comic reader that auto-sorts the pages or treat it as a 7z archive using tools like 7-Zip, Keka, or p7zip.
A quick way to check if a .CB7 file is safe is to open it using 7-Zip and look for the classic comic layout, which means mostly JPG/PNG files named in order and maybe a `cover.jpg` or `ComicInfo.xml`; if instead you find executables or scripts like `.exe`, `.bat`, `.ps1`, `.js`, or any non-image clutter, that’s a strong warning sign, and real comics typically show consistent file sizes, with any 7-Zip read errors suggesting corruption or an invalid file.
