Why can't I just trust a file's extension to know its type?

A file's extension is just part of its name and can be changed or faked trivially — a malicious file could be renamed to `.jpg` while actually containing executable code. The MIME type sent in an HTTP header (or detected by inspecting the actual file content) is a more reliable, though still not foolproof, signal of what a file actually is.

What's the difference between .jpg and .jpeg?

They're just two common extensions for the exact same file format and share the same MIME type, `image/jpeg` — the shorter `.jpg` exists mainly for historical compatibility with older systems that only supported 3-character file extensions.

What's the difference between application/x-www-form-urlencoded and multipart/form-data?

`application/x-www-form-urlencoded` encodes form fields as URL-style key-value pairs in the request body — fine for simple text fields, but it can't handle file uploads. `multipart/form-data` splits the request into distinct parts, which is required whenever a form includes a file input.

Why does .docx have such a long MIME type?

Modern Office formats (.docx, .xlsx, .pptx) are actually ZIP archives containing XML files internally, and their MIME types (following the OOXML/Open Packaging Conventions standard) explicitly reflect that structure — hence the long `application/vnd.openxmlformats-officedocument...` string, compared to the much shorter legacy `.doc` MIME type from before that format existed.

How do I set the correct MIME type when serving files from my own server?

Most web servers and frameworks (Express, Nginx, Apache) automatically set the correct `Content-Type` header based on the file extension using a built-in MIME type mapping — you typically only need to set it manually for custom API responses or unusual file types not in the server's default mapping.

MIME Type Finder

Find the Correct MIME Type for Any File Extension

Need to use MIME Type Finder right now?

Setting a Content-Type header or validating a file upload requires the exact correct MIME type string for a given file extension — get it wrong, and a browser or API may reject or mishandle the file. This tool looks up the accurate MIME type for any extension instantly.

No sign-upNo uploads 100% free

.htmltext/html

.csstext/css

.jstext/javascript

.jsonapplication/json

.xmlapplication/xml

.pdfapplication/pdf

.zipapplication/zip

.txttext/plain

.csvtext/csv

.pngimage/png

.jpg / .jpegimage/jpeg

.gifimage/gif

.svgimage/svg+xml

.webpimage/webp

.icoimage/x-icon

.mp3audio/mpeg

.wavaudio/wav

.mp4video/mp4

.webmvideo/webm

.wofffont/woff

.woff2font/woff2

.ttffont/ttf

.docapplication/msword

.docxapplication/vnd.openxmlformats-officedocument.wordprocessingml.document

.xlsapplication/vnd.ms-excel

.xlsxapplication/vnd.openxmlformats-officedocument.spreadsheetml.sheet

.pptapplication/vnd.ms-powerpoint

.mp4v / .m4vvideo/x-m4v

.wasmapplication/wasm

.form-urlencodedapplication/x-www-form-urlencoded

.multipartmultipart/form-data

Features

Runs entirely in your browser
Privacy-first — your data is never uploaded
Real-time, instant results
100% free, no sign-up required
Works on desktop, tablet, and mobile
No installation needed

Who uses this tool?

Software engineersWeb developersAPI testersDevOps engineersStudents

People also search for

MIME Type Lookup Content-Type Header Lookup File Extension to MIME Type Lookup Image MIME Type Checker JSON Formatter tool

About MIME Type Finder

A MIME type (also called a media type or content type) is a standardized string that tells a browser, email client, or server exactly what kind of data a file contains — independent of the file's name or extension — so the receiving system knows how to handle it. When a server sends an image, it includes a `Content-Type: image/png` header; when a browser receives that header, it knows to render the bytes as an image rather than trying to display them as text, regardless of what the file happened to be named.

This matters constantly in web development: setting the correct `Content-Type` header when serving a file from a custom server or API, configuring file upload validation to accept or reject specific MIME types rather than trusting a file's extension (which is trivial to fake), setting the `accept` attribute on an HTML file input to restrict what a user can select, or simply understanding what MIME type corresponds to a file extension you're working with.

This reference covers the MIME types you'll encounter most often in everyday web and application development: common document formats (HTML, CSS, JavaScript, JSON, PDF), image formats (PNG, JPEG, SVG, WebP), audio and video formats (MP3, MP4, WebM), fonts (WOFF, WOFF2, TTF), and Microsoft Office formats (the modern XML-based `.docx`/`.xlsx` types alongside their older `.doc`/`.xls` equivalents), plus the two form-submission content types (`application/x-www-form-urlencoded` and `multipart/form-data`) that every web developer eventually needs to know the difference between.

Search by either the file extension or a keyword from the MIME type itself — searching "image" surfaces every image format at once, which is useful when you're not sure of the exact extension but know the general category of file you're working with.

How it works

Search by extension or type. Type a file extension (like .png) or a keyword (like "image").
Copy the MIME type. Click the copy icon next to any result to grab the exact MIME type string.

Examples

Looking up .svg

Input

.svg

Output

image/svg+xml