iPhone: Set up Fitbit to Apple Health via Google Health in 10 minutes

Yes, you can combine Fitbit tracker data with Apple Health, using the Google Health app on iPhone as the official bridge. No paid workaround is required for most metrics anymore. You’ll need iOS 16.4 or later, a Google account linked to your tracker, and permission grants in both Google Health and Apple Health before anything starts flowing across.

TL;DR:

• Most Fitbit data types, including steps, sleep, heart rate, and workouts, can now sync bidirectionally with Apple Health using the Google Health app without needing paid workarounds.
• The sync process requires updating the Google Health app, signing into the same Google account linked to Fitbit, granting permissions, and verifying categories are correctly enabled on both apps.
• Heart rate variability and some skin temperature readings may remain read-only on iOS due to Apple’s data-sharing policies, although they can be writable on Android through Google Health.
• Discrepancies between Fitbit and Apple Health numbers are common because the platforms use different sensors and algorithms; consistently treating one as your primary source minimizes confusion.
• Automatic synchronization only transfers recent activity, so exporting older Fitbit data manually may be necessary for a complete historical record in Apple Health.

Table of Contents

• How to connect Fitbit and Apple Health via Google Health
• Which data types actually move across?
• Fixing a sync that stalls, lags, or duplicates
• Setting Apple Health’s source priority correctly
• What you’re actually granting when you connect these apps
• Bringing your old Fitbit history into Apple Health
• Do you still need a third-party bridge app?
• Why Apple Health and Fitbit numbers rarely match exactly
• Keeping your numbers consistent once everything’s connected
• Does constant syncing drain your battery?
• Why centralising your data still needs a human check
• Turn your synced Apple Health data into a daily plan
• Sources
• FAQ

How to connect Fitbit and Apple Health via Google Health

The route that matters here runs through the Google Health app, which added native write access to Apple Health in 2026. This closed the gap that frustrated iPhone owners with Fitbit trackers for years, and the setup takes about ten minutes.

Here’s the process from a clean install:

1. Update or install Google Health. Check the App Store for the latest version. If you already have it, force an update anyway. Older builds don’t show the Apple Health connection option.
2. Sign in with the Google account tied to your tracker. This has to be the same account your Fitbit device already syncs with, or the connection won’t find any data to move.
3. Go to Connections → Apps and services → Apple Health, then tap “Get started.” This is the exact path Google documents in its own help centre guidance, and it’s the step people most often skip past too fast.
4. Grant permissions. You can tap “Turn All Categories On” for a full handover, or go category by category if you’d rather be selective from day one.
5. Complete the consent prompts. Apple Health will ask you to confirm sharing on its end too. Don’t back out of this screen; it’s easy to assume you’ve finished when you haven’t.
6. Force an initial sync. Open Google Health and pull to refresh, or wait for the automatic sync window.
7. Check Apple Health. Go to Sharing → Apps → Google Health and confirm each category you want is toggled on.

Before you start, run through this checklist: iOS 16.4 or newer, an active internet connection, background app refresh switched on for Google Health, and confirmation that your tracker has synced with Google Health recently. Skip that last one and you’ll be troubleshooting a connection that’s actually working fine. It just has nothing to send yet.

Which data types actually move across?

Most day-to-day metrics sync cleanly in both directions once the connection is live. According to reporting on the 2026 Google Health update, the categories that now write into Apple Health include:

• Steps, distance, and floors climbed
• Active calories and total energy burned
• Exercise sessions, including GPS routes
• Sleep sessions and sleep stages
• Heart rate and resting heart rate
• Blood oxygen readings
• Weight and body measurements
• Nutrition fields, where logged

Heart rate variability is the exception worth knowing about. On iOS, HRV and some skin temperature readings tend to stay read-only. Google Health can display them, but it can’t always write them into Apple Health’s own store, since Apple treats certain biometric calculations as source-specific rather than shareable across apps. If you’re on Android instead, Health Connect governs the same exchange differently. Google’s own Fitbit and Health Connect support page notes that some fields, HRV among them, can be writable there when they’re not on iOS. Worth remembering if you ever switch platforms and wonder why a metric you relied on suddenly stops appearing.

Fixing a sync that stalls, lags, or duplicates

Most connection problems trace back to one of four causes, and each has a specific fix rather than a generic “restart everything” shrug.

1. Permissions didn’t fully take. Open Apple Health → Sharing → Apps and check that every Google Health toggle you expect is actually on. If one’s missing, reauthorise from inside Google Health rather than just flicking the switch in Apple Health.
2. An app is out of date. Update iOS and both apps before doing anything else. A stalled connection is often just an app that hasn’t caught up with a permissions change on the other side.
3. The account link has gone stale. Sign out of Google Health completely and sign back in. This forces a fresh handshake that a simple app restart won’t trigger.
4. Duplicate entries are showing up. This usually means two sources are both writing the same metric. Head to Apple Health’s Data Sources & Access screen for that metric and move your preferred source to the top.

