file-type vs mime-types
文件类型识别与 MIME 映射技术对比
file-typemime-types类似的npm包:

文件类型识别与 MIME 映射技术对比

file-type 和 mime-types 都用于处理文件类型信息,但工作原理完全不同。file-type 通过读取文件内容的“魔法数字”(magic numbers)来识别文件的真实格式,不依赖文件扩展名,适合安全验证场景。mime-types 则是一个查找表,根据文件扩展名映射到标准的 MIME 类型字符串,主要用于设置 HTTP 响应头或静态资源服务。两者常配合使用,但解决的是不同层面的问题。

npm下载趋势

3 年

GitHub Stars 排名

统计详情

npm包名称
下载量
Stars
大小
Issues
发布时间
License
file-type04,339142 kB08 天前MIT
mime-types01,47922.9 kB261 年前MIT

文件类型识别与 MIME 映射技术对比

file-type 和 mime-types 都是 Node.js 生态中处理文件类型的常用工具,但它们的底层逻辑和适用场景截然不同。file-type 关注文件“实际上是什么”,而 mime-types 关注文件“名义上应该是什么”。理解这一区别对于构建安全的文件上传服务和正确的 HTTP 响应至关重要。

🕵️ 核心机制:内容检查 vs 扩展名查找

file-type 读取文件头部的二进制数据(魔法数字)。

  • 它不关心文件名叫什么,只关心文件内容结构。
  • 即使把 .jpg 改名为 .txt,它仍能识别出是图片。
// file-type: 基于内容检测
import { fileTypeFromFile } from 'file-type';

const type = await fileTypeFromFile('photo.jpg');
console.log(type); 
// 输出: { ext: 'jpg', mime: 'image/jpeg' }

mime-types 查询内置的扩展名映射数据库。

  • 它只看文件名的后缀部分。
  • 如果文件扩展名被篡改,它会返回错误的类型。
// mime-types: 基于扩展名查找
import mime from 'mime-types';

const type = mime.lookup('photo.jpg');
console.log(type); 
// 输出: 'image/jpeg'

🔒 安全信任:真实验证 vs 名称推测

file-type 提供更高的安全信任度。

  • 适合处理用户上传的文件,防止恶意脚本伪装成图片上传。
  • 需要读取文件内容,因此有轻微的 IO 开销。
// file-type: 验证上传文件安全性
import { fileTypeFromBuffer } from 'file-type';

async function validateUpload(buffer) {
  const type = await fileTypeFromBuffer(buffer);
  if (type?.mime !== 'image/png') {
    throw new Error('Invalid file type');
  }
}

mime-types 仅作为类型提示,不可用于安全验证。

  • 适合内部可信环境,或仅用于设置浏览器如何解析文件。
  • 无法防御扩展名欺骗攻击。
// mime-types: 设置响应头(不可信用于安全验证)
import mime from 'mime-types';
import fs from 'fs';

function serveFile(res, filePath) {
  const contentType = mime.lookup(filePath) || 'application/octet-stream';
  res.setHeader('Content-Type', contentType);
  fs.createReadStream(filePath).pipe(res);
}

⚡ 性能开销:磁盘 IO vs 内存查找

file-type 需要读取文件片段。

  • 必须访问磁盘或网络流来获取文件头。
  • 在高并发上传场景下,IO 等待可能成为瓶颈。
// file-type: 涉及异步 IO 操作
const type = await fileTypeFromFile('/path/to/large_video.mp4');
// 需要等待文件系统读取头部数据

mime-types 纯内存同步操作。

  • 只是字符串查找,速度极快。
  • 适合在请求处理链路中频繁调用,无性能压力。
// mime-types: 同步内存查找
const ext = mime.extension('text/html');
// 立即返回 'html',无 IO 等待

🌐 环境支持:全平台 vs Node.js 为主

file-type 支持 Node.js 和现代浏览器。

  • 在浏览器中需要配合 Blob 或 ArrayBuffer 使用。
  • 适合全栈应用,包括前端直接处理文件预览。
// file-type: 浏览器环境示例
import { fileTypeFromBuffer } from 'file-type';

async function checkFileInput(input) {
  const arrayBuffer = await input.files[0].arrayBuffer();
  const type = await fileTypeFromBuffer(arrayBuffer);
  return type;
}

mime-types 主要为 Node.js 设计。

  • 依赖 Node.js 的 path 模块逻辑。
  • 在浏览器中通常不需要,因为浏览器自有 MIME 处理机制。
// mime-types: Node.js 环境示例
import mime from 'mime-types';

// 通常在服务器端使用
if (process.platform === 'win32') {
  // 处理路径分隔符等 Node 特定逻辑
}

🤝 相似之处:共同的基础设施

虽然用途不同,这两个库在文件处理流程中经常一起出现,且有一些共同点。

1. 📦 都处理 MIME 类型字符串

  • 最终输出都包含标准的 MIME 类型(如 image/png)。
  • 都遵循 IANA 注册的媒体类型标准。
// file-type 输出
// { ext: 'png', mime: 'image/png' }

// mime-types 输出
// 'image/png'

2. 🛠️ 都用于 Web 文件服务

  • 都是构建文件上传、下载、静态服务的基础工具。
  • 常出现在 Express、Koa 等后端中间件中。
// 组合使用示例
import mime from 'mime-types';
import { fileTypeFromFile } from 'file-type';

// 先用 file-type 验证安全,再用 mime-types 设置头(或直接用车 type 的结果)

3. ✅ 都有广泛的格式支持

  • 支持常见的图片、视频、音频、文档格式。
  • 社区维护更新,跟进新格式标准。
// 两者都能识别常见格式
// image/jpeg, application/pdf, video/mp4 等

📊 总结:关键差异对比

特性file-typemime-types
识别依据🕵️ 文件内容(魔法数字)🏷️ 文件扩展名
安全性🔒 高(防欺骗)⚠️ 低(仅推测)
性能🐢 异步 IO,稍慢🚀 同步内存,极快
主要用途上传验证、内容审计HTTP 头设置、静态服务
环境🌐 Node.js + 浏览器🖥️ 主要 Node.js

💡 最终建议

file-type 是你的安全网关 🛡️ — 当文件来自不可信的用户上传时,必须用它来确认文件真实身份。不要相信用户提供的扩展名。

mime-types 是你的通信协议员 📮 — 当文件已经确认为安全,需要告诉浏览器如何显示或下载时,用它来设置正确的 Content-Type。

最佳实践:在生产环境中,通常先使用 file-type 验证上传内容的真实性,验证通过后,可以使用 file-type 返回的 MIME 类型,或者继续使用 mime-types 根据标准扩展名设置响应头。两者互补,而非互斥。

如何选择: file-type vs mime-types

  • file-type:

    选择 file-type 当你需要验证用户上传文件的真实格式,防止通过修改扩展名进行欺骗。它适合处理未知来源的文件、无扩展名文件,或需要确保文件内容与声明类型一致的安全敏感场景。

  • mime-types:

    选择 mime-types 当你需要根据文件扩展名设置 HTTP 响应头(Content-Type),或在静态文件服务器中映射资源类型。它适合处理已知扩展名的文件,且对性能要求较高、不需要深度内容检查的场景。

file-type的README

file-type logo

Detect the file type of a file, stream, or data

The file type is detected by checking the magic number of the buffer.

This package is for detecting binary-based file formats, not text-based formats like .txt, .csv, .svg, etc.

We accept contributions for commonly used modern file formats, not historical or obscure ones. Open an issue first for discussion.

Install

npm install file-type

This package is an ESM package. Your project needs to be ESM too. Read more. For TypeScript + CommonJS, see load-esm. If you use it with Webpack, you need the latest Webpack version and ensure you configure it correctly for ESM.

[!IMPORTANT] File type detection is based on binary signatures (magic numbers) and is a best-effort hint. It does not guarantee the file is actually of that type or that the file is valid/not malformed.

Robustness against malformed input is best-effort. When processing untrusted files on a server, enforce a reasonable file size limit and use a worker thread with a timeout (e.g., make-asynchronous). These are not considered security issues in this package.

