LZ77 and LZ78

<h2 id="theoretical-efficiency">Theoretical efficiency</h2>
In the second of the two papers that introduced these algorithms they are analyzed as encoders defined by finite-state machines. A measure analogous to <a href="/facts/Information_entropy/NLg4NLvt">information entropy</a> is developed for individual sequences (as opposed to probabilistic ensembles). This measure gives a bound on the <a href="/facts/Data_compression_ratio/eDEWGzTv">data compression ratio</a> that can be achieved. It is then shown that there exists finite lossless encoders for every sequence that achieve this bound as the length of the sequence grows to infinity. In this sense an algorithm based on this scheme produces asymptotically optimal encodings. This result can be proven more directly, as for example in notes by <a href="/facts/Peter_Shor/YIztGkMY">Peter Shor</a>.<a class="footnote-ref" id="fnref:7" href="#fn:7">7</a>
Formally, (Theorem 13.5.2 <a class="footnote-ref" id="fnref:8" href="#fn:8">8</a>).

LZ78 is universal and entropic—If 
 
 
 
 X
 
 
 {\textstyle X}
 
 is a binary source that is stationary and ergodic, then 
 
 
 
 
 lim sup
 
 n
 
 
 
 
 1
 n
 
 
 
 l
 
 L
 Z
 78
 
 
 (
 
 X
 
 1
 :
 n
 
 
 )
 ≤
 h
 (
 X
 )
 
 
 {\displaystyle \limsup _{n}{\frac {1}{n}}l_{LZ78}(X_{1:n})\leq h(X)}
 
 with probability 1. Here 
 
 
 
 h
 (
 X
 )
 
 
 {\textstyle h(X)}
 
 is the entropy rate of the source.

Similar theorems apply to other versions of LZ algorithm.
<h2 id="lz77">LZ77</h2>
LZ77 algorithms achieve compression by replacing repeated occurrences of data with references to a single copy of that data existing earlier in the uncompressed data stream. A match is encoded by a pair of numbers called a length-distance pair, which is equivalent to the statement "each of the next length characters is equal to the characters exactly distance characters behind it in the uncompressed stream". (The distance is sometimes called the offset instead.)
To spot matches, the encoder must keep track of some amount of the most recent data, such as the last 2 <a href="/facts/Kilobyte/jIe6t4yv">KB</a>, 4 KB, or 32 KB. The structure in which this data is held is called a sliding window, which is why LZ77 is sometimes called sliding-window compression. The encoder needs to keep this data to look for matches, and the decoder needs to keep this data to interpret the matches the encoder refers to. The larger the sliding window is, the longer back the encoder may search for creating references.
It is not only acceptable but frequently useful to allow length-distance pairs to specify a length that actually exceeds the distance. As a copy command, this is puzzling: "Go back four characters and copy ten characters from that position into the current position". How can ten characters be copied over when only four of them are actually in the buffer? Tackling one byte at a time, there is no problem serving this request, because as a byte is copied over, it may be fed again as input to the copy command. When the copy-from position makes it to the initial destination position, it is consequently fed data that was pasted from the beginning of the copy-from position. The operation is thus equivalent to the statement "copy the data you were given and repetitively paste it until it fits". As this type of pair repeats a single copy of data multiple times, it can be used to incorporate a flexible and easy form of <a href="/facts/Run-length_encoding/3k6x9afM">run-length encoding</a>.
Another way to see things is as follows: While encoding, for the search pointer to continue finding matched pairs past the end of the search window, all characters from the first match at offset D and forward to the end of the search window must have matched input, and these are the (previously seen) characters that compose a single run unit of length LR, which must equal D. Then as the search pointer proceeds past the search window and forward, as far as the run pattern repeats in the input, the search and input pointers will be in sync and match characters until the run pattern is interrupted. Then L characters have been matched in total, L > D, and the code is [D, L, c].
Upon decoding [D, L, c], again, D = LR. When the first LR characters are read to the output, this corresponds to a single run unit appended to the output buffer. At this point, the read pointer could be thought of as only needing to return int(L/LR) + (1 if L mod LR ≠ 0) times to the start of that single buffered run unit, read LR characters (or maybe fewer on the last return), and repeat until a total of L characters are read. But mirroring the encoding process, since the pattern is repetitive, the read pointer need only trail in sync with the write pointer by a fixed distance equal to the run length LR until L characters have been copied to output in total.
Considering the above, especially if the compression of data runs is expected to predominate, the window search should begin at the end of the window and proceed backwards, since run patterns, if they exist, will be found first and allow the search to terminate, absolutely if the current maximal matching sequence length is met, or judiciously, if a sufficient length is met, and finally for the simple possibility that the data is more recent and may correlate better with the next input.

