Skip to content
💾 Free general-purpose data compression software with high compression ratio and excellent multi-threaded performance..
C C++ Roff M4 Objective-C Assembly Other
Branch: master
Clone or download
Pull request Compare This branch is 241 commits ahead of xz-mirror:master.
Type Name Latest commit message Commit time
Failed to load latest commit information.
build-aux Rename api/lzma to api/flzma to avoid installation clash Mar 26, 2019
debug Rename lzma.h; modify doc; change -9 dict to 128Mb; pass thread count… Mar 26, 2019
doc Spelling May 29, 2019
extra extra/scanlzma: Fix compiler warnings. Apr 29, 2018
lib Put the interesting parts of XZ Utils into the public domain. Apr 13, 2009
m4 tuklib_integer: Autodetect support for unaligned access on ARM. Jun 1, 2019
macosx Rename xz to fxz Mar 20, 2019
po Update German translation, mostly wrt orthography Aug 27, 2015
src libflzma: Read hash input with unaligned access helper instead of macro Sep 15, 2019
tests Merge branch 'master' of into dev Sep 1, 2019
windows windows: remove fast-lzma2 include folder and old preprocessor defs Sep 15, 2019
.gitignore Change presets; add rmf to xz options Mar 19, 2019
AUTHORS Fix formatting Mar 27, 2019
COPYING Update the home page URLs to HTTPS. Apr 19, 2017
COPYING.GPLv2 Update the copies of GPLv2 and LGPLv2.1 from Nov 4, 2010
COPYING.GPLv3 Imported to git. Dec 8, 2007
COPYING.LGPLv2.1 Update the copies of GPLv2 and LGPLv2.1 from Nov 4, 2010
ChangeLog Update docs Mar 27, 2019 Spelling May 29, 2019
INSTALL Update INSTALL May 31, 2019
INSTALL.generic Update INSTALL.generic. Oct 19, 2010 Remove dos build May 31, 2019
NEWS Spelling May 29, 2019
PACKAGERS Update docs. Oct 19, 2010
README Update README May 28, 2019
THANKS Merge branch 'master' of into dev Sep 1, 2019
TODO Added a comment about "autoconf -fi" to Jun 29, 2009 Merge branch 'master' of into dev Sep 1, 2019


FXZ Utils

    0. Overview
    1. Documentation
       1.1. Overall documentation
       1.2. Documentation for command-line tools
       1.3. Documentation for libflzma
    2. Version numbering
    3. Reporting bugs
    4. Translating the fxz tool
    5. Other implementations of the .xz format
    6. Contact information

0. Overview

    FXZ Utils is a fork of XZ Utils. It adds a multi-threaded radix
    match finder and optimized encoder. The documentation, including this
    file, is based upon the XZ Utils documentation.

    The fxz command-line tool, derived from xz, provides faster
    compression than xz on most inputs, but a slightly larger output.
    These tests on the 723 MiB 'raspbian-jessie-lite-20151121.tar' from
    the Squash Compression Corpus demonstrate performance relative to xz
    using 4 threads:

          Preset   Size  Time  MiB/s  RAM MiB
      xz     4    222.6  1:06  10.9      333
      fxz    4    222.8  0:42  16.9       50
      xz     6    213.4  1:33   7.7      661
      fxz    6    214.2  0:53  13.6       92
      xz     8    195.9  1:47   6.7    2,629
      fxz    8    196.7  1:02  11.5      336

    FXZ Utils provide a general-purpose data-compression library plus
    command-line tools. The native file format is the .xz format, but
    also the legacy .lzma format is supported. The .xz format supports
    multiple compression algorithms, which are called "filters" in the
    context of FXZ Utils. The primary filter is currently LZMA2. With
    typical files, FXZ Utils create about 30 % smaller files than gzip.

    To ease adapting support for the .xz format into existing applications
    and scripts, the API of libflzma is somewhat similar to the API of the
    popular zlib library. For the same reason, the command-line tool fxz
    has a command-line syntax similar to that of gzip.

    When aiming for the highest compression ratio, the LZMA2 encoder uses
    a lot of CPU time and may use, depending on the settings, even
    hundreds of megabytes of RAM. However, in fast modes, the LZMA2 encoder
    competes with bzip2 in compression speed, RAM usage, and compression

    LZMA2 is reasonably fast to decompress. It is a little slower than
    gzip, but a lot faster than bzip2. Being fast to decompress means
    that the .xz format is especially nice when the same file will be
    decompressed very many times (usually on different computers), which
    is the case e.g. when distributing software packages. In such
    situations, it's not too bad if the compression takes some time,
    since that needs to be done only once to benefit many people.

    With some file types, combining (or "chaining") LZMA2 with an
    additional filter can improve the compression ratio. A filter chain may
    contain up to four filters, although usually only one or two are used.
    For example, putting a BCJ (Branch/Call/Jump) filter before LZMA2
    in the filter chain can improve compression ratio of executable files.

    Since the .xz format allows adding new filter IDs, it is possible that
    some day there will be a filter that is, for example, much faster to
    compress than LZMA2 (but probably with worse compression ratio).
    Similarly, it is possible that some day there is a filter that will
    compress better than LZMA2.

    FXZ Utils doesn't support multithreaded decompression yet. It has been
    planned though and taken into account when designing the .xz file format.

