Google Research unveils SensorFM: trained on a trillion minutes of wearable data, wins 33 of 35 health tasks

Pretrained on 5 million people, 2 billion hours of wearable data — a frozen encoder with a single linear head beats supervised baselines on 34 of 35 health tasks.
By Google Research07-10 · 8 min read⚑ Research paper
🎧 Listen to the podcast0:00 / --:--
0:00 / --:--
Research Explainer · XiaoHu Explains
60-Second Rundown
  • Google Research has released SensorFM, a health foundation model pretrained on over a trillion minutes of wearable sensor data, detailed in a paper at arXiv:2605.22759.
  • The training data comes from 5 million consenting users, spanning over 100 countries and all 50 U.S. states, covering 20+ Fitbit and Pixel Watch device models, from September 2024 to September 2025.
  • In scaling experiments spanning four orders of magnitude, the largest model, SensorFM-B, won 33 of 35 health prediction tasks; freezing the encoder and attaching just a linear head still beat traditional feature-engineering-plus-supervised-learning baselines on 34 of 35 tasks.
  • The core technique is AIM (Adaptive Inheritance Masking): it treats data genuinely dropped by the device and data artificially masked during training as the same problem, so the model is inherently built to handle incomplete information.
  • In a blinded clinician evaluation using a personal health agent, health summaries generated from SensorFM predictions scored no statistically significant difference from summaries generated using real medical measurements.
⚑ This is Google Research's own official blog post introducing its own model, SensorFM. The data scale, task win rates, and blind-test conclusions below all come from Google's official account and its paper, and have not yet been independently reproduced by a third party.
1Background

Wearables have piled up a decade of data, most of it never really put to use

Over the past decade, watches and wristbands have logged massive amounts of heart rate, blood oxygen, sleep, and activity data. Yet most of this data just sits dormant on the device, or gets used for one narrow purpose: counting today's steps, checking how well you slept. Getting it to actually predict health risk runs into three walls with the traditional approach.

Dilemma 01

One task, one model

Want to predict diabetes? Train a dedicated diabetes model. Want to predict depression? Train a separate depression model. Each model needs its own set of labeled data, and knowledge doesn't transfer between them.

Dilemma 02

Labels are expensive and hard to get

A health label (say, "this person has been diagnosed with diabetes") sits behind medical exams, lab work, and diagnosis — slow and costly. Many labels simply can't be retrieved retroactively; you can't send someone back three years to get a checkup redone.

Dilemma 03

Individual variation is huge

The exact same heart-rate trace can be perfectly normal in one person and a risk signal in another. A one-size-fits-all model can't handle that kind of person-to-person difference.

2Enter

Google Research's answer: SensorFM

On July 9, 2026, Google Research published a blog post introducing SensorFM, a foundation model for wearable health data, with the corresponding paper on arXiv (number 2605.22759).

It aims to use a single, unified model to make sense of the body's various physiological signals, then transfer that capability across dozens of health prediction tasks — from cardiovascular to metabolic, from sleep to mental health. It's built to tear down exactly the three walls from the previous section.
💡
This is the largest dataset ever used to train a wearable health model: over a trillion minutes, 5 million people. The largest model won 33 of 35 health prediction tasks; freezing the encoder and adding just a linear head still beats traditional feature-engineering-plus-supervised-learning on 34/35 tasks.
Here's an analogy

Just as GPT learned the general patterns of language from a mountain of text, SensorFM learns the general patterns of human physiology from over a trillion minutes of sensor data. It first learns a general-purpose base, then attaches different specific tasks on top.

3Training data

What it was fed: a trillion minutes of body data

First, let's look at just how much data it consumed. This dataset comes from 5 million consenting users, spanning September 2024 to September 2025, covering over 100 countries including all 50 U.S. states.

5 millionusers who consented to provide data
100+ countriescoverage, including all 50 U.S. states
20+ modelsFitbit and Pixel Watch devices
2 billion hoursweeks of signal per person, summed
1 trillion minutestotal signal duration at minute-level resolution

This is by far the largest and most diverse batch of wearable data ever used to train a model. It brings together 34 per-minute aggregated features from five kinds of sensors.

SensorAbbreviationWhat it measures
PhotoplethysmographyPPGheart rate, heart rate variability, blood oxygen saturation
AccelerometerAccelerometrymotion, step count
Electrodermal activityEDAskin conductance (stress response)
Skin temperatureSkin Tempbody temperature changes
AltimeterAltimetryaltitude / elevation gain

