VS Code Settings Sync Not Working

Share
Workaround available All Updated November 13, 2026Based on 2 user reportsHow we research

Quick answer

Check the Settings Sync log, resolve conflicts or turn sync off and on again. Size limits and Linux keyring problems are common causes.

Most likely fix: Read the logs

How to fix it

Try these in order — the most common fix is first.

  1. 1. Read the logs

    1. Open the Log (Settings Sync) output channel
    2. Run Settings Sync: Show Synced Data
    Did this fix it?
  2. 2. Resolve conflicts

    1. Choose Accept Local, Accept Remote, or Show Conflicts and Complete Merge
    Did this fix it?
  3. 3. Reset sync

    1. Run Settings Sync: Turn Off, optionally tick 'clear the data from the cloud'
    2. Turn sync on again
    Did this fix it?
  4. 4. Check limits

    1. Keep settings, keybindings and tasks under 100 KB each
    2. Use Settings Sync: Configure to re-enable a disabled category
    Did this fix it?
  5. 5. Unlock the Linux keyring

    1. Unlock the Login keyring; on KDE open kdewallet
    2. Or set password-store in argv.json
    Did this fix it?

Symptoms

Settings do not sync between machines, conflict prompts appear, or sync turns itself off.

Why it happens

  • Merge conflicts
  • Settings, keybindings or tasks over 100 KB
  • More than 20 profiles
  • Locked Linux keyring
  • Stable and Insiders mismatch

This guide also covers

  • vscode settings sync not working
  • vscode settings sync conflict

Still not working?

If VS Code keeps failing, you're not alone. See every VS Code problem users report or the alternatives people switch to.

Need a custom web app or internal tool? Our small team builds it, on your domain or hosted by us. Price agreed together.

Get a quote
Fixed it? Share this guide

Other VS Code errors

All 12 VS Code errors and fixes →