Usage

Node.js

Determine file type from a file:

import {fileTypeFromFile} from 'file-type';

console.log(await fileTypeFromFile('Unicorn.png'));
//=> {ext: 'png', mime: 'image/png'}

Determine file type from a Uint8Array/ArrayBuffer, which may be a portion of the beginning of a file:

import {fileTypeFromBuffer} from 'file-type';
import {readChunk} from 'read-chunk';

const buffer = await readChunk('Unicorn.png', {length: 4100});

console.log(await fileTypeFromBuffer(buffer));
//=> {ext: 'png', mime: 'image/png'}

Determine file type from a stream:

import {fileTypeFromStream} from 'file-type';

const url = 'https://upload.wikimedia.org/wikipedia/en/a/a9/Example.jpg';

const response = await fetch(url);
const fileType = await fileTypeFromStream(response.body);

console.log(fileType);
//=> {ext: 'jpg', mime: 'image/jpeg'}

API

fileTypeFromBuffer(buffer, options)

Detect the file type of a Uint8Array or ArrayBuffer.

The file type is detected by checking the magic number of the buffer.

If file access is available, it is recommended to use fileTypeFromFile() instead.

Returns a Promise for an object with the detected file type:

Or undefined when there is no match.

buffer

Type: Uint8Array | ArrayBuffer

A buffer representing file data. It works best if the buffer contains the entire file. It may work with a smaller portion as well.

fileTypeFromFile(filePath, options)

Detect the file type of a file path.

Only available in environments where node:fs is available, such as Node.js. To read from a File, see fileTypeFromBlob().

The file type is detected by checking the magic number of the file.

Returns a Promise for an object with the detected file type:

Or undefined when there is no match.

filePath

Type: string

The file path to parse.

fileTypeFromStream(stream, options)

Detect the file type of a web ReadableStream.

The file type is detected by checking the magic number of the buffer.

Returns a Promise for an object with the detected file type:

Or undefined when there is no match.

stream

Type: Web ReadableStream

A readable stream representing file data.

[!TIP] If you have a Node.js stream.Readable, convert it with Readable.toWeb().

fileTypeFromBlob(blob, options)

Detect the file type of a Blob.

[!TIP] A File object is a Blob and can be passed in here.

It will stream the underlying Blob.

The file type is detected by checking the magic number of the blob.

Returns a Promise for an object with the detected file type:

Or undefined when there is no match.

import {fileTypeFromBlob} from 'file-type';

const blob = new Blob(['<?xml version="1.0" encoding="ISO-8859-1" ?>'], {
	type: 'text/plain',
	endings: 'native'
});

console.log(await fileTypeFromBlob(blob));
//=> {ext: 'xml', mime: 'application/xml'}

blob

Type: Blob

fileTypeFromTokenizer(tokenizer, options)

Detect the file type from an ITokenizer source.

This method is used internally, but can also be used for a special "tokenizer" reader.

A tokenizer propagates the internal read functions, allowing alternative transport mechanisms, to access files, to be implemented and used.

Returns a Promise for an object with the detected file type:

Or undefined when there is no match.

An example is @tokenizer/http, which requests data using HTTP-range-requests. A difference with a conventional stream and the tokenizer, is that it can ignore (seek, fast-forward) in the stream. For example, you may only need and read the first 6 bytes, and the last 128 bytes, which may be an advantage in case reading the entire file would take longer.

import {makeTokenizer} from '@tokenizer/http';
import {fileTypeFromTokenizer} from 'file-type';

const audioTrackUrl = 'https://test-audio.netlify.com/Various%20Artists%20-%202009%20-%20netBloc%20Vol%2024_%20tiuqottigeloot%20%5BMP3-V2%5D/01%20-%20Diablo%20Swing%20Orchestra%20-%20Heroines.mp3';

const httpTokenizer = await makeTokenizer(audioTrackUrl);
const fileType = await fileTypeFromTokenizer(httpTokenizer);

console.log(fileType);
//=> {ext: 'mp3', mime: 'audio/mpeg'}

