Zero Signup ToolsFree browser tools

Developer Tools

MIME Type Lookup

Look up the MIME type for any file extension or search a curated media type database. Includes Content-Type header, aliases, charset, and IANA status.

Top-level type

application/*

application/json

JavaScript Object Notation. The default payload format for most modern REST and HTTP APIs.

File extensions
.json
Charset parameter
No (binary)
Status
Registered with IANA
Aliases seen in the wild
text/json
Reference
RFC 8259

Suggested Content-Type

Content-Type: application/json

Download disposition

Content-Disposition: attachment; filename="file.json"

Browse 126 matches

Click a card to see the details above

application/*

Arbitrary data, executables, archives, structured documents, and most JSON/XML payloads.

text/*

Human-readable text. May carry a charset parameter.

image/*

Bitmap and vector still images.

audio/*

Audio recordings and streams.

video/*

Video recordings and streams.

font/*

Font files. font/* was registered in 2017 (RFC 8081).

multipart/*

Composite bodies containing several parts with boundary markers.

message/*

Encapsulated messages such as email or HTTP request bodies.

model/*

3D models, scenes, and geometry.

Anatomy of a MIME type

A MIME type (also called media type) is type/subtype[+suffix][;parameter=value]. The top-level type names the broad category, the subtype names the specific format, the optional structured suffix shows the underlying encoding, and parameters such as charset or boundary attach extra detail.

  • Top-level types: application, text, image, audio, video, font, multipart, message, model.
  • vnd. prefix: vendor trees, registered by an organization (vnd.ms-excel, vnd.android.package-archive).
  • x. prefix: reserved for experimental use. The legacy x- prefix (e.g. application/x-tar) is discouraged by RFC 6648 but remains very common.
  • +json, +xml, +zip, +yaml: structured suffixes that hint at the underlying syntax for parsing and content negotiation.

Common pitfalls

  • image/jpg is not the IANA-registered form. Use image/jpeg. Browsers tolerate both.
  • text/xml is superseded by application/xml in RFC 7303.
  • audio/wav is non-standard. The IANA-registered form is audio/vnd.wave; browsers accept both.
  • application/octet-stream is the safe fallback for unknown binary data and usually triggers a download in browsers.
  • Always set charset=utf-8 on text/* responses to avoid encoding ambiguity.
See all 185 indexed file extensions

How to use

  1. Type a file extension (pdf, png, mp4), a full MIME type (image/jpeg, application/json), or a keyword (calendar, archive, font) into the search field.
  2. Optionally filter by top-level type (application/*, text/*, image/*, audio/*, video/*, font/*, multipart/*, message/*, model/*) using the pills above the results.
  3. Click any card in the browse list to load its full breakdown into the detail card, including extensions, charset, status, aliases, and reference.
  4. Use the copy buttons to grab the canonical MIME string, the full Content-Type header, or the Content-Disposition download header for use in code or server config.
  5. Open the indexed-extensions disclosure at the bottom to scan every extension this tool knows about.

About this tool

MIME Type Lookup is a searchable database of common media (MIME) types and the file extensions they ship with. Type a file extension (pdf, docx, webp, mp4, csv), a full MIME string (image/jpeg, application/json, audio/vnd.wave), or any keyword from a description (manifest, archive, font, calendar) to find the canonical IANA name, the structured suffix when one is present (+json, +xml, +zip), the file extensions normally bound to that type, any aliases that show up in the wild (image/jpg, audio/wav, text/xml), whether the type takes a charset parameter, the IANA registration status (registered, provisional, vendor tree, x-prefix, deprecated), and the RFC or vendor reference. The selection card shows the exact Content-Type header to send (with charset=utf-8 added for text/* responses) and a suggested Content-Disposition header for downloads, both with one-click copy. Use it when configuring nginx, Apache, Caddy, or IIS to serve a new file type, when setting Content-Type on an upload, API response, or download, when validating an accept= or multipart/form-data list, when decoding a data: URL, or when checking which RFC defines a given format. Everything runs locally in your browser; no extension or file you type is sent anywhere.

Free to use. Works in your browser. No signup, no login.

Related tools

You may also like

All tools
All toolsDeveloper Tools