DevCoreTools

MIME Type Lookup

Search MIME types and file extensions to understand content types, common uses, and HTTP Content-Type headers.

Find a content type

Search by MIME type, extension, category, Content-Type header, common use, or keyword.

Processed locally in your browser Limit Search text. Your input is processed in your browser and is not uploaded or sent to a server. Avoid pasting production secrets, access tokens, private keys, passwords, or sensitive customer data unless you understand the risk.

Browse MIME types

16 matching content types grouped by category.

Text

Human-readable text formats commonly sent with a charset.

Image

Raster and vector image formats used by browsers, APIs, and assets.

Audio

Audio media containers and codecs exposed through Content-Type.

Video

Video media containers commonly streamed or downloaded.

Application

Structured documents, archives, JSON, XML, and binary payloads.

Font

Web font formats referenced by CSS and browser font loaders.

Multipart

HTTP body formats that contain several parts separated by boundaries.

Application

application/json

Extensions

.json, .map

Content hint

Usually text-readable payload. Extension lookup is a best-effort hint and does not verify file contents.

Common uses

  • REST API responses
  • Configuration files
  • Source maps

Example header

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

Notes

  • Use application/json for JSON API payloads and include a charset only if your stack requires it.

MIME type guide for HTTP APIs and browsers

MIME types identify the media type of a payload so clients can parse, preview, download, or reject content intentionally.

MIME types and Content-Type

A response header such as Content-Type: application/json tells a client how to interpret the body. Request bodies use the same header to describe what the server is receiving.

Extension versus MIME type

A file extension is only a naming convention. Servers, browsers, and storage systems may map extensions to MIME types, but that mapping does not prove the actual bytes match the extension.

Text and charset

Text formats such as text/plain, text/html, and text/css are commonly sent with charset=utf-8 so clients decode characters consistently.

application/octet-stream

application/octet-stream is the generic binary fallback. It is useful for unknown downloads, but a specific MIME type is clearer when your application knows the payload.

multipart/form-data

multipart/form-data is used for form and API file uploads. Actual HTTP requests include a boundary parameter that separates each part in the body.

Browser and API usage

Correct MIME types help browsers load scripts, styles, images, fonts, audio, and video safely. APIs use them for negotiation, validation, and predictable client parsing.

Keep working

View all API & Auth tools
HTTP Headers Parser / FormatterParse, format, inspect, and export HTTP headers locally with structured warnings.HTTP Status Code LookupLook up HTTP response status codes locally with meanings, examples, and API notes.OpenAPI ValidatorValidate OpenAPI and Swagger specs locally with structured errors and warnings.cURL to Code ConverterConvert cURL commands into readable HTTP request code snippets locally.URL Parser / Query String ParserEncoding & DecodingParse full URLs, relative URLs, and query strings into structured parts.JSON FormatterJSON ToolsFormat, validate, inspect, and export JSON locally.
Learn more: JWT Guide

FAQ

Does this lookup upload files or inspect file contents?

No. It searches a static local dataset and optionally reads only the text you type as a file name. It does not upload files, sniff bytes, or validate actual content.

Can an extension prove a MIME type?

No. Extension lookup is a best-effort hint. A file named report.pdf may be served as application/pdf, but only content-aware validation can prove what the file contains.

When should I use application/octet-stream?

Use it when a payload is truly generic binary data or when the server cannot choose a more specific type. Prefer specific types such as application/pdf or image/png when known.

Why does multipart/form-data need a boundary?

The boundary separates the individual form fields and file parts in the HTTP body. Clients usually generate it automatically when building form-data requests.

Should JSON be text/json or application/json?

Use application/json for JSON APIs and JSON documents. It is the standard type clients expect for structured JSON payloads.