Compression

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
(Specific file formats/programs)
(Compression algorithms and compressed data formats)
Line 18: Line 18:
 
* [[DEFLATE]]
 
* [[DEFLATE]]
 
* [[DivANS]]
 
* [[DivANS]]
 +
* [[Fractal compression]]
 
* [[HPACK (HTTP)|HPACK]] (used to compress HTTP headers)
 
* [[HPACK (HTTP)|HPACK]] (used to compress HTTP headers)
 
* [[Huffman coding]]
 
* [[Huffman coding]]

Revision as of 02:24, 26 July 2021

File Format
Name Compression
Ontology

{{{caption}}}

Contents

Stream compression formats

A stream format takes a stream of bytes, and outputs a different, hopefully smaller, stream of bytes. These compression formats are often used internally in other data structures to compress data, as well as in network protocols, such as http. Used stand-alone, a stream compression format does not offer archiving capability, however in the UNIX doctrine, an archiver like tar can be combined with an archive format to produce a proper compressed archive.

Compression algorithms and compressed data formats

(excluding formats usually used as file formats)

Graphics compression

See Graphics#Compression for compression formats used primarily with graphics.

Specific file formats/programs

(multi-file compressors are in Archiving)

Transparent file compression

(A mostly-obsolete technique in which a background process hooks into the OS and decompresses files transparently when they are read. Compression might be done manually. The line between this and Disk compression can be blurry.)

Disk compression

(Transparent disk compression software and the like, excluding filesystem formats.)

For filesystem formats that feature compression, see Filesystem (especially Filesystem#Compressed filesystems).

Executable compression

See Executable compression.

See also

Links

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox