Three modes, one decision
Lightning for speed, Balanced for the middle, Compact for size. The panel tells you which is fastest and which is smallest instead of hiding it behind a number from 1 to 9.
Features
What is actually built, tested and running. Anything half-finished is named on this page rather than implied.
Lightning for speed, Balanced for the middle, Compact for size. The panel tells you which is fastest and which is smallest instead of hiding it behind a number from 1 to 9.
A match finder, a canonical Huffman stage and a two-level decode table — all in this project's own code. No third-party compression library is linked into the program.
Blocks are compressed in parallel across the processors you allow, inside a memory cap you set in Settings. A smaller cap still finishes; it just overlaps less.
Revisions of one document, exports sharing a schema, logs in one format: a dictionary built across them has measured 16.7% of the archive those same files produce without it. It is off by default, because on a mixed folder it buys nothing.
.jab is the native container: fastest to write, per-block checksums, and the only one of the three that can carry a password here. .zip and .7z are written plainly so that any other tool opens them without comment.
Store and deflate for ZIP, LZMA2 folders for 7z including the x86 branch filter when reading, ustar with GNU long names for tar.
A .zip written here has no AES, no extended timestamps and no Unix permissions. A .7z has one LZMA2 folder per solid block and no per-file filters. For better compression, per-block SHA-256 or a password, the answer is a .jab.
One record per block, a 96-bit nonce and a 128-bit tag, from the operating system's own implementation. No cryptography is invented in this project.
The manifest — file names, sizes, timestamps, attributes — is one encrypted record, and so is the chunk table that holds the per-block SHA-256 and CRC-32C values.
A tag over an empty plaintext tells a reader the password is wrong after a single PBKDF2 derivation, instead of after decoding the whole archive.
Reserve 1–30% of spare data inside a .jab and a damaged block can be rebuilt rather than merely reported. It has to be added before the damage happens, and only .jab can carry one.
Every block carries a CRC-32C; SHA-256 per block is on unless you turn it off. The first says a block is wrong, the second makes a silent miss vanishingly unlikely.
Check thoroughly reads the header, footer, chunk table and manifest for consistency, then decodes every block. Decode only skips the structural pass. Neither writes a file.
Neither check can tell you an archive was not tampered with: whoever can edit the data can recompute both values. Only a password-protected archive answers that question.
An archive is written to a .partial file and renamed when it is whole, so an interrupted run never leaves something that looks finished.
Write .001, .002, … beside the archive at 10, 25, 100 or 700 MB, or any size you type. The parts are not readable on their own; merging checks every part before writing.
Compares whole files by SHA-256 inside an archive, so only exact copies are reported, and tells you how much space removing the extras would reclaim. Empty files are skipped.
Checks whether a folder still matches what was archived. Both sides are hashed, so a change that kept the same size and timestamp is still found.
Scan reports which shards are damaged and writes nothing. Repair rewrites exactly the parts that are wrong, using the recovery record.
No web view, no framework: the interface is painted with Direct2D and DirectWrite, which is why it starts instantly and stays responsive while a job runs.
Open an archive, sort and filter its contents, and preview text, images, PDFs — one page — and audio without extracting first.
Jobs run one at a time in the order they were added. A waiting job can be reordered or dropped, the running one can be held, and a long job can be sent to the background instead of blocking the window.
Find an archive by name, then press Enter to look inside the ones it found. It says plainly how many it read, how many were missing and how many it could not open.
Right-click entries for compressing, extracting and testing, added from the Settings screen and removed from the same place.
Every string in the interface is translated into 28 languages, with plural rules per language rather than one English rule applied everywhere.
The same engine, scriptable. Create, extract, list, test and verify, with the thread count, memory budget and integrity level as flags. A password is never accepted as an argument — the full command line of a running process is readable by other processes under the same account — so it is read from stdin or prompted for with the echo off.
Guide> jab c .\project -o project.jab --mode lightning
scanning 412 files, 268 MB
writing project.jab
output 96.4 MB (36.0% of input)
elapsed 1.84 s — 145.7 MB/s
> jab t project.jab
412 entries · 268 MB checked · structure and every block
ok
> jab x project.jab -o .\restored --overwrite fail
412 files written, 0 skipped
elapsed 0.94 s
No installer and no code signature: 1.0 is a portable build, and Windows will warn about an unsigned program.
No right-to-left layout, which is why Arabic and Hebrew are written but withheld.
An incremental archive cannot record a deletion, and keyfiles are not implemented.
Thread scaling is still below RAR's, and RAR5 Normal still compresses smaller.