Task scheduling (postTask, yield)
Lets a page prioritize its own tasks and yield to input so it stays responsive.
In one line
Can sort its own tasks so the page stays quick when you tap
Lets a page prioritize its own tasks and yield to input so it stays responsive.
A site can order its work and split long tasks. It cannot run when the tab is hidden any faster; it only improves smoothness inside the page.
What it can and can't do
What the user does: Nothing. It happens while the page runs and you scroll or tap.
It can
- Run important page tasks before less important ones
- Pause its own long work so taps and scrolls feel smooth
- Cancel or move its own queued tasks
It cannot
- Change what other tabs or other sites do
- Speed up the device itself
- Skip the browser's own power saving rules
- Work in Safari or on iPhone, where it is not offered yet
How it differs between platforms: Chrome and Edge and Firefox support it. Safari, including on iPhone, does not yet.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 94 | 2021-09-21 | None |
| Edge | Supported | 94 | 2021-09-24 | None |
| Firefox | Supported | 142 | 2025-08-19 | None |
| Safari | Not supported | Not available | Not listed | None |
| Safari on iPhone | Not supported | Not available | Not listed | None |
| Chrome on Android | Supported | 94 | 2021-09-21 | None |
| Samsung Internet | Supported | 17.0 | 2022-05-04 | None |
How a site asks for it
| API | scheduler.postTask(fn, {priority}); scheduler.yield(); isInputPending() |
| Browser compat keys | api.Scheduler.postTaskapi.Scheduler.yield |
| How access is granted | none |
| What the user sees | None (no browser prompt) |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| Activation | none |
| How long it lasts | None |
| How to take it back | Nothing to revoke (no permission is stored) |
| Inside an iframe | No iframe flag |
Typical flow
- Call scheduler.postTask with a priority
- Browser runs it after higher priority work
- AbortController can cancel it
Data you get
Shape: none
No individual data fields. The signal is the access itself.
Technical limits
- Priorities: user-blocking, user-visible, background
- Does not bypass background tab throttling
- Support per MDN BCD: Chrome 94 (postTask) and 129 (yield), Firefox 142, no Safari support
The story
What it is
A page can rank its own jobs so it stays responsive when you tap.
For you
You never see it. A page that uses it responds faster when you tap a button while it is still loading something else.
For makers
Makers use it to meet speed scores that affect search ranking and sales. Giving the browser room to handle taps first makes heavy pages feel quick.
Where you see it
| Type | Example | Apps |
|---|---|---|
| shopping | A busy product page loads reviews in the background so the Add to cart button answers right away. | Amazon, Shopify stores |
| games | A browser game keeps frames steady by deferring low priority work, like loading far away level pieces. | None named |
| productivity | A big web spreadsheet recalculates in small chunks so typing is not delayed. | Google Sheets |
| analytics | Measurement scripts are queued at low priority so they do not slow the page. | Google Tag Manager |
| ads | Ads load at a lower priority than the article text. | None named |
| social | A feed renders posts slice by slice as you scroll. | X, Facebook |
Risks
- Few for readers
- Unequal priority for ads
What the platform says
- Google: Optimize long tasks. Chrome's web.dev guide teaches splitting work and yielding so pages respond quickly to taps and keys.
Good uses and abuse
Legitimate uses
- INP and responsiveness work
Known abuse
- None meaningful
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 3 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
- 2021-09, Chrome 94: scheduler.postTask ships
- 2024-09, Chrome 129: scheduler.yield ships
- 2025-08, Firefox 142: Scheduler API ships
Sources
How well checked: Based on official documentation.