External Term Format ELI5

To communicate with the outer world and other Erlang nodes, also to save things on disk, Erlang uses special encoding — External Term Format.

The main requirements to the format:

• Easy for human and machine to see an encoded term and what it is. An external term always starts with byte 131 (0x83).

• Compact with optional compression. A tag 131 (0x83), 80 (0x50), U32/big length marks a compressed term.

• Cross-platform, all integers are encoded as big endian (from most significant bytes to least), floats use big endian IEEE encoding, text uses UTF-8 or ISO-8859-1 (ASCII superset).

To encode a term see erlang:term_to_binary and the opposite operation is erlang:binary_to_term.

Decoding a crafted binary allows us to construct terms which are impossible to make with standard library functions, such as non-existing ports and pids.

Usually atoms are encoded as strings. But in the distributed mode (over the network) to further reduce the protocol size a distribution header can be added. It contains a table of atom names which are included in the encoded message. Atoms in the message are placed in this table and their occurences are replaced with indexes.

It is impossible to encode internal VM value types which never appear in Erlang programs, such as THE_NON_VALUE, references to registers, CP (continuation pointer) etc.

See also

External Term Format documentation.