MIME type lookup

Reference & converters

Map file extensions to MIME types for accurate Content-Type headers.

Updated May 30, 2026

Search by extension or MIME

Matches (15)

Extension	MIME Type	Description
.html	text/html	HTML document
.css	text/css	CSS stylesheet
.js	text/javascript	JavaScript file
.json	application/json	JSON document
.xml	application/xml	XML document
.png	image/png	PNG image
.jpg	image/jpeg	JPEG image
.svg	image/svg+xml	SVG image
.webp	image/webp	WebP image
.pdf	application/pdf	PDF document
.zip	application/zip	ZIP archive
.csv	text/csv	CSV file
.md	text/markdown	Markdown file
.mp4	video/mp4	MP4 video
.mp3	audio/mpeg	MP3 audio

Quick start

How to lookup MIME types

Search by extension or MIME string and map content types quickly.

Step 1

Enter query

Type extension (.pdf) or MIME (application/json).
Step 2

Find mapping

Review extension to MIME relationship.
Step 3

Use headers

Set correct Content-Type in server/storage config.

In-depth guide

MIME types: matching file extensions to the right Content-Type

A MIME type (now formally a "media type") is the label that tells a browser or API what a file actually is — image/png, application/json, text/css. Get it wrong and a stylesheet refuses to load or a download opens as gibberish. This tool maps extensions to their correct MIME types so your Content-Type headers are right.

Why Content-Type matters

Browsers decide how to handle a response largely from its Content-Type, not its file extension. Serve JavaScript as text/plain and the browser refuses to execute it; serve a PDF as application/octet-stream and it downloads instead of previewing. Modern browsers also enforce X-Content-Type-Options: nosniff, so a wrong type is fatal, not forgiven.

How to use this tool

Search by file extension (.webp) or by MIME fragment (font).
Copy the correct media type.
Set it as the Content-Type in your static host, API gateway or download endpoint config.

Text needs a charset; binaries do not

For text formats, append a charset so characters render correctly — text/html; charset=utf-8. Binary formats (images, fonts, archives) do not take a charset. When you genuinely do not know a file's type, application/octet-stream is the safe "unknown binary" fallback that triggers a download.

Privacy

This is a local lookup — the extension or MIME fragment you search is matched in your browser and nothing is uploaded.

When to use it vs alternatives

Use this tool for quick browser-based work when you need an answer or output immediately. Use a dedicated application or automated workflow when you need bulk processing, approvals, or repeatable production rules.

Common pitfalls

Check the result before replacing the original input.
Watch for unit, format, encoding, and browser memory limits on large inputs.
Keep a copy of important source material until the output is verified.

Frequently asked questions

Can I look up by extension and by MIME string?

Yes. Search works for both a file extension like .webp and a MIME fragment like font.

Is this list exhaustive?

It focuses on the frequently used web and document MIME mappings you meet when configuring hosting and APIs.

Why does the MIME type matter?

Browsers decide how to handle a response from its Content-Type, not its file extension. A wrong type can stop a stylesheet loading or turn a preview into a download.

Do I need to add a charset?

For text formats, yes — append a charset like text/html; charset=utf-8 so characters render correctly. Binary formats such as images and fonts do not take a charset.

What type should I use for an unknown file?

application/octet-stream is the safe fallback for unknown binary data. It tells the browser to download the file rather than try to render it.

Is the lookup done locally?

Yes. The extension or MIME fragment you search is matched in your browser and nothing is uploaded.

Keep exploring