GnuCash 5.x: double entry accounting you run yourself
GnuCash Double-Entry Accounting Program.
At a glance
- What is it?
- GnuCash is a C application for personal and small business bookkeeping that keeps its books in a plain file on your own disk. Its accounting engine is strict, its install path splits neatly between packaged builds and a CMake source build, and it asks you to understand double entry before it will let you record anything.
- Who is it for?
- Adopt GnuCash if you want a locally run accounting application and accept learning double-entry bookkeeping. You can use prebuilt packages without maintaining its source code.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly C, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 14, 2026, and from our analysis. They are not legal advice.
Star history
- Gnucash/gnucash4,412 ★ · +58
| Repository | 2026-09-23 | 2026-11-14 |
|---|---|---|
| Gnucash/gnucash | 4.4k | 4.4k |
58 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Every transaction passes through the double entry ledger engine
GnuCash targets one job: keeping personal and small business books in double entry form. That constraint explains most of its behaviour, including the parts that frustrate people arriving from single entry tools. A transaction is not a row in a spreadsheet. It is a set of postings whose debit and credit sides have to balance before the ledger accepts it.
The consequence is that the audit trail is structural. You cannot record a transaction that moves money without saying which accounts moved, and the accounts themselves carry types that decide how they behave. Closing a period, generating a balance sheet and producing a profit and loss statement are all reports over data that was already constrained at entry time.
That model is the reason a book in GnuCash survives a year of sloppier handling than most, provided the opening balances were right. It is also the reason the first hour is slow. A spreadsheet will accept a number you meant to fix later; the ledger will not.
Local files and database storage options
GnuCash supports XML and SQLite files, as well as MySQL and PostgreSQL server storage when configured with the required drivers. Invocation takes the program name and, optionally, that filename. Files ending in .gnucash are native account files and open through the Open File menu entry. Files ending in .qif are Quicken Import Format and open through Import QIF, which is the migration path for people leaving a commercial tool.
Sample account files ship in the repository under doc/examples, so a new user can open something populated rather than staring at an empty chart of accounts. That detail matters more than it sounds. A sample file demonstrates the shape of the data faster than any manual.
The close-reading catch here is the mismatch between what the program claims to be for and what it ships as a distribution story. The description calls it a personal and small business application, yet the README relies on distribution packagers for GNU/Linux and *BSD binaries apart from the Flathub flatpaks. A small business tool whose packaging you do not control is a different product from one with a signed installer.
GNUC_BOOTSTRAP_SCM and friends are startup overrides, not configuration files
GnuCash is a Guile program inside a C application, and its environment variables exist to relocate parts of that load path during startup. GNC_BOOTSTRAP_SCM names the location of the initial bootstrapping scheme code. GUILE_LOAD_PATH overrides the load path used when loading scheme files, and GNC_MODULE_PATH does the same for GnuCash modules. Both expect a string in the same form as PATH or LD_LIBRARY_PATH.
A fourth variable, GNC_DEBUG, turns on debugging output earlier in startup than the --debug flag can reach. The distinction is worth knowing before you chase a problem: the command line flag misses the earliest phase, the environment variable does not.
None of these are settings most users will ever touch, and there is no file-based preference system described in the README beyond the account file itself. Chart of accounts, accounts and reports live in the data, not in a config file. That keeps the mental model simple for the common case and pushes anyone with a bespoke deployment into per-shell environment variables, which does not scale past a couple of machines.
Interface language follows the desktop locale when a translation exists, and the README defers the override procedure to the wiki page on locale settings rather than documenting it here. So the localisation story is complete in one direction and thin in the other: automatic by default, manual through a document that is not in this repository.
Installing from source means satisfying CMake, SWIG 2.0.10 and a partial Gnome stack
Precompiled binaries exist, so building is not the first route. Sources and Mac and Windows binaries are hosted on SourceForge and GitHub, with links for the current version on the project site, and Linux flatpaks for x86_64 and arm64 are published on Flathub. If you want something newer than your distribution ships and you will not use a flatpak, the README is direct about the consequence: you have to build from source.
The source path is CMake. Build dependencies live in README.dependencies and are kept current there rather than in the main README. What the main README does pin is the toolchain floor: SWIG 2.0.10 or later, plus cmake, the Gnome development headers and libraries, and libxml2. Ninja is optional, and the README says CMake can generate build rules for it and that Ninja generally gives faster builds than Makefile based ones. You need the Gnome libraries installed, but not a Gnome desktop.
Once configured, the staged install uses DESTDIR, which relocates objects into a staging area rather than the runtime prefix:
make DESTDIR=/tmp/staging installThat places install objects under /tmp/staging, with each path prefixed by the DESTDIR value, which is what package maintainers need when assembling images. After installing, the manpage in doc/gnucash.1 carries the invocation options, and the program itself answers the same questions:
gnucash --helpOne wrinkle worth naming: if you have split Gnome across prefixes, the README tells you to set GNOME_PATH and GNOME_LIBCONFIG_PATH and points at the gnome-config manpage. That is the point at which a clean source build turns into an afternoon.
Online price quotes depend on Perl, and Windows needs it installed for you
The optional online stock and currency price retrieval feature is not native code. It runs through Perl, and Perl modules have to be installed alongside it. On Gnu/Linux, *BSD and macOS Perl is generally already there, so the cost is the modules rather than the interpreter.
Windows and macOS handle that differently. Microsoft Windows users are told to run the "Install Online Quotes" program from the Start menu Gnucash group, which installs Perl and the required modules more or less automatically. macOS users find "Update Finance Quote" inside the distribution disk image, which automates running the same updater:
gnc-fq-updateThe README says to run that script as root to obtain the latest versions of the required packages. That is a genuinely awkward instruction in 2026, and it is also the honest state of the feature: quote retrieval is maintained outside the C tree, through a scripting layer with different packaging rules on each platform. If your accounting needs live prices, budget for the setup rather than assuming a checkbox will do it.
The deeper limitation is scope. GnuCash is described as a personal and small business accounting application.
Five platforms are named, and everything else is left to the mailing list
The README names what GnuCash 5.x is known to work with: GNU/Linux on x86_64 and arm64, FreeBSD on x86_64, OpenBSD on x86_64, macOS on x86_64 at version 10.13 and later plus Apple Silicon, and Windows 11 on x86. Beyond that list the README says the project can probably be made to work on any platform where Gtk+ works and a C++11 compiler is available, given sufficient expertise and effort, and mentions having heard of Linux builds on Sparc, PowerPC and IBM s390x hardware.
Read that last part carefully, because it is the failure mode stated plainly. Unsupported hardware is not blocked by a build error. It is blocked by nobody being there when your build breaks, and the fallback the README offers is a mailing list, [email protected].
The platform list also explains the packaging gap. Because the project does not ship Linux and BSD binaries itself and relies on distribution packagers, the version you get depends on your distribution's release cycle. A distribution that ships 5.11 will keep shipping 5.11 while the project publishes 5.17, and the gap between those two numbers is where upgrade friction lives. Flatpak is the documented way to close it on x86_64 and arm64 Linux, which makes that the sensible first check for anyone whose distribution lags.
The repository itself is not small. Alongside the C sources in gnucash/ and libgnucash/ it carries bindings/, po/ for translations, util/, contrib/, doxygen configuration, and an unbroken run of ChangeLog files from ChangeLog.1999 through ChangeLog.2025. Twenty-seven years of accumulated history is evidence of a working release process, and also of how much surface a contributor has to get familiar with before touching anything.
Where the alternative sits: server ledgers versus the local file
The comparison people actually make is with Quicken-style tools and with QuickBooks, and the difference is not features, it is where the ledger lives. QuickBooks offers hosted products, while GnuCash runs as a desktop application and supports local XML or SQLite files and configured MySQL or PostgreSQL storage. Backups must cover the selected storage backend.
That buys two things and costs one. You gain a project you can read, audit and archive for as long as you keep the format, with no vendor deciding when your historical access ends. You gain a program whose accounting rules do not loosen because a subscription lapsed.
For a sole proprietor with a desktop, that trade is easy. For a household with two people both entering receipts, or a business with a bookkeeper and an owner with separate logins, it is disqualifying, and no amount of configuration changes the arithmetic.
On the timeline question: the last push to the repository was on 2026-11-02, and the 5.x series is running with 5.17 released on 2026-09-27 after 5.16 in June and 5.15 in March. That cadence says the project is still shipping, and it says nothing about the version your Linux distribution packaged last year.
Editorial conclusion
Adopt GnuCash if you want a locally run accounting application and accept learning double-entry bookkeeping. You can use prebuilt packages without maintaining its source code. Do not adopt it if you need a browser-based multi-user ledger or a paid support contract. Verify first that the package your distribution ships is close enough to the 5.x series you need, because the project hands Linux and BSD binaries to packagers rather than building them itself.
Frequently asked questions
Is GnuCash really free?
The project is a personal and small business double entry accounting application distributed as free software, with sources and Mac and Windows binaries hosted on SourceForge and GitHub and Linux flatpaks on Flathub. There is no paid edition described in the repository.
Can GnuCash replace QuickBooks?
GnuCash is positioned as a personal and small business double entry accounting application, and its data lives in a local .gnucash file rather than a hosted account.
How do I install GnuCash?
Precompiled binaries and sources are on SourceForge and GitHub, and Linux flatpaks for x86_64 and arm64 come from Flathub. Anything newer than your distribution packages means building from source with CMake and SWIG 2.0.10 or later, plus the Gnome development libraries.
How do I use GnuCash for small business?
Create or open a native .gnucash account file, which you can pass to the program at the command line or open through the Open File menu entry. Sample account files sit in doc/examples if you want a populated chart of accounts to start from rather than an empty one.
Is GnuCash safe to use?
The project is not archived and the last push to the repository was on 2026-11-02, with 5.17 released on 2026-09-27. Because your books are a local file, the security question is mostly about how that file is copied and backed up rather than about a hosted account.
What are the reviews and complaints about GnuCash?
The repository itself records no user reviews, and the README does not discuss complaints. What the source does show is a desktop application whose online price quotes require Perl and root level module installation, and whose Linux and BSD binaries are supplied by distribution packagers rather than the project.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/gnucash-gnucash)Star history chart for your README
[](https://hysenlabs.com/projects/gnucash-gnucash)Was this useful?