Open Desktop Authenticator

Move your Steam authenticator from your phone to a PC

Reviewed by MASTERPANEL LLC 3 min read Sources and testing: Phone policy checked against Valve's Steam Guard FAQ; ODA steps against its transfer screen. Outcomes are scoped to the historical one-account test record, not a new release test Editorial method

Open Desktop Authenticator can replace a phone authenticator with one stored in its PC vault. You need the current authenticator for sign-in and access to the linked phone number. If you already have a usable SDA maFile, import it instead; copying an existing secret does not require this transfer.

Before you start

Do not remove the authenticator from your phone first. A successful transfer replaces it on Steam's side: the old secrets stop working. Save the new recovery code and complete the recovery-backup step before relying on the PC.

This desktop workflow is unofficial. Valve documents a two-day restriction for its phone-to-phone route. One historical ODA transfer received that short restriction; it is not a promise for your account. Check Steam's resulting notice.

What you need before starting#

If the current authenticator is already lost, start with Steam's recovery options. Do not remove and re-add it just to satisfy these prerequisites.

Move from phone in ODA#

Yes — the transfer is built into the published application. It uses the flow described below and never substitutes remove-and-add.

  1. Unlock the vault and choose Move from phone.

    Check the account name, complete sign-in with the current authenticator and read the replacement warning.

  2. Request and enter the phone code.

    Use only the code for the transfer you started. Enter it in ODA, not a message's link or a third-party support chat.

  3. Save the new recovery code.

    At this point Steam has already replaced the authenticator. Record the new code away from this PC, acknowledge it in ODA, and finish any encrypted recovery-backup warning. Do not rely on the old recovery code.

  4. Select Done, then check the account.

    After saving the recovery information, return to the account list. Confirm a fresh code is accepted at a Steam sign-in you initiate. Check Confirmations separately and read Steam's trade/Market notice. A working login code does not prove approval of a trade has been tested.

If the transfer stops#

Sign-in fails before the phone-code step
Check the account and current Guard code. Pause if Steam reports too many attempts. Do not remove the phone authenticator.
No phone code arrives
Confirm access to the linked number and follow Valve's delivery troubleshooting. Repeated requests can delay delivery; some regions use Telegram for the linked number.
Timeout or storage error after submitting the phone code
Steam may already have replaced the authenticator. Follow ODA's recovery screen instead of starting a new transfer. If it says the replacement is only in memory, keep ODA open and use Finish recovery after correcting the reported storage problem.
Vault saved, separate backup still pending
Save the displayed recovery code and use the offered recovery-backup retry. Retain the vault and passphrase; a backup warning does not mean Steam reversed the transfer.

If no usable authenticator or retained recovery material remains, use Steam Support.

What changes on Steam, and what has been tested#

The replacement flow issues new authenticator secrets rather than extracting the old ones from the phone. The previous authenticator no longer works after replacement. Removing an authenticator is a separate operation with a 15-day trade and Market restriction.

The project's historical live-test record covers one account: Steam accepted the new codes, the old phone's authenticator was removed, its sessions signed out, and the short restriction was observed. That run fetched an empty confirmation list; it did not approve a real confirmation with the transferred secret. This is retained evidence, not a new test of the latest release.