Status: 1.5.1, available from all three sources#
Open Desktop Authenticator 1.5.1 is available from three official download sources: Microsoft Store, GitHub and Softonic. Choose a Windows installer, portable build or x64 Linux package on the download page. Published packages and platforms tested by a person are listed separately there.
Current limits: builds are not yet reproducible and no independent audit has happened. Read the release and testing details.
Code signing policy: signed Windows downloads, Store package signing, Linux verification and checksum-list signatures — read it here.
What it does#
Steam Guard codes#
The five-character code, regenerated every thirty seconds, with the time remaining shown as it drains. Copy puts it on the clipboard and attempts to clear that entry on a timer. Clipboard history and other apps' copies are outside that clearing.
Trade and market confirmations#
Approve or cancel the confirmations Steam would otherwise send to a phone. Optional automatic confirmation is limited to market listings and trades, and cannot be widened to cover account-recovery requests.
Import from SDA#
Reads .maFile accounts, including encrypted ones with their
manifest.json. Nothing is written to your vault until you
choose what to keep. How importing works.
An encrypted vault#
Secrets are sealed with a key derived from your passphrase using scrypt, then encrypted with AES-256-GCM. The vault locks itself when you stop using it. The full security model.
Adding a new authenticator#
Move Steam Guard onto this app for an account that does not have an authenticator yet, including the revocation code you must write down and confirm you have saved outside this computer. Complete Steam's separate activation challenge as shown by the app.
Recovery that exists in advance#
Encrypted account recovery files are created during import, enrollment and transfer, and retained after a vault entry is removed. They need the passphrase used when written. Keep an independent backup: a file on the same disk cannot protect you from losing that disk.
Find us on AlternativeTo
Explore our listing, compare alternatives, and share your experience with ODA.
Available on Softonic
Find Open Desktop Authenticator for Windows on Softonic, published by MASTERPANEL LLC. Softonic displays “Trusted Program” and “Official distributor” on our listing.
Softonic reports a clean VirusTotal scan and confirms authorization to distribute ODA. Its download is the Windows x64 installer. Compare all three sources and read what the labels mean.
Why this exists#
ODA provides a desktop workspace for people who already manage Steam accounts and maFile backups on a PC. It is a separate implementation, with its own source, release process and support. The original Steam Desktop Authenticator and ODA are different projects; that guide links the genuine original and explains your choices, including Valve's official mobile app.
Using a desktop authenticator puts the Steam session and its second factor on the same computer. If you do not need that workflow, use Steam Mobile on a separate phone. If you choose ODA, review its security model, verify the download and keep an independent backup before importing accounts.
What it will not do#
- No ODA backend. No ODA account. No cloud sync. No telemetry. Steam operations you request contact Valve and send the data needed for that operation. In a direct build from GitHub or Softonic, the optional update check asks GitHub's public releases API whether a newer version exists; GitHub receives that request and its source IP, but no Steam account or vault data. Store builds do not perform that GitHub check. The in-app browser is the deliberate exception: its web pages have no vault API access and can load external resources. The browser holds login cookies scoped to Steam domains so Steam pages open signed in; those cookies are not sent to arbitrary third-party sites. The selected browser route determines which traffic uses the account's proxy; Steam-only mode permits specified third-party sites to connect directly. The routed in-app browser is available in GitHub 1.5.1 and Microsoft Store 1.5.1. The security model sets out what each part can access.
- Direct downloads are updated manually. If enabled, the GitHub update check reports a newer version and links to its release; it does not download or install it. The Microsoft Store manages updates for the Store edition, subject to your Store settings.
- It never auto-confirms an account-recovery request. Automatic confirmation works from a fixed allowlist of two types — trades and market listings — and account recovery is not on it and cannot be added by a setting. Those two types can still move items and money, which is why the feature is off until you turn it on, per account, and why the security model describes what it costs you.