You chatted with Claude in your laptop browser all morning, open the mobile app in the afternoon, and the history shows only chats from a few days ago — or nothing at all. The web and the app feel like they’re on different planets.
Fastest fix (works ~80% of the time): check that the app is signed into the exact same account as the web. App → tap your initials in the top-right corner → Settings → note the email. Compare it to claude.ai/settings/account on the web. If they differ, sign out of the app and sign back in through the same login method (Google / Apple / corporate SSO). That one mismatch causes the large majority of “not syncing” reports.
Mental model: Claude chats are stored server-side and bound to your account. “Sync” just means the mobile app pulls your conversation list with the same access token. If any link in that auth chain points at a different account — or the request is blocked — you get the “half visible, half not” pattern. This is almost never a Claude server bug.
Which bucket are you in?
Match your exact symptom to the most likely cause before you start changing things.
| Symptom | Most likely cause | Jump to |
|---|---|---|
| App shows some old chats but not today’s web chats | Wrong account, or app didn’t pull-to-refresh | Step 1, Step 4 |
| App history is completely empty after login | Wrong account, or enterprise mobile restriction | Step 1, Step 7 |
A specific chat shows Some conversation history couldn't be loaded | Known Claude Code / long-session app bug — open it on the web | FAQ |
| Chats started in the desktop app never appear on mobile or web | Known desktop-app isolation bug (see FAQ) | FAQ |
| Chats vanished everywhere, including the web | You archived or deleted them | Step 6 |
| Works on cellular but not office Wi-Fi | Network partition (proxy / IPv6 / DNS) | Step 3 |
Common causes, by hit rate
1. Mobile app is signed into a different account
By far the most common. Web uses you@company.com (SSO). The mobile app is annoying to type into, so you used you@gmail.com via one-tap Google or Apple sign-in. That’s two separate accounts, each with its own chat list, and no sync between them.
Claude has no password — login is always Google, Apple, or an emailed magic link — so it’s easy to land on the wrong identity without noticing. As of June 2026 there is no merge: chats created under one account never move to another.
How to spot it: App → tap your initials, top-right → Settings → read the full email. Compare to the web at claude.ai/settings/account. Different = your culprit.
2. App version too old
Older builds (roughly six-plus months back) may not render newer chat types — Project chats, chats with Artifacts, Cowork sessions — so they appear “missing” even though they synced.
How to spot it: App Store / Google Play shows an update available, or your installed version is several releases behind the current public one.
3. Enterprise account has a mobile-access restriction
Team / Enterprise admins can restrict mobile access from the admin console. The app logs in fine, but pulling chat history returns an empty list with no clear UI signal.
How to spot it: Web claude.ai/settings/account shows a Team or Enterprise org. Ask your admin whether a mobile policy is set.
4. iOS Background App Refresh off / Low Power Mode on
With background refresh disabled, the app only fetches the latest list when you bring it to the foreground — and Low Power Mode pauses background refresh entirely. If you expected the list to be instantly current, this can look like a sync failure.
How to spot it: iOS Settings → General → Background App Refresh → is Claude enabled?
5. Network partition (corporate proxy / IPv6 / VPN)
Corporate Wi-Fi that forces IPv6 when the route is broken, a VPN landing in a restricted region, or a proxy blocking specific API paths can all stop the app from reaching the server even while other apps work. Anthropic’s own support guidance points to unstable networks and corporate network policies as a cause, and recommends switching to a mobile hotspot to rule out DNS, proxy, or firewall interference.
How to spot it: Switch the phone to 4G/5G, turn the VPN off, reopen the app. If it syncs, the original network was the problem.
6. You archived or deleted the chats from another device
“Not syncing” sometimes means “you archived them in the web UI.” The mobile app does not show archived conversations in the normal list.
How to spot it: On the web, look for the archived view (sidebar / Settings) and check whether the “missing” chats are sitting there.
Shortest path to fix
Work top to bottom; most people are fixed by Step 1 or Step 2.
Step 1: Account-consistency check
This resolves the majority of cases, so do it first.
App: tap initials (top-right) → Settings → read full email
Web: open claude.ai/settings/account → copy the email
They must be identical.
If they differ:
In the app: Sign out → sign back in with the SAME method web uses.
If it's SSO, use the SAME entry point (Google / Apple / Corp SSO) —
a Google sign-in and a magic-link to the same address can still be
two different accounts.Step 2: Update the app, then force-quit
App Store / Google Play → search "Claude" → Update.
Then force-quit:
iOS: swipe up to the App Switcher → swipe Claude away → reopen
Android: Settings → Apps → Claude → Force stop → reopenWait about 10 seconds after the first launch so the app can pull the server list.
Step 3: Network switch test
1. Turn the VPN off
2. Switch to 4G/5G (not Wi-Fi)
3. Reopen the app and check the historyIf it works on cellular, the problem is your Wi-Fi (corporate proxy / IPv6 / DNS), not Claude.
Step 4: Manual pull-to-refresh
On the main chat-list screen, drag down with one finger to force a refresh. If new chats exist server-side but the app hasn’t auto-pulled them, this forces the fetch immediately.
Step 5: iOS Background App Refresh
Settings → General → Background App Refresh
→ confirm the global toggle is on
→ find Claude in the list and enable itThen turn Low Power Mode off (it pauses background refresh) and retest.
Step 6: Check archived chats
On the web, open the archived view (sidebar or Settings → archived conversations). Unarchive the “missing” chats; they reappear on mobile within seconds. Note: as of June 2026 some users report the archived view can be hard to find or buggy after a UI change — if you can’t locate it, use chat search on the web instead, and if a chat is genuinely gone everywhere, it was deleted, not archived.
Step 7: Escalate an enterprise policy
Email to your admin:
"With the same SSO account I see all chats in the web UI, but the
iOS / Android app doesn't sync them. Can you check the admin console
for a mobile-access restriction and allow my account if one applies?"How to confirm it’s fixed
- On the web, start a brand-new chat and send one message (e.g. “sync test”).
- On the phone, open Claude and pull-to-refresh the chat list.
- The new “sync test” chat should appear within a few seconds.
If that new chat syncs but old ones still don’t, the old chats are under a different account or archived — recheck Step 1 and Step 6. If even the brand-new chat won’t appear, you’re almost certainly on the wrong account (Step 1) or behind a blocked network (Step 3).
Is it actually an outage?
Before spending more time, rule out a real incident: check status.anthropic.com. A genuine outage shows up there and affects the web too — if your web chats load fine, it is not a server-side sync outage and the steps above apply.
FAQ
Why does one chat say Some conversation history couldn't be loaded?
That specific error is a known app-side bug, most common on long, tool-heavy Claude Code or Cowork sessions, where the app can’t render the full transcript. The data isn’t lost — open the same conversation in a web browser at claude.ai and the full history is there. As of June 2026 the reliable workaround is to use the web for those heavy sessions.
I started chats in the Claude desktop app and they don’t show on mobile or web. Why? There’s a separate, reported issue (seen through mid-2026) where some Claude desktop-app conversations stay isolated and don’t propagate to mobile or web, even on the same account. Until it’s resolved, do anything you need synced across devices in the web app or the mobile app rather than the desktop app, and check status.anthropic.com for related incidents.
Will signing out of the mobile app delete my chats? No. Chats live server-side, tied to your account, not on the device. Signing out and back in is safe and is often the actual fix — it forces a fresh token and a clean pull of your list.
I’m on the same email but still nothing syncs. Now what? Same email isn’t always the same account. A Google one-tap login and an emailed magic link to that same address can resolve to different identities. Sign out and sign back in using the identical method you use on the web, then run the “How to confirm it’s fixed” test above.
How long should syncing take? Seconds. Open the app, pull-to-refresh, and a current chat list should arrive within a few seconds on a normal connection. If it’s been minutes with nothing, it’s an account or network problem, not slow sync.
Prevention
- Use the same email and the same login method on web and mobile — don’t one-tap Apple ID on the app while using SSO on the web.
- Keep auto-update on in the App Store / Google Play; Claude iterates fast and one or two versions behind can break rendering.
- Keep Background App Refresh on globally and for Claude.
- For work accounts, confirm the mobile-access policy with your admin on day one — don’t wait until you’re locked out.
- Don’t casually archive important chats; archive hides, it doesn’t delete, but mobile won’t show archived chats.
- Sync issue? Try 4G first to rule out the network layer in seconds.
Related
Tags: #Claude #Troubleshooting