Or use @tokenizer/s3 to determine the file type of a file stored on Amazon S3:

import {S3Client} from '@aws-sdk/client-s3';
import {makeChunkedTokenizerFromS3} from '@tokenizer/s3';
import {fileTypeFromTokenizer} from 'file-type';

// Initialize S3 client
const s3 = new S3Client();

// Initialize the S3 tokenizer.
const s3Tokenizer = await makeChunkedTokenizerFromS3(s3, {
	Bucket: 'affectlab',
	Key: '1min_35sec.mp4'
});

// Figure out what kind of file it is.
const fileType = await fileTypeFromTokenizer(s3Tokenizer);
console.log(fileType);

Note that only the minimum amount of data required to determine the file type is read (okay, just a bit extra to prevent too many fragmented reads).

tokenizer

Type: ITokenizer

A file source implementing the tokenizer interface.

fileTypeStream(webStream, options?)

Returns a Promise which resolves to the original readable stream argument, but with an added fileType property, which is an object like the one returned from fileTypeFromFile().

This method can be handy to put in a stream pipeline, but it comes with a price. Internally stream() builds up a buffer of sampleSize bytes, used as a sample, to determine the file type. The sample size impacts the file detection resolution. A smaller sample size will result in lower probability of the best file type detection.

webStream

Type: Web ReadableStream

The input stream.

options

Type: object

Supports the following options in addition to the general options:

sampleSize

Type: number
Default: 4100

The sample size in bytes.

Example

import {fileTypeStream} from 'file-type';

const url = 'https://upload.wikimedia.org/wikipedia/en/a/a9/Example.jpg';

const response = await fetch(url);
const stream = await fileTypeStream(response.body, {sampleSize: 1024});

if (stream.fileType?.mime === 'image/jpeg') {
	// stream can be used to stream the JPEG image (from the very beginning of the stream)
}

supportedExtensions

Returns a Set<string> of file extensions that can be detected.

supportedMimeTypes

Returns a Set<string> of MIME types that can be detected.

Options

customDetectors

Array of custom file type detectors to run before default detectors.

For example:

import {fileTypeFromFile} from 'file-type';
import {detectXml} from '@file-type/xml';

const fileType = await fileTypeFromFile('sample.kml', {customDetectors: [detectXml]});
console.log(fileType);

maxBufferSize

Type: number
Default: Infinity

Maximum size in bytes of an individual buffer allocated to read file content, or a stream lookahead request. Must be a positive safe integer or Infinity.

File content can determine how much data a detector requests, for example through a field specifying the length of a metadata entry. This opt-in limit bounds the memory allocations needed to fulfill those reads, including reads made by custom detectors. Setting a finite cap can help prevent excessive read-buffer allocations driven by untrusted file content (CWE-789: Memory Allocation with Excessive Size Value). Built-in reads already have format-specific bounds; choose a finite cap to suit your application. An oversized request rejects detection with strtok3.BufferSizeError, which exposes requestedSize and maxBufferSize. During gzip content probing, this error is suppressed and detection falls back to gz; the cap still prevents the oversized allocation.

const fileType = await fileTypeFromFile('sample.bin', {maxBufferSize: 64 * 1024 * 1024});

This is not a total memory limit. It does not cover buffers allocated directly by detectors or fileTypeStream() sampling. When using fileTypeFromTokenizer(), configure maxBufferSize on the input reader itself; this option does not override that reader’s limits. The built-in format-specific limits, including ZIP text-entry limits, apply independently of this option.

For FileTypeParser.toDetectionStream(), configure detection options such as maxBufferSize through the parser constructor. The method only accepts stream options such as sampleSize.

mpegOffsetTolerance

Default: 0

Specifies the byte tolerance for locating the first MPEG audio frame (e.g. .mp1, .mp2, .mp3, .aac).

Allows detection to handle slight sync offsets between the expected and actual frame start. Common in malformed or incorrectly muxed files, which, while technically invalid, do occur in the wild.

A tolerance of 10 bytes covers most cases.

Custom detectors

