From Wikipedia, the free encyclopedia

LEB128 or Little Endian Base 128 is a variable-length code compression used to store arbitrarily large integers in a small number of bytes. LEB128 is used in the DWARF debug file format[1][2] and the WebAssembly binary encoding for all integer literals.[3]

Encoding format[edit]

LEB128 format is very similar to variable-length quantity (VLQ) format; the primary difference is that LEB128 is little-endian whereas variable-length quantities are big-endian. Both allow small numbers to be stored in a single byte, while also allowing encoding of arbitrarily long numbers. There are two versions of LEB128: unsigned LEB128 and signed LEB128. The decoder must know whether the encoded value is unsigned LEB128 or signed LEB128.

Unsigned LEB128[edit]

To encode an unsigned number using unsigned LEB128 (ULEB128) first represent the number in binary. Then zero extend the number up to a multiple of 7 bits (such that if the number is non-zero, the most significant 7 bits are not all 0). Break the number up into groups of 7 bits. Output one encoded byte for each 7 bit group, from least significant to most significant group. Each byte will have the group in its 7 least significant bits. Set the most significant bit on each byte except the last byte. The number zero is encoded as a single byte 0x00.

As an example, here is how the unsigned number 624485 gets encoded:

MSB ------------------ LSB
      10011000011101100101  In raw binary
     010011000011101100101  Padded to a multiple of 7 bits
 0100110  0001110  1100101  Split into 7-bit groups
00100110 10001110 11100101  Add high 1 bits on all but last (most significant) group to form bytes
    0x26     0x8E     0xE5  In hexadecimal

→ 0xE5 0x8E 0x26            Output stream (LSB to MSB)

Unsigned LEB128 and VLQ (variable-length quantity) both compress any given integer into not only the same number of bits, but exactly the same bits—the two formats differ only in exactly how those bits are arranged.

Signed LEB128[edit]

A signed number is represented similarly: Starting with an -bit two's complement representation, where is a multiple of 7, the number is broken into groups as for the unsigned encoding.

For example, the signed number -123456 is encoded as 0xC0 0xBB 0x78:

MSB ------------------ LSB
         11110001001000000  Binary encoding of 123456
     000011110001001000000  As a 21-bit number
     111100001110110111111  Negating all bits (ones' complement)
     111100001110111000000  Adding one (two's complement)
 1111000  0111011  1000000  Split into 7-bit groups
01111000 10111011 11000000  Add high 1 bits on all but last (most significant) group to form bytes
    0x78     0xBB     0xC0  In hexadecimal

→ 0xC0 0xBB 0x78            Output stream (LSB to MSB)

Fast decoding[edit]

A straightforward scalar implementation of LEB128 decoding is fairly slow, even more so on modern hardware where branch misprediction is relatively expensive. A series of papers presents SIMD techniques for accelerating decoding (it is called VByte in these papers, but is another name for the same encoding). The "Vectorized VByte Decoding" paper[4] presented "Masked VByte", which demonstrated speeds of 650–2700 million integers per second on commodity Haswell hardware, depending on encoding density. A followup paper presented a variant encoding, "Stream VByte: Faster Byte Oriented Integer Compression",[5] which increased speeds to over 4 billion integers per second. This stream encoding separates the control stream from the encoded data, so is not binary compatible with LEB128.

C-like pseudocode[edit]

Encode unsigned integer[edit]

do {
  byte = low-order 7 bits of value;
  value >>= 7;
  if (value != 0) /* more bytes to come */
    set high-order bit of byte;
  emit byte;
} while (value != 0);

Encode signed integer[edit]

more = 1;
negative = (value < 0);

/* the size in bits of the variable value, e.g., 64 if value's type is int64_t */
size = no. of bits in signed integer;

while (more) {
  byte = low-order 7 bits of value;
  value >>= 7;
  /* the following is only necessary if the implementation of >>= uses a
     logical shift rather than an arithmetic shift for a signed left operand */
  if (negative)
    value |= (~0 << (size - 7)); /* sign extend */

  /* sign bit of byte is second high-order bit (0x40) */
  if ((value == 0 && sign bit of byte is clear) || (value == -1 && sign bit of byte is set))
    more = 0;
    set high-order bit of byte;
  emit byte;

Decode unsigned integer[edit]

result = 0;
shift = 0;
while (true) {
  byte = next byte in input;
  result |= (low-order 7 bits of byte) << shift;
  if (high-order bit of byte == 0)
  shift += 7;

Decode signed integer[edit]

result = 0;
shift = 0;

/* the size in bits of the result variable, e.g., 64 if result's type is int64_t */
size = number of bits in signed integer;

do {
  byte = next byte in input;
  result |= (low-order 7 bits of byte << shift);
  shift += 7;
} while (high-order bit of byte != 0);

/* sign bit of byte is second high-order bit (0x40) */
if ((shift <size) && (sign bit of byte is set))
  /* sign extend */
  result |= (~0 << shift);

JavaScript code[edit]

Encode signed 32-bit integer[edit]

const encodeSignedLeb128FromInt32 = (value) => {
  value |= 0;
  const result = [];
  while (true) {
    const byte_ = value & 0x7f;
    value >>= 7;
    if (
      (value === 0 && (byte_ & 0x40) === 0) ||
      (value === -1 && (byte_ & 0x40) !== 0)
    ) {
      return result;
    result.push(byte_ | 0x80);

Decode signed 32-bit integer[edit]

const decodeSignedLeb128 = (input) => {
  let result = 0;
  let shift = 0;
  while (true) {
    const byte = input.shift();
    result |= (byte & 0x7f) << shift;
    shift += 7;
    if ((0x80 & byte) === 0) {
      if (shift < 32 && (byte & 0x40) !== 0) {
        return result | (~0 << shift);
      return result;


  • The Android project uses LEB128 in its Dalvik Executable Format (.dex) file format.[6]
  • Compressing tables in Hewlett-Packard IA-64 exception handling.[7]
  • The DWARF file format uses both unsigned and signed LEB128 encoding for various fields.[2]
  • LLVM, in its Coverage Mapping Format[8] LLVM's implementation of LEB128 encoding and decoding is useful alongside the pseudocode above.[9]
  • The Microsoft .NET Framework supports a "7-bit encoded int" format in the BinaryReader and BinaryWriter classes.[10] When writing a string to a BinaryWriter, the string length is encoded with this method.
  • Minecraft uses LEB128 in its protocol for measuring lengths of data within packets.[11]
  • The mpatrol debugging tool uses LEB128 in its tracing file format.[12]
  • osu! uses LEB128 in its osu! replay (.osr) format.[13]
  • W3C Efficient XML Interchange (EXI) represents unsigned integers using LEB128, in exactly the same way as described here.[14]
  • WebAssembly, in its portable binary encoding of the modules[3]
  • In the xz file format[15]

Related encodings[edit]

  • Dlugosz' Variable-Length Integer Encoding (original) uses multiples of 7 bits for the first three size breaks, but after that the increments vary. It also puts all the prefix bits at the beginning of the word, instead of at the beginning of each byte.
  • Human interface device report descriptor bytes use a byte-count bitfield of 2 bits to encode the size of the following integer of zero, one, two, or four bytes, always little endian. Signedness, i.e. whether to expand the shortened integer with sign or not, depends on the descriptor type.
  • The LLVM bitcode file format uses a similar technique[16] except that the value is broken into groups of bits of context-dependent size, with the highest bit indicating a continuation, instead of a fixed 7 bits.
  • Protocol Buffers (Protobuf) uses the same encoding for unsigned integers, but encode signed integers by prepending the sign as the least significant bit of the first byte.
  • ASN.1 BER, DER Encode values of each ASN.1 type as a string of eight-bit octets


  1. ^ UNIX International (July 1993), "7.8", DWARF Debugging Information Format Specification Version 2.0, Draft (PDF), retrieved 2009-07-19
  2. ^ a b Free Standards Group (December 2005). "DWARF Debugging Information Format Specification Version 3.0" (PDF). p. 70. Retrieved 2009-07-19.
  3. ^ a b WebAssembly Community Group (2020-11-12). "Values — Binary Format — WebAssembly 1.1". Retrieved 2020-12-31.
  4. ^ Plaisance, Jeff; Kurz, Nathan; Lemire, Daniel (2015). "Vectorized VByte Decoding". arXiv:1503.07387. {{cite journal}}: Cite journal requires |journal= (help)
  5. ^ Lemire, Daniel; Kurz, Nathan; Rupp, Christoph (February 1028). "Stream VByte: Faster Byte-Oriented Integer Compression". Information Processing Letters. 130. First International Symposium on Web Algorithms (published June 2015): 1–6. arXiv:1709.08990. doi:10.1016/j.ipl.2017.09.011. S2CID 8265597.
  6. ^ "Dalvik Executable Format". Retrieved 2021-05-18.
  7. ^ Christophe de Dinechin (October 2000). "C++ Exception Handling for IA-64". Retrieved 2009-07-19.
  8. ^ LLVM Project (2016). "LLVM Code Coverage Mapping Format". Retrieved 2016-10-20.
  9. ^ LLVM Project (2019). "LLVM LEB128 encoding and decoding". Retrieved 2019-11-02.
  10. ^ System.IO.BinaryWriter.Write7BitEncodedInt(int) method and System.IO.BinaryReader.Read7BitEncodedInt() method.
  11. ^ "Minecraft Modern Varint & Varlong". wiki.vg. 2020. Retrieved 2020-11-29.
  12. ^ "MPatrol documentation". December 2008. Retrieved 2009-07-19.
  13. ^ "Osr (file format) - osu!wiki". osu.ppy.sh. Retrieved 2017-03-18.
  14. ^ "Efficient XML Interchange (EXI) Format 1.0". www.w3.org (Second ed.). World Wide Web Consortium. 2014-02-11. Retrieved 2020-12-31.
  15. ^ "The .xz File Format". tukaani.org. 2009. Retrieved 2017-10-30.
  16. ^ "LLVM Bitcode File Format — LLVM 13 documentation".

See also[edit]