The purpose of this library is to be very fast and small. It’s suitable for server-side or client-side. Really any platform that supports ArrayBuffer and its ilk (Uint8Array, etc.).

I wrote it because the other libraries were large and very robust; I just needed something that could extract the metadata out without requiring 30KB of JavaScript. audio-metadata.min.js comes in at 6.1K/2.1K minified/gzipped.

To accomplish the small size and speed, it sacrifices several things.

  1. It’s very naive. For example, the OGG format stipulates that the comment header must come second, after the identification header. This library assumes that’s always true and ignores the header type byte.
  2. Text encoding is for losers. ID3v2 in particular has a lot of flexibility in terms of the encoding of text for ID3 frames. This library will handle UTF8 properly, but everything else is just spit out as ASCII.
  3. It assumes that ID3v2 tags are always the very first thing in the file (as they should be). The spec is mum on whether that’s ”required”, but this library assumes it is.
  4. ID3v1.1 (extended tags with “TAG+”) are not supported; Wikipedia suggests they aren’t really well-supported in media players anyway.

As such, the code is a bit abstruse, in that you’ll see some magic numbers, like offset += 94 where it’s ignoring a bunch of header data to get to the good stuff.

Don’t judge me based on this code. It works and it’s tested; it’s just hard to read.

Of course, since this isn’t an actual parser, invalid files will also work.

This means, for example, you could only read the first couple hundred bytes of an MP3 file and still extract the metadata from it, rather than requiring actual valid MP3 data.


The library operates solely on ArrayBuffers, or Buffers for Node’s convenience. So you’ll need to preload your audio data before using this library.

The library defines three methods:

// extract comments from OGG container

// extract ID3v2 tags

// extract ID3v1 tags

The result is an object with the metadata. It attempts to normalize common keys:

  • title: (TIT1 and TIT2 in id3v2)
  • artist: (TSE1 in id3v2)
  • composer: (TCOM in id3v2)
  • album: (TALB in id3v2)
  • track: (TRCK in id3v2, commonly TRACKNUMBER in vorbis comments)
  • year: (TDRC (date recorded) is used in id3v2)
  • encoder: (TSSE in id3v2)
  • genre: (TCON in id3v2)

Everything else will be keyed by its original name. For id3v2, anything that is not a text identifier (i.e. a frame that starts with a “T”) is ignored. This includes comments (COMM).


Install it using NPM: npm install audio-metadata or npm install -g audio-metadata if you want to use it from the shell.

var audioMetaData = require('audio-metadata'),
	fs = require('fs');

var oggData = fs.readFileSync('/path/to/my.ogg');
var metadata = audioMetaData.ogg(oggData);
  "title": "Contra Base Snippet",
  "artist": "Konami",
  "album": "Bill and Lance's Excellent Adventure",
  "year": "1988",
  "tracknumber": "1",
  "track": "1",
  "encoder": "Lavf53.21.1"

For more information click here.

Published by Tamil S

Tamil has a great interest in the fields of Cyber Security, OSINT, and CTF projects. Currently, he is deeply involved in researching and publishing various security tools with Kali Linux Tutorials, which is quite fascinating.

Leave a comment

Your email address will not be published. Required fields are marked *