How to sync contacts between Gmail and iPhone (and the default-account trap)

Syncing Gmail contacts to an iPhone is a two-minute settings change: add the Google account, switch the Contacts toggle on. What breaks address books is the part after — the Default Account setting silently decides where every new contact is born, and most people discover years too late that theirs have been splitting between iCloud and Google the whole time.

One list, two stores

The iPhone’s Contacts app is a viewer, not a database. It overlays however many contact stores you’ve connected — iCloud, Google, Exchange — into one alphabetical list and hides the seams. The seams are still there.

Each contact record lives in exactly one account. “Anna” saved to iCloud exists on your Apple devices and at iCloud.com; she does not exist in Gmail, won’t appear in Google Contacts on your laptop, and won’t follow you to an Android phone. Her twin saved to Google does the reverse. Contact sync keeps each store consistent across its own devices — it never moves people between stores.

Under the hood, iOS talks to Google via CardDAV, the open contact-sync protocol standardized as RFC 6352 (Daboo, 2011) — the same vCard format your contacts export to. The practical consequence of an open protocol: the connection is native, robust, and needs no third-party app. The setup is genuinely this short:

1. Add the Google account

   Open Settings → Apps → Contacts → Contacts Accounts → Add Account and pick Google (on iOS 17 and earlier, the path is Settings → Contacts → Accounts → Add Account). Sign in with your Google credentials.

2. Switch Contacts on

   After sign-in, iOS shows toggles for Mail, Contacts, Calendars, and Notes. Switch Contacts on. If the Google account was already on the phone for Gmail, this toggle is the only thing you need to touch.

3. Verify in the Contacts app

   Open Contacts, tap Lists (top left), and you should see your Gmail account with its contacts. Initial sync takes a few minutes for large lists. From now on, edits made at contacts.google.com appear on the phone and vice versa.

CardDAV, and why manual setup rarely pays off for Gmail

The “Google” account type in Settings is really CardDAV with the fiddly parts hidden. Picking it does two things automatically: it points the connection at Google’s current server, and it completes the OAuth 2.0 handshake Google’s contacts API requires. Google’s own developer documentation is explicit that client apps should never hardcode a CardDAV server address, because it can change — which is precisely why the generic manual path has gotten less reliable for personal Gmail accounts over time, not more.

That leaves manual CardDAV for the cases the “Google” button doesn’t cover:

1. When you'd actually use it

   Non-Google CardDAV providers (Fastmail, self-hosted address books, some business directory servers), or a Google Workspace admin-managed directory that issues its own server address and app-specific credentials rather than routing through consumer OAuth.

2. Where to find it

   Settings → Apps → Contacts → Contacts Accounts → Add Account → Other → Add CardDAV Account. Enter the server, user name, password, and a description supplied by the provider — there’s no generic address that works for every service.

3. What it does not replace

   For a personal Gmail account, the “Google” account type above remains the reliable path. Reach for manual CardDAV only when a provider hands you server credentials directly, not as a substitute for signing in through Google.

The default-account trap

Here is the pitfall that produces the classic complaint — “my new contacts never show up in Gmail.” iOS saves every newly created contact to one account: whatever is set under Settings → Apps → Contacts → Default Account. Out of the box, that’s iCloud. (This setting only appears once Contacts is switched on for two or more accounts — with a single account there’s nothing to choose between.)

The trap is invisible because the unified list hides it. You save a new colleague; they appear in your contact list; everything looks correct. But they were born in iCloud — so they never reach Google Contacts, never appear on your Android tablet or in Gmail’s autocomplete on your work laptop. After two years of this, your address book is split across two stores along a line you never chose. (If that’s already happened, the fix is consolidation — export one store, import into the other, then merge the duplicates.)

The setting takes ten seconds: Settings → Apps → Contacts → Default Account → Gmail (or iCloud — the right answer is whichever ecosystem you’d keep if you switched phones tomorrow). Decide once, deliberately, and the split never starts.

A second version of the same trap deserves its own mention: multiple Google accounts. Anyone running a personal and a work Gmail on one phone can set Default Account to the wrong one of the two — and spend a year feeding a work account that evaporates at the next job change. New personal contacts belong in the personal account; it’s worth a ten-second check every time a new account joins the phone.

What syncs — and what doesn’t

For the fields that matter daily, Google-to-iPhone sync is solid: names, phone numbers, email addresses, postal addresses, birthdays, notes, URLs, and contact photos all travel in both directions. Birthdays even flow into calendar birthday feeds on both platforms, which is the foundation of a birthday system that actually works.

The edges are where expectations break:

Other contacts stay home. Google quietly auto-saves everyone you’ve interacted with — emailed, shared a Drive file or Photos album with, accepted a calendar invite from — into an “Other contacts” bucket. Those are not in your My Contacts group and do not sync to the phone. If someone is missing on the iPhone, check contacts.google.com → Other contacts first — one click on “Add to contacts” promotes them into the synced set.

Structure is platform-specific. Field data is portable vCard territory; organization is not. Google labels and iOS lists don’t map onto each other reliably, custom field labels can get renamed in transit, and per-contact ringtones or text tones are Apple-only decoration that never leaves the device.

Sync is fetch, not push. Google contact changes reach the iPhone by periodic fetch, not instant push. A change made on the web can take from minutes to an hour to land — check Settings → Apps → Mail → Mail Accounts → Fetch New Data if it consistently lags, and pull down on the contact list to force a refresh.

