fetchLater
Queues a request now that the browser sends later, even if the page closes first.
In one line
Can queue a report now and have the browser send it later, even after you close
Queues a request now that the browser sends later, even if the page closes first.
Gives analytics a reliable way to report at page end. The browser sends it after a chosen delay or when the page is discarded or goes into bfcache. Chrome shipped it in version 135 (Apr 2025).
What it can and can't do
What the user does: Nothing. It happens as you use a page that sets up a delayed report
It can
- Queue a request that the browser sends when the page closes
- Send it at a time the page sets
- Update or cancel the queued report while the page is open
It cannot
- Send the report forever; the browser sends it after a limit
- Work in Firefox, Safari or iPhone browsers
- Send large amounts of data
- Show a prompt or any sign that a report is waiting
How it differs between platforms: Only Chrome, Edge and Chrome on Android support it.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 135 | 2025-04-01 | None |
| Edge | Supported | 135 | 2025-04-04 | None |
| Firefox | Not supported | Not available | Not listed | None |
| Safari | Not supported | Not available | Not listed | None |
| Safari on iPhone | Not supported | Not available | Not listed | None |
| Chrome on Android | Supported | 135 | 2025-04-01 | None |
| Samsung Internet | Not supported | Not available | Not listed | None |
How a site asks for it
| API | fetchLater(url, {activateAfter}) |
| Browser compat keys | api.Window.fetchLater |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | No |
| How long it lasts | Sent by the browser at the delay or page end; can be cancelled by the page |
| How to take it back | Clear site data, browser privacy settings |
| Inside an iframe | Not listed |
Data you get
What comes back: Deferred request
Shape: event
How often: after delay or at exit
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
activateAfter | integer | milliseconds | 0 to a page defined maximum | exact |
Technical limits
- Per-origin quota of about 64 KiB
- Only in secure contexts
- Chrome only for now
- Cookies for the target origin are sent
The story
What it is
Lets a page queue a message that the browser sends later, even if you close the page first.
For you
You never see it. A page can write a note now, and the browser sends it after a delay or when you leave. If you close the tab, it still goes out.
For makers
End of visit data is the hardest to send, since pages die without warning. fetchLater gives analytics a reliable last send, and the browser picks a safe time. It beats old tricks that slowed down pages.
Where you see it
| Type | Example | Apps |
|---|---|---|
| analytics | A web speed tool queues a report of your page load and layout shifts and sends it when you leave. | Google Analytics |
| ads | An ad network queues a report about how long an ad was visible and sends it as the tab closes. | Google Ad Manager |
| games | A browser game queues your session stats, such as time played and level reached, and sends them after you quit. | None named |
| video | A video site queues the total watch time and buffering counts, sent when you leave. | YouTube |
| shopping | A store queues the final cart state so a cart reminder can be sent even if you abandon the tab. | Shopify |
| developer | An app queues error logs from a session and sends them with the closing report to Sentry or a custom server. | Sentry |
Risks
- Data goes out after you leave
- Only in some browsers so far
What the platform says
- Google Chrome: fetchLater API. Chrome describes it as a way to queue a request that goes out later, so end of visit reports are not lost.
Good uses and abuse
Legitimate uses
- Reliable exit analytics
Known abuse
- Persistent post-leave reporting
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 3 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
History
- 2025-04, Chrome 135: Shipped as the successor to unload beacons
Related capabilities
Related
- navigator.sendBeacon. Can send a small report that the browser delivers even as you leave the page
- pagehide, visibilitychange and unload. Can tell a page when you hide or leave it, so it can send a report
Sources
How well checked: Checked against real behavior.