Pco Format Spec

January 18, 2026 ยท View on GitHub

This document aims to describe the Pco format exactly.

All values encoded are unsigned integers. All bit packing (and thus integer encoding) is done in a little-endian fashion. Bit packing a component is completed by filling the rest of the byte with 0s.

Let dtype_size be the number type's number of bits. A "raw" value for a number is a dtype_size value that maps to the number via its from_unsigned function.

Version Compatibility

Define "compatibility line" to be a non-API-breaking sequence of SemVer versions, e.g 0.4.x or 1.x.y. Pco's compatibility guarantee is:

Each library version will be able to decompress any data compressed by

  • earlier or equal library versions (in the sense of SemVer precedence), and
  • later library versions in the same compatibility line, unless opt-in features are added to the API and opted into by the user during compression.

Note that we allow:

  • New library versions may support decompressing data that was previously considered corrupt.
  • Data produced by new compatibility lines may be considered corrupt by old compatibility lines.
  • Within a compatibility line, opt-in compressor features may be added that produce data that was previously considered corrupt.

Wrapped Format Components

The wrapped format consists of 3 components: header, chunk metadata, and data pages. Wrapping formats may encode these components any place they wish. Pco is designed to have one header per file, possibly multiple chunks per header, and possibly multiple pages per chunk.

Plate notation for chunk metadata component:

Pco wrapped chunk meta plate notation

Plate notation for page component:

Pco wrapped page plate notation

Pco's header specifies its major and (as of major version 4) minor versions, allowing Pco to make small format changes in the future if necessary. To explain the meaning of these: suppose a decompressor supports version a.b, and is reading a file with version c.d.

  • If a < c, the decompressor will definitely be unable to read the file; the file has modifications the decompressor does not support.
  • If a >= c, b < d, the decompressor might be able to read the file; the file may or may not contain additions the decompressor does not support.
  • If a >= c, b >= d, the decompressor will definitely be able to read the file.

The header simply consists of

  • [8 bits] the major format version
  • [8 bits] the minor format version

So far, these format versions exist:

format version1st reader lib version1st writer lib versionformat modificationsformat additions
00.0.00.0.0
10.1.00.1.0IntMult mode
20.3.00.3.0FloatQuant mode, 16-bit types
30.4.00.4.0delta encoding variantsLookback delta encoding
4.00.4.8-minor version
4.11.0.01.0.0Dict mode

Chunk Metadata

It is expected that decompressors raise corruption errors if any part of metadata is out of range. For example, if the sum of bin weights does not equal the tANS size; or if a bin's offset bits exceed the data type size.

Each chunk meta consists of

  • [4 bits] mode, using this table:

    valuemodeprimary latentsecondary latentextra_mode_bits
    0ClassicT::L0
    1IntMultT::LT::Ldtype_size
    2FloatMultT::LT::Ldtype_size
    3FloatQuantT::LT::L8
    4Dictu32variable*
    5-15<reserved>

    Here, T::L refers to the latent type with the same number of bits as the number type, e.g. u64 for i64. Dict mode's payload is a 25-bit integer for the count of values in the dictionary, followed by those raw values.

  • [extra_mode_bits bits] for certain modes, extra data is parsed. See the mode-specific formulas below for how this is used, e.g. as the mult, k, or dict values. The value encoded in these bits should be validated; namely, mult mode bases should be finite and nonzero, quant mode must have 0 < k <= MANTISSA_BITS, int modes cannot apply to floats, and vice versa. Parsing the dict value is more complex than the others: it is formed by reading 25 bits for dict_len, followed by 0s until byte-aligned, followed by dict_len raw values that consitute dict.

  • [4 bits] delta_encoding, using this table:

    valuedelta encodingn latent variablesextra_delta_bits
    0None00
    1Consecutive04
    2Lookback110
    3Conv10variable
    4-15<reserved>
  • [extra_delta_bits bits]

    • for consecutive, this is 3 bits for order from 1-7, and 1 bit for whether the mode's secondary latent is delta encoded. An order of 0 is considered a corruption. Let state_n = order.
    • for lookback, this is 5 bits for window_n_log - 1, 4 for state_n_log, and 1 for whether the mode's secondary latent is delta encoded. Let state_n = 1 << state_n_log.
    • for conv1, this is 5 bits for quantization, 64 bits for a raw bias value (i64), 5 bits for the order (number of weights), and 32 bits per raw weight value (i32).
  • per latent variable (ordered by delta latent variables followed by mode latent variables),

    • [4 bits] ans_size_log, the log2 of the size of its tANS table. This may not exceed 14.
    • [15 bits] the count of bins
    • per bin,
      • [ans_size_log bits] 1 less than weight, this bin's weight in the tANS table
      • [dtype_size bits] the lower bound of this bin's numerical range, encoded as a raw value.
      • [log2(dtype_size) + 1 bits] the number of offset bits for this bin e.g. for a 64-bit data type, this will be 7 bits long.