Deletions sync too — handle with care

Sync means symmetry. The same mechanism that carries a new phone number to every device also carries a deletion to every device.

The corollary is reassuring: if your contacts “vanished” after fiddling with accounts, they almost certainly still exist server-side. Sign back in, re-enable the toggle, and the list repopulates. Real panic is only warranted once you’ve checked contacts.google.com itself, including its Trash, and the entry genuinely isn’t there.

Two-way sync: what actually syncs back (and what doesn’t)

The two methods this guide covers behave completely differently, and mixing them up is where most “is this even syncing?” confusion starts.

Add the Google account and flip the Contacts toggle, and you get genuine two-way sync over CardDAV: edit a name, number, email, address, birthday, note, or URL on either the phone or contacts.google.com, and the change appears on the other side within the fetch window already covered above. Deletions propagate the same two directions — the mechanics are covered above, not repeated here.

• Edits — bidirectional, over the Google-account/CardDAV connection.
• Deletions — bidirectional too; removing a contact on either side removes it everywhere.
• Photos — asymmetric: live sync carries them both ways, but a vCard export/import round-trip drops them (see above).
• iCloud-method transfers — the export/import vCard move is a one-time copy, not sync. Nothing keeps the two accounts in step afterward.

Know which method you’re actually running, and “is this syncing?” has an obvious answer.

Moving contacts between iCloud and Google, step by step

Sync repair often surfaces the harder question underneath: should your contacts live in iCloud or in Google at all? There is no universally right answer, but there is a right criterion — pick the store you’d keep if you changed phone platforms tomorrow. Deep in Apple hardware with no Android in sight, iCloud is fine. Using Gmail, an Android tablet, or a work machine with Google Workspace, Google is the safer center of gravity.

The move itself is an export-import, not a migration project — but the exact buttons matter, and both web apps have moved theirs around over the years.

1. Export from iCloud.com

   Sign in at icloud.com/contacts. Click Actions → Select All Contacts (or hold Cmd/Ctrl and click individual cards), then click Share → Export vCard. Selecting multiple contacts exports one vCard file containing all of them.

2. Export from Google Contacts

   At contacts.google.com, select the contacts (or select-all), click More actions → Export, choose vCard as the format, and click Export. Google’s vCard export carries the core fields but drops contact photos — plan to re-add those by hand afterward.

3. Import into the keeper

   Import into Google via contacts.google.com → Import → choose the .vcf file. Import into iCloud via icloud.com/contacts → the Add button → Import Contact → choose the file. Either app accepts the other’s vCard export directly.

4. Finish the switch

   Set Default Account to the keeper, switch the old account’s Contacts toggle off, and merge the duplicates the import just created — the same person now exists in both the old and new accounts until you do.

Half an hour, once — and every future sync question collapses to a single store behaving or not.

Troubleshooting matrix: symptom, cause, fix

When something looks wrong, matching the symptom to its cause is faster than guessing:

Duplicate contacts after an import or sync. Two cards for the same person inside one account are a true duplicate — open Contacts, tap View Duplicates under My Card, then Merge All. Two cards for the same person across accounts (say, one iCloud and one Google) aren’t duplicates in the technical sense — use Edit → Link Contacts to show them as one card without merging the underlying records. On the Google side, contacts.google.com → Menu → Merge & fix → Merge duplicates does the same job for that account. See contact deduplication for the general pattern.

Missing fields after sync or import. Field data (names, numbers, emails, addresses, birthdays, notes, URLs) travels cleanly. Field structure — custom labels, Google’s field groupings, iOS lists — does not always map cleanly and can be renamed or dropped in transit. This is a platform limitation, not a bug to chase; verify anything structurally important after a big import rather than assuming it carried over.

Missing photos after an export/import round-trip. Google’s vCard export does not include contact photos. Live sync (an added Google account, not an export) does carry photos both ways — so treat export/import as a one-time migration tool, not a routine sync method, and expect to re-add photos manually after any vCard move.

Sync delay — a change doesn’t show up. Google contacts reach the iPhone by fetch, not push. Give it up to an hour on Automatic settings; check Settings → Apps → Mail → Mail Accounts → Fetch New Data for a tighter schedule, and pull down on the contact list to force an immediate check.

A new contact went to the wrong account. This is the Default Account trap — check Settings → Apps → Contacts → Default Account. It’s especially easy to get wrong with two Google accounts on one phone (personal and work); confirm which one is actually set before contacts pile up in the wrong place.

Troubleshooting, in order

If none of the above matches what you’re seeing, work the chain in sequence — the failure points are ordered, and checking them in order finds the break in under five minutes. Toggle first (Settings → Apps → Contacts → Contacts Accounts → your Google account — is Contacts actually on?). Then the refresh: pull down on the contact list. Then the Default Account (new contacts going to a store you’re not looking at is the classic). Then Fetch New Data, for staleness rather than absence. Then the Other-contacts bucket on the web. And finally the blunt instrument that resolves most wedged states: remove the account from the phone and add it again — local copies are discarded and re-downloaded fresh from the server.

If you’re cleaning all of this up as part of a bigger overhaul, do the sync repair first and the full address-book triage second — there’s no point organizing a list that’s still splitting itself in two. And once your contacts live consistently in one store, anything built on top of them gets simpler: Endearist, for instance, imports the whole consolidated set as vCard or CSV into a local database in one pass.