<h3>Pseudocode</h3>
The following pseudocode is a reproduction of the LZ77 compression algorithm sliding window.

while input is not empty do
 match := longest repeated occurrence of input that begins in window
 
 if match exists then
 d := distance to start of match
 l := length of match
 c := char following match in input
 else
 d := 0
 l := 0
 c := first char of input
 end if
 
 output (d, l, c)
 
 discard l + 1 chars from front of window
 s := pop l + 1 chars from front of input
 append s to back of window
repeat

<h3>Implementations</h3>
Even though all LZ77 algorithms work by definition on the same basic principle, they can vary widely in how they encode their compressed data to vary the numerical ranges of a length–distance pair, alter the number of bits consumed for a length–distance pair, and distinguish their length–distance pairs from literals (raw data encoded as itself, rather than as part of a length–distance pair). A few examples:

<ul><li>The algorithm illustrated in Lempel and Ziv's original 1977 article outputs all its data three values at a time: the length and distance of the longest match found in the buffer, and the literal that followed that match. If two successive characters in the input stream could be encoded only as literals, the length of the length–distance pair would be 0.</li>
<li><a href="/facts/Lempel%E2%80%93Ziv%E2%80%93Storer%E2%80%93Szymanski/KHe7a3eJ">LZSS</a> improves on LZ77 by using a 1-bit flag to indicate whether the next chunk of data is a literal or a length–distance pair, and using literals if a length–distance pair would be longer.</li>
<li>In the PalmDoc format, a length–distance pair is always encoded by a two-byte sequence. Of the 16 bits that make up these two bytes, 11 bits go to encoding the distance, 3 go to encoding the length, and the remaining two are used to make sure the decoder can identify the first byte as the beginning of such a two-byte sequence.</li>
<li>In the implementation used for many games by <a href="/facts/Electronic_Arts/fy7Ppdem">Electronic Arts</a>,<a class="footnote-ref" id="fnref:9" href="#fn:9">9</a> the size in bytes of a length–distance pair can be specified inside the first byte of the length–distance pair itself; depending on whether the first byte begins with a 0, 10, 110, or 111 (when read in <a href="/facts/Endianness/wbrQnyu3">big-endian</a> bit orientation), the length of the entire length–distance pair can be 1 to 4 bytes.</li>
<li>As of 2008<a href="https://en.wikipedia.org/w/index.php?title=LZ77_and_LZ78&action=edit">[update]</a>, the most popular LZ77-based compression method is <a href="/facts/DEFLATE/XnBt1GKV">DEFLATE</a>; it combines LZSS with <a href="/facts/Huffman_coding/dBgMBz48">Huffman coding</a>.<a class="footnote-ref" id="fnref:10" href="#fn:10">10</a> Literals, lengths, and a symbol to indicate the end of the current block of data are all placed together into one alphabet. Distances can be safely placed into a separate alphabet; because a distance only occurs just after a length, it cannot be mistaken for another kind of symbol or vice versa.</li></ul>
<h2 id="lz78">LZ78</h2>
The LZ78 algorithms compress sequential data by building a dictionary of token sequences from the input, and then replacing the second and subsequent occurrence of the sequence in the data stream with a reference to the dictionary entry. The observation is that the number of repeated sequences is a good measure of the non random nature of a sequence. The algorithms represent the dictionary as an n-ary tree where n is the number of tokens used to form token sequences. Each dictionary entry is of the form dictionary[...] = {index, token}, where index is the index to a dictionary entry representing a previously seen sequence, and token is the next token from the input that makes this entry unique in the dictionary. Note how the algorithm is greedy, and so nothing is added to the table until a unique making token is found. The algorithm is to initialize last matching index = 0 and next available index = 1 and then, for each token of the input stream, the dictionary searched for a match: {last matching index, token}. If a match is found, then last matching index is set to the index of the matching entry, nothing is output, and last matching index is left representing the input so far. Input is processed until a match is not found. Then a new dictionary entry is created, dictionary[next available index] = {last matching index, token}, and the algorithm outputs last matching index, followed by token, then resets last matching index = 0 and increments next available index. As an example consider the sequence of tokens AABBA which would assemble the dictionary;

