MIME

MIME Type List & Content-Type Reference

Find MIME types by extension (png, jpg, mp3, pdf, json) with copy-ready output

API & HTTP

🔒 100% client-side — your data never leaves this page

Maintained by ToolsKit Editorial Team•Updated: April 7, 2026•Reviewed: April 9, 2026

Editorial Policy/Privacy/Report issue

English version/Chinese version

Page mode

MIME Type List (HTTP Content-Type)

Search by extension or MIME value across images, media, docs, fonts, archives, and common HTTP Content-Type mappings.

Quick CTA

Search an extension or MIME first to get the exact Content-Type and copy it immediately; category lookups and answer cards stay in Deep.

Popular MIME quick lookup

.pngimage/png

.jpgimage/jpeg

.mp3audio/mpeg

.pdfapplication/pdf

.jsonapplication/json

.xmlapplication/xml

.csvtext/csv

.webpimage/webp

114 results / 114 total entries

.jpg

image/jpegJPEG Image

.jpeg

image/jpegJPEG Image

.png

image/pngPNG Image

.gif

image/gifGIF Image

.webp

image/webpWebP Image

.svg

image/svg+xmlSVG Vector Image

.ico

image/x-iconIcon File

.avif

image/avifAVIF Image

.bmp

image/bmpBitmap Image

.tiff

image/tiffTIFF Image

.heic

image/heicHEIC Image

.heif

image/heifHEIF Image

.apng

image/apngAnimated PNG

.jp2

image/jp2JPEG 2000

.jxl

image/jxlJPEG XL

.psd

image/vnd.adobe.photoshopAdobe Photoshop

.mp4

video/mp4MP4 Video

.m4v

video/mp4M4V Video

.webm

video/webmWebM Video

.mov

video/quicktimeQuickTime Video

.avi

video/x-msvideoAVI Video

.mkv

video/x-matroskaMatroska Video

.ogv

video/oggOgg Video

.3gp

video/3gpp3GPP Video

.3g2

video/3gpp23GPP2 Video

.mpeg

video/mpegMPEG Video

.mpg

video/mpegMPEG Video

.ts

video/mp2tMPEG Transport Stream

.m2ts

video/mp2tM2TS Stream

.flv

video/x-flvFlash Video

.wmv

video/x-ms-wmvWindows Media Video

.mp3

audio/mpegMP3 Audio

.wav

audio/wavWAV Audio

.ogg

audio/oggOgg Audio

.aac

audio/aacAAC Audio

.flac

audio/flacFLAC Audio

.weba

audio/webmWebM Audio

.m4a

audio/mp4M4A Audio

.opus

audio/opusOpus Audio

.amr

audio/amrAMR Audio

.aif

audio/aiffAIFF Audio

.aiff

audio/aiffAIFF Audio

.mid

audio/midiMIDI Audio

.midi

audio/midiMIDI Audio

.html

text/htmlHTML Document

.htm

text/htmlHTML Document

.css

text/cssCSS Stylesheet

.js

text/javascriptJavaScript

.mjs

text/javascriptJavaScript Module

.cjs

text/javascriptCommonJS JavaScript

.ts

text/typescriptTypeScript

.tsx

text/typescriptTypeScript TSX

.jsx

text/javascriptJSX Script

.csv

text/csvCSV Spreadsheet

.tsv

text/tab-separated-valuesTSV Spreadsheet

.txt

text/plainPlain Text

.md

text/markdownMarkdown

.markdown

text/markdownMarkdown

.rtf

application/rtfRich Text Format

.xml

application/xmlXML Document

.yaml

application/yamlYAML

.yml

application/yamlYAML

.ics

text/calendariCalendar

.vtt

text/vttWebVTT Subtitle

.srt

application/x-subripSubRip Subtitle

.json

application/jsonJSON Data

.jsonld

application/ld+jsonJSON-LD

.map

application/jsonSource Map

.pdf

application/pdfPDF Document

.wasm

application/wasmWebAssembly

.doc

application/mswordWord Document (legacy)

.docx

application/vnd.openxmlformats-officedocument.wordprocessingml.documentWord Document

.xls

application/vnd.ms-excelExcel (legacy)

.xlsx

application/vnd.openxmlformats-officedocument.spreadsheetml.sheetExcel Spreadsheet

.ppt

application/vnd.ms-powerpointPowerPoint (legacy)

.pptx

application/vnd.openxmlformats-officedocument.presentationml.presentationPowerPoint

.odt

application/vnd.oasis.opendocument.textOpenDocument Text

.ods

application/vnd.oasis.opendocument.spreadsheetOpenDocument Spreadsheet

.odp

application/vnd.oasis.opendocument.presentationOpenDocument Presentation

.epub

application/epub+zipEPUB eBook

.sqlite

application/vnd.sqlite3SQLite Database

.db

