HTTPREF
← Back to MIME types

MIME Type

application/javascript

Web Asset

Common MIME type for JavaScript files used in browsers and web apps.

MIME type reference, HTTP example, browser usage, common mistakes, and related content.

What is the application/javascript MIME type?

The MIME type application/javascript is used to tell browsers, APIs, and servers how a file or response body should be interpreted.

MIME stands for Multipurpose Internet Mail Extensions, and MIME types are now a standard part of HTTP responses and web content delivery.

When a browser or client receives a response with application/javascript, it uses that information to decide how the content should be processed, rendered, downloaded, or executed.

Example

Content-Type: application/javascript

HTTP example

HTTP/1.1 200 OK
Content-Type: application/javascript
Content-Length: 1256

Common file extensions

.js.mjs

Common use cases

  • Frontend scripts
  • Bundled JS assets
  • Browser modules

Common mistakes

  • Using the wrong MIME type for the file being served
  • Returning text/plain instead of application/javascript
  • Forgetting required parameters like charset when relevant
  • Using a deprecated MIME type in older server configurations
  • Serving assets with a mismatched Content-Type header, causing browser parsing issues

How browsers use it

Browsers use the Content-Type response header to decide how a response should be handled. For example, HTML is rendered as a page, CSS is parsed as styles, JavaScript is executed as script, and images are displayed visually. If the MIME type is incorrect, the browser may refuse to load the file correctly or may treat it as plain text or a download instead.

Browser support

Widely supported in modern browsers and recommended for JavaScript delivery.

Developer note

Modern browsers are strict about JavaScript MIME types, especially for ES modules.

Related MIME types