Steam maFiles: where to find them, how to open and import them
Published 23/10/2026
Contents
A maFile stores Steam Guard authenticator data. Apps use its secrets to generate sign-in codes and confirm trades and sales. You may already have these files if you set up Steam Desktop Authenticator or another compatible application for your Steam accounts.
You can inspect an unencrypted maFile in a regular text editor. To import one, you need the file belonging to your account. You cannot download a matching maFile from the internet just by knowing your Steam username.
What is inside a maFile?
An unencrypted maFile contains JSON: field names and their values. The exact contents depend on the application that saved it. The main fields are defined in the SteamAuth source code:
| Field | Contents |
|---|---|
| account_name | The Steam account login name |
| shared_secret | The secret used to generate Steam Guard sign-in codes |
| identity_secret | The secret used to sign trade and market confirmation requests |
| revocation_code | The code used to remove the authenticator |
| device_id | The authenticator device identifier |
| Session | Session data; the fields depend on the application version |
An application needs shared_secret to generate new codes. The code currently displayed in the Steam app expires and does not belong in this field. The identity_secret has a separate purpose: it is used for confirmations.
A maFile usually has no Steam password, so you need to provide it separately. Some apps add a password field.
Where to find Steam maFiles
Steam Desktop Authenticator keeps its maFiles folder beside the application executable. This location is defined in SDA's file storage code. There is no universal path inside the Steam installation: the location depends on where you extracted SDA.
- Open the folder from which you ran Steam Desktop Authenticator.
- Find the
maFilesdirectory. - Copy the whole directory to a protected location before making changes.
- Find the account file in that copy. Its name often follows the pattern
SteamID64.maFile.
You may also see manifest.json. SDA uses it as a file index; entries for encrypted files also contain decryption parameters. Keep it with your folder backup.
If you only use the official Steam mobile app, there is no reason to look for an SDA folder on your computer. Enabling Steam Guard on a phone does not create a maFile beside your desktop Steam installation. Use the official Steam app when setting up a new authenticator.
How to open a maFile
Open a copy with Notepad or another local text editor using “Open with.” Readable JSON has braces and quoted field names such as account_name and shared_secret.
You do not need a dedicated maFile editor to view it. To import it, try uploading the whole file first. Copying long values by hand makes it easier to miss a character or add a space.
If you need to edit a file, work on a copy and preserve its JSON structure. Replacing a secret with a random string will not create valid Steam Guard credentials.
Renaming a file changes only its name. To change account.maFile.txt to account.maFile, first enable file extensions in your file manager and check the full name. The required filename depends on the application you are importing into.
How to handle an encrypted maFile
An encrypted file may look like a long string with no readable fields. SDA has a separate file encryption mechanism. Decryption requires the SDA encryption password and the parameters from the matching manifest.json entry. Your Steam password and encryption password can be different.
If an app needs plain JSON, turn off encryption in the app that created the file and save a copy. Changing the extension does not decrypt it. The ArchiSteamFarm documentation also describes importing an existing SDA file.
The developers of Steam Desktop Authenticator have ended support and warn about fake builds. Do not install a random “updated version” just to open a file.
If you have lost the file or its encryption password, look for a backup. If you have lost access to the authenticator itself, use Steam's recovery process. Downloading someone else's file will not restore your access.
How to import maFiles into Split Team
Upload maFiles when adding accounts in Split Team. The dashboard reads shared_secret, the login name in account_name, and identity_secret if it is present.
- Open Accounts and click “Add account.”
- Switch to the “In bulk” tab and drag your maFiles into the upload area.
- Check the login names in the preview. If a file has no
account_name, enter the login name manually. - Add the Steam password for each row. You can upload a
login:passwordlist alongside the files: the dashboard merges data with matching login names. - Check the rows and click “Add.” The button shows how many accounts will be added.
Signing in with Steam Guard needs a working shared_secret. You can import a file without identity_secret, but that secret is needed for trade and sale confirmations. Enter the Steam password separately if it is not in the file.
The dashboard expects readable JSON with the required fields. It cannot directly import an encrypted SDA file. A readable copy with a .json extension is accepted if its contents contain maFile data.
The old desktop panel has a separate archived maFiles guide in Russian. The current cloud service does not require configuring a folder on a panel computer. See Steam account management for dashboard features.
Why a file will not import
No shared_secret field
Check that you selected an account file. manifest.json contains a file index and does not replace a maFile. Without shared_secret, the dashboard cannot generate Steam Guard codes from that file.
A login name or password is missing in the preview
Complete the row manually or upload a list of login names and passwords. The login name must match account_name in the file. A numeric SteamID in the filename and a profile display name do not replace the Steam login name.
The file opens, but sign-in fails
A file can open without errors and still contain old data. Check the password and make sure the file belongs to the right account. If you replaced the authenticator, the old file’s secrets may no longer work. Do not guess replacement values: return to the working authenticator or Steam recovery.