Downlink

Limited availability

This feature is not Baseline because it does not work in some of the most widely-used browsers.

Experimental: This is an experimental technology
Check the Browser compatibility table carefully before using this in production.

The HTTP Downlink request header is used in Client Hints to provide the approximate bandwidth in Mbps of the client's connection to the server.

The hint allows a server to choose what information is sent based on the network bandwidth. For example, a server might choose to send smaller versions of images and other resources on low bandwidth networks.

Note: The Vary header is used in responses to indicate that a different resource is sent for every different value of the header (see HTTP Caching Vary). Even if Downlink is used to configure what resources are sent, consider omitting it in the Vary header — it is likely to change often, which effectively makes the resource uncacheable.

Header type Request header, Client hint
Forbidden header name No

Syntax

http
Downlink: <number>

Directives

<number>

The downlink rate in Mbps, rounded to the nearest 25 kilobits. The downlink rate may be used as a fingerprinting variable, so values for the header are intentionally coarse to reduce the potential for its misuse.

Examples

A server first needs to opt in to receive the Downlink header by sending the Accept-CH response header containing Downlink.

http
Accept-CH: Downlink

Then on subsequent requests the client might send a Downlink header back:

http
Downlink: 1.7

Specifications

Specification
Network Information API
# downlink-request-header-field

Browser compatibility

Report problems with this compatibility data on GitHub
desktopmobile
Chrome
Edge
Firefox
Opera
Safari
Chrome Android
Firefox for Android
Opera Android
Safari on iOS
Samsung Internet
WebView Android
WebView on iOS
Downlink
Experimental

Legend

Tip: you can click/tap on a cell for more information.

Full support
Full support
No support
No support
Experimental. Expect behavior to change in the future.
See implementation notes.

See also