

This tag may contain free-form metadata key/value pairs. "ISFT", "encoder" - note that this is automatically filled in by libavformatįFmpeg's FLV muxer generates an onMetaData tag when creating a FLV file.Further, libavformat encodes its version using the key "WM/EncodingSettings".įFmpeg’s AVI muxer honors the following metadata keys, writing them into FourCC chunks in the file header: FFmpeg does not allow this key to be overridden from the command line.įFmpeg’s ASF muxer honors the following metadata keys:īeyond these keys, the ASF muxer accepts free-form key/value metadata keys to be encoded into the header. Information dialog when selecting "Show Description" in context menuįurther, the MOV muxer encodes libavformat version string into the '\251too' field.

For the interested but uninitiated, the notation, e.g., '\251nam' indicates a 4-byte code consisting of the byte A9 in hexadecimal (or 251 in octal) followed by the ASCII characters 'n', 'a', and 'm'. The low-level identifier column lists the atom name that the format uses to encode the data on disc, which is not interesting to most readers. The following table shows the metadata keys that FFmpeg honors when muxing a QuickTime file. This page documents which keys FFmpeg will encode into which formats. Many formats only support a handful of metadata keys. Whether the metadata key/value pairs are actually encoded into the output file is dependent upon the file format being muxed. The option is -metadata and is used as such:įfmpeg -i inputfile -metadata title="Movie Title" -metadata year="2010" outputfile FFmpeg has a free-form command line option that allows the user to specify key/value pairs for encoding metadata.
