This is a database of all mime types. It consists of a single, public JSON file and does not include any logic, allowing it to remain as un-opinionated as possible with an API. It aggregates data from the following sources:

• http://www.iana.org/assignments/media-types/media-types.xhtml
• http://svn.apache.org/repos/asf/httpd/httpd/trunk/docs/conf/mime.types
• http://hg.nginx.org/nginx/raw-file/default/conf/mime.types

npm install mime-db

If you're crazy enough to use this in the browser, you can just grab the JSON file using RawGit. It is recommended to replace master with a release tag as the JSON format may change in the future.

https://cdn.rawgit.com/jshttp/mime-db/master/db.json

var db = require('mime-db');

// grab data on .js files
var data = db['application/javascript'];

The JSON file is a map lookup for lowercased mime types. Each mime type has the following properties:

• .source - where the mime type is defined. If not set, it's probably a custom media type.
  • apache - Apache common media types
  • iana - IANA-defined media types
  • nginx - nginx media types
• .extensions[] - known extensions associated with this mime type.
• .compressible - whether a file of this type can be gzipped.
• .charset - the default charset associated with this type, if any.

If unknown, every property could be undefined.

The JSON file extensions-db.json is a reverse mapping from extension to mime type. The database contains ambiguities for this mapping direction and the mapping may not be stable. However, two rules try to limit ambiguities:

• Any available mime type is preferred over the mime type application/octet-stream. E.g. application/x-iso9660-image is preferred for the extension iso over application/x-iso9660-image
• Mime types without an x- are preferred over mime types with x-. E.g. the extension m4a maps to the mime type audio/mp4 and not to the mime type audio/x-m4a

To edit the database, only make PRs against src/custom.json or src/custom-suffix.json.

To update the build, run npm run build.

The best way to get new media types included in this library is to register them with the IANA. The community registration procedure is outlined in RFC 6838 section 5. Types registered with the IANA are automatically pulled into this library.