Configure your servers correctly. Instantly lookup the exact IANA-standardized HTTP Content-Type string for any file extension on the web.
50 results
Prevent broken image links and forced downloads by declaring the exact data classification in your HTTP headers.
When you programmatically upload a file to an Amazon S3 bucket via an SDK, you must explicitly pass the `ContentType` parameter. Use this database to find the exact string required.
Stop guessing file formats. This database provides the official, standardized prefixes (`application/`, `image/`, `audio/`) mandated by the Internet Assigned Numbers Authority.
Are you looking at an API response header containing a weird string like `application/x-tar`? Search the database to instantly reverse-engineer what file extension the server is actually sending.
When a web browser downloads a file from the internet, it has absolutely no idea what that file is. A file extension (like .png or .html) is just a human convention; operating systems often ignore them entirely. To understand how to safely render data, the browser relies entirely on the HTTP Content-Type header (the MIME type) sent by the server.
In the early 1990s, the internet could only transmit ASCII text. You could not attach an image or a PDF to an email because the network protocol literally could not understand binary data.
Engineers invented the MIME specification to solve this. It created a standardized classification system (e.g., image/jpeg or application/pdf). When you send an email today with a photo attached, the email client attaches the MIME type to the payload. The receiving computer looks at the MIME type, realizes it's receiving a picture, and routes the binary data to the graphics card instead of the text renderer.
When the World Wide Web was invented, HTTP adopted this exact same MIME protocol. A MIME Types reference list is now a critical tool for any backend web developer.
What happens if you configure your Nginx server incorrectly and it forgets to send a MIME type?
When a browser receives a file with an unknown or missing Content-Type, it defaults to the ultimate fallback: application/octet-stream.
This string literally translates to "a raw stream of unknown binary bytes." For security reasons, a browser will NEVER attempt to open or render an octet-stream. Instead, it will immediately force the file to download to the user's hard drive. If your website's logo image keeps downloading instead of displaying on the screen, your server's MIME configuration is broken.
MIME types are not just for static files like images. They are the backbone of modern API architecture.
Content-Type: application/json. If it doesn't, the frontend React application will fail to parse the payload.multipart/form-data. The backend server reads this MIME type and instantly knows it must route the incoming data stream to its file-parsing middleware.