Developer Tools

Clear Fork Cache on Mac

Clearing the Fork cache frees a little space and often fixes a sluggish or misbehaving app, while your repositories and settings stay put. The cache is rebuilt automatically the next time you open the app. Use any cache-clearing option the app offers first, and remove the cache folder by hand only if you need to.

Last updated: October 31, 20262 min read

Clear the Fork cache without guessing

Fork 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: Fork
Typical data size: 200 MB – 2 GB
Category: Developer Tools
File Location: ~/Library/Application Support/com.DanPristupov.Fork

Fork cache folders you can clear

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

~/Library/Caches/com.DanPristupov.Fork Cache · app cache Yes, rebuilt automatically~/Library/Saved Application State/com.DanPristupov.Fork.savedState Window state · window positions from the last session Yes, rebuilt automatically

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

What the Fork cache holds and when clearing helps

Specific to Fork

The cache folder at ~/Library/Caches/com.DanPristupov.Fork holds temporary data that the app rebuilds automatically. It is not where your repositories or settings are kept, and it is only part of the data the app typically takes up, which ranges from 200 MB – 2 GB. Clearing the cache is worth trying when the app feels sluggish, shows stale information, or behaves oddly. A fresh cache replaces anything that has become damaged, so if the problem remains afterwards, the cache was probably not its cause.

What happens after you clear the Fork cache

The first launch afterwards takes longer, because the app rebuilds its cache from nothing. Your repository list, settings and app data stay where they are, so you should not need to set them up again. Your code remains in its own folders, since Fork only tracks repositories by location. Window positions from the last session are also rebuilt automatically, so windows may reopen in different places once.

If the app offers a cache-clearing option, use it while it is open.Quit Fork completely before removing anything by hand.Show the hidden Library folder from Finder's Go menu.Move only the cache folder to Trash, restorable until emptied.

0 of 4 done

Try it without risk

Download and scan for freeSee every Fork 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 I need to set up my repositories again?

No. Fork keeps its list of repositories in its support folder, and clearing the cache leaves that folder untouched.

Why is the app slower the first time I open it?

The app has to rebuild its cache from nothing, which takes a little longer. Normal speed should return after that first launch.