0 {0,_}
1 {0,A}
2 {1,B}
3 {0,B}
and the output sequence of the compressed data would be 0A1B0B. Note that the last A is not represented yet as the algorithm cannot know what comes next. In practice an EOF marker is added to the input – AABBA$ for example. Note also that in this case the output 0A1B0B1$ is longer than the original input but compression ratio improves considerably as the dictionary grows, and in binary the indexes need not be represented by any more than the minimum number of bits.<a class="footnote-ref" id="fnref:11" href="#fn:11">11</a>
Decompression consists of rebuilding the dictionary from the compressed sequence. From the sequence 0A1B0B1$ the first entry is always the terminator 0 {...} , and the first from the sequence would be 1 {0,A} . The A is added to the output. The second pair from the input is 1B and results in entry number 2 in the dictionary, {1,B}. The token "B" is output, preceded by the sequence represented by dictionary entry 1. Entry 1 is an 'A' (followed by "entry 0" – nothing) so AB is added to the output. Next 0B is added to the dictionary as the next entry, 3 {0,B} , and B (preceded by nothing) is added to the output. Finally a dictionary entry for 1$ is created and A$ is output resulting in A AB B A$ or AABBA removing the spaces and EOF marker.

<h2 id="lzw">LZW</h2>
<a href="/facts/Lempel%E2%80%93Ziv%E2%80%93Welch/hJfgYm9j">LZW</a> is an LZ78-based algorithm that uses a dictionary pre-initialized with all possible characters (symbols) or emulation of a pre-initialized dictionary. The main improvement of <a href="/facts/Lempel%E2%80%93Ziv%E2%80%93Welch/hJfgYm9j">LZW</a> is that when a match is not found, the current input stream character is assumed to be the first character of an existing string in the dictionary (since the dictionary is initialized with all possible characters), so only the last matching index is output (which may be the pre-initialized dictionary index corresponding to the previous (or the initial) input character). Refer to the <a href="/facts/Lempel%E2%80%93Ziv%E2%80%93Welch/hJfgYm9j">LZW</a> article for implementation details.
BTLZ is an LZ78-based algorithm that was developed for use in real-time communications systems (originally modems) and standardized by CCITT/ITU as <a href="/facts/V.42bis/P85K5Jgw">V.42bis</a>. When the <a href="/facts/Trie/cXNr0ScT">trie</a>-structured dictionary is full, a simple re-use/recovery algorithm is used to ensure that the dictionary can keep adapting to changing data. A counter cycles through the dictionary. When a new entry is needed, the counter steps through the dictionary until a leaf node is found (a node with no dependents). This is deleted and the space re-used for the new entry. This is simpler to implement than LRU or LFU and achieves equivalent performance.

<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Lempel%E2%80%93Ziv%E2%80%93Stac/EexMXmjd">Lempel–Ziv–Stac</a> (LZS)</li></ul>

