Browser

MIME Types

Supported types

Live Playground

Analyzing your browser...0%

API Docs

Endpoint

GET /api/fingerprint/mime-types

Examples

About

MIME types fingerprinting enumerates browser-supported media types and codecs through multiple APIs including navigator.mimeTypes (deprecated but still exposed), HTMLMediaElement.canPlayType(), MediaSource.isTypeSupported(), and MediaRecorder.isTypeSupported(). Different browsers, browser versions, operating systems, and installed codecs produce vastly different lists of supported media formats. For example, Safari natively supports H.265/HEVC video while Chrome requires special builds, Firefox supports Ogg Theora/Vorbis while Chrome dropped support, and Microsoft Edge includes Windows Media codecs that other browsers lack. The technique tests hundreds of MIME type strings including video codecs (H.264, VP9, AV1, HEVC), audio codecs (AAC, Opus, FLAC, MP3), image formats (WebP, AVIF, JPEG XL), and container formats (MP4, WebM, MKV, OGG). Results include 'probably', 'maybe', or '' (not supported), providing graded confidence levels. Codec parameters like profile levels (avc1.42E01E, avc1.64001F) reveal hardware decoding capabilities and OS codecs. Media Source Extensions (MSE) support varies: some browsers support MSE for certain formats but not others. MediaRecorder API support indicates recording capabilities. Proprietary formats (Windows Media, RealMedia, QuickTime) are OS-specific. DRM support (Encrypted Media Extensions) varies significantly: Widevine on Chrome/Firefox, FairPlay on Safari, PlayReady on Edge. Audio context support for different sample rates and channel configurations adds entropy. The combination of codec support creates a highly distinctive fingerprint that correlates strongly with browser, OS, OS version, and installed media frameworks. This fingerprint also evolves as browsers add/remove codec support, potentially enabling browser version detection.

Use Cases

•Format support
•Plugin availability
•Capability testing

Other Fingerprints

Compare related fingerprint signals

Move from this collector to the CreepJS signal index, live checker, API docs, and other high-value fingerprinting explainers.

Core pages

Browser Fingerprinting PlatformRun a privacy-first browser fingerprint check and learn what websites can infer about your device.Fingerprint CheckerTest your browser privacy with a live fingerprint scan, collector coverage, and privacy leakage analysis.IP Risk CheckerCheck IP risk, ASN, geolocation, proxy, VPN, Tor, datacenter, and routing signals through the CreepJS API.Browser Fingerprint SignalsBrowse the full CreepJS library of browser fingerprinting signals, including canvas, WebGL, WebRTC, fonts, storage, and privacy checks.DocumentationRead the CreepJS API, SDK, collector, and integration documentation for privacy-first browser fingerprinting.API PlaygroundGenerate a token, inspect sample payloads, and test CreepJS browser fingerprinting API calls.What Is Browser Fingerprinting?Learn how browser fingerprinting works, which signals are collected, and how privacy tools reduce tracking.

Popular fingerprint signals

Canvas FingerprintCanvas rendering fingerprint based on how the browser draws graphics. Test your browser's unique canvas signature.WebGL FingerprintWebGL GPU information and rendering capabilities. Detect your graphics card and WebGL implementation.WebRTC FingerprintWebRTC capabilities and IP leakage checks. Detect peer connection support and potential network exposure signals.Anti-Fingerprinting DetectionDetection of privacy tools and browser modifications. Identify fingerprint resistance.Navigator InformationBrowser navigator properties and user agent information. Analyze browser capabilities and settings.Font DetectionInstalled system fonts detection. Discover which fonts are available on your system.