application/octet-streamDatabase Binary

.bin

application/octet-streamBinary File

.exe

application/vnd.microsoft.portable-executableWindows Executable

.dmg

application/x-apple-diskimagemacOS Disk Image

.iso

application/x-iso9660-imageISO Disk Image

.apk

application/vnd.android.package-archiveAndroid Package

.msi

application/x-msdownloadWindows Installer

.deb

application/vnd.debian.binary-packageDebian Package

.rpm

application/x-rpmRPM Package

.jar

application/java-archiveJava Archive

.war

application/java-archiveWeb Application Archive

.class

application/java-vmJava Bytecode Class

.swf

application/x-shockwave-flashShockwave Flash

.ps

application/postscriptPostScript

.ai

application/postscriptAdobe Illustrator

.webmanifest

application/manifest+jsonWeb App Manifest

.zip

application/zipZIP Archive

.gz

application/gzipGzip Archive

.tar

application/x-tarTAR Archive

.tgz

application/gziptar.gz Archive

.bz2

application/x-bzip2Bzip2 Archive

.xz

application/x-xzXZ Archive

.7z

application/x-7z-compressed7-Zip Archive

.rar

application/vnd.rarRAR Archive

.zst

application/zstdZstandard Archive

.lz

application/x-lzipLzip Archive

.woff

font/woffWeb Font WOFF

.woff2

font/woff2Web Font WOFF2

.ttf

font/ttfTrueType Font

.otf

font/otfOpenType Font

.eot

application/vnd.ms-fontobjectEmbedded OpenType

.sfnt

font/sfntSFNT Font

.ttc

font/collectionTrueType Collection

Next step workflow

Parse header params Generate Content-Type Generate CORS response

Page reading mode

Deep expands pitfalls, recipes, snippets, FAQ, and related tools when you need troubleshooting or deeper follow-through.

About this tool

Use this searchable MIME type list to map file extensions to correct HTTP Content-Type headers. It covers 120+ common formats, including PNG, JPG, MP3, PDF, JSON, XML, CSV, WebP, SVG, fonts, archives, and office documents. You can search by extension or MIME value and copy ready-to-use results for API responses, uploads, downloads, and static asset delivery.

Suggested Workflow

API Debugging Checklist: From Broken Response to Root Cause

A practical debugging flow for API payload errors, auth failures, and malformed responses.

Document Handoff Workflow for Real Client and Review Delivery

Use small support tools around a document workflow so secure sharing, OCR review, and messy exports feel less fragile.

Base64 Decoding Troubleshooting for API and Data Pipelines

Fix garbled payloads, URL-safe mismatches, and decode failures with a repeatable checklist.

Quick Decision Matrix

One asset type is consumed by browser, crawler, and API clients

Recommend: Enforce explicit MIME + charset policy at origin and CDN edge.

Avoid: Avoid depending on downstream sniffing behavior differences.

Local exploration and temporary diagnostics

Recommend: Use fast pass with lightweight verification.

Avoid: Avoid promoting exploratory output directly to production artifacts.

Production release, compliance, or cross-team handoff

Recommend: Use staged workflow with explicit validation records.

Avoid: Avoid one-step execution without replayable evidence.

Failure Input Library

Serving SVG as generic text/plain

Bad input: CDN rule returns text/plain for .svg assets.

Failure: Browser rendering and CSP checks behave inconsistently across pages.

Fix: Return image/svg+xml and align CSP/image policy with actual media type.

Input assumptions are not normalized

Bad input: Edge payloads omit required fields.

Failure: Output appears valid locally but fails during downstream consumption.

Fix: Normalize contracts and enforce preflight checks before export.

Compatibility boundaries are implicit

Bad input: One-step execution bypasses review checkpoints.

Failure: Same source data yields inconsistent outcomes across environments.

Fix: Declare compatibility constraints and verify with an independent consumer.

Direct Answers

Q01

What MIME should I use when the file type is still uncertain?

Start with application/octet-stream as the fallback, then replace it with a specific MIME once you confirm the real payload format.

Q02

Why does a browser download a file instead of rendering it inline?

The response often uses a mismatched Content-Type or a generic binary fallback, so the client cannot safely render the asset.

Failure Clinic (Common Pitfalls)

Relying only on the filename extension

Cause: Extensions can be renamed while the actual payload format stays different, especially in uploads and generated exports.

Fix: Verify the real file format and make the returned Content-Type reflect the actual payload, not only the file name suffix.

Serving human-readable text without an explicit charset

Cause: Browsers and API clients may guess the wrong encoding for HTML, CSS, CSV, or plain text responses.

Fix: Add a charset parameter when you serve text responses that must render consistently across environments.

Compare & Decision

Specific MIME vs application/octet-stream

Specific MIME

Use it when the client should render, preview, or process the payload as a known format.

application/octet-stream

