Five-Second Heart Rate: What Changes for HealthKit Apps

What do the new Apple Watch sensors change for HealthKit apps? Apple Watch Series 12 and Apple Watch Ultra 4 “now measure heart rate every five seconds, all day long,” and heart rate variability “as often as every five minutes,” which Apple calls “24x more frequently,” and which the release ties to a daily readiness score and two HRV variants. Apple’s releases describe what the watch measures, not what it writes to HealthKit; the HealthKit documentation index has no readiness type, and it does have one new HRV type, heartRateVariabilityRMSSD, introduced in iOS 27. So the safe assumption for September 18, when the watches ship, is a lot more heart-rate samples than any earlier watch produced, and the work is in how your app queries, aggregates, and stores them.

Apple announced the two watches on September 9, 2026, with a Health Sensing System of new optical and electrical heart sensors on both. The consumer story is readiness. The developer story is density, and Apple gave two numbers that let you plan for it.

TL;DR: Heart rate every five seconds is 17,280 readings a day if every one becomes a sample; HRV as often as every five minutes is up to 288 a day, against a previous cadence that Apple’s “24x” figure puts at about once every two hours. Apple has not said how many readings reach HealthKit or whether readiness is queryable; the current HealthKit index has no readiness identifier, and it adds a second HRV identifier, heartRateVariabilityRMSSD, that Apple has not connected to either HRV variant by name. Apps that re-read whole days, chart raw samples, or mirror samples into their own store should move to anchored queries, statistics collections, and aggregation before storage, and measure on a Series 12 the day it arrives.

What Apple said, verbatim

Three claims carry the change, and they are worth quoting rather than summarizing.

On heart rate: “With larger, power-efficient green LEDs on the optical heart sensor, Apple Watch Series 12 and Apple Watch Ultra 4 now measure heart rate every five seconds, all day long. This continuous, passive measurement delivers deeper insight into a user’s fitness and physiological state while making Exercise and Move Activity rings even more accurate.”

On HRV, the health release says it “is now measured as often as every five minutes,” which it calls “24x more frequently,” and is “available to view in a new section of the Heart Rate app”; the hardware releases say “up to 24 times more often.” And, from the Series 12 release: “Apple Watch provides two separate variants of HRV for better understanding of a user’s health status. Recovery HRV is best for identifying daily signals of stress and recovery, while overall HRV is best for insights into a user’s broader health, including cardiovascular health.”

On readiness: the health release describes “a new feature that analyzes a user’s recent activity, vitals, and sleep score, and then provides a single 0-10 score each day with a clear, actionable recommendation: Recover, Pace Yourself, Ready, or Go For It.” Both hardware releases list a fourth input, training load; the health release omits it.

The watches ship Friday, September 18, and watchOS 27 arrives for Series 9 and later, SE 3, and Ultra 2 and later on Monday, September 14.

What the old cadence was

Apple’s support page on heart rate describes the background behavior of every Apple Watch since Series 1 in one sentence: it “measures your heart rate throughout the day when you’re still, and periodically when you’re walking,” and continuously during a workout plus three minutes after. Apple does not publish the background interval. For HRV, Apple’s own “24x more frequently” against “every five minutes” puts the old cadence at roughly once every two hours, which matches my experience of the SDNN stream: a handful of samples a day, mostly overnight.

So the change is mostly not a new API. It is the same heartRate and heartRateVariabilitySDNN types, potentially carrying an order of magnitude more samples, plus one new type, heartRateVariabilityRMSSD. The iOS 27 HealthKit post covers the workout-zone and reproductive-health additions.

What reaches HealthKit is the open question

Apple’s releases are about measurement. Neither the releases nor the iOS 27 SDK documentation states, as of September 9, whether every five-second reading becomes an HKQuantitySample or whether the watch aggregates before writing. The heartRate page does carry a standing caveat that “sample data may be condensed and/or coalesced by HealthKit,” and the article it points to scopes that to first-party workouts “at least a few months old,” where HealthKit “coalesces quantities that have the same value and occurred close together” into one interval quantity, which is one more reason to read statistics rather than samples. A 24-hour count is unaffected by it; a months-old count of first-party workout samples is not. Three specific unknowns:

1. Sample density. Earlier watches already write workout heart rate at roughly one sample every five seconds; my own Watch logged 639 heart-rate samples in a 53-minute run and 870 in a 70-minute one. Background heart rate arrives every few minutes. The new part is the five-second cadence outside workouts. If Series 12 writes at its measurement rate all day, the arithmetic is 17,280 samples a day per user. If it writes background readings at the old rate and keeps the five-second data for its own algorithms, nothing changes for you. Only a device will tell.
2. The two HRV variants. HealthKit has carried one HRV identifier, heartRateVariabilitySDNN, and the iOS 27 SDK adds a second, heartRateVariabilityRMSSD, documented so far as a bare declaration with no discussion. Apple has not said whether Recovery HRV and overall HRV map onto RMSSD and SDNN, so read both types on day one and compare them with what the Heart Rate app shows.
3. Readiness. Apple describes it as a feature with a score and a recommendation. There is no readiness type in the HealthKit documentation index today, and the releases do not mention third-party access. Treat it as Apple-only until an SDK says otherwise.

What to change before September 18

None of these require the new hardware. They are the patterns that stay correct whether the density is one sample every ten minutes, 144 a day, or one every five seconds, 17,280.

Read deltas, not days. HKAnchoredObjectQuery returns only samples added or deleted since an anchor you persist, and it can stay open to receive updates. An app that re-runs a sample query over the last 24 hours on every launch is fine at a few hundred samples and painful at twenty thousand.

Chart statistics, not samples. HKStatisticsCollectionQuery returns min, max, and average per interval you choose, computed by HealthKit, and a chart of one value per five minutes reads the same whether the underlying data was one sample or sixty. Raw-sample charts were already the wrong tool for heart rate; they become unworkable at this density.

Choose background delivery deliberately. enableBackgroundDelivery(for:frequency:) takes an HKUpdateFrequency, and the system wakes your app “at most once per time period defined by the specified frequency”; .immediate wakes your app “whenever a process saves or deletes samples of the specified type,” which for watch data means each sync batch, and on watchOS the documentation says “most data types have an hourly maximum frequency” regardless. Hourly is enough for almost every non-medical use, and the anchored query picks up everything that arrived in between.

Aggregate before you store. Apps that mirror HealthKit into their own database, for offline charts or for sync, should store per-minute or per-five-minute aggregates and keep raw samples only for the windows that need them, such as a workout. The SwiftData performance post covers what happens to a store that grows by thousands of rows a day.

Cap your queries. HKSampleQuery takes a limit and sort descriptors; use both. For incremental reads, give HKAnchoredObjectQuery a limit and continue from the anchor it returns rather than paging by date.

Keep beat-to-beat separate. Denser BPM readings are not RR intervals, so do not pour them into a heartbeat series. HKHeartbeatSeriesSample already exists for beat-to-beat intervals, written with HKHeartbeatSeriesBuilder; use it for RR-interval data your app collects, and keep BPM readings, at any rate, in heartRate samples.

Where the product opening is

Readiness ships with the watches. A redesigned Health app arriving “later this year, starting in U.S. English” adds a Longevity tab, which includes Health Age and which Apple says draws on “third-party apps and devices” as well as its own data, and users “will be able to schedule and purchase” lab panels at $119 in the U.S. In my view a general fitness dashboard competes with that and loses. What Apple did not build is the specific: recovery for one sport, pacing for one condition, a coaching loop for one community, a view a clinician asked for. Denser heart-rate data makes those better, and the data your app writes back to HealthKit will feed Apple’s Longevity view when the redesigned Health app ships, which is a reason to write good samples rather than none.

The test to run on day one

On September 18, with a Series 12 on a wrist for a full day, run a sample query for heartRate over the previous 24 hours and count the results, then group them by hour and by source device. Do the same for heartRateVariabilitySDNN. Those two numbers decide whether the sections above are precautions or emergencies, and they are not in any document Apple has published.

Key Takeaways

For HealthKit developers: - Series 12 and Ultra 4 measure heart rate every five seconds and HRV as often as every five minutes; Apple has not said how much of that reaches HealthKit. - Move to anchored queries and statistics collections now; both are correct at any density. - Leave background delivery at hourly unless a feature needs faster, and aggregate before storing.

For product decisions: - Readiness and Health Age have no third-party surface in Apple’s releases or the current HealthKit index; HRV gains a second type, heartRateVariabilityRMSSD. Build on the samples, not the scores. - The opening is specificity: one sport, one condition, one community, where Apple’s general dashboard stops.

FAQ

Does HealthKit receive every five-second heart-rate reading?

Apple has not said. The releases describe measurement on the watch, not storage in HealthKit. Measure it on a Series 12 on September 18 with a 24-hour sample count.

Is the readiness score available to third-party apps?

Not in anything Apple has published. There is no readiness type in the HealthKit documentation index, and the releases do not mention third-party access.

Are Recovery HRV and overall HRV separate HealthKit types?

Unknown. HealthKit has exposed heartRateVariabilitySDNN, and the iOS 27 SDK adds heartRateVariabilityRMSSD as a bare declaration. Apple has not said which variant, if either, each one carries.

Do older watches change on watchOS 27?

Apple’s five-second and five-minute figures are specific to Series 12 and Ultra 4 and their new sensors. watchOS 27 runs on Series 9 and later, but the releases attribute the new cadence to the hardware.

Will my heart-rate charts break?

Charts built on HKStatisticsCollectionQuery will not; charts that draw raw samples will get slow and dense. Switch them before the watches ship.

Sources

1. Apple Newsroom, Introducing Apple Watch Series 12, with the all-new Health Sensing System, September 9, 2026. Quoted: the two HRV variants; HRV “up to 24 times more often”; readiness inputs including training load.
2. Apple Newsroom, Apple advances health and fitness capabilities using Apple Intelligence, September 9, 2026. Quoted: heart rate every five seconds on both watches with the Activity-rings sentence; HRV “as often as every five minutes” and “24x more frequently”; the readiness definition and the four recommendations; the redesigned Health app “later this year, starting in U.S. English”; the Longevity tab’s third-party data.
3. Apple Newsroom, Apple unveils Apple Watch Ultra 4, September 9, 2026. HRV “up to 24 times more often”; readiness inputs including training load; watchOS 27 availability on September 14; availability September 18; “will be able to schedule and purchase” lab panels at $119.
4. Apple Support, Monitor your heart rate with Apple Watch, fetched September 9, 2026. Quoted: background measurement “throughout the day when you’re still, and periodically when you’re walking”; continuous measurement during workouts and for three minutes after.
5. Apple Developer Documentation, HKAnchoredObjectQuery.
6. Apple Developer Documentation, HKStatisticsCollectionQuery.
7. Apple Developer Documentation, enableBackgroundDelivery(for:frequency:withCompletion:) and HKUpdateFrequency.
8. Apple Developer Documentation, heartRateVariabilitySDNN, heartRateVariabilityRMSSD (introduced iOS 27.0, watchOS 27.0), and heartRate, which notes “Sample data may be condensed and/or coalesced by HealthKit”; the linked article Accessing condensed workout samples scopes it to first-party workouts “at least a few months old” and describes coalescing same-value heart-rate quantities into interval quantities; the HKQuantityTypeIdentifier and HKCategoryTypeIdentifier indexes list no readiness or Health Age identifier as of September 9, 2026.
9. Apple Developer Documentation, HKSampleQuery.
10. Apple Developer Documentation, HKHeartbeatSeriesSample and HKHeartbeatSeriesBuilder.