Explainers · Explainer
What Is the WordPress Heartbeat API? A Plain Explanation

Short answer
The WordPress Heartbeat API is a built-in polling system that lets your browser and server exchange small updates while you are logged into the dashboard. It sends a short request every 15 seconds in the post editor and every 60 seconds on the dashboard. It runs autosave, post locking, and login session checks in the background.
Key takeaways
- The Heartbeat API is a built-in polling system that exchanges small updates between browser and server.
- It ticks every 15 seconds in the post editor and every 60 seconds on the dashboard by default.
- It runs autosave, post locking, and login session checks while you are logged in.
- Each pulse is an uncacheable POST request to admin-ajax.php that uses a PHP worker.
- Throttling the interval to 60 seconds cuts editor requests to a quarter without breaking autosave.
- Disabling it completely also disables autosave and post locking, so slow it down instead.
What is the WordPress Heartbeat API?
The WordPress Heartbeat API is a built-in polling system that lets your browser and your server exchange small updates while you are logged into the dashboard.
It runs quietly in the background, sending a short request to the server every few seconds and receiving a short reply. You never see it working, but it is the reason your drafts auto-save, another editor gets warned when you are editing the same post, and your login session stays alive while you work.
The WordPress developer handbook describes it as a simple server polling API built into WordPress that allows near-real-time frontend updates (Heartbeat API). It was introduced in WordPress 3.6, and it manages session checks, auto-saving posts, and post locking, so two editors do not overwrite each other's work (Taming the Heartbeat API).
How does the Heartbeat API work?
The browser sends a timed request, called a tick, to the server, and the server sends back a JSON reply.
When a dashboard page loads, the Heartbeat script sets up an interval that runs every 15 to 120 seconds, according to the WordPress developer handbook (Heartbeat API).
On each tick, the browser gathers data, sends it to the server, and waits for a response. On the server, an admin-ajax handler takes the data, prepares a reply, and returns it in JSON format.
Each request is a POST to /wp-admin/admin-ajax.php. All WordPress AJAX requests must be sent to that file, according to the WordPress AJAX handbook (AJAX in Plugins).
Because it is a POST to the admin backend, the request bypasses page caching, and WordPress loads its core, active plugins, and theme to answer it. That is cheap for one user, but it adds up fast when many people have the dashboard open at once.
What does the Heartbeat API do for you?
It keeps three everyday features working: autosave, post locking, and login session checks.
Autosave is the one most people notice. As you edit a post, WordPress saves revisions in the background, and the default autosave interval is 60 seconds, according to the WordPress developer handbook on wp-config.php (Editing wp-config.php). If your browser crashes, the autosaved copy is there when you come back.
Post locking is the second job. When you open a post for editing, Heartbeat tells the server you hold it, so another editor who opens the same post sees a warning instead of editing over your work.
Delicious Brains notes that the API manages post locking so two editors do not accidentally overwrite each other (Taming the Heartbeat API).
The third job is session awareness. Heartbeat lets WordPress warn you before your login expires, and it lets plugins send small live updates to the dashboard without a page reload.
How often does the Heartbeat API send requests?
By default, it sends a request every 15 seconds on post edit screens and every 60 seconds on the dashboard.
The Heartbeat Control plugin page on WordPress.org states both defaults plainly: AJAX requests are sent every 15 seconds on post edit pages, and every 60 seconds on the dashboard (Heartbeat Control). The developer handbook gives the wider range the system supports, with ticks running every 15 to 120 seconds (Heartbeat API).
That means one editor with a post open sends about 240 requests per hour. Ten editors working at once send about 2,400 requests per hour, all of them uncacheable. On a small site that is rarely a problem, but on a busy site it can be the largest source of admin traffic.
| Location | Default interval | Requests per hour, one user |
|---|---|---|
| Post editor | 15 seconds | About 240 |
| Dashboard | 60 seconds | About 60 |
| Frontend (logged in) | 15 to 120 seconds | Varies by setup |
Why can the Heartbeat API slow down a site?
Each pulse uses a PHP worker, and too many pulses at once can leave too few workers for visitors.
Delicious Brains explains that every pulse requires a dedicated PHP worker to process, and that 50 users with the dashboard open can generate hundreds of uncacheable requests per minute (Taming the Heartbeat API).
PHP workers are the processes that run your site's PHP code, so when Heartbeat occupies them, fewer are left to serve real visitors.
The Heartbeat Control plugin page warns of the same effect in plainer terms: if you leave your WordPress admin open for long periods, the AJAX requests can pile up and generate high CPU usage, leading to server performance issues and even hosting account suspensions (Heartbeat Control).
The symptom is easy to spot in server logs. If your access log is full of repeated POST requests to /wp-admin/admin-ajax.php with the action heartbeat, the API is the likely cause, as Delicious Brains notes (Taming the Heartbeat API).
A slow admin dashboard has many possible causes, and Heartbeat is one of the first to check.
How do you slow down the Heartbeat API?
Change the interval with the heartbeat_settings filter, or use a plugin that offers the same control.
The developer handbook documents the filter, and Delicious Brains shows the standard example: set $settings['interval'] to 60 to stretch the editor pulse from 15 seconds to 60 seconds (Taming the Heartbeat API). That single change cuts editor requests to a quarter of their default rate, while autosave and post locking keep working.
If you prefer no code, the Heartbeat Control plugin adds settings under “Settings > Heartbeat Control” where you can set rules per location: dashboard, frontend, or post editor (Heartbeat Control). A 60-second interval in the editor is a common choice, and it matches the dashboard default.
How do you check if Heartbeat is the problem?
Open your browser developer tools on a dashboard page and watch the Network tab.
Filter the list by admin-ajax and leave the tab open for a minute. On a post edit screen you should see a new heartbeat request about every 15 seconds, and on the dashboard about every 60 seconds.
If the requests appear far more often than that, a plugin may be adding its own Heartbeat calls on top of the default ones.
The server access log gives the same answer for the whole site. Search it for POST requests to /wp-admin/admin-ajax.php with the action heartbeat, as Delicious Brains recommends (Taming the Heartbeat API).
Count them over an hour and compare with the number of logged-in users. If the count is far higher than the defaults explain, throttling the interval or disabling Heartbeat on the frontend is a reasonable next step.
If the count is low, the slowdown lies elsewhere, and fixing high CPU usage is the better place to look.
Should you disable the Heartbeat API completely?
No, because disabling it breaks autosave and post locking, so slow it down instead.
Delicious Brains warns against disabling the API entirely, since doing so would break useful features like auto-save, and recommends throttling the interval instead (Taming the Heartbeat API). The one place where disabling is usually safe is the frontend for logged-out visitors, where Heartbeat serves no purpose.
You can stop the script on the frontend with a small code snippet that deregisters the heartbeat script outside the admin area, as shown in the same Delicious Brains guide (Taming the Heartbeat API). Keep it running in the editor and on the dashboard, where its features matter.
If your site still feels slow after throttling Heartbeat, the cause is probably elsewhere. Our guide to how to speed up WordPress covers caching and other fixes.
Start with the server-side checks for high CPU usage before you change anything else.
What mistakes should you avoid?
The most common mistakes are disabling Heartbeat everywhere, setting the interval too low, and blaming it for problems it did not cause.
Do not set the interval below 15 seconds. The handbook range starts at 15 seconds, and shorter intervals only add load without helping autosave or locking. Do not disable Heartbeat in the editor to save CPU, because you will lose autosave and post locking, and a lost draft costs more than the CPU you saved.
Finally, do not assume Heartbeat is the cause of every slow dashboard. Check the access log for repeated heartbeat requests first. If they are rare, look at plugins, cron jobs, and PHP workers instead.
A stuck cron job can look like a Heartbeat problem, so check our guide to fixing WP-Cron not running if scheduled tasks are failing too.
Frequently asked questions
Is the Heartbeat API part of WordPress core?
Yes, it is part of WordPress core since version 3.6, so there is nothing to install. It runs whenever you are logged into the dashboard, and plugins can use it to send their own small updates. You only need a plugin or code if you want to change how often it runs.
How do I reduce Heartbeat API load without breaking autosave?
Slow it down instead of turning it off. Set the interval to 60 seconds with the heartbeat_settings filter or a control plugin, and disable it on the frontend for logged-out visitors. Turning it off everywhere also turns off autosave and post locking.
Does the Heartbeat API slow down my site?
Each pulse is a small POST request to admin-ajax.php, so it adds load on every logged-in tab. One editor is trivial, but 50 users with the dashboard open can generate hundreds of uncacheable requests per minute. Throttle the interval to 60 seconds to cut editor requests to a quarter.
What is the difference between the Heartbeat API and WP-Cron?
They are different jobs. The Heartbeat API sends regular small requests from the browser while you are logged in. WP-Cron runs scheduled tasks, such as publishing scheduled posts, in the background. Both use admin-ajax.php or wp-cron.php, but they serve different purposes.
How can I see Heartbeat requests on my site?
Open your browser developer tools on a dashboard page, go to the Network tab, and filter by admin-ajax. You will see a heartbeat request about every 15 seconds in the editor and every 60 seconds on the dashboard. Your server access log shows the same requests for all logged-in users.
Sources
- Heartbeat API WordPress Developer Resources
- Heartbeat Control WordPress.org
- Taming the Heartbeat API: Preventing admin-ajax.php Overload Delicious Brains
- Editing wp-config.php WordPress Developer Resources
- AJAX in Plugins WordPress Codex
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