1. Documentation

1.1. Overall documentation

    README              This file

    INSTALL.generic     Generic install instructions for those not familiar
                        with packages using GNU Autotools
    INSTALL             Installation instructions specific to FXZ Utils
    PACKAGERS           Information to packagers of FXZ Utils

    COPYING             FXZ Utils copyright and license information
    COPYING.GPLv2       GNU General Public License version 2
    COPYING.GPLv3       GNU General Public License version 3
    COPYING.LGPLv2.1    GNU Lesser General Public License version 2.1

    AUTHORS             The main authors of FXZ Utils
    THANKS              Incomplete list of people who have helped making
                        this software
    NEWS                User-visible changes between FXZ Utils releases
    ChangeLog           Detailed list of changes (commit log)
    TODO                Known bugs and some sort of to-do list

    Note that only some of the above files are included in binary

1.2. Documentation for command-line tools

    The command-line tools are documented as man pages. In source code
    releases (and possibly also in some binary packages), the man pages
    are also provided in plain text (ASCII only) and PDF formats in the
    directory "doc/man" to make the man pages more accessible to those
    whose operating system doesn't provide an easy way to view man pages.

1.3. Documentation for libflzma

    The libflzma API headers include short docs about each function
    and data type as Doxygen tags. These docs should be quite OK as
    a quick reference.

    If you have never used libflzma, libbzip2, or zlib, I recommend
    learning the *basics* of the zlib API. Once you know that, it should
    be easier to learn libflzma.

2. Version numbering

    The version number format of FXZ Utils is X.Y.ZS:

      - X is the major version. When this is incremented, the library
        API and ABI break.

      - Y is the minor version. It is incremented when new features
        are added without breaking the existing API or ABI. An even Y
        indicates a stable release and an odd Y indicates unstable
        (alpha or beta version).

      - Z is the revision. This has a different meaning for stable and
        unstable releases:

          * Stable: Z is incremented when bugs get fixed without adding
            any new features. This is intended to be convenient for
            downstream distributors that want bug fixes but don't want
            any new features to minimize the risk of introducing new bugs.

          * Unstable: Z is just a counter. API or ABI of features added
            in earlier unstable releases having the same X.Y may break.

      - S indicates stability of the release. It is missing from the
        stable releases, where Y is an even number. When Y is odd, S
        is either "alpha" or "beta" to make it very clear that such
        versions are not stable releases. The same X.Y.Z combination is
        not used for more than one stability level, i.e. after X.Y.Zalpha,
        the next version can be X.Y.(Z+1)beta but not X.Y.Zbeta.

3. Reporting bugs

    If the bug exists in XZ Utils too, it would be better to report it
    to the maintainer of that project, as it is widely used and XZ
    fixes can easily be incorporated into FXZ. For information see

    Naturally it is easiest for me if you already know what causes the
    unexpected behavior. Even better if you have a patch to propose.
    However, quite often the reason for unexpected behavior is unknown,
    so here are a few things to do before sending a bug report:

      1. Try to create a small example how to reproduce the issue.

      2. Compile FXZ Utils with debugging code using configure switches
         --enable-debug and, if possible, --disable-shared. If you are
         using GCC, use CFLAGS='-O0 -ggdb3'. Don't strip the resulting

      3. Turn on core dumps. The exact command depends on your shell;
         for example in GNU bash it is done with "ulimit -c unlimited",
         and in tcsh with "limit coredumpsize unlimited".

      4. Try to reproduce the suspected bug. If you get "assertion failed"
         message, be sure to include the complete message in your bug
         report. If the application leaves a coredump, get a backtrace
         using gdb:
           $ gdb /path/to/app-binary   # Load the app to the debugger.
           (gdb) core core   # Open the coredump.
           (gdb) bt   # Print the backtrace. Copy & paste to bug report.
           (gdb) quit   # Quit gdb.

    Report your bug via email (see Contact information below).
    Don't send core dump files or any executables. If you have a small
    example file(s) (total size less than 256 KiB), please include
    it/them as an attachment. If you have bigger test files, put them
    online somewhere and include a URL to the file(s) in the bug report.

    Always include the exact version number of FXZ Utils in the bug report.
    If you are using a snapshot from the git repository, use "git describe"
    to get the exact snapshot version. If you are using FXZ Utils shipped
    in an operating system distribution, mention the distribution name,
    distribution version, and exact fxz package version; if you cannot
    repeat the bug with the code compiled from unpatched source code,
    you probably need to report a bug to your distribution's bug tracking

4. Other implementations of the .xz format

    7-Zip and the p7zip port of 7-Zip support the .xz format starting
    from the version 9.00alpha.

    XZ Embedded is a limited implementation written for use in the Linux
    kernel, but it is also suitable for other embedded use.

5. Contact information

    If you have questions, bug reports, patches etc. related to FXZ
    Utils, contact Conor McCarthy <>.
    I'm sometimes slow at replying. If you haven't got a reply within two
    weeks, assume that your email has got lost and resend it.
You can’t perform that action at this time.