Withings Now Charges $99.50 a Year to Use Your Own Data in Apple Health

The Charge

At 00:00 UTC on 13 October 2026, Withings made automatic export of health data to third-party apps a Withings+ feature for every account created from that moment on. There was no press release, no blog post, no email. The change surfaced as a banner on the developer site, a disclaimer pasted into its partner-app support articles, and a paywall screen that new buyers hit during scale setup, in Frandroid's words, before the first synced weigh-in.

A note on the date, because Withings' own materials do not state it consistently. The developer site's headline says the requirement applies "from October 12, 2026," while the same page's footnote says it applies to accounts "created after October 12"; the Apple Health support article says accounts created "on or after" 13 October; two other support articles say "after October 13th"; the staff reply says "from October 13." Every source agrees that accounts from 12 October or earlier are exempt. The status of an account created on 13 October itself is stated inconsistently. This article uses 13 October, the date Withings gives for the change going live at 00:00 UTC, and does not pretend Withings has reconciled its wording.

Here is what Withings has actually done, stated narrowly so that it cannot be waved away.

What changed

Withings' support articles for Apple Health, Health Connect, MyFitnessPal, Runkeeper and Samsung Health now carry the same disclaimer: changes to the API and "new privacy measures" took effect 13 October 2026, and users need an active Withings+ subscription to export Withings data to third-party apps if they create an account on or after that date. The developer site goes further: Withings+ is now required on the free API plan, so accounts created after the cutoff need a membership to share data with any free-plan app, "including apps that are already live." That sweeps in Strava, MyFitnessPal, Runkeeper and every small developer who built on the public API.

Who pays

Accounts created from 13 October 2026. The official staff reply in Withings' own community forum, signed "Team Withings" on 15 October, puts it plainly: for those accounts, "automatic sync to third-party apps is part of Withings+" (staff reply).

Who does not

Anyone whose account existed on or before 12 October. The grandfathering is tied to the account, not the device: buying a new scale or watch later "won't affect it. Your sync stays free." The support disclaimer says such accounts "will never need to worry about this change." No terms-and-conditions clause backs that promise; the Withings+ T&Cs reserve the right to change plans and prices at any time.

The price

$9.95 a month or $99.50 a year in the US; €9.95 / €99.50 in the eurozone; £8.95 / £89.50 in the UK (Withings+ page, subscription article). Devices bought on the Withings web store include one free month; subscribing in-app gives two weeks.

What stays free

This matters, and CHI states it fully. Without Withings+, a new customer can still see every measurement and trend in the Withings app; export the full history as CSV or PDF at any time; import data from other apps into Withings; and share data with a doctor through HealthLink and PDF reports (export article). Withings does not hold the data hostage. It holds the pipe.

When you stop paying

Nothing is deleted. If a membership ends, sync pauses, no data is lost, and sync resumes as soon as the membership is active again. No hardware capability is removed. No software is uninstalled. A gate closes.

The sentence that convicts. The same staff reply explains the purpose of the fee: Withings+ "funds the services around your data, while your data itself stays yours."

Read that sentence twice. Withings is not claiming the data is theirs. It is claiming the right to charge rent on the space around the data, and it has defined "around" to include the act of the data leaving.

Count ICharging for the Gate

There are two ways a company can take more money from a customer. It can make something new and sell it. Or it can find something the customer already does, stand in the path, and charge for stepping aside. The first is value creation. The second is friction monetization. They look identical on an invoice. They are not identical in substance, and the difference is the whole of this case.

Before 13 October, a Withings customer who wanted their weight in Apple Health did this: opened the Withings app, toggled a switch, and granted permission. From then on, the app wrote each new measurement into the iPhone's Health store. Withings has identified nothing about that step that became harder, rarer, or more expensive to perform on 13 October. The toggle is the same toggle. The write is the same write. What changed is that for a new account, the toggle now sits behind a subscription screen.

So ask the only question that matters: what did Withings create?

Not the measurement; the customer's body did that. Not the hardware; the customer bought that. Not the destination; Apple and Google built HealthKit and Health Connect, and neither platform's published documentation identifies any fee for writing to them beyond the standard $99-a-year Apple Developer Program and the $25 one-time Google Play registration (Apple, Google). Not the integration itself; Withings wrote it years ago, and told Google's developer blog in March 2023 that moving to Health Connect cut its third-party sync code by 50% and was, in its own engineer's words, "a powerful, interesting, and easy tool to use" (Android Developers Blog).

What Withings created on 13 October is a condition. The gate existed before; the meter is new.

This is the structural signature of a toll. A toll is not priced by what it costs to open the barrier. It is priced by what the traveler will pay to get through.

Withings' own terms of use, re-dated to 13 October 2026, make the mechanism explicit. Section 6.4 defines "sharing" to include transfers made through "a mechanism specific to your phone's operating system." Section 6.4.1: "Sharing with third-party services requires that you have a valid Withings+ subscription," with a carve-out that "certain types of sharing" may be exempt, which Withings does not enumerate (Terms of Use). Read with the developer FAQ, which answers the question "Can my users share through Apple Health or Google Health instead?" with "No. The requirement covers those routes too" (API plans page), the picture is complete. CHI makes no claim about what was said in the room. It does not need to. Whatever Withings' internal reasoning, the economic effect of the rule is plain on the face of the documents: leaving the operating-system route open would have let new customers keep moving their data without Withings+. Closing it makes the subscription necessary. The same FAQ tells partners that integrating "on Enterprise is the only way to guarantee your users can share data without their own membership."

A rule whose function is to make the membership unavoidable is a gate, whatever it was called when it was built.

Count II"Your Data Is Yours," With Conditions

Withings says the data is yours. CHI takes it at its word, and then asks what the word is worth.

In one sense Withings is telling the truth. You can open the app and look at every reading. You can request a CSV of your entire history and have it emailed to you. You can download a PDF. You can give a doctor a HealthLink. Withings' digital product lead told Numerama: "L'exportation de données via CSV, PDF, Health Link, c'est gratuit. Tout ça, c'est la loi" (exporting data via CSV, PDF, HealthLink is free; all of that is the law) (Numerama interview).

Note the framing. The free paths are free because the law requires them to be. The automated routes the law does not clearly require are the routes Withings has priced.

Now consider what a CSV actually is to the person who owns the scale. It is a snapshot, produced on request, by hand, after the fact. It does not know you weighed yourself this morning. Apple Health and Health Connect are not filing cabinets for snapshots; they are live ledgers that other things read from: a doctor's app, a nutrition tracker, a trend line that only means something if it is continuous. DC Rainmaker, who has reviewed scales for fifteen years, calls the CSV route a weak substitute for the simple reason that there is no standard weight-import format to carry it into (DC Rainmaker).

CHI does not overstate this. A customer with a CSV is not locked in. What they cannot do, without paying, is have their data behave like data: move on its own, in machine form, to the place they chose. Withings has split ownership into two tiers. The right to possess a copy is free. The right to have the thing you own participate in the world is $99.50 a year.

That is a real form of ownership. It is also a diminished one. It is ownership in the way that owning a car you may only drive off the lot on a trailer is ownership.

Withings has written the split directly into its terms. Section 6.4.1 says the subscription requirement "does not affect your right to data portability, which is not considered sharing with a third-party service" (Terms of Use). That sentence is doing careful work. It defines portability as the thing the law protects, defines sharing as the thing Withings sells, and draws the line between them exactly where the money is. Writing a reading into the Health store on your own phone, through a mechanism Apple provides for precisely that purpose, is on the paid side of the line.

If the data is mine, why does leaving require rent?

Not access. Not a copy. Leaving, in the ordinary, automated sense in which the other scales on the shelf do it. Withings' honest answer, from its own staff reply, is that the membership "funds the services around your data." Fine. Then the sync is a service around the data, and the customer is being charged for the perimeter of a thing Withings concedes it does not own.

Count IIIThe $99.50 Question

Where does the $99.50 go? CHI tried to find out. Withings has published no cost figure, no architecture description, and no explanation that ties the price to the function. So we did the work for them.

How the sync actually works