If none of that resolves it, rebooting both devices and checking Bluetooth pairing on your tracker solves a surprising number of stuck connections, a pattern echoed in community troubleshooting threads covering similar wearable integrations.

Pro Tip: If data seems delayed rather than missing entirely, wait 24 hours before troubleshooting. Some categories, sleep in particular, report a day behind by design, and chasing a “fault” that’s really just a lag wastes time you don’t need to spend.

Setting Apple Health’s source priority correctly

Apple Health doesn’t average conflicting sources. It picks one and displays that. Here’s how to make sure it’s the one you actually want:

• Open the Health app and choose a metric, Steps is the easiest to start with.
• Tap Data Sources & Access, then Change Order.
• Drag Google Health to the top of the list.

Here’s the quirk that catches people out: newly added sources often appear at the top automatically when you first connect them, so your priority order might already be right without you doing anything. But it can also shift after an app update or a reconnection, quietly demoting Google Health beneath your iPhone’s built-in Motion & Fitness tracking. Apple’s own support documentation confirms that the top-ranked source is what gets shown when multiple apps write the same data.

After reordering, give it a day or two and compare your totals against what your tracker’s own app reports. A gap of a few hundred steps usually means the iPhone’s own motion sensor is still contributing alongside Google Health rather than being cleanly overridden.

What you’re actually granting when you connect these apps

Read and write permissions aren’t the same thing, and Apple Health lets you control both at the category level. Read means an app can see your data. Write means it can add to your Apple Health record. You manage both under Sharing → Apps for every connected service.

A few habits worth adopting from day one:

• Only turn on categories you genuinely use elsewhere, not everything by default.
• Check what a third-party app’s privacy policy says before granting broad access, particularly for anything touching reproductive or mental health categories.
• Revoke access the moment you stop using an app. Dormant permissions are the most common way data lingers longer than anyone intended.

Pro Tip: Going through Google Health directly, rather than a third-party bridge app, means your data passes through fewer intermediary servers on its way into Apple Health. Fewer hops generally means fewer places for something to go wrong or linger.

Bringing your old Fitbit history into Apple Health

Connecting the apps only starts a forward sync. It doesn’t automatically pull years of historical Fitbit data into Apple Health’s records, and that catches a lot of long-time trackers off guard when they realise their sync only shows activity from the connection date onward.

The Google Health app typically pulls in a backfill window once the connection is confirmed, often stretching back several weeks or months depending on what’s stored against your account. For anything older than that, you’re working with what your Fitbit account already has archived rather than a live resync. If you want a genuinely complete historical record inside Apple Health, exporting your Fitbit data directly from your account settings and keeping that export as a standalone archive is more reliable than expecting the sync to reach back years.

It’s also worth checking your data a week after the initial connection, not just on day one. Some historical categories, sleep architecture especially, populate on a delay as Google Health processes the backlog. If a chunk of history genuinely never appears, that’s usually a sign the original Fitbit sync gap predates your Google account link, not a fault in the current connection.

Realistically, most readers don’t need five years of step counts sitting in Apple Health. What matters more is that everything from today onward lands correctly and stays consistent, which is where the setup steps above earn their keep.

Do you still need a third-party bridge app?

For most people, no. Before Google Health added native write access, apps like Sync Solver existed specifically to plug this gap, pulling Fitbit data out and pushing it into Apple Health for a subscription fee. That entire category of workaround exists because Apple and Fitbit’s parent company hadn’t built a direct line between the two platforms.

The 2026 Google Health update removed most of the need for that middle layer. If your only goal is getting steps, sleep, heart rate, and workouts into Apple Health, the official route covers it without a recurring cost or another app holding a copy of your health data.

Third-party bridges still have a narrow use case: if you need a specific metric that Google Health doesn’t currently write, or you want data reformatted in a way neither native app supports. But for the overwhelming majority of readers asking how to get their tracker history into Apple Health, paying for a bridge app in 2026 is solving a problem that mostly no longer exists. Check what you actually need synced before assuming you need to pay for it.

Why Apple Health and Fitbit numbers rarely match exactly

Even with a clean official sync, don’t expect Apple Health and your tracker’s own app to show identical numbers side by side. The two platforms use different sensors, different step-counting algorithms, and different rules for what counts as an “exercise minute.”

Your iPhone’s accelerometer and your wrist-worn tracker are measuring the same walk from two different vantage points, and small differences compound over a day. Heart rate during high-intensity intervals is a common flashpoint too. Optical sensors on a wrist tracker and the underlying calculation Apple Health applies to imported data don’t always agree during rapid changes, which is part of why HRV in particular tends to show day-to-day mismatches once you start comparing it across apps.

None of this means the sync is broken. It means the two systems were never built to produce identical figures, only comparable ones. Treat Apple Health’s combined view as your single reference point going forward, rather than trying to reconcile it against your tracker’s app every single day.

Keeping your numbers consistent once everything’s connected

Discrepancies are far easier to manage than to eliminate entirely, and a handful of habits keep them from spiralling.

