By Deck Quill editorial team · Last verified [date] · Current release [tag]
Sync is optional
the client installs as a local spaced repetition client. You can study without an account. the sync service adds backup and multi-device sync when you choose it.
Related: first run, installed, is it safe.
Preference path
Open Tools → Preferences and review Syncing options. Keep media sync decisions written on the lab card when shared machines use the same the sync service account.
Safety habits
Use a unique password for the sync service. Do not paste credentials into random download portals. The install door stays GitHub Releases, winget, or brew even when sync is enabled.
When to skip sync
Air-gapped labs and exam rooms often keep sync off. Local collections still schedule reviews. Document the choice so substitutes do not force a login during a demo.
Update door stays separate
Upgrade with the same MSI, winget, or brew door you used to install. Sync conflicts are a different ticket from a broken installer. Guide: update and uninstall.
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
Do I need the sync service to use anki?
No. Local decks and reviews work offline after install. the sync service is optional backup and multi-device sync. Prefer official GitHub Releases or the verified package doors, then prove one review after install.
Where do I turn on sync in anki?
Open Tools → Preferences and use the Syncing options, or follow the Sync button in the main window after you create an the sync service account. Prefer official GitHub Releases or the verified package doors, then prove one review after install.
Is the sync service the same as the Windows MSI?
No. The MSI, winget id Anki.Anki, and brew cask anki install the desktop app. the sync service is the optional sync service. Prefer official GitHub Releases or the verified package doors, then prove one review after install.