Abstract dictionary book-spine panels with a copper lemma notch on frost paper.
Lemma-spine mark: stacked dictionary spines with one umber lemma cutout for local lookup. Maple Notch original lemma-spine geometry for factory-dictionary (not a GoldenDict logo).

Windows is the primary path for this dictionary guide because GitHub Releases for goldendict/goldendict ships GoldenDict-*-Install.exe plus portable QT_*.7z archives on the same tag. No winget package id was verified here, so stay on those release assets.

Download the installer

Open goldendict/goldendict releases in a new tab. Confirm you are on the current tag, then download GoldenDict-*-Install.exe (about 28 MB on the the current release tag). Refuse any site that renames the setup or bundles a toolbar.

Portable users who cannot run installers can take GoldenDict-*_.QT_5123.64bit.7z (or the other QT_*.7z builds on the same tag), extract with a 7z tool, and launch from that folder.

Run and confirm

Run Install.exe. If SmartScreen warns, prefer the Releases URL you typed yourself over a redirected marketing page. After install, open GoldenDict from the Start menu so the dictionary window appears.

Add packs and index

GoldenDict does not ship commercial lexicon text inside the installer. Open the Dictionaries dialog, add a StarDict, Babylon, Lingvo, Dictd, or MDict folder you are licensed to use, and wait for indexing. Prove one lookup before you enable online sources or hotkeys.

Update door

Return to the same GitHub Releases page for the next Install.exe. Do not stack Softonic-style wrappers. Longer notes: Windows installer notes, download safe, first hour.

Common Windows mistakes

Downloading a twin installer from a review portal is the top failure. Matching the exact filename on GitHub Releases fixes it. Expecting packs to appear automatically is second; add folders yourself. Skipping indexing is third; wait before judging speed. Mixing Install.exe and portable trees on one PATH is fourth; pick one style per machine.

Portable QT builds

The the current release tag includes QT_5123.64bit, QT_5123, and QT_486 portable archives. Prefer 64-bit QT_5123 when your PC supports it. Extract to a folder you own, keep packs outside that folder if you want cleaner updates, and note the build in a short runbook.

After install checklist

Confirm the window opens, add one pack, wait for indexes, look up a known word, and bookmark Releases. Then read first run and is it safe. If policy blocks unknown executables, ask an admin instead of smuggling a random mirror binary.

Why Releases instead of a store page

This guide verified the Install.exe asset names on GitHub Releases and did not verify a winget id. Inventing a store command would mislead readers. When Microsoft or the project publishes a verified package later, re-check with fetch:gh and update the research file. Until then, Releases remains the honest Windows door for this dictionary.

Classroom and shared PCs

Shared labs often block unknown publishers. Document the asset name in your image build notes. Students who need offline packs can use a portable 7z only when policy allows. Keep lexicon licences with the packs so redistribution stays legal.

Network and offline

You need network once to download Install.exe. After packs and indexes live on disk, lookups work offline unless you enable online dictionaries. That split is why a desktop dictionary beats a fragile tab for travel and exam conditions that forbid phones but allow installed software.

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.

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.