Improving Performance

Last updated: March 2026

Use this page to diagnose slow or unresponsive behavior in GitKraken Desktop, especially in large or complex repositories. It focuses on practical fixes such as repository maintenance, graph-size limits, auto-fetch changes, branch cleanup, LFS cleanup, and build verification for macOS systems.

Requirements and limits

• Scope: Troubleshooting performance problems in GitKraken Desktop repositories and UI rendering
• Common trigger: Large repositories with many references or heavy graph rendering
• Primary fixes: Repo maintenance, graph-size reduction, auto-fetch changes, branch cleanup, and LFS cleanup
• macOS-specific note: Version 11.5.1 performance can be affected by using the wrong Intel vs Apple Silicon build
• Escalation path: Contact GitKraken Support if maintenance and configuration fixes do not help

Quick Start

Common fixes:

• Run Perform Repo Maintenance from the Command Palette. This executes git maintenance run to optimize the repository’s internal data structures.
• Set the Auto-fetch interval to 0 in Preferences > General to disable automatic background fetches.
• Lower the Max Commits in Graph value in Preferences > General to reduce the number of commits rendered.
• Delete unnecessary local branches to reduce reference overhead.
• If Git LFS is in use, run an LFS prune to clean up unreferenced objects.
• Clone a fresh copy of the repository to a clean directory if the local copy has accumulated issues.

macOS users on version 11.5.1: Confirm the installed build matches your chip type (Apple Silicon or Intel) by checking the GitKraken menu. Download the correct version from gitkraken.com if there is a mismatch.

If problems persist after these steps, contact GitKraken support.

How to improve performance

Performance issues are commonly linked to large repositories with many references. Try these steps to improve responsiveness:

Repository-level actions

• Use the Perform Repo Maintenance command from the Command Palette. This runs git maintenance run, which may take several minutes on large repos.
• Run git gc in your local repository.
• Clone a fresh copy of the repository to a new directory.

Interface optimization

• Disable auto-fetch by setting the Auto-fetch interval to 0.
• Reduce the number of commits shown in the graph by setting a lower Max Commits value.
• Solo or Hide branches and tags to reduce visual complexity.

Cleanup and maintenance

• Delete unnecessary local branches.
• If using Git LFS, perform an LFS prune.
• Run git status to check for unexpected working directory states.
• Restart GitKraken Desktop daily to clear any accumulated memory or cache usage.

How to verify your GitKraken Desktop build on macOS

Some Mac users have noticed that GitKraken Desktop 11.5.1 may feel less responsive. In most cases, the Mac installed the wrong build for the machine’s chip (Intel vs. Apple Silicon).

It’s an easy check:

1. Open GitKraken. Navigate to the GitKraken menu from the top left of your machine.

   

2. Confirm the build matches your Mac’s chip (Apple Silicon/arm64 vs. Intel/x64).

3. If it doesn’t match, download the correct version and reinstall.