Developer Tools · head to head
GitHub Desktop vs Preact

GitHub Desktop
Developer Tools
A free, open source Git client from GitHub for Windows and macOS that covers common workflows rather than all of Git.
- From
- Free
- Free plan
- Yes

Preact
Web Development
3kB alternative to React with the same modern API
- From
- Free
- Free plan
- Yes
The short version
- Both are free.
- Only GitHub Desktop lists line-level staging; only Preact lists 3kB runtime.
- Where Preact falls short: compatibility through preact/compat is good but not total, and some React libraries break in ways that are hard to diagnose.
- Prices and features on this page were last checked on 13 November 2026.
Where they differ
Only the attributes on which GitHub Desktop and Preact actually diverge.
| Attribute | GitHub Desktop | Preact |
|---|---|---|
| Pricing model | Free | Open source, no licence fee |
| Platforms | Windows, macOS | Web |
| Category | Developer Tools | Web Development |
Identical on both: starting price (Free), free tier (Yes).
Not yet recorded: founded for Preact.
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in GitHub Desktop
- Line-level staging
- Branch and merge UI
- Pull request integration
- Enterprise authentication
- Squash and reorder
- Drag cherry-pick
- Co-author attribution
- Editor and shell handoff
Only in Preact
- 3kB runtime
- preact/compat
- Same modern API
- Fast rendering
What people use each for
The jobs each tool is most often brought in to do.
GitHub Desktop
- Onboarding designers or technical writers who need to commit to a docs or assets repository without learning the command linenot Preact
- A new engineer's first weeks, where seeing the diff and the branch state visually prevents the common early mistakesnot Preact
- Reviewing a colleague's pull request branch locally with a readable diff before approving itnot Preact
- Small teams standardised entirely on GitHub who want SSO-backed authentication to work without managing personal access tokens by handnot Preact
Preact
- Embedded widgets that load inside someone else’s page and must stay smallnot GitHub Desktop
- Marketing and content sites where JavaScript payload affects Core Web Vitalsnot GitHub Desktop
- Applications targeting low-bandwidth or low-powered devicesnot GitHub Desktop
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
GitHub Desktop
- There is no official Linux build; the application ships for Windows and macOS only, and the community fork at shiftkey/desktop that packages it for Linux is maintained separately and lags official releases, so a mixed-OS team cannot standardise on one client
- Submodules are effectively unsupported: the app shows a submodule change as an opaque single line and gives you no way to initialise, update or navigate into it, so any repository using them needs the terminal anyway
- History rewriting is limited to squashing and reordering local commits by drag and drop; interactive rebase, fixup chains, editing an old commit's contents and bisect are all absent, which is exactly the set of operations a beginner needs help with most
- Pull request features only exist for GitHub remotes, so a team on GitLab or Bitbucket gets a plain Git client with an empty pull request pane and no review or checks view at all
- Commit signing with a key that requires a passphrase generally fails, because the app cannot surface the pinentry prompt, and the resulting error message does not say that is the cause
- GitHub staffs it lightly compared with its web and CI products, so long-standing feature requests and bugs sit open for years; if you file an issue you should plan around it rather than expect a fix
Preact
- Compatibility through preact/compat is good but not total, and some React libraries break in ways that are hard to diagnose
- Behavioural differences from React exist in edge cases, particularly around event handling
- A much smaller community, so unusual problems have fewer existing answers than React
Pricing, plan by plan
GitHub Desktop
Free- FreeFree
- Git repository management
- GitHub integration
- Visual diff tools
Preact
Free- PreactFree
- Full library
- Commercial use permitted
- No usage limits
Which should you pick?
Choose GitHub Desktop if
- You need line-level staging.
- You want to start without paying.
- You work on Windows, macOS.
- You also want branch and merge ui.
Choose Preact if
- You need 3kb runtime.
- You want to start without paying.
- You also want preact/compat.
Questions people ask
- Is GitHub Desktop or Preact better?
- Neither clearly leads. GitHub Desktop starts at Free and Preact at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, GitHub Desktop or Preact?
- GitHub Desktop starts at Free and Preact at Free.
- Does GitHub Desktop or Preact run on more platforms?
- GitHub Desktop runs on Windows, macOS. Preact runs on Web.
- Can I use GitHub Desktop for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is GitHub Desktop best used for?
- GitHub Desktop is most often used for onboarding designers or technical writers who need to commit to a docs or assets repository without learning the command line, a new engineer's first weeks, where seeing the diff and the branch state visually prevents the common early mistakes, reviewing a colleague's pull request branch locally with a readable diff before approving it, small teams standardised entirely on github who want sso-backed authentication to work without managing personal access tokens by hand. Of those, onboarding designers or technical writers who need to commit to a docs or assets repository without learning the command line and a new engineer's first weeks, where seeing the diff and the branch state visually prevents the common early mistakes are not what Preact is typically brought in for.
- What can GitHub Desktop do that Preact cannot?
- GitHub Desktop covers Line-level staging, Branch and merge UI, Pull request integration, Enterprise authentication. Preact covers 3kB runtime, preact/compat, Same modern API, Fast rendering.
Answered from the vendors’ own pages
GitHub Desktop: Is there a Linux version?
Not an official one. GitHub ships Windows and macOS builds only. A community fork, shiftkey/desktop, produces Linux packages, but it is maintained by volunteers and trails the official releases.
Preact: Is Preact free?
Yes, open source under the MIT licence.
GitHub Desktop: Does it work with GitLab or Bitbucket?
For plain Git operations, yes: you can clone, commit, push and pull against any remote. The pull request, review and checks features only work against GitHub.com and GitHub Enterprise.
Preact: Can I use React libraries with Preact?
Most, through the preact/compat layer. Compatibility is good but not complete, so libraries relying on React internals can break.
GitHub Desktop: What does it cost?
Nothing. It is free and the source is published under the MIT licence, and it is separate from any GitHub plan you may or may not pay for.
Preact: Why choose Preact over React?
Bundle size, almost always. If payload is not a binding constraint, React’s ecosystem is usually the better trade.
GitHub Desktop: Will it handle submodules?
No. Submodule changes appear as an unreadable single-line diff and there are no controls for initialising or updating them. Repositories that use submodules need the command line.
GitHub Desktop: Do I still need to learn Git?
For everyday work, no. For recovery, yes. Anything beyond the curated set of operations, including interactive rebase and reflog recovery, happens in the terminal, so a team using it should have at least one person who knows Git properly.
GitHub Desktop: Does it work with GitHub Enterprise Server?
Yes. It signs in to GitHub Enterprise Server and GitHub Enterprise Cloud as well as GitHub.com, and it honours organisations that enforce SAML single sign-on.
Related pages
More on GitHub Desktop
Other head to heads
- GitHub Desktop vs GitLab
- GitHub Desktop vs Postman
- GitHub Desktop vs Atlantis
- GitHub Desktop vs Depot
- GitHub Desktop vs JetBrains Rider
- GitHub Desktop vs Claude Code
- GitHub Desktop vs RAD Studio
- GitHub Desktop vs Docker
- GitHub Desktop vs Earthly
- GitHub Desktop vs Jenkins
- GitHub Desktop vs Deep Code
- GitHub Desktop vs Ansible
- GitHub Desktop vs Buildkite
- GitHub Desktop vs Helix
- GitHub Desktop vs Neovim
- GitHub Desktop vs pnpm
- GitHub Desktop vs JetBrains IntelliJ IDEA
- GitHub Desktop vs Tilt
- GitHub Desktop vs React
- GitHub Desktop vs SolidJS
- GitHub Desktop vs MUI
- GitHub Desktop vs Bootstrap
- GitHub Desktop vs esbuild
- GitHub Desktop vs Lit
- GitHub Desktop vs Docusaurus
- GitHub Desktop vs Vue.js
- GitHub Desktop vs Angular
- GitHub Desktop vs MySQL
- GitHub Desktop vs Radix UI
- GitHub Desktop vs shadcn/ui
- GitHub Desktop vs Vercel
- GitHub Desktop vs Alpine.js
- GitHub Desktop vs Astro
- GitHub Desktop vs Carrd
- GitHub Desktop vs HTMX
- GitHub Desktop vs Node.js
- Preact vs GitLab
- Preact vs Postman
- Preact vs Atlantis
- Preact vs Depot
- Preact vs JetBrains Rider
- Preact vs Claude Code
- Preact vs RAD Studio
- Preact vs Docker
- Preact vs Earthly
- Preact vs Jenkins
- Preact vs Deep Code
- Preact vs Ansible
- Preact vs Buildkite
- Preact vs Helix
- Preact vs Neovim
- Preact vs pnpm
- Preact vs JetBrains IntelliJ IDEA
- Preact vs Tilt
- Preact vs React
- Preact vs SolidJS
- Preact vs MUI
- Preact vs Bootstrap
- Preact vs esbuild
- Preact vs Lit
- Preact vs Docusaurus
- Preact vs Vue.js
- Preact vs Angular
- Preact vs MySQL
- Preact vs Radix UI
- Preact vs shadcn/ui
- Preact vs Vercel
- Preact vs Alpine.js
- Preact vs Astro
- Preact vs Carrd
- Preact vs HTMX
- Preact vs Node.js
