Developer Tools

Clear GitHub Desktop Cache on Mac

Clearing the GitHub Desktop cache frees space and can fix slow or odd behaviour, and you can keep the app. Most of the data it uses is rebuildable, and the typical total is 200 MB – 2 GB.

Last updated: October 31, 20262 min read

Clear the GitHub Desktop cache without guessing

GitHub Desktop data usually takes 200 MB – 2 GB on a Mac. The free scan shows the exact size on your Mac before you change anything.

Scan your Mac free

Free scan · No account · Nothing is deleted without your OK · Moves to the Trash first · macOS 14+

Application: GitHub Desktop
Typical data size: 200 MB – 2 GB
Category: Developer Tools
File Location: ~/Library/Application Support/GitHub Desktop

GitHub Desktop cache folders you can clear

These folders are rebuilt automatically, so removing them does not touch your own files.

~/Library/Caches/com.github.GitHubClient Cache · app network cache Yes, rebuilt automatically~/Library/Caches/com.github.GitHubClient.ShipIt Cache · downloaded app updates Yes, rebuilt automatically~/Library/HTTPStorages/com.github.GitHubClient Network cookies · network cookies used by the app itself Yes, rebuilt automatically~/Library/Application Support/GitHub Desktop/Cache Cache · GitHub Desktop web content cache Yes, rebuilt automatically~/Library/Application Support/GitHub Desktop/Code Cache Cache · compiled JavaScript cache Yes, rebuilt automatically~/Library/Application Support/GitHub Desktop/GPUCache Cache · GPU shader cache Yes, rebuilt automatically~/Library/Application Support/GitHub Desktop/logs Logs · GitHub Desktop logs Yes, rebuilt automatically

Locations are the standard macOS folders GitHub Desktop uses; some appear only after you use the matching feature.

What the GitHub Desktop cache holds and when clearing helps

Specific to GitHub Desktop

Most of the cache is temporary: web content, compiled JavaScript, GPU shader data, network cache and logs are all rebuilt automatically. Clearing them helps when the app loads pages slowly, shows display glitches after an update, or keeps stale network responses. Two things are not cache: your cloned repositories, which sit in your Documents folder under GitHub by default, and your repository list and settings. Your sign-in token is kept in the Keychain, not in any cache folder. Clear only the rebuildable folders and leave the repositories alone.

What happens after you clear the GitHub Desktop cache

The first launch after clearing is slower, because the app rebuilds its web content, compiled code, shader cache and network cache. Your repositories, settings and repository list stay exactly where they were. Your sign-in token remains in the Keychain, so you should not need to sign in again; if the app does ask, that is the only account change to expect. Nothing you cloned or committed is affected.

If the app offers a cache-clearing option, use it while GitHub Desktop is open.Push or save any unfinished work in your repositories first.Quit GitHub Desktop before removing any cache folders by hand.Reopen the app and expect a slower first start.

0 of 4 done

Account and sync: GitHub Desktop signs in to GitHub or GitHub Enterprise; the token is kept in the Keychain.

Try it without risk

Download and scan for freeSee every GitHub Desktop file and its size. No account needed.
Clean free for 7 daysStart the 7-day free trial of the yearly plan inside the app.
Keep it or cancelCancel in your App Store settings at least 24 hours before the trial ends and you won't be charged.

Download free and scan

After the free trial, Pro costs $39.99 per year in your country's App Store; cancel any time.

Frequently asked questions

Yes. Folders marked “Yes, rebuilt automatically” are rebuilt automatically; removing them only makes the next start slower.

Will my cloned repositories still be there?

Yes. Repositories cloned with GitHub Desktop stay in your Documents folder under GitHub, and clearing the cache does not touch them.

Do I need to reinstall GitHub Desktop afterwards?

No. Keep the app; the cache folders are rebuilt automatically the next time you open it.