Reputation: 10867
Pretty simple question but can't seem to find it anywhere online. I'm trying to make a program that depending on the file type will give me the extension.
Upvotes: 581
Views: 520827
Reputation: 7144
tl;dr There is no MIME type image/jpg
; there is image/jpeg
. However, there is much variation in official documented mappings between files with file name extension .jpg
and MIME types. But in practice, nearly all software handles image files named *.jpg
in an expected manner
This particular topic is confusing because the varying association of file name extension associated to a MIME type depends which organization created the table of file name extensions to MIME types. In other words, file name extension .jpg
could be many different things, "officially" (but in practice is always a JPEG image).
For example, here are three "complete lists" and one RFC that with varying JPEG Image format file name extensions and the associated MIME types.
.jfif
, .jfif-tbnl
, .jpe
, .jpeg
, .jpg
→ image/jpeg
.jfif
, .jpe
, .jpeg
, .jpg
→ image/pjpeg
.jpeg
, .jpg
→ image/jpeg
.jpeg
, .jpg
→ image/x-citrix-jpeg
.pjpeg
→ image/pjpeg
jpg
not mentionedjpeg
→ see RFC 2045 (no mention), see RFC 2046 → image/jpeg
13JPEG
→ video/JPEG
jpeg2000
→ video/jpeg2000
jpm
→ image/jpm
(JPEG 2000)jpx
→ image/jpx
(JPEG 2000)vnd.sealedmedia.softseal.jpg
→ image/vnd.sealedmedia.softseal.jpg
These "complete lists" and RFC do not have MIME type image/jpg
! But for MIME type image/jpeg
some lists do have varying file name extensions (.jpeg
, .jpg
, …). Other lists do not mention MIME type image/jpeg
.
Also, there are different types of JPEG Image formats (e.g. Progressive JPEG Image format, JPEG 2000, etcetera) and "JPEG Extensions" that may or may not overlap in file name extension and declared MIME type.
Another confusing thing is RFC 3745 does not appear to match IANA Media Types yet the same RFC is supposed to inform the IANA Media Types document. For example, in RFC 3745 .jpf
is preferred file extension for image/jpx
but in IANA Media Types the name jpf
is not present (and that IANA document references RFC 3745!).
Another confusing thing is IANA Media Types lists "names" but does not list "file name extensions". This is on purpose, but confuses the endeavor of mapping file name extensions to MIME types.
Another confusing thing: is it "mime", or "MIME", or "MIME type", or "mime type", or "mime/type", or "MIME sub-type", or "media type"?
The most official seeming document by IANA is surprisingly inadequate. No MIME type is registered for file extension .jpg
yet there exists the odd vnd.sealedmedia.softseal.jpg
. File extension.JPEG
is only known as a video
type while file extension .jpeg
is an image type (when did lowercase and uppercase letters start mattering!?). At the same time, jpeg2000
is type video
yet RFC 3745 considers JPEG 2000 an image
type! The IANA list seems to cater to company-specific jpeg formats (e.g. vnd.sealedmedia.softseal.jpg
).
Because of the prior confusions, it is difficult to find an industry-accepted canonical document that maps file name extensions to MIME types (and vice-versa), particularly for the JPEG Image File Format.
This document is not related to the definition of the MIME sub-type image/jpeg, which is partly defined by [ISO-JPEG-1], and partly by the file format specification defined in [JFIF].
JFIF
(JPEG File Interchange Format) does not mention any MIME types or file name extensions.ISO-JPEG-1
(ISO/IEC 10918-1:1994) requires a fair amount of money to view.Related question "List of ALL MimeTypes on the Planet, mapped to File Extensions?".
Upvotes: 77
Reputation: 501
Media type allows us to cater not just for data in storage but also in transit. A dynamically generated image has no file extension, but still has a media type. Linux and MacOS don't enforce file extensions, but do have or infer media types (see the format indicators section of https://en.wikipedia.org/wiki/Magic_number_(programming)).
Here's some additional reading on file extensions (or lack thereof) in Linux and MacOS:
Try emailing a Windows executable file to someone by changing the file extension to .jpg (or .png). See why the email client refuses to send it, even though the file type, based on the file extension, is absolutely harmless.
People/systems invent extensions freely (have you spotted the extension jpg_large)? A media types is the standard means to specify content types and is managed by the Internet Assigned Numbers Authority (IANA). See https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types
William Shakespeare foresaw media types when he wrote this: "A rose by any other name would smell as sweet" - This is what he had in mind: all roses by any name have the media type flower/rose :-)
Upvotes: 0
Reputation: 9999
No, image/jpg
is not the same as image/jpeg
.
You should use image/jpeg
. Only image/jpeg
is recognised as the actual mime type for JPEG files.
See https://www.rfc-editor.org/rfc/rfc3745, https://www.w3.org/Graphics/JPEG/ .
Serving the incorrect Content-Type of image/jpg
to IE can cause issues, see http://www.bennadel.com/blog/2609-internet-explorer-aborts-images-with-the-wrong-mime-type.htm.
Upvotes: 830
Reputation: 16291
The important thing to note here is that the mime type is not the same as the file extension. Sometimes, however, they have the same value.
https://www.iana.org/assignments/media-types/media-types.xhtml includes a list of registered Mime types, though there is nothing stopping you from making up your own, as long as you are at both the sending and the receiving end. Here is where Microsoft comes in to the picture.
Where there is a lot of confusion is the fact that operating systems have their own way of identifying file types by using the tail end of the file name, referred to as the extension. In modern operating systems, the whole name is one long string, but in more primitive operating systems, it is treated as a separate attribute.
The OS which caused the confusion is MSDOS, which had limited the extension to 3 characters. This limitation is inherited to this day in devices, such as SD cards, which still store data in the same way.
One side effect of this limitation is that some file extensions, such as .gif
match their Mime Type, image/gif
, while others are compromised. This includes image/jpeg
whose extension is shortened to .jpg
. Even in modern Windows, where the limitation is lifted, Microsoft never let the past go, and so the file extension is still the shortened version.
Given that that:
The short answer is:
image/jpg
, so the answer is
that it is not the same as image/jpeg
While we’re at it …
Legacy versions of Internet Explorer took the liberty of uploading jpeg
files with the Mime Type of image/pjpeg
, which, of course, just means more work for everybody else. They also uploaded png
files as image/x-png
.
Upvotes: 7