Pick one app as your source of truth and stick to it. Constantly cross-checking Apple Health against your tracker’s native app invites confusion, especially once you’ve deliberately set a source priority. Recheck your Data Sources & Access settings after any major iOS or app update, since updates occasionally reset priority order without warning. And if you switch trackers or add a second device, immediately review which source is now writing which metric. It’s the single most common trigger for a sudden jump or drop in your totals that has nothing to do with your actual activity.

If you’re relying on Apple Health data to feed into a broader training or nutrition plan, consistency matters more than raw precision. A tool that reads your Apple Health timeline as a single feed, rather than trying to reconcile multiple raw device feeds itself, sidesteps a lot of this friction entirely.

Does constant syncing drain your battery?

Background syncing does draw more power than a phone left alone, but the effect is modest rather than dramatic. Google Health checking in periodically to pull tracker data and push it to Apple Health runs in the background refresh cycle iOS already manages for every app on your phone, not as some standalone drain running independently.

The bigger factor is usually your tracker itself, not the phone-side sync. A device pinging your iPhone every few minutes to hand off heart rate data uses more of its own battery than the occasional handshake between Google Health and Apple Health. If you notice a real dip in phone battery life after setting this up, check whether background app refresh is enabled for dozens of other apps too. Sync is rarely the sole culprit once you actually audit what’s running.

Performance-wise, the sync itself is lightweight. It’s a data handoff, not a continuous process taxing your processor. If your phone feels sluggish after connecting these apps, that’s far more likely to be an unrelated update or storage issue than anything to do with Google Health talking to Apple Health.

Why centralising your data still needs a human check

Getting Fitbit data into Apple Health solves a real problem: one timeline instead of three apps disagreeing with each other. Any tool that reads a single consolidated feed, rather than reconciling separate raw device streams, produces more consistent daily insights and training adjustments as a result.

That said, treat high-precision metrics like HRV with a healthy dose of scepticism even after a clean sync, and consider what to look for in an integrated app if you want more actionable insights. Different platforms calculate it differently, so occasional mismatches are normal, not a sign something’s broken. The sensible habit is spot-checking anything you’re using to make real decisions, rather than trusting a single number blindly.

This is precisely the gap an app like Heala is built to sit in. It reads across multiple connected trackers and uses the combined signal, not just one device’s view, to adjust training, recovery, and nutrition guidance day to day.

— Kerem

Turn your synced Apple Health data into a daily plan

Once your Fitbit data is flowing into Apple Health, you’ve got a single accurate feed, but a feed on its own doesn’t tell you what to do with it. Some apps read data from Apple Health and offer adaptive workout, recovery, and nutrition guidance that adjusts as your numbers change, rather than leaving you to interpret HRV dips or sleep debt yourself.

Where a comparison against how Heala approaches tracker data versus Fitbit’s own app shows the difference clearly is in what happens after the numbers land. Instead of a dashboard full of separate charts, you get one daily plan that accounts for last night’s sleep, this morning’s readiness, and what you logged for breakfast. Heala’s free tier covers the basics, and the Pro plan unlocks deeper analytics and AI coaching for anyone who wants their synced data doing more work than sitting in a chart. If you’re serious about getting more out of a tracker you already own, consider setting up a free account with a health app and connecting your Apple Health data today.

Sources

• How do I use Apple Health with the Google Health app? - Google Health Help Center
• Manage Health data on your iPhone, iPad, or Apple Watch - Apple Support
• Fitbit data can finally sync to Apple Health - MacRumors

FAQ

Can you combine Fitbit and Apple Watch data in one place?

Yes. Apple Health can hold data from both a Fitbit tracker and an Apple Watch simultaneously, showing combined totals based on whichever source you’ve set as top priority for each metric. You control this in Data Sources & Access, dragging your preferred device to the top for steps, heart rate, or any other overlapping category.

How do I sync Apple Health data back to the Fitbit app?

Apple Health doesn’t send data back to Fitbit’s own app; the official Google Health bridge works primarily one way, moving tracker data into Apple Health rather than the reverse. If you need Fitbit’s app to reflect something logged only in Apple Health, you’d have to enter it manually there.

Can you export data from Apple Health?

Yes, Apple Health supports a full export of your health records, generating an XML file you can save or share. This is useful as a backup before making changes to source priority or disconnecting an app, since it preserves a snapshot of everything currently stored.

Is the iPhone or a Fitbit tracker more accurate for counting steps?

Neither is definitively more accurate; they measure differently. A wrist-worn Fitbit uses motion sensors tuned for arm movement, while the iPhone’s own sensor tracks steps based on how the phone itself moves, which is less reliable if it’s left in a bag or on a desk. For most people, a worn tracker gives more consistent step counts throughout the day than a phone carried inconsistently.

Do I need a paid app to sync Fitbit with Apple Health?

No, not for most metrics. The Google Health app now writes steps, sleep, heart rate, and workouts into Apple Health without any subscription. A paid bridge app is only worth considering if you need a specific metric the official connection doesn’t currently support.

Recommended

• Heala vs Fitbit — the tracker and the plan
• Heala vs Apple Fitness and Apple Health
• Heala vs MyFitnessPal: logging a meal in 2026