View Diffs, File History, and Blame in GitKraken Desktop
Last updated: November 2026
Use this page to compare uncommitted changes, inspect commit diffs, switch between diff views, review file history or blame, set up an external diff tool, and create or apply patches in GitKraken Desktop.
Key constraints
- Patch support: Patch creation and application are preliminary features
- Binary files: GitKraken Desktop does not generate patches from binary files
- External diff tools: Beyond Compare, FileMerge, Kaleidoscope, KDiff, Araxis, and P4Merge are supported directly
- Other tools: Use Git Config Default and your global
.gitconfigif your preferred diff tool is not listed in Preferences
Quick Start
To view a diff:
- Click a file in the staging area (WIP node) to see your uncommitted changes.
- Click a commit in the graph, then click any file in the Commit Panel to view that commit’s changes.
- Select 2 commits with Shift + click to compare them directly.
To switch diff view modes, use the Hunk, Inline, or Split toggles in the diff viewer. To revert a specific block of changes, use the Revert Hunk button in Hunk view.
To view file history or blame:
- Open the diff for any file and click the History or Blame button in the upper-right corner.
- Or right-click a file after selecting a commit in the graph.
To create or apply a patch:
- Right-click a commit and select Create patch from commit.
- To apply a patch, open the Command Palette (Cmd/Ctrl + P), type
Apply patch, and select your.patchfile.
To use an external diff tool, go to Preferences > External Tools and select your preferred application.
To review what a coding agent changed across its commits and worktree, see Review and Undo AI Coding Agent Changes.
What Is a Diff in GitKraken Desktop?
A diff displays lines added and removed from a file:
- Red indicates removed lines.
- Green indicates added lines.
Use the built-in diff when: you want to inspect changes, compare commits, or review file history directly in GitKraken Desktop. Use an external diff tool when: you need a specialized comparison workflow that is not covered well by the built-in viewer.
The built-in diff viewer in GitKraken Desktop includes:
- Word diffing
- Syntax highlighting
- File mini-map
- Toggleable views: Hunk, Inline, Split
- Word wrap toggle
- Arrows to navigate between change sets
Use the button to edit the file directly. See Editing Files.
Where Can I Access the Diff?
You can view diffs from:
- Staging area: Click a file to open its diff
- Commit node: Select a commit and click any file
- GitHub pull request: Right-click a pull request in the Left Panel’s Pull Requests section, or a branch that has a pull request, and select View changes in #N
Selecting 2 commits shows the differences between them.
View changes in #N is available for GitHub and GitHub Enterprise pull requests. It selects the pull request’s base and head commits in the graph, and the Commit Panel shows every change in the pull request. If the pull request comes from a remote you have not added, such as a fork, GitKraken Desktop asks to add that remote first. If the base or head commit is not loaded in the graph, scroll down or increase Initial Commits in Graph in Preferences > General, then try again.
Select consecutive commits in the graph using Shift or Cmd/Ctrl + click to show their combined changes in the Commit Panel, titled Viewing diff of N commits. You can include the WIP if your selection reaches the latest commit. If you select more than 2 nonconsecutive items, GitKraken Desktop explains why it cannot show a combined diff, and the AI actions for the selection are hidden.
When to use Hunk View
Hunk View displays only the changed blocks of a file.
Use Hunk View when: you want to focus only on changed blocks or revert a specific hunk quickly. Do not use it when: you need full-file context around the changes.
How to revert a hunk
In Hunk View, you can roll back a specific block of changes. Click the Revert Hunk button next to any hunk to apply an equal and opposite change to your working directory.
You revert only the hunk you choose, without a reset or manual edits.
When to use Inline View
Inline View displays changes within the full context of the file.
Use Inline View when: you want to read edits in the flow of the full file. Do not use it when: side-by-side comparison is easier for the change you are reviewing.
When to use Split View
Split View displays changes side-by-side, with the original file on the left and the updated version on the right.
Use Split View when: you want to compare old and new content line-by-line. Do not use it when: you want a more compact, single-column review for small changes.
How to use Word Wrap in the diff view
The Word Wrap toggle wraps long lines in the diff view so that the full content of each line is visible without horizontal scrolling. Use it to review files with long lines, such as Markdown documents, minified JavaScript, or LaTeX files.
To toggle word wrap, click the Word Wrap button in the toolbar of the diff view, file view, file history, or merge conflict resolution panel.
How to use external diff tools
Configure an external diff tool in Preferences External Tools:
Use an external diff tool when: you already rely on a supported third-party app or need its advanced comparison features. Do not use an external tool when: GitKraken Desktop’s built-in diff already gives you the context and controls you need.
Supported tools include:
- Beyond Compare
- FileMerge
- Kaleidoscope
- KDiff
- Araxis
- P4Merge
If a supported tool does not appear in the dropdown, verify that its command line tools are installed.
To use a different diff tool, go to Preferences External Tools and set External Diff Tool to Git Config Default. Then add the appropriate configuration in your global .gitconfig:
macOS
[diff]
tool = meld
[difftool "meld"]
cmd = open -a Meld --args "$LOCAL" "$REMOTE"Linux
[diff]
tool = meld
[difftool "meld"]
cmd = meld "$LOCAL" "$REMOTE"Windows
[diff]
tool = meld
[difftool]
prompt = false
[difftool "meld"]
cmd = meld "$LOCAL" "$REMOTE"How to compare a WIP against another commit or branch
To compare your Work in Progress (WIP) with another commit or branch:
- Use Ctrl/Cmd + click to select the WIP and another commit
- Or, right-click a commit or branch and select Compare commit against working directory
How to view file blame and history
To view a file’s history or blame, open its diff and click History or Blame in the upper-right corner.
Alternatively, right-click a file after selecting a commit in the graph.
Blame view color-codes each line or hunk by author.
Use the toggle in the top-right to switch between Diff View (showing changes) and File View (showing the full file with blame).
How patch files work in GitKraken Desktop
Use patches when: you need to share changes without pushing them to a remote. Do not rely on patches for binary files: GitKraken Desktop does not generate patches from binary files.
A patch (or patch file) records the differences between files. Use patches to share changes without pushing them to a remote repository.
How to create a patch from files or commits
To create a patch:
- Right-click a commit and choose Create patch from commit
- Right-click a file and choose Create patch from file changes
GitKraken Desktop asks you to name the patch file.
You can also multi-select files or commits using Shift or Cmd/Ctrl + click, then right-click to create a patch. For selected commits, the patch contains the same combined changes shown in the Commit Panel. If GitKraken Desktop cannot show a combined diff for the selection, the patch action is unavailable.
How to create a patch from the Command Palette
Launch the Command Palette from the toolbar or with Cmd/Ctrl + P, then search for “Create patch”.
How to apply a patch from the Command Palette
To apply a patch:
- Open the Command Palette (Cmd/Ctrl + P).
- Type “Apply patch” and select the command.
- Choose your
.patchfile in the file explorer.
Note: GitKraken Desktop does not generate patches from binary files. Patch support is a preliminary feature. For feedback, contact the GitKraken support team.