Claude Projects Not Syncing Across Devices: What to Check

If Claude Projects are not syncing across devices, first confirm that both devices use the same account and the same personal or organization workspace. Then identify whether the missing material is a project, a conversation, an uploaded file, or a file that exists only on your computer.

Save the latest visible work before changing settings or signing out. fenbs can preserve the current task state and a recovery handoff outside Claude while you investigate, so a troubleshooting session does not erase your understanding of what remains.

What should you check first?

1. Keep the working device open. Copy any unsent draft and save the current result somewhere appropriate before refreshing.
2. Compare the exact signed-in email address and active account on both devices, including the selected organization.
3. Open the same project link on both devices where possible. Note whether it opens, shows an access error, or displays older content.
4. Try Claude on the web in a current browser to separate an app display problem from an account or project problem.
5. Check the service status and connection, then retry after preserving the work. Avoid deleting or rebuilding the project during diagnosis.

Write a specific symptom: “Project opens on laptop and phone, but the latest uploaded PDF is missing on phone.” That gives you a testable difference. “Sync is broken” can describe several unrelated issues, and each needs a different next step.

Anthropic’s login guide↗ (opens in a new tab) says to use the same email address across devices and explains switching between personal and organization accounts. Matching the email is necessary, but check the selected account as well.

Are you in the same account and organization?

A familiar name or profile picture is not enough evidence. Compare the address in account settings, then look for the active personal or organization account. If you belong to several organizations, select the one that contains the project before searching again.

Ask a teammate to confirm which organization owns a shared project and whether you still have access. An invitation sent to a different address can make a project look absent. Use the intended account; creating a duplicate project in another workspace complicates the diagnosis.

Try the original project link after selecting the correct account. If it opens but is missing from the expected list, record that distinction. If it refuses access, capture the wording for the owner or support rather than assuming the underlying content was deleted.

Our Claude project sharing guide covers collaboration, while organizing Claude projects covers keeping an existing set findable. Neither requires recreating a project just because one device cannot find it.

Is the missing item actually stored in the project?

Compare the project name, its instructions, its available files, and the specific conversation. A file on your laptop is not the same thing as a file uploaded to a Claude project. Check whether the upload completed and whether you placed it in this project or only attached it to one conversation.

Anthropic’s Projects documentation↗ (opens in a new tab) describes project knowledge and instructions, and distinguishes project experiences as the product changes. Compare the version and location you actually use rather than expecting identical navigation everywhere.

When you recover the right source, preserve the current goal and next action in a work handoff. Finding a file solves access to the evidence; it does not establish which of its proposals was approved.

Could local files explain the difference?

If the work used desktop file access, find the original folder and the output path Claude reported. Check the actual file contents and modification time. A document can be correctly saved on one computer while another device has no access to that folder.

Anthropic’s Cowork guide↗ (opens in a new tab) distinguishes cloud sessions from local file access on desktop. Do not treat access to your computer’s files as a promise that every file is copied to every device. Inspect the output and use an approved way to make the necessary copy available.

Avoid asking two sessions to edit different copies while the location is unclear. Choose the authoritative file, label any recovered version, and compare differences before replacing anything. If the latest result exists only on the working computer, protect that copy first.

How do you test the connection and app safely?

Check the official Claude status page↗ (opens in a new tab) for an incident affecting the surface you are using. A status page is evidence about known service problems, not a guarantee that your account or network is working. Record any visible error and the time it occurred.

After saving unsent work, refresh the affected page or restart the app. Update an outdated app and compare with the web version. If policy allows, try another trusted network or a browser without optional extensions to see whether the problem is specific to one environment.

Change one thing at a time and repeat the same direct-link test. Signing out and back in may help confirm account selection, but copy drafts first. Do not clear all browser data, reinstall apps, or remove projects as your opening move when they may contain your only accessible work.

An answer that fails to recall a detail is a separate symptom from a missing project. The Claude project memory guide explains that distinction. Verify the source is available before diagnosing the assistant’s interpretation of it.

What should you send to support if it still fails?

Prepare a short comparison: device type, app or browser version, active workspace, project link, last time it worked, and the exact error. State what you can still access on the working device and the troubleshooting steps that changed nothing.

Use the vendor’s private support channel for account details. Remove sensitive project content from screenshots unless support specifically needs it and your organization permits it. Do not post a private project link or transcript in a public forum to demonstrate the issue.

Keep a recovery note while waiting: last verified result, authoritative file location, outstanding checks, and next safe step. If you must work elsewhere, mark the new output clearly and reconcile it when access returns, rather than treating both copies as final.

How to do this with fenbs

1. Create a free account and add the project whose work you need to continue.
2. Add the current tasks and record what is completed, what is checked, and what remains inaccessible. Keep private account diagnostics in the support conversation.
3. Record approved decisions and relevant reference links so a recovery summary does not become a new interpretation of the work.
4. Connect a supported assistant through Integrations. Ask it to read the project context, and save Where we left off with the recovery status and next action before stopping.

fenbs does not repair Claude synchronization, recover deleted chats, or copy local files between devices. It helps preserve the work state around the problem. If the only issue is an outdated app and restarting fixes it, you may not need an additional work record.

The AI handoffs topic collects more ways to preserve progress when a session, device, or tool changes.