Apple's HealthKit is an on-device framework. The iPhone stores all HealthKit data locally; an app saves a reading by calling a local save method on the Health store; Apple publishes no server-side API through which a third party can write into a user's Health store, and cross-device movement happens through the user's own iCloud backup (Apple: protecting user privacy, saving data to HealthKit). Google's Health Connect is the same shape: an on-device store written through a local insertRecords call, "device-centric" with "no OAuth required" (Android: Fit migration guide, migration FAQ).

Withings' own support pages confirm that its Apple Health write happens in the app, on the phone: "due to an iOS restriction" the sync is not fully automatic, and users are told to open the Withings app, open Apple Health, and pull to refresh (Withings support). That is a local write bounded by iOS, not a Withings cloud pipeline. Withings publishes no architecture description, so CHI states only what its documents show: for its Wi-Fi scales and blood-pressure monitors the measurement travels to Withings' servers first (the support article tells users to confirm the data "has been properly synced with the servers" before troubleshooting Apple Health), and it does that whether or not you ever touch Apple Health, because that is how the app gets the number at all.

What it costs to be let in, and what it cost to build

Neither platform publishes any HealthKit or Health Connect fee beyond the company-wide developer registrations already noted. And Withings told Google in 2023 that adopting Health Connect halved its sync code and replaced the "onerous" work of maintaining per-app APIs (Android Developers Blog). The OS-level routes are, by Withings' own account, the cheap ones.

What Withings says the money is for