Use it only as a safe binary fallback when the exact payload type is still unknown.

Note: A specific MIME improves browser and API client behavior; the generic fallback is safer only when certainty is missing.

Content sniffing fallback vs explicit MIME policy

Explicit MIME policy

Use in production APIs and static asset delivery.

Rely on client sniffing

Use only in temporary diagnostics where strict typing is not possible.

Note: Explicit MIME is more predictable for cache, security, and rendering.

Fast pass vs controlled workflow

Fast pass

Use for low-impact exploration and quick local checks.

Controlled workflow

Use for production delivery, audit trails, or cross-team handoff.

Note: Mime Types is more reliable when acceptance criteria are explicit before release.

Direct execution vs staged validation

Direct execution

Use for disposable experiments and temporary diagnostics.

Stage + verify

Use when outputs will be reused by downstream systems.

Note: Staged validation reduces silent compatibility regressions.

Production Snippets

JSON API response baseline

HTTP

Content-Type: application/json; charset=utf-8

Scenario Recipes

Verify a static asset mapping before launch

Goal: Confirm that the extension, payload type, and returned Content-Type all match before debugging CDN or browser behavior.

Search the extension or MIME value in the tool.
Copy the canonical Content-Type you expect to serve.
Compare it with the response header in your network trace.

Result: You can isolate whether the issue is a MIME mapping problem or a later cache/CORS problem.

Validate CDN static asset MIME map before cache warmup

Goal: Catch incorrect MIME mappings before CDN caches the wrong headers globally.

List high-risk extensions (svg, json, wasm, csv) used in this release.
Compare configured MIME values with tool lookup and origin response headers.
Warm cache only after extension-to-MIME mapping is verified.

Result: You avoid global cache poisoning by wrong content rendering types.

Mime Types readiness pass for cross-team handoff validation

Goal: Validate assumptions before output enters shared workflows.

Run representative samples and capture output structure.
Replay edge cases with downstream acceptance criteria.
Publish only after sample and edge-case checks both pass.

Result: Delivery quality improves with less rollback and rework.

Mime Types incident replay for legacy contract stabilization

Goal: Convert recurring failures into repeatable diagnostics.

Rebuild problematic inputs in an isolated environment.
Compare expected and actual outputs against explicit pass criteria.
Document reusable runbook steps for on-call and handoff.

Result: Recovery time drops and operational variance shrinks.

Practical Notes

MIME Types Reference works best when you apply it with clear input assumptions and a repeatable workflow.

Practical usage

Use this tool as part of a repeatable debugging workflow instead of one-off trial and error.

Capture one reproducible input and expected output so teammates can verify behavior quickly.

Engineering tips

Keep tool output in PR comments or issue templates to shorten communication loops.

When behavior changes after deployment, compare old and new outputs with the same fixture data.

Use It In Practice

MIME Type List & Content-Type Reference is most reliable with real inputs and scenario-driven decisions, especially around "One asset type is consumed by browser, crawler, and API clients".

Use Cases

When One asset type is consumed by browser, crawler, and API clients, prioritize Enforce explicit MIME + charset policy at origin and CDN edge..
When Local exploration and temporary diagnostics, prioritize Use fast pass with lightweight verification..
Compare Specific MIME vs application/octet-stream for Specific MIME vs application/octet-stream before implementation.

Quick Steps

Search the extension or MIME value in the tool.
Copy the canonical Content-Type you expect to serve.
Compare it with the response header in your network trace.

Avoid Common Mistakes

Common failure: Browser rendering and CSP checks behave inconsistently across pages.
Common failure: Output appears valid locally but fails during downstream consumption.

Frequently Asked Questions

What is a MIME type in HTTP?

A MIME type identifies the media format of a response body. In HTTP, it is sent in the Content-Type header so browsers and clients know whether the payload is an image, JSON, audio, HTML, or another format.

What are common MIME types for png, jpg, mp3, pdf, and json?

Common pairs include png -> image/png, jpg/jpeg -> image/jpeg, mp3 -> audio/mpeg, pdf -> application/pdf, and json -> application/json. Use exact values to avoid rendering or download issues.

Should I use text/javascript or application/javascript?

For modern web delivery, text/javascript is broadly used by browsers. application/javascript is also seen in older setups. Keep your server behavior consistent and verify with your CDN and framework defaults.

What MIME type should I use for unknown binary files?

Use application/octet-stream when you cannot determine a specific type. This signals generic binary content and usually triggers download behavior in browsers.

Can a wrong Content-Type affect SEO or indexing?

Yes. Wrong Content-Type headers can prevent proper rendering or parsing, especially for HTML, CSS, JS, and feeds. That can indirectly harm crawl quality and indexing efficiency.

Does this tool run fully client-side?

Yes. All searches and filtering run in your browser, and no input data is uploaded to a backend service.