Skip to content
TextArray1.41.0
100% local

MIME type lookup

Look up the MIME type for a file extension, or the usual extensions for a MIME type.

Input
Output
Related tools
Charset detectorEncoding & conversion
HTTP header parserDeveloper tools
Base64 encode and decodeEncoding & conversion
i18n key diffDeveloper tools
TOML to JSON converterDeveloper tools
SQL to JSONDeveloper tools
MIME type lookup
Paste a list of file extensions or filenames and this tool appends the matching MIME type to each — png becomes image/png, a filename like archive.tar.gz resolves by its last extension to application/gzip. Switch direction and it works the other way: paste a MIME type like image/jpeg and get back the extensions commonly used for it (jpg, jpeg, jpe). It covers everyday web, document, media, font and archive formats, so you rarely need to leave the tab to check a Content-Type header or configure a server's static-file handling.
The output format option shapes the result for wherever it is going next. "Plain list" prints one arrow-separated line per entry, readable on its own. "Table" aligns everything into columns with a header, handy for pasting into documentation. "nginx types" produces lines shaped like nginx's mime.types file, and "Apache AddType" produces one AddType directive per entry, ready to drop into an .htaccess file or a virtual host config — both save you from hand-typing the directive syntax around a value you already looked up.
"Mark unknown entries" controls what happens when something doesn't match: turned on, the entry still appears in the output labelled unknown, so a typo or an obscure format is visible rather than silently missing; turned off, unmatched entries are dropped and the output only contains resolved matches. Matching is case-insensitive and ignores parameters on a MIME type (image/jpeg; charset=binary matches the same as image/jpeg), and a leading dot on an extension is optional.
Everything runs in your browser from a small built-in table — no extension, filename or MIME type you paste is ever uploaded anywhere, which makes it safe to point at real file listings, server configs or API response headers. The tally under the output reports how many entries were processed, how many matched and how many were unknown, so a surprising result is easy to explain at a glance.
FAQ
Can I paste full filenames instead of bare extensions?
Yes. A filename like report.final.docx is matched by its last extension (docx), the same as pasting docx on its own.
What happens with a dotfile that has no real extension, like .gitignore?
It resolves to no match and is counted as unknown — there is no extension after the leading dot to look up.
How do the nginx and Apache formats differ from the plain list?
"nginx types" formats each match as a line from an nginx mime.types file; "Apache AddType" formats each as an AddType directive for an .htaccess file or virtual host config. Both are meant to be copied straight into a server config rather than read as prose.
Does the MIME type → extension direction return every possible extension?
It returns the extensions this tool knows for that MIME type, ordered as they are commonly seen — not an exhaustive registry of every extension anyone has ever used for it.
Is my file list or server config uploaded anywhere?
No. The lookup runs entirely in your browser against a small built-in table — nothing you paste here is sent to a server.