Based on chunk metadata, 4-way interleaved tANS decoders should be initialized using the simple spread_state_tokens algorithm from this repo.

Page

If there are n numbers in a page, it will consist of ceil(n / 256) batches. All but the final batch will contain 256 numbers, and the final batch will contain the rest (<= 256 numbers).

Each page consists of

  • per latent variable,
    • if delta encoding is applicable, for i in 0..state_n,
      • [dtype_size bits] the ith delta state
    • for i in 0..4,
      • [ans_size_log bits] the ith interleaved tANS state index
  • [0-7 bits] 0s until byte-aligned
  • per batch of k numbers,
    • per latent variable,
      • for i in 0..k,
      • for i in 0..k,
        • [bin[i].offset_bits bits] offset for ith latent

Standalone Format

The standalone format is a minimal implementation of the wrapped format. It consists of

  • [32 bits] magic header (ASCII for "pco!")
  • [8 bits] standalone version
  • [8 bits] either a uniform number type which all following chunks must share, or 0.
  • [6 bits] 1 less than n_hint_log2
  • [n_hint_log2 bits] n_hint, the total count of numbers in the file, if known; 0 otherwise
  • [0-7 bits] 0s until byte-aligned
  • a wrapped header
  • per chunk,
    • [8 bits] the number type
    • [24 bits] 1 less than chunk_n, the count of numbers in the chunk
    • a wrapped chunk metadata
    • a wrapped page of chunk_n numbers
  • [8 bits] a magic termination byte (0).

So far, these standalone versions exist:

format versionfirst Rust versionformat modifications
00.0.0
10.1.0
20.1.1explicit standalone version (previously was implicit and equaled wrapped major version), added n_hint
30.4.5uniform number type

As well as these number type 1-byte representations:

number typebyte
f169
f325
f646
i811
i168
i323
i644
u810
u167
u321
u642

Processing Formulas

In order of decompression steps in a batch:

Bin Indices and Offsets -> Latents

To produce latents, we simply do l[i] = bin[i].lower + offset[i].

Delta Encodings

Depending on delta_encoding, the mode latents are further decoded. Note that the delta latent variable, if it exists, is never delta encoded itself.

None

No additional processing is applied.

Consecutive

Latents are decoded by taking a cumulative sum repeatedly. The delta state is interpreted as delta moments, which are used to initialize each cumulative sum, and get modified for the next batch.

For instance, with 2nd order delta encoding, the delta moments [1, 2] and the deltas [0, 10, 0] would decode to the latents [1, 3, 5, 17, 29].

Lookback

Letting lookback be the delta latent variable. Mode latents are decoded via l[i] += l[i - lookback[i]].

The decompressor should error if any lookback exceeds the window.

Conv1

Supposing the latents are k-bit, conv1 arithmetic is mainly done in 2k-bit signed values to avoid overflow. Latents are decoded in order via l[i] += ((bias + sum[weight[j] * l[i - order + j]]) >> quantization) as L. The bit shift here is arithmetic, not logical.

Modes

Based on the mode, latents are joined into the finalized numbers. Let l0 and l1 be the primary and secondary latents respectively.

modedecoding formula
Classicfrom_latent_ordered(l0)
Dictfrom_latent_ordered(dict[l0])
IntMultfrom_latent_ordered(l0 * mult + l1)
FloatMultint_float_from_latent(l0) * mult + (l1 + MID) ULPs
FloatQuantfrom_latent_ordered((l0 << k) + (l0 << k >= MID ? l1 : 2^k - 1 - l1)

Here ULP refers to unit in the last place, MID is the middle value for the latent type (e.g. 2312^{31} for u32), and dict is a dictionary of unique values, stored in as the Dict mode metadata payload. Each number type has an order-preserving bijection to an unsigned latent type known as from_latent_ordered and to_latent_ordered. For instance, floats have their first bit toggled, and the rest of their bits toggled if the float was originally negative:

fn from_unsigned(unsigned: u32) -> f32 {
  if unsigned & (1 << 31) > 0 {
    // positive float
    f32::from_bits(unsigned ^ (1 << 31))
  } else {
    // negative float
    f32::from_bits(!unsigned)
  }
}

Signed integers have an order-preserving wrapping addition and wrapping conversion like so:

fn from_unsigned(unsigned: u32) -> i32 {
  i32::MIN.wrapping_add(unsigned as i32)
}