Stacked flashcards and review-tick panel listing Windows MSI, winget, Homebrew cask, and AGPL licence doors.
Verified doors: Windows win-x64 MSI on current tags, verified winget and Homebrew cask doors. Deck Quill original card-stack geometry for this install guide (not an upstream project logo).

By Deck Quill editorial team · Last verified [date] · Current release [tag]

Download the Linux tarball

Open [GitHub Releases](https://github.com/the upstream repository/releases) for the current non-prerelease tag. Download linux-x86_64.tar.zst for typical 64-bit desktops. Map: releases.

Extract and install

Extract the archive, change into the folder, and run sudo ./install.sh. Keep the downloaded tarball hashed beside the machine note so updates replace a known file.

tar xaf anki-*-linux-x86_64.tar.zst && cd anki-*-linux-x86_64 && sudo ./install.sh

After install

Create one deck, add a few Basic cards, and prove Study Now. First hour: installed. Optional sync: optional cloud sync.

Shared lab note

Write the tarball name and architecture on the lab card. After imaging, prove one review before demos. Prefer the same Releases door next update.

Windows and macOS doors stay MSI/winget and dmg/brew. Do not paste Linux install.sh onto a Windows ticket.

Lab checklist without drama

Shared rooms move faster when the ticket names the installer door, the OS build, and the exact symptom. Attach a screenshot of the Decks list when reviews look wrong. Mention whether sync toggled during the failure.

Borrowing a random USB installer from a drawer is how adware returns. Prefer a hashed copy on trusted media or the same package id the fleet already allows. When package managers are blocked, the Releases asset is the honest fallback.

Trainers should rehearse the prove step on a tiny local deck so demos stay short. Students learn the habit faster when the checklist fits on an index card. Overnight monitors appreciate a note that says whether cloud sync is expected on that image.

When a semester ends, uninstall from machines that leave the pool and clear local collections per retention rules. Keep checksum verification optional for threat models that require hashes from the same tag.

Imaging season notes

Golden images should freeze only after a reboot and a prove-one-review step. Login scripts that delay first launch hide broken Start Menu shortcuts. Antivirus first scans that quarantine a fresh installer need a known exception path written for the helpdesk.

Internal runbooks should quote the package id, the brew cask, and the Releases URL without marketing adjectives. Staff skim under stress. A short checklist with five boxes outperforms a long essay nobody finishes.

Include a rollback line: where the previous installer lives, how to uninstall, and who owns the software library hash list. Rollback plans fail when the only copy sat on a retired laptop.

Translate jargon for volunteers. Say use the official GitHub installer file instead of assuming everyone knows which mirror is safe. Clarity beats cleverness during the first week of a new semester.

Frequently asked questions

How do I install anki on Linux?

Download anki-*-linux-x86_64.tar.zst from a non-prerelease tag, extract it, then run sudo ./install.sh from the extracted folder. An aarch64 tarball also ships on the same tag. Prefer official GitHub Releases or the verified package doors, then prove one review after install.

Should I use a distro package instead?

Distro packages can work, but they may lag the GitHub tag your runbook pins. The official tar.zst keeps Linux desks on the same door as Windows MSI and macOS dmg assets. Prefer official GitHub Releases or the verified package doors, then prove one review after install.

What about linux-aarch64?

Take anki-*-linux-aarch64.tar.zst on ARM64 Linux machines. Default x86_64 desks should prefer the linux-x86_64 tarball. Prefer official GitHub Releases or the verified package doors, then prove one review after install.