← Back to MIME types
MIME Type
application/wasm
Web AssetMIME type for WebAssembly binary modules used in modern web applications.
MIME type reference, HTTP example, browser usage, common mistakes, and related content.
What is the application/wasm MIME type?
The MIME type application/wasm 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/wasm, it uses that information to decide how the content should be processed, rendered, downloaded, or executed.
Example
Content-Type: application/wasm
HTTP example
HTTP/1.1 200 OK Content-Type: application/wasm Content-Length: 1256
Common file extensions
.wasm
Common use cases
- WebAssembly apps
- High-performance browser code
- Tooling and compute-heavy frontend features
Common mistakes
- Using the wrong MIME type for the file being served
- Returning text/plain instead of application/wasm
- 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
Supported in modern browsers, but server configuration must be correct or browsers may refuse to load the module.
Developer note
Important for modern web tooling, games, and performance-sensitive browser applications.