Three things, none of which is the marginal cost of the sync. The support disclaimer attributes the change to the Withings AI Connector, an MCP server letting AI assistants query Withings data, which "required changes to our API and new privacy measures" (AI Connector FAQ). The developer plans page says Withings+ "funds the clinical validation, regulatory clearances and infrastructure behind the data you consume" (API plans page). And Vincent Brand, Withings' digital product lead ("chef de produit digital"), told Numerama that applications such as ChatGPT Health and Bevel were exploiting Withings data for free: "Nous, on prend des risques pendant trois ans en R&D. Tout est simple pour eux" (we take three years of R&D risk; everything is simple for them). What made Withings' value yesterday was hardware and clinical studies; "Aujourd'hui, la valeur, c'est la donnée" (today, the value is the data) (Numerama; CHI's translations).

The first two are fixed-cost rationales: validation, clearances, infrastructure, an API rebuild. Real costs, all of them, and all borne whether or not any given customer ever enables Apple Health; Withings carries them for the grandfathered accounts it syncs for free. The third is a value-capture rationale, and it is the candid one. Withings is not saying "the gate is expensive to keep open." It is saying "the data on the other side of the gate is valuable, and others were taking it." The customer, whose body made the data, is the party being asked to pay.

Hold the rationales apart, because Withings' statements slide between them. A cost rationale says: this function costs us X per user, and the price recovers it. Withings has given no X. A value-capture rationale says: others profit from this data, so we will charge for access to it. Withings said that, in those terms, to Numerama. And if AI companies are the free riders, why is the consumer being billed? Withings already operates the targeted instrument for that problem. Its Enterprise plan, priced "based on number of active users" and paid by the partner, lifts the end user's membership requirement "for specific use cases" named in the partner's agreement (API plans page). A company that wanted AI firms to pay for the data had a contract ready to make them. It chose to bill the person on the scale as well.

To be exact: CHI does not say synchronization costs Withings nothing. Withings runs a cloud; the scale talks to it; that costs money. But the cloud leg exists for every user, subscriber or not, because it is how the app gets the reading at all. The step Withings has priced is the one after it: the app writing a value it already holds into a local store on the phone, through a free platform API. Withings has shown no marginal cost for that step that bears any plausible relationship to $99.50 a year.

The arithmetic

Withings+ at $99.50 a year, against Withings' own US list prices on 20 October 2026 (scales, watches, blood pressure):

Cumulative: $199 after two years, $298.50 after three, $497.50 after five, $995 after ten. In the eurozone, where Withings+ is €99.50 and the Body Smart is €99.95, the first year of subscription costs within fifty cents of the scale itself, and the second month of the second year takes it past the hardware price.

A customer who buys the entry-level scale and keeps it for a decade pays Withings nearly eight times the hardware price to have the readings appear in the Health app that came free with their phone. If they never open the AI assistant, they will have received no additional product. They will have paid for the gate alone.

If Withings has a figure that shows the opposite, a per-user annual marginal cost of HealthKit and Health Connect sync that approaches $99.50, or even $9.95, CHI will print it. It has not been offered, and the architecture makes it implausible.

Count IVThe Grandfathering Problem

Two people stand on two identical Body Smart scales on the morning of 20 October 2026. Both scales send the reading to Withings' servers. Both Withings apps are set to export to Apple Health. For the person whose account was opened on 12 October, the reading appears in Apple Health for free, on Withings' word indefinitely, and will keep doing so for every Withings device they ever buy. For the person whose account was opened on 13 October, the reading stops at a paywall.

Same scale. Same app. Same code. Same servers. Same destination. Two prices: zero, and $99.50 a year.

CHI is careful here. Grandfathering does not prove that the sync costs nothing. A company can absorb a cost for an installed base as goodwill, and Withings deserves credit for not pulling the function from people who bought on the old terms. Several customers in Withings' forum said as much.

But grandfathering does establish something, and it does serious damage to any cost-based defense.

If automatic sync carried an unavoidable recurring cost large enough to justify $99.50 a year (servers, API maintenance, privacy infrastructure, compliance), then Withings has just committed to carrying that cost, uncapped and open-ended, for its entire existing user base, including on devices they have not yet bought. The support disclaimer says those accounts "will never need to worry about this change." The staff reply says the exemption follows the account, not the hardware, so a grandfathered customer who buys a BodyScan 2 in 2030 syncs it free.

A company can absorb a real legacy cost for good reasons: reputation, retention, the risk of a retroactive-change lawsuit. So grandfathering does not prove the function is free. What it shows is narrower and sufficient. Whatever synchronization costs Withings, Withings has demonstrated that it regards that cost as absorbable at the scale of its whole installed base, indefinitely, with no cap and no opt-out. That makes it very hard to argue that $99.50 reflects the marginal economics of the function. A cost a company will carry for its entire existing installed base, indefinitely, is not a cost it needs $99.50 a year from each new customer to cover.

The explanation that fits the two prices is the one Withings' product lead gave Numerama: the new price is not about cost, it is about value, specifically the value of data now that AI tools can interpret it. On that account, existing customers were excused not because their data is cheaper to move but because charging them would have been a retroactive breach of the terms they bought on. New customers, by definition, had not bought under the previous terms and therefore could be presented with the new proposition prospectively.

That is price discrimination by acquisition date against a function that is identical on both sides of the line. It is also an admission of sorts. A company that believed sync was a $99.50 product on its own merits would at least try to sell it to the users it is now giving it to for free.

Count VBundling Value With Captivity

Let CHI be unambiguous about what is legitimate in Withings+.

A board-certified cardiologist reviewing your ECG within 24 hours is a product. An AI assistant that remembers your profile and builds a plan is a product. Heart Age, Readiness and Glucose Resilience scores are products: algorithms Withings designed, running on Withings' compute, producing something that did not exist before. Discounted access to Sunrise, Fay and Dune clinicians is a product. An MCP server that lets ChatGPT or Claude query your health history is, arguably, the most interesting product Withings has shipped in years. Withings is entitled to price every one of these, and $99.50 a year for the bundle is not, on its face, outrageous.

The question is why automatic sync is in the box.

It is not there because it belongs with the others. Without it, the other Withings+ features would have to sell themselves on their own merits. Adding a function most buyers treat as a baseline changes that proposition: the baseline carries the bundle. The customer who wants only interoperability must buy the cardiologist too.

That is not ordinary bundling. It is leverage: a baseline function customers already expect, placed behind the same door as services they may never use.

Is this normal?

CHI checked ten comparators against their own documentation, and dropped four others (Samsung, Amazfit, Renpho, Eight Sleep) whose official pages left a cell ambiguous. The answer is no.

Of the ten, one, Oura, also requires a membership for Apple Health sync. But Oura gates almost its entire app and launched that model with new hardware in 2021; it did not sell a free sync and then remove it. WHOOP has no free tier, so sync is simply part of a membership you cannot avoid. Every company CHI checked that, like Withings, sells hardware with a free app and an optional premium tier (Garmin, Google, Polar, Omron) leaves the OS-level sync on the free side, as do the four with no paid tier at all (Eufy, Xiaomi, COROS, Ultrahuman). Garmin's Connect+ press release promised existing features would stay free. Omron, whose blood-pressure monitors compete directly with BPM Connect, lists Apple Health and Health Connect connection as a feature of the free tier. A $30 iHealth scale syncs to Apple Health free (AppleInsider); so do a $20 Etekcity scale and a $34 travel scale (DC Rainmaker).

Subscriptions are not unusual in this market. Charging specifically for OS-level health-data synchronization inside an otherwise free app tier is. Among the ten companies CHI checked, Withings is the only one that has taken a previously free Apple Health / Health Connect sync on outright-sold hardware and moved it behind a membership. CHI found no earlier instance in the consumer health-hardware market, and does not claim to have searched every company that has ever existed. Numerama reports that Withings itself acknowledges being the first connected-device maker to take this step (Numerama); CHI has not seen that acknowledgment in Withings' own words.

What Withings used to say

For a decade, interoperability was part of how Withings sold the hardware. Archived product pages, all first-party:

• BPM Connect, May 2021: "Works with Apple Health," with the line "Syncs seamlessly with Apple Health to export or import your blood pressure & heart rate data." The same page, under the separate heading "Free data storage," promised "full control of your data, at no extra cost—forever"; that promise concerned storage, not sync, and CHI does not read it as more (archive).
• Body+, June 2022: "Connect with 100+ apps" (archive).
• Body Smart, June 2023: can "easily be connected to Apple Watch, Apple Health, Google Fit"; Withings+ described only as analysis and guidance (archive).
• ScanWatch 2, June 2024: spec sheet lists "Apple Health, Google Health Connect & Google Fit compatible" (archive).
• Body Scan, March 2025: "Your data, in your hands" (archive).
• Body Smart, July 2026, three months before the change: still "connected to Apple Watch, Apple Health, Health Connect" (archive).

Withings' Withings+ FAQ, still live, says: "All the rest of the app (what we already have) will remain free for our users" (Withings+ FAQ). Its June 2025 press release for Withings Intelligence said the core health-tracking experience "remains free and fully accessible to all users" (press release, PDF). The App Store listing, today, invites you to "connect your health apps like Apple Health, Strava, MyFitnessPal" (App Store).

The redesigned product pages on withings.com, as of 20 October, no longer mention Apple Health or Health Connect at all; they say access to baseline metrics "remains free within the Withings app." CHI cannot say whether the compatibility claims were removed deliberately or lost in a redesign. It can say that none of the product pages it reviewed that day mentions the subscription requirement for sync, and that, per Frandroid, buyers meet it in the app during setup.

CHI does not call this a bait-and-switch. Existing customers were not switched; they were grandfathered. But the proposition offered to every future customer has been inverted, quietly, with the old marketing still circulating and the new condition absent from the pages a buyer would read before buying.

The Law, Briefly

This is an economic indictment, not a legal prosecution. CHI does not allege that Withings has broken the law, and no regulator has said it has. The legal context matters for one reason only: it shows where the floor is, and therefore what Withings has chosen to monetize above it.

GDPR Article 20 gives a person the right to receive their data in a machine-readable format and, on request, to have it transmitted to another controller "where technically feasible," free of charge (Art. 20, Art. 12(5)). The right is request-based; regulators' guidance does not clearly require continuous automatic push (WP242). Withings' free CSV export plausibly satisfies that floor, and Withings' product lead says so: the free exports are free because "c'est la loi."

The EU Data Act, in force since September 2025, goes further in spirit. Article 4(1) requires connected-product data to be made available to the user free of charge in a machine-readable format and, "where relevant and technically feasible, continuously and in real-time" (Art. 4). Withings' own compliance notice already describes its devices as connected products generating data continuously (Withings notice, PDF). Whether that language reaches a paywalled Apple Health sync, or a paywalled Strava sync, is unsettled; Apple and Google, as DMA gatekeepers, are excluded from the Act's third-party-sharing provisions, and no authority has ruled. Numerama's read is that Withings is "playing with legality" (Numerama); Withings' read is that free export is enough. Both can be true at once.

What the law tells us anyway: European regulation increasingly favors machine-readable portability and continuous access, and the EU wrote "continuously and in real-time" into Article 4 because it understood that a downloadable file is not a working connection. Withings has read the same statutes and built its paywall in the space between what the law mandates and what it meant. That is not illegality. It is a company deciding that the floor the regulator set is also the ceiling of what it will give away. The fuller legal analysis, including the App Store guideline and US rules, is in the appendix.

What the Customers Said

Customer anger is not the case. The structure of the transaction is the case. The reaction corroborates it, because customers objected to the right thing.

A thread in Withings' own support community, "Unacceptable: Apple Health Sync is now behind a $99/year paywall for new accounts," had 329 votes and 249 comments as of 20 October (Withings community); a Hacker News thread, 404 points and 287 comments (Hacker News); MacRumors' forum, about 180 (MacRumors).

The recurring arguments were not "subscriptions bad." They were the arguments in this article. A MacRumors user who had spent roughly $950 on Withings hardware: "It's my data, I shouldn't have to pay them for it." Another would pay for online services "but not HealthKit syncing," a distinction Android Authority drew editorially too: rivals monetize coaching and AI, not data access (Android Authority). On grandfathering, a MacRumors moderator emeritus: "For now, until it isn't free." And across all three venues the dominant stance, including from grandfathered users the change does not touch, was that it affects their next purchase; the top-voted comment in Withings' own forum, from a grandfathered customer, was that he would not buy from Withings again.

Defenders existed. One argued that cloud sync is real engineering and the fee is "under 27¢ a day"; a few said a company may charge whatever people will pay. Nobody argued that the sync itself had become more expensive. Withings' only public response was the 15 October staff reply quoted throughout this article; PCMag and Numerama both reported no indication that Withings intends to change course (PCMag).

The Defense

Cross-Examination

Verdict

CHI finds that Withings has converted a basic interoperability function, the automatic movement of measurements generated by customer-owned hardware and the customer's own body into the health platform the customer chose, into a recurring toll.

The finding rests on five facts drawn from Withings' own documents. The sync existed and was free for a decade. Withings has identified no change in the marginal cost or technical operation of ordinary Apple Health and Health Connect synchronization that comes close to explaining a new $99.50 annual charge; the changes it cites concern its API and AI connector. Neither Apple's nor Google's published documentation identifies any recurring per-user fee for the platform write. Withings has publicly committed to provide the sync free, on its own word indefinitely and on any device, to its entire existing installed base. And Withings' own stated reason for the charge is not cost but the value of the data to others.

This is friction monetization. The price is attached not to anything Withings built in October but to Withings' position between the customer and the exit. The value of the thing being sold arises entirely from the fact that Withings controls the gate; remove the gate and there is nothing left to charge for. That is the definition of rent, and the fact that the rent is collected as a "membership" alongside features of real value does not change what it is. Bundling the toll with services of genuine value makes the nature of the charge harder to see.

It is hostile to the customer's economic interests in a specific way. The customer bears a recurring cost for which they receive nothing they did not already have, on a device they already own, for data they already produced and already possess. Over the life of an entry-level scale the toll exceeds the scale's price several times over. The customer's alternatives are to pay, to do by hand what $30 competitors do automatically, or to buy elsewhere. The product pages do not tell them this before they buy.

CHI also finds that the grandfathering, the free export, the free trial and the continued free use of the app are real mitigations and are stated in full above. They establish that Withings is not holding anyone's data hostage. They do not establish that charging $99.50 a year for a step whose marginal cost Withings has never stated, and cannot plausibly approach that figure, is anything other than what it looks like.

The principle is not complicated. A company may charge for what it makes. It does not get to manufacture a toll because it controls the gate.