<h2 id="external-links">External links</h2>
<ul><li> Media related to LZ77 algorithm at Wikimedia Commons</li>
<li> Media related to LZ78 algorithm at Wikimedia Commons</li>
<li><a href="https://archive.today/20130107232302/http://oldwww.rasip.fer.hr/research/compress/algorithms/fund/lz/lz77.html">"The LZ77 algorithm"</a>. Data Compression Reference Center: RASIP working group. <a href="/facts/Faculty_of_Electrical_Engineering_and_Computing,_University_of_Zagreb/A2rvugTa">Faculty of Electrical Engineering and Computing, University of Zagreb</a>. 1997. Archived from <a href="http://oldwww.rasip.fer.hr/research/compress/algorithms/fund/lz/lz77.html">the original</a> on 7 January 2013. Retrieved 22 June 2012.</li></ul>
<ul><li><a href="https://archive.today/20130107200800/http://oldwww.rasip.fer.hr/research/compress/algorithms/fund/lz/lz78.html">"The LZ78 algorithm"</a>. Data Compression Reference Center: RASIP working group. Faculty of Electrical Engineering and Computing, University of Zagreb. 1997. Archived from <a href="http://oldwww.rasip.fer.hr/research/compress/algorithms/fund/lz/lz78.html">the original</a> on 7 January 2013. Retrieved 22 June 2012.</li></ul>
<ul><li><a href="https://archive.today/20130107170646/http://oldwww.rasip.fer.hr/research/compress/algorithms/fund/lz/lzw.html">"The LZW algorithm"</a>. Data Compression Reference Center: RASIP working group. Faculty of Electrical Engineering and Computing, University of Zagreb. 1997. Archived from <a href="http://oldwww.rasip.fer.hr/research/compress/algorithms/fund/lz/lzw.html">the original</a> on 7 January 2013. Retrieved 22 June 2012.</li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1">Ziv, Jacob; Lempel, Abraham (May 1977). "A Universal Algorithm for Sequential Data Compression". IEEE Transactions on Information Theory. 23 (3): 337–343. CiteSeerX 10.1.1.118.8921. doi:10.1109/TIT.1977.1055714. S2CID 9267632. <a href="/wiki/Jacob_Ziv" target="_blank">/wiki/Jacob_Ziv</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></li>
<li id="fn:2">Ziv, Jacob; Lempel, Abraham (September 1978). "Compression of Individual Sequences via Variable-Rate Coding". IEEE Transactions on Information Theory. 24 (5): 530–536. CiteSeerX 10.1.1.14.2892. doi:10.1109/TIT.1978.1055934. <a href="/wiki/Jacob_Ziv" target="_blank">/wiki/Jacob_Ziv</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></li>
<li id="fn:3">US Patent No. 5532693 Adaptive data compression system with systolic string matching logic <a href="https://image-ppubs.uspto.gov/dirsearch-public/print/downloadPdf/5532693" target="_blank">https://image-ppubs.uspto.gov/dirsearch-public/print/downloadPdf/5532693</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></li>
<li id="fn:4">"Lossless Data Compression: LZ78". cs.stanford.edu. <a href="https://cs.stanford.edu/people/eroberts/courses/soco/projects/data-compression/lossless/lz78/concept.htm" target="_blank">https://cs.stanford.edu/people/eroberts/courses/soco/projects/data-compression/lossless/lz78/concept.htm</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></li>
<li id="fn:5">"Milestones:Lempel–Ziv Data Compression Algorithm, 1977". IEEE Global History Network. Institute of Electrical and Electronics Engineers. 22 July 2014. Retrieved 9 November 2014. <a href="https://www.ieeeghn.org/wiki/index.php/Milestones:Lempel-Ziv_Data_Compression_Algorithm,_1977" target="_blank">https://www.ieeeghn.org/wiki/index.php/Milestones:Lempel-Ziv_Data_Compression_Algorithm,_1977</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></li>
<li id="fn:6">Joanna, Goodrich. "IEEE Medal of Honor Goes to Data Compression Pioneer Jacob Ziv". IEEE Spectrum: Technology, Engineering, and Science News. Retrieved 18 January 2021. <a href="https://spectrum.ieee.org/ieee-medal-of-honor-goes-to-data-compression-pioneer-jacob-ziv" target="_blank">https://spectrum.ieee.org/ieee-medal-of-honor-goes-to-data-compression-pioneer-jacob-ziv</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></li>
<li id="fn:7">Peter Shor (14 October 2005). "Lempel–Ziv notes" (PDF). Archived from the original (PDF) on 28 May 2021. Retrieved 9 November 2014. <a href="/wiki/Peter_Shor" target="_blank">/wiki/Peter_Shor</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></li>
<li id="fn:8">Cover, Thomas M.; Thomas, Joy A. (2006). Elements of information theory (2nd ed.). Hoboken, N.J: Wiley-Interscience. ISBN 978-0-471-24195-9. <a href="978-0-471-24195-9" target="_blank">978-0-471-24195-9</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></li>
<li id="fn:9">"QFS Compression (RefPack)". Niotso Wiki. Retrieved 9 November 2014. <a href="http://wiki.niotso.org/QFS_compression" target="_blank">http://wiki.niotso.org/QFS_compression</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></li>
<li id="fn:10">Feldspar, Antaeus (23 August 1997). "An Explanation of the Deflate Algorithm". comp.compression newsgroup. zlib.net. Retrieved 9 November 2014. <a href="https://www.zlib.net/feldspar.html" target="_blank">https://www.zlib.net/feldspar.html</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></li>
<li id="fn:11">https://math.mit.edu/~goemans/18310S15/lempel-ziv-notes.pdf [bare URL PDF] <a href="https://math.mit.edu/~goemans/18310S15/lempel-ziv-notes.pdf" target="_blank">https://math.mit.edu/~goemans/18310S15/lempel-ziv-notes.pdf</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></li>
</ol>

LZ77 and LZ78 open-in-new

LZ77 and LZ78