Close detail of dictionary spine geometry used as the Dictionary mark.
Spine detail for the Dictionary mark used across this install guide. Maple Notch original lemma-spine geometry for factory-dictionary (not a GoldenDict logo).

Linux readers have three verified doors for this dictionary guide: Flatpak on Flathub (org.goldendict.GoldenDict), the Debian/Ubuntu goldendict package where the archive ships it, and a source build from the upstream README. GitHub Releases for the current release tag do not attach Linux installers, so do not invent an AppImage name.

Flatpak first

flatpak install flathub org.goldendict.GoldenDict

The Flathub appstream id resolves for GoldenDict. After install, launch from your applications menu, add packs in Dictionaries, and prove one lookup. Updates follow your normal Flatpak update habit.

apt alternate

sudo apt install goldendict

Debian sources list a goldendict package across several suites. Versions may lag the GitHub tag. That is acceptable when you want distro integration more than the newest Windows-matching release.

Source build

Install build dependencies from the README (Qt development packages, vorbis, hunspell, and friends). Then:

git clone https://github.com/goldendict/goldendict.git
cd goldendict
qmake
make

Use Qt5 qmake paths when your distro defaults to an older tool. Optional CONFIG flags match the macOS guide.

What to avoid

Random .deb files from blogs, renamed “dictionary converter” installers, and invented snap ids. Prefer Flathub, your distro archive, or a build you compile yourself. Pair with download safe and troubleshooting.

Desktop sessions

GoldenDict expects a desktop session for the GUI. Headless servers are the wrong target unless you only care about compiling. On immutable or managed fleets, Flatpak often fits policy better than a hand-built binary in $HOME.

Packs and SELinux/AppArmor notes

If the window opens but cannot read a pack folder, check permissions and sandbox portals for Flatpak. Grant filesystem access to your lexicon directory, then reindex. Distro packages usually see $HOME without extra prompts.

Choosing among Flatpak, apt, and source

Pick Flatpak when you want a consistent id across distros. Pick apt when you want OS updates to own the package. Pick source when you need optional CONFIG features the packages omit. Document the choice so the next reimage does not guess.

Verify against research notes

  • README and Releases assets
  • Flathub appstream id
  • Debian package listings

Facts on this page come from the goldendict/goldendict README, GitHub Releases tag assets, Flathub appstream for org.goldendict.GoldenDict, and Debian package listings checked on 2026-09-15. If a newer tag appears, prefer the live Releases list and exact filenames over any hard-coded memory of the current release alone. The home install panel reads gh.json at build time so the current release link stays fresh.

Keep one update door

One install style per machine. Write it down.

Pick one install style per machine and write it down. Windows Install.exe users return to GitHub Releases. Portable 7z users replace the extracted folder carefully. Flatpak users run flatpak update. apt users use their distro tools. Source builders pull and rebuild. Mixing three doors on one PATH creates confusing dual launches and stale packs.

Privacy and offline use

  • Local packs keep lookups on disk after indexes build.
  • Online dictionaries are optional network queries.

Local packs keep lookups on your disks after indexes build. Online dictionaries inside GoldenDict are optional and reintroduce network queries. Leave them off for confidential terminology until policy says otherwise. You still need network for the first installer or package download.

Read the download-safe, releases, GitHub, for-this-computer, and installed pages when you need cluster detail beyond this guide. The guides hub lists every how-to in one place.

Practical lab notes

  • Document install style and pack folder path.
  • Share Releases URL or Flatpak id, not random exe drops.
  • Re-download once from the known door when blocked.

Treat the dictionary install like any other signed tool on a shared PC. Write down whether you used Install.exe, a portable QT_*.7z, Flatpak, apt, or a source build, plus the folder that holds your lexicon packs.

Exact names matter: GoldenDict-*-Install.exe on the current release tag, plus org.goldendict.GoldenDict on Flathub. Do not hand people Dropbox copies of unnamed exe files.

If SmartScreen, Gatekeeper-like warnings, or Flatpak portals interrupt you, stop and re-check the source. A second download from a review portal almost never fixes a blocked first file.

  • Give indexes time on spinning disks before restarting.
  • Empty articles usually mean wrong folder depth or unsupported format.
  • Leave online dictionaries off until offline packs cover daily words.

Licence discipline is part of safety. GPL-3.0+ covers the program; pack licences cover the words. For updates, reuse the door you documented. For uninstalls, back up packs first.

Frequently asked questions

Is GoldenDict free?

Yes. GoldenDict the program is free under GPL-3.0+, so you can install it for local dictionary work without a seat fee. Packs you add later may be free or paid under their own licences, which stay separate from the program licence.

Where is the safe download?

Prefer GitHub Releases for goldendict/goldendict when you need the Windows Install.exe or portable 7z builds. On Linux use Flatpak org.goldendict.GoldenDict or apt goldendict. Skip Softonic-style wrappers that rename the setup for a dictionary search ranking.

Do dictionaries ship inside the installer?

No. The installer is only the GoldenDict shell. After install, open Dictionaries and add licensed StarDict, Babylon, Lingvo, Dictd, or MDict folders you already have rights to use, then wait for indexing before you judge speed.