unrar-free vs unrar: Key Limitations Explained

When managing RAR archives on Linux distributions, users frequently encounter two distinct packages: unrar-free and the non-free unrar. While unrar-free is fully open-source and included in default repositories to satisfy strict free-software guidelines, it lacks significant functionality compared to the proprietary unrar utility maintained by RARLAB. This article outlines the major limitations of unrar-free, including its inability to handle modern RAR formats, encryption issues, and missing archive-management features.

Lack of RAR5 Format Support

The most critical limitation of unrar-free is its historical and ongoing incompatibility with the RAR 5.0 (RARv5) compression format. WinRAR introduced the RAR5 standard in 2013, making it the default format for modern archives.

  • unrar (non-free): Natively supports both legacy RAR formats (RAR 1.5 to 4.x) and the modern RAR5 format.
  • unrar-free: Generally only supports older RAR versions (up to RAR 2.x or partial RAR 3.x/4.x depending on the backend version). Attempting to unpack a RAR5 file with unrar-free typically produces an error stating the archive is corrupt or uses an unsupported compression method.

Incomplete or Broken Password and Encryption Handling

Modern RAR archives use AES-256 encryption to protect filenames and data.

  • unrar (non-free): Seamlessly prompts for passwords and extracts archives encrypted with AES-128 or AES-256, including those with encrypted file headers (where file names are hidden until the password is provided).
  • unrar-free: Often fails completely when encountering encrypted headers. Even with standard encrypted archives, decryption support can be unreliable, frequently causing extraction failures or silent errors.

Multi-Volume (Split) Archive Issues

Users frequently encounter archives split across multiple files (.part1.rar, .part2.rar or .r00, .r01).

  • unrar (non-free): Automatically tracks, verifies, and spans across all consecutive volumes as long as they reside in the same directory.
  • unrar-free: Often struggles to automatically detect subsequent parts, especially if modern naming conventions are used, leading to incomplete extractions.

Missing Advanced Features and Archive Metadata

The official unrar utility includes extensive options for interacting with the internal structures of RAR files, whereas unrar-free is a bare-bones implementation. Missing features in unrar-free include:

  • Solid Archive Support: While basic extraction may work, extraction speed and reliability on large "solid" archives (where multiple files are compressed as a single continuous data stream) are significantly worse.
  • Recovery Records: unrar can detect and use built-in recovery records to repair damaged archives. unrar-free cannot utilize this data.
  • File Attributes and Permissions: Preservation of POSIX permissions, symlinks, extended attributes, and accurate file modification times is often incomplete in unrar-free.
  • Testing and Integrity Checks: The -t (test) command in unrar performs a robust cyclic redundancy check (CRC) verification across the entire archive, which is less dependable or entirely absent in older iterations of unrar-free.

Why These Differences Exist

The non-free unrar binary is compiled directly from source code provided by RARLAB. While the source is publicly viewable, its license explicitly forbids reverse-engineering the compression algorithm to create a RAR-compatible compressor, classifying it as non-free software under the Debian Free Software Guidelines (DFSG).

In contrast, unrar-free was written from scratch or adapted from separate open-source libraries (such as older versions of libarchive) to ensure complete licensing freedom. Because the RAR format is proprietary and continuously updated, the open-source alternative perpetually lags behind in compatibility and feature parity.