This feature is non-standard and is not on a standards track. Do not use it on production sites facing the Web: it will not work for every user. There may also be large incompatibilities between implementations and the behavior may change in the future.
Large-Allocation response header tells the browser that the page being loaded is going to want to perform a large allocation.
WebAssembly or asm.js applications can use large contiguous blocks of allocated memory. For complex games, for example, these allocations can be quite large, sometimes as large as 1GB. The
Large-Allocation tells the browser that the web content in the to-be-loaded page is going to want to perform a large contiguous memory allocation and the browser can react to this header by starting a dedicated process for the to-be-loaded document, for example.
|Header type||Response header|
|Forbidden header name||no|
Large-Allocation: 0 Large-Allocation: <megabytes>
- 0 is a special value which represents uncertainty as to what the size of the allocation is.
- The expected size of the allocation to be performed, in megabytes.
Large-Allocation: 0 Large-Allocation: 500
Not part of any current specifications. An explainer of the ideas behind this header can be found in this document.
The compatibility table in this page is generated from structured data. If you'd like to contribute to the data, please check out https://github.com/mdn/browser-compat-data and send us a pull request.
|Large-Allocation||No support||No support||No support1||No support||No support||No support||No support|
|Feature||Android||Chrome for Android||Edge Mobile||Firefox for Android||IE Mobile||Opera Mobile||Safari Mobile|
|Large-Allocation||No support||No support||No support||No support||No support||No support||No support|
1. Available if the preference
dom.largeAllocationHeader.enabled is set to true in about:config