Custom file type detectors are plugins designed to extend the default detection capabilities. They allow support for uncommon file types, non-binary formats, or customized detection behavior.

Detectors can be added via the constructor options or by directly modifying FileTypeParser#detectors. Detectors provided through the constructor are executed before the default ones.

[!NOTE] Not safe for concurrent use. Create a new instance per call if you need concurrency.

Example adding a detector

import {FileTypeParser} from 'file-type';
import {detectXml} from '@file-type/xml';

const parser = new FileTypeParser({customDetectors: [detectXml]});
const fileType = await parser.fromFile('sample.kml');
console.log(fileType);

Available third-party file-type detectors

  • @file-type/av: Improves detection of audio and video file formats, with accurate differentiation between the two
  • @file-type/cfbf: Detects Compound File Binary Format (CFBF) based formats, such as Office 97–2003 documents and .msi.
  • @file-type/pdf: Detects PDF based file types, such as Adobe Illustrator
  • @file-type/xml: Detects common XML file types, such as GLM, KML, MusicXML, RSS, SVG, and XHTML

Detector execution flow

If a detector returns undefined, the following rules apply:

  1. No Tokenizer Interaction: If the detector does not modify the tokenizer's position, the next detector in the sequence is executed.
  2. Tokenizer Interaction: If the detector modifies the tokenizer's position (tokenizer.position is advanced), no further detectors are executed. In this case, the file type remains undefined, as subsequent detectors cannot evaluate the content. This is an exceptional scenario, as it prevents any other detectors from determining the file type.

Writing your own custom detector

Below is an example of a custom detector. This can be passed to the FileTypeParser via the customDetectors option.

import {FileTypeParser} from 'file-type';

const unicornDetector = {
	id: 'unicorn', // May be used to recognize the detector in the detector list
	async detect(tokenizer) {
		const unicornHeader = [85, 78, 73, 67, 79, 82, 78]; // "UNICORN" in ASCII decimal

		const buffer = new Uint8Array(unicornHeader.length);
		await tokenizer.peekBuffer(buffer, {length: unicornHeader.length, mayBeLess: true});
		if (unicornHeader.every((value, index) => value === buffer[index])) {
			return {ext: 'unicorn', mime: 'application/unicorn'};
		}

		return undefined;
	}
}

const buffer = new Uint8Array([85, 78, 73, 67, 79, 82, 78]);
const parser = new FileTypeParser({customDetectors: [unicornDetector]});
const fileType = await parser.fromBuffer(buffer);
console.log(fileType); // {ext: 'unicorn', mime: 'application/unicorn'}
/**
@param tokenizer - The [tokenizer](https://github.com/Borewit/strtok3#tokenizer) used to read file content.
@param fileType - The file type detected by standard or previous custom detectors, or `undefined` if no match is found.
@returns The detected file type, or `undefined` if no match is found.
*/
export type Detector = {
	id: string;
	detect: (tokenizer: ITokenizer, fileType?: FileTypeResult) => Promise<FileTypeResult | undefined>;
};

Abort signal

Some async operations can be aborted by passing an AbortSignal to the FileTypeParser constructor.

import {FileTypeParser} from 'file-type';

const abortController = new AbortController();

const parser = new FileTypeParser({signal: abortController.signal});

const promise = parser.fromStream(blob.stream());

abortController.abort(); // Abort file-type reading from the Blob stream.

Supported file types

MIME media subtypes prefixed with x-ft- are custom and defined by us. They are neither formally registered with IANA nor based on any informal conventions.

  • 3g2 - Multimedia container format defined by the 3GPP2 for 3G CDMA2000 multimedia services
  • 3gp - Multimedia container format defined by the Third Generation Partnership Project (3GPP) for 3G UMTS multimedia services
  • 3mf - 3D Manufacturing Format
  • 7z - 7-Zip archive
  • Z - Unix Compressed File
  • aac - Advanced Audio Coding
  • ac3 - ATSC A/52 Audio File
  • ace - ACE archive
  • aif - Audio Interchange file
  • alias - macOS Alias file
  • amr - Adaptive Multi-Rate audio codec
  • ape - Monkey's Audio
  • apk - Android package format
  • apng - Animated Portable Network Graphics
  • ar - Archive file
  • arj - Archive file
  • arrow - Columnar format for tables of data
  • arw - Sony Alpha Raw image file
  • asar - Archive format primarily used to enclose Electron applications
  • asf - Advanced Systems Format
  • avi - Audio Video Interleave file
  • avif - AV1 Image File Format
  • avro - Object container file developed by Apache Avro
  • blend - Blender project
  • bmp - Bitmap image file
  • bpg - Better Portable Graphics file
  • bz2 - Archive file
  • cab - Cabinet file
  • caf - Apple Core Audio Format
  • cfb - Compound File Binary Format
  • chm - Microsoft Compiled HTML Help
  • class - Java class file
  • cpio - Cpio archive
  • cr2 - Canon Raw image file (v2)
  • cr3 - Canon Raw image file (v3)
  • crx - Google Chrome extension
  • cur - Icon file
  • dat - Windows registry hive file
  • dcm - DICOM Image File
  • deb - Debian package
  • dff - Direct Stream Digital Interchange File Format (DSDIFF)
  • dmg - Apple Disk Image
  • dng - Adobe Digital Negative image file
  • docm - Microsoft Word macro-enabled document
  • docx - Microsoft Word document
  • dotm - Microsoft Word macro-enabled template
  • dotx - Microsoft Word template
  • drc - Google's Draco 3D Data Compression
  • dsf - Sony DSD Stream File (DSF)
  • dwg - Autodesk CAD file
  • elf - Unix Executable and Linkable Format
  • eot - Embedded OpenType font
  • eps - Encapsulated PostScript
  • epub - E-book file
  • exe - Executable file
  • f4a - Audio-only ISO base media file format used by Adobe Flash Player
  • f4b - Audiobook and podcast ISO base media file format used by Adobe Flash Player
  • f4p - ISO base media file format protected by Adobe Access DRM used by Adobe Flash Player
  • f4v - ISO base media file format used by Adobe Flash Player
  • fbx - Filmbox is a proprietary file format used to provide interoperability between digital content creation apps.
  • flac - Free Lossless Audio Codec
  • flif - Free Lossless Image Format
  • flv - Flash video
  • gif - Graphics Interchange Format
  • glb - GL Transmission Format
  • gz - Archive file
  • heic - High Efficiency Image File Format
  • icc - ICC Profile
  • icns - Apple Icon image
  • ico - Windows icon file
  • ics - iCalendar
  • indd - Adobe InDesign document
  • iso - ISO 9660 disc image
  • it - Audio module format: Impulse Tracker
  • j2c - JPEG 2000
  • jar - Java archive
  • jls - Lossless/near-lossless compression standard for continuous-tone images
  • jmp - JMP data file format by SAS Institute
  • jp2 - JPEG 2000
  • jpg - Joint Photographic Experts Group image
  • jpm - JPEG 2000
  • jpx - JPEG 2000
  • jxl - JPEG XL image format
  • jxr - Joint Photographic Experts Group extended range
  • key - Apple Keynote presentation
  • ktx - OpenGL and OpenGL ES textures
  • lnk - Microsoft Windows file shortcut
  • lz - Archive file
  • lz4 - Compressed archive created by one of a variety of LZ4 compression utilities
  • lzh - LZH archive
  • m4a - Audio-only MPEG-4 files
  • m4b - Audiobook and podcast MPEG-4 files, which also contain metadata including chapter markers, images, and hyperlinks
  • m4p - MPEG-4 files with audio streams encrypted by FairPlay Digital Rights Management as were sold through the iTunes Store
  • m4v - Video container format developed by Apple, which is very similar to the MP4 format
  • macho - Mach-O binary format
  • mid - Musical Instrument Digital Interface file
  • mie - Dedicated meta information format which supports storage of binary as well as textual meta information
  • mj2 - Motion JPEG 2000
  • mkv - Matroska video file
  • mobi - Mobipocket
  • mov - QuickTime video file
  • mp1 - MPEG-1 Audio Layer I
  • mp2 - MPEG-1 Audio Layer II
  • mp3 - Audio file
  • mp4 - MPEG-4 Part 14 video file
  • mpc - Musepack (SV7 & SV8)
  • mpg - MPEG-1 file
  • mts - MPEG-2 Transport Stream, both raw and Blu-ray Disc Audio-Video (BDAV) versions
  • mxf - Material Exchange Format
  • nef - Nikon Electronic Format image file
  • nes - Nintendo NES ROM
  • numbers - Apple Numbers spreadsheet
  • odg - OpenDocument for drawing
  • odp - OpenDocument for presentations
  • ods - OpenDocument for spreadsheets
  • odt - OpenDocument for word processing
  • oga - Audio file
  • ogg - Audio file
  • ogm - Audio file
  • ogv - Audio file
  • ogx - Audio file
  • opus - Audio file
  • orf - Olympus Raw image file
  • otf - OpenType font
  • otg - OpenDocument template for drawing
  • otp - OpenDocument template for presentations
  • ots - OpenDocument template for spreadsheets
  • ott - OpenDocument template for word processing
  • pages - Apple Pages document
  • parquet - Apache Parquet
  • pcap - Libpcap File Format
  • pdf - Portable Document Format
  • pgp - Pretty Good Privacy
  • png - Portable Network Graphics
  • potm - Microsoft PowerPoint macro-enabled template
  • potx - Microsoft PowerPoint template
  • ppsm - Office PowerPoint 2007 macro-enabled slide show
  • ppsx - Office PowerPoint 2007 slide show
  • pptm - Microsoft PowerPoint macro-enabled document
  • pptx - Microsoft PowerPoint document
  • ps - PostScript
  • psd - Adobe Photoshop document
  • pst - Personal Storage Table file
  • qcp - Tagged and chunked data
  • raf - Fujifilm RAW image file
  • rar - Archive file
  • reg - Windows registry (entries) file format
  • rm - RealMedia
  • rpm - Red Hat Package Manager file
  • rtf - Rich Text Format
  • rw2 - Panasonic RAW image file
  • s3m - Audio module format: ScreamTracker 3
  • sav - SPSS Statistical Data File
  • shp - Geospatial vector data format
  • skp - SketchUp
  • spx - Audio file
  • sqlite - SQLite file
  • stl - Standard Tessellated Geometry File Format (ASCII only)
  • swf - Adobe Flash Player file
  • tar - Tape archive or tarball
  • tar.gz - Gzipped tape archive (tarball)
  • tif - Tagged Image file
  • ttc - TrueType Collection font
  • ttf - TrueType font
  • vcf - vCard
  • voc - Creative Voice File
  • vsdx - Microsoft Visio File
  • vtt - WebVTT File (for video captions)
  • wasm - WebAssembly intermediate compiled format
  • wav - Waveform Audio file
  • webm - Web video file
  • webp - Web Picture format
  • woff - Web Open Font Format
  • woff2 - Web Open Font Format
  • wv - WavPack
  • xcf - eXperimental Computing Facility
  • xlsm - Microsoft Excel macro-enabled document
  • xlsx - Microsoft Excel document
  • xltm - Microsoft Excel macro-enabled template
  • xltx - Microsoft Excel template
  • xm - Audio module format: FastTracker 2
  • xml - eXtensible Markup Language
  • xpi - XPInstall file
  • xz - Compressed file
  • zip - Archive file
  • zst - Archive file

ISO 9660 requires random-access input or fileTypeStream() with sampleSize >= 32_774; fileTypeFromStream() is unsupported.

When [Content_Types].xml cannot be reached — it may trail the content entries, and only so much of what precedes it is scanned — the type is guessed from the archive's directory names: word/, xl/ and ppt/ are reported as docx, xlsx and pptx. Macro-enabled and template variants are therefore reported as their base type, and a non-OOXML archive containing one of those directories is reported as OOXML.

Pull requests are welcome for additional commonly used file types.

The following file types will not be accepted, but most of them are supported by third-party detectors.

Related

Maintainers