This specification defines the preload keyword that may be used with link elements. This keyword provides a declarative fetch primitive that initiates an early fetch and separates fetching from resource execution.

This is a work in progress and may change without any notices.

Implementers SHOULD be aware that this document is not stable. Implementers who are not taking part in the discussions are likely to find the specification changing out from under them in incompatible ways. Vendors interested in implementing this document before it eventually reaches the Candidate Recommendation stage SHOULD join the mailing lists below and take part in the discussions.


The terms link, inserted into a document, resolve, url, crossorigin, origin, delay the load event, external resource link, valid media query list, queue a task, fetch and process the linked resource, match the environment, and process the linked resource are defined in [[HTML]].

The terms Document, Content-Type metadata, fire an event , in a document tree and node document are defined in [[!DOM]].

The terms request destination and network error are defined in [[!FETCH]].

The terms parsable MIME type and unsupported MIME type are defined in [[!MIMESNIFF]].

The term prefetch is defined in [[RESOURCE-HINTS]].

The terms integrity metadata and verification of HTML document subresources are defined in [[SRI]].


Many applications require fine-grained control over when resources are fetched, processed, and applied to the document. For example, the loading and processing of some resources may be deferred by the application to reduce resource contention and improve performance of the initial load. This behavior is typically achieved by moving resource fetching into custom resource loading logic defined by the application - i.e. resource fetches are initiated via injected elements, or via `XMLHttpRequest`, when particular application conditions are met.

However, there are also cases where some resources need to be fetched as early as possible, but their processing and execution logic is subject to application-specific requirements - e.g. dependency management, conditional loading, ordering guarantees, and so on. Currently, it is not possible to deliver this behavior without a performance penalty.

The preload keyword on link elements provides a declarative fetch primitive that addresses the above use case of initiating an early fetch and separating fetching from resource execution. As such, preload keyword serves as a low-level primitive that enables applications to build custom resource loading and execution behaviors without hiding resources from the user agent and incurring delayed resource fetching penalties.

For example, the application can use the preload keyword to initiate early, high-priority, and non-render-blocking fetch of a CSS resource that can then be applied by the application at appropriate time:

<!-- preload stylesheet resource via declarative markup -->
<link rel="preload" href="/styles/other.css" as="style">

<!-- or, preload stylesheet resource via JavaScript -->
var res = document.createElement("link");
res.rel = "preload"; = "style";
res.href = "styles/other.css";

As above examples illustrate, the resource can be specified via declarative markup, Link HTTP header ([[!RFC5988]]), or scheduled via JavaScript. See use cases section for more hands-on examples of how and where preload can be used.

There is only one class of product that can claim conformance to this specification: a user agent.

Use cases

Early fetch of critical resources

Preload parsers are used by most user agents to initiate early resource fetches while the main document parser is blocked due to a blocking script. However, the preload parsers do not execute JavaScript, and typically only perform a shallow parse of CSS, which means that the fetch of resources specified within JavaScript and CSS is delayed until the relevant document parser is able to process the resource declaration.

In effect, most resources declarations specified within JavaScript and CSS are "hidden" from the speculative parsers and incur a performance penalty. To address this, the application can use a preload link to declaratively specify which resources the user agent must fetch early to improve page performance:

Above markup initiates four resource fetches: a font resource, a stylesheet, an unknown resource type from another origin, and a font resource from another origin. Each fetch is initialized with appropriate request headers and priority - the unknown type is equivalent to a fetch initiated `XMLHttpRequest` request. Further, these requests do not block the parser or the load event.

Preload links for CORS enabled resources, such as fonts or images with a `crossorigin` attribute, must also include a `crossorigin` attribute, in order for the resource to be properly used.

Early fetch and application defined execution

The preload link can be used by the application to initiate early fetch of one or more resources, as well as to provide custom logic for when and how each response should be applied to the document. The application may:

The preload link provides a low-level and content-type agnostic primitive that enables applications to build custom resource loading and execution behaviors without incurring the penalty of delayed resource loading.

For example, preload link enables the application to provide `async` and `defer` like semantics, which are only available on `script` elements today, but for any content-type: applying the resource immediately after it is available provides `async` functionality, whereas adding some ordering logic enables `defer` functionality. Further, this behavior can be defined across a mix of content-types - the application is in full control over when and how each resource is applied.

  function preloadFinished(e) { ... }
  function preloadError(e)  { ... }
<!-- listen for load and error events -->
<link rel="preload" href="app.js" as="script" onload="preloadFinished()" onerror="preloadError()">

By decoupling resource fetching from execution, the preload link provides a future-proof primitive for building performant application specific resource loading strategies.

Developer, server, and proxy-initiated fetching

The preload link can be specified by the developer, or be automatically generated by the application server or an optimization proxy (e.g. a CDN).

  <link rel="preload" href="//" as="document">
  var res = document.createElement("link");
  res.rel = "preload"; = "document";
  res.href = "/other/widget.html";

IANA Considerations

The link relation type below has been registered by IANA per Section 6.2.1 of [[!RFC5988]]:

Relation Name:
Refers to a resource that should be loaded early in the processing of the link's context, without blocking rendering.
W3C Preload Specification (
Additional target attributes establish the detailed fetch properties of the link.

Privacy and Security

Preload is a declarative fetch primitive that initiates early fetch of resources and separates fetching from resource execution. In effect, it is conceptually similar to initiating a scripted fetch for a resource, but with additional constraints and benefits:

The site authors are encouraged to take the necessary precautions and specify the relevant [[CSP3]], [[MIXED-CONTENT]], and [[REFERRER-POLICY]] rules, such that the browser can enforce them when initiating the preload request. Additionally, if preload directives are provided via the `Link` HTTP response header, then the relevant policies should also be delivered as an HTTP response header - e.g. see Processing Complications for CSP.


This document reuses text from the [[HTML]] specification, edited by Ian Hickson, as permitted by the license of that specification.