Two of these abbreviations are worth explaining. PPG (photoplethysmography) is how a watch shines light against your skin and infers heartbeat and blood oxygen from how blood vessels absorb the changing light — this is also the main principle behind how smartwatches measure heart rate. EDA (electrodermal activity) measures conductance on the skin's surface; when a person gets nervous and sweats, conductance changes, so it's often used as an indirect signal of stress and emotion.

4Core innovation · AIM

Watches drop out — how the model learns not to sweat it

One of SensorFM's most crucial design choices is how it handles "incomplete data." Watches get taken off to charge, go into power-saving mode, and sensors switch on and off. For wearable data, incompleteness is the norm, not the exception.

Core Innovation · AIM

There were two old approaches to handling incomplete data: guessing to fill in the gaps, but the guessed values can be wrong and introduce bias; or simply discarding incomplete time windows, which wastes a lot of valuable data. SensorFM takes a third path, AIM (Adaptive Inheritance Masking): it treats data genuinely dropped by the device and data artificially masked during training as the same thing, so the model is inherently used to incomplete information, learning to treat "missingness" itself as something it must learn to fill in.

Old approach

Fill in the gaps, and a wrong guess introduces bias; discard incomplete windows, and you waste data. The premise is "data must be complete."

AIM's approach

Real missingness and artificial masking are treated the same way, and filling in the missing parts becomes the training task itself. The premise is "incompleteness is normal to begin with."

Two kinds of missingness, one treatment Real missingness device removed / power-saving Artificial masking deliberately masked in training
Same heart-rate waveform: the gray block is data genuinely dropped by the device, the hatched block is data deliberately masked during training. AIM treats both as the same thing, letting the model reconstruct the masked portion (the flashing red line) back to complete.
Here's an analogy

It's a bit like training a person to infer missed words from context on a bad phone connection, instead of requiring the signal to be full bars before they'll even try to listen. AIM gets the model used to reconstructing the full meaning even when it "can't hear everything."

Trained this way, SensorFM is inherently "missingness-aware": it not only tolerates incomplete data, it can actually use the incompleteness to learn.

SensorFM missingness-aware masked reconstruction pretraining diagram
SensorFM is pretrained on over a trillion minutes of multimodal sensor data through "missingness-aware masked reconstruction." Source: Google Research
5Scaling effects

Scale it up, and performance keeps climbing — with no ceiling in sight

What happens when you scale up data and model size together? Google ran a set of experiments spanning four orders of magnitude: data volume from 2 million to 2 billion sensor-hours, model size from 100K to 100M parameters.

-31%
reduction in reconstruction loss, largest model vs. smallest
+9%
improvement in average AUC on classification tasks
+21%
improvement in Pearson correlation on regression tasks
33/35
tasks won by the largest model, SensorFM-B

Pretraining loss falls steadily as data and model size grow, winning 33 of 35 tasks. More importantly: the performance curve shows no sign of saturating — meaning more data and more parameters will very likely make it even stronger.

Two metrics worth explaining here. AUC measures how accurate a classification judgment is (0.5 is equivalent to a coin flip, 1 is a perfect judgment); Pearson correlation measures how closely predicted values track real values (ranging from -1 to 1, with values closer to 1 meaning tighter tracking).

SensorFM scaling experiment curves
Scaling data volume and model capacity together by orders of magnitude, both pretraining and downstream task performance keep climbing, with no sign of saturation. Source: Google Research
6Transfer capability

Freeze the model, attach a linear head, and it's already good enough

There's an easy way to test whether a model's learned representation is actually useful: freeze the model itself with not a single parameter changed, attach a simple linear head (called a linear probe) onto its output physiological representation, and see if it can directly get the job done.

Frozen SensorFM encoder
→
Physiological representation
→
Linear head (only this layer is trained)
→
Health prediction

Tested on 35 discriminative health tasks (data from 3 IRB-approved prospective studies, 13,985 participants total), spanning six major categories of health signals.

Cardiovascular health Metabolic risk Mental health Sleep Demographics Lifestyle

34 of 35 tasks beat the traditional baseline (each dot is one task; the hollow one is the sole task not won):

Training only that lightweight linear head beat the "feature-engineering-plus-supervised-learning" traditional baseline on 34 tasks. Two more details worth noting: the larger the model, the better it implicitly captures demographic features like age and gender on its own (so the added benefit of separately feeding in that information keeps shrinking); and for conditions like depression and anxiety, whose signals are notoriously faint and hard to measure through sensors, it also picks up on them — beating the baseline with only a small number of labeled samples.

This means the same physiological representation can transfer across dozens of health prediction tasks, dramatically compressing the labeled data and development time needed to adapt to a new task.

SensorFM linear probe downstream task performance gains
Adding just a linear probe on top of the frozen SensorFM representation, relative performance gains over baseline across various discriminative health tasks. Source: Google Research
7Core innovation · Agentic classroom

A room full of AI agents, racing to build it a prediction head

Turning a physiological representation into a predictor for a specific task traditionally requires manual feature engineering, architecture selection, and hyperparameter tuning — tedious work. Google simply had AI do this itself.

Core Innovation · Agentic Classroom

They built a "multi-agent collaborative classroom" (agentic classroom): a group of AI agents that collaborate and compete with each other, repeatedly generating, testing, and improving executable code to build prediction heads. The whole system searched through over 30,000 candidate solutions.

Generate prediction-head code
→
Automated testing and scoring
→
Collaborate, compete, improve
↻
Converge on better solutions
A group of AI agents repeats this loop, cumulatively searching through more than 30,000 candidate solutions.
16/20
classification tasks where the agent-designed head beat the simple linear probe
12/15
regression tasks where the agent-designed head beat the simple linear probe

Two more patterns: solution quality improved monotonically as the search progressed; and switching to a stronger AI model (like a newer version of Gemini) produced better solutions.

AI agent classroom iteratively writing code to build prediction heads
AI agents in a "classroom" repeatedly write, test, and improve code to build prediction heads for SensorFM representations, with solutions steadily improving over time. Source: Google Research
8Blind-test validation

Doctors couldn't tell AI's guess from real checkup results

Finally, Google put SensorFM into a "Personal Health Agent" and ran a tightly designed experiment: having it generate health summaries, then comparing quality across three input conditions.

Condition 1 · Baseline

Demographics + daily metrics

Summaries generated using only basic information and daily wearable data. Trailed across the board on all five dimensions.

Condition 2 · SensorFM

Plus SensorFM predictions

On top of the baseline, adding in the model's inferred health metrics. Scored higher than baseline on every dimension.

Condition 3 · Ceiling reference

Plus real measurements

On top of the baseline, adding in real medical measurements (ground truth), used as a ceiling reference for comparison.

Baseline < SensorFM predictions ≈ real measurements
≈ means clinician scores showed no statistically significant difference

How it worked: a panel of clinicians, under blind conditions, scored the summaries across five dimensions — context, relevance, plausibility, personalization, and potential harm — producing 1,860 expert ratings in total, consuming over 40 hours of expert evaluation time.

1,860
total expert ratings from the blinded clinician evaluation
40+ hours
expert evaluation time invested

Two conclusions: adding SensorFM predictions raised scores above baseline on all five dimensions; and more importantly, clinician scores for summaries using SensorFM predictions versus real measurements showed no statistically significant difference. In other words, in this health-assistant scenario, the model's inferences are almost as useful as actual medical measurements.

SensorFM as a personal health agent tool improving answer quality
Clinician ratings of generated responses improve after adding SensorFM as a tool for the personal health agent. Source: Google Research
9Limitations

What's still missing: privacy, clinical validation, and the correlation trap

Beyond these results, a few things need to be said clearly.

Privacy

How do you keep 5 million people's health data secure? Google emphasizes that the data used is "consented" and "de-identified," but privacy for health data at this scale is always something to keep an eye on.

Clinical validation

Currently still at the research stage — rigorous clinical trials still stand between this and actual deployment in medical applications.

Accessibility

It depends on devices like Fitbit and Pixel Watch, so anyone who can't afford or doesn't use them is locked out — a digital divide.

Correlation isn't causation

What the model learns is correlation between signals, which is useful for prediction, but doesn't mean it can explain the underlying causation.

Freezing the encoder and training only a lightweight linear head still beat traditional feature-engineering-plus-supervised-learning on 34 of 35 health tasks. Google Research · SensorFM
This article was compiled by XiaoHu Explainer based on Google Research's official blog post "SensorFM: Towards a general intelligence and interface for wearable health data" (published July 9, 2026, corresponding paper arXiv:2605.22759). All data scale, task win-rate, and blind-test figures in this article come from Google's official account and its paper, and have not yet been independently reproduced by a third party. Image credit: Google Research.
Source
Google ResearchGoogle Research·Read the source
↑ End of article
✓ This article is free to read in full

Members can copy or download the full Markdown, and let their AI subscribe and ask.

Read the original ↗
📮 New explainers, straight to your inbox

Found this useful? Leave your email — every new explainer, the moment it's out. Unsubscribe anytime.