How to fix Steam_api.dll missing or not found error?

steam_api.dll, and its 64-bit twin steam_api64.dll, is the Steamworks library a game ships in its own folder, not a Windows file. When it is missing, an antivirus quarantined it or the game's installation is damaged. Check Windows Security's Protection history first, then let Steam verify the game's files.

Facts checked on 14 October 2026. Steps written for Steam on Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What steam_api.dll is and what "steam_api.dll was not found" means

steam_api.dll is the Steamworks API library. Valve's Steamworks documentation tells developers to link steam_api[64].lib into the game and to "ship the steam_api[64].dll in your run-time directory (next to your program's executable, or in your dll search path)". The game calls it for achievements, cloud saves, the overlay, multiplayer lobbies and the ownership check.

Two builds

steam_api.dll for 32-bit games and steam_api64.dll for 64-bit games. The documentation writes both as steam_api[64].dll.

Where it comes from

The redistributable_bin folder of Valve's Steamworks SDK. The developer copies it into the game, and Steam downloads it with the game's files.

What it needs

A running Steam client. Valve says the client provides the implementations of the Steamworks interfaces, so the DLL alone does nothing.

Other systems

On macOS the same library is libsteam_api.dylib, on Linux libsteam_api.so. This page is about the Windows .dll.

The error box comes from Windows, not from Steam. Windows reads the list of DLLs the game's .exe needs before the game runs a single line of its own code. If one of them cannot be found in the game's folder or any other folder Windows searches, it stops the start and shows the box.

• Same file, other spellings: steam api dll, steam.api.dll, steamapi.dll, steam_api dll and "steam api not found" in searches all mean steam_api.dll. Windows ignores upper and lower case, so Steam_api.dll is the same name.
• The 64-bit name: a 64-bit game asks for steam_api64.dll. Everything on this page applies to it in the same way.
• Windows 11 and Windows 10: the box and the fixes are the same on both. Windows 10 left support on 14 October 2025, which does not change this error.
• Not this error: "Steam must be running to play this game" or "SteamAPI_Init() failed" appear when the file is present but cannot reach Steam. Fix 6 covers them.

Where the steam_api.dll file belongs: the game's folder, not Windows

Every game that uses Steamworks carries its own copy. Steam Support gives the default place of installed games as C:\Program Files (x86)\Steam\steamapps\common\, with one folder per game. If you added another Steam library on a second drive, the same steamapps\common structure sits there. The DLL lies next to the game's .exe, which in some games is a subfolder such as bin.

• Not a Windows file. Windows does not ship steam_api.dll, so DISM, SFC and Windows Update cannot restore it. A copy in C:\Windows\System32 or SysWOW64 was put there by hand or by a tool and does not belong.
• Not the Steam client's copy. Reinstalling Steam does not rewrite the folders of your games, which is why the earlier version of this guide's first tip rarely helped.
• Not shared between games. Each game ships the build from the Steamworks SDK version its developer used. Copying the file from one game to another can trade the missing-file box for an entry point error.
• Open the folder from Steam. Right-click the game in your Library and select Manage > Browse local files. That opens the exact folder, even on a second drive.

What causes the steam_api.dll missing or not found error, from most to least common

Most often an antivirus removed the file. Cracked copies of games replace steam_api.dll with a modified one, so security software watches for changed copies of this name and sometimes flags a genuine one too. Less often the game's installation is incomplete or damaged. Rarely, the copy of the game never came from Steam at all.

steam_api.dll download: why a DLL site or a cracked file is the wrong fix

Search for the file name and DLL sites fill the first page. For steam_api.dll that route is worse than for most DLLs, because the genuine file is already available to you for free: Steam puts back the exact copy your game was built with when you verify its files. A downloaded file can only be a guess.

• Wrong version. Each game ships its own SDK build. A copy of another version can fail with the entry point error, crash later, or break achievements and cloud saves.
• Wrong build. A site may give you steam_api.dll when your game needs steam_api64.dll, and the result is the Bad Image window.
• Unknown builder. The game loads this file into its own process, with your rights, every time it starts. A file of unknown origin runs there too.
• Cracked replacements. Steam "emulators" work, by their own README, by replacing the game's steam_api(64).dll with theirs. Repacks ship such files. Anything that replaces this DLL is code from an unknown author running inside the game.
• Real campaigns. Malwarebytes reported in June 2026 a campaign hidden in cracked and repacked games that researchers estimate infected more than 400,000 devices, delivering password-stealing malware.

The same rule holds for other missing DLLs, but the cure differs by family. A Microsoft runtime file has an official installer, as our guide to the VCRUNTIME140_1.dll was not found error shows. steam_api.dll has no installer of its own: its only genuine source is the game's own files on Steam.

How to fix the steam_api.dll missing or not found error

Fix 1 checks whether your antivirus took the file and brings it back. Fix 2 lets Steam replace it with the genuine copy, and Fix 3 stops the antivirus from removing it again. Fix 4 reinstalls the game. Fix 5 is for a copy that did not come from Steam, and Fix 6 for the case where the file is back but the game cannot reach Steam.

Fix 1. Restore steam_api.dll from Microsoft Defender quarantine

5 minutesLow riskYour game is bought on Steam and Windows Security, or another antivirus, removed the file.

An antivirus that quarantines a file moves it out of the game's folder, and Windows then reports it as not found. Protection history shows whether this happened, the exact path and the detection name. Restoring a genuine Steam file puts it back where the game expects it.

1. Close the game and keep Steam open.
2. Open Windows Security from the Start menu and select Virus & threat protection.
3. Under Current threats, select Protection history. Use Filters > Quarantined items if the list is long.
4. Open the entry whose Affected items path ends in steam_api.dll or steam_api64.dll inside steamapps\common. Note the detection name and the path.
5. Decide: if the path is your own Steam game folder and you never added a patch or crack, select Actions > Restore.
6. Microsoft says a restored file is detected again and shows up as Threat found - action needed. Open that entry and select Allow on device only for the genuine Steam file.
7. Start the game from Steam.

• Another antivirus. Avast, AVG, Bitdefender, Kaspersky, Norton and others keep their own quarantine, often called Virus Chest or Quarantine. The idea is the same: find the entry with the game's path, restore it, then add the exception from Fix 3. Their menus differ, so follow the vendor's help.
• When Restore does nothing. Users report that Restore can fail silently on some PCs. Then skip it: Fix 2 downloads a fresh copy from Steam, which is just as good.

Fix 2. Verify the integrity of the game's files in Steam

5 to 30 minutesNo riskThe game is in your Steam library, whether or not an antivirus was involved.

Steam compares every installed file of the game with the version on its servers and downloads what is missing or changed. That includes the exact steam_api.dll or steam_api64.dll the developer shipped, so you get the right build and version without guessing.

1. Restart the PC and open Steam, as Steam Support's own steps begin.
2. Right-click the game in your Library, or select the gear icon on the game's Library page.
3. Select Properties.
4. Open the Installed Files tab and select Verify integrity of game files.
5. Wait until Steam finishes. Do not run a virus scan or verify another game at the same time.
6. Start the game from Steam.

The other launchers have the same check, and a game bought there may also ship steam_api.dll when it is a Steam build sold elsewhere. Steps for Steam, Epic Games, the EA app, the Xbox app, Battle.net and GOG Galaxy: How to verify game files in Steam, Epic Games, Xbox app, EA app, Battle.net and GOG Galaxy

Fix 3. Stop your antivirus from removing steam_api.dll again

10 minutesLow riskThe genuine Steam file keeps disappearing after Fix 1 or Fix 2, and you are sure the game is from Steam.

Steam Support says antivirus programs can flag games by mistake, and that players can create exclusions for confirmed false positives and then verify the files again. A narrow exclusion for one game's folder keeps the restored file in place without lowering protection for the rest of the PC.

1. First report the false positive. In Windows Security > Virus & threat protection > Manage settings, select Submit a sample manually and send the flagged steam_api.dll to Microsoft.
2. Still under Manage settings, scroll to Exclusions and select Add or remove exclusions.
3. Select Add an exclusion > Folder.
4. Choose the one game's folder in steamapps\common, not your whole Steam folder and not a drive.
5. Verify the game's files again with Fix 2, so Steam puts back anything that was removed.
6. Start the game. Remove the exclusion after the next game update if detection updates have fixed the false positive.

Steam Support also notes that many antivirus vendors offer a Game Mode or exclusions for game files and processes. In a third-party antivirus, look for those names in its settings. To test whether the antivirus is the cause at all, a short pause with protection turned back on afterwards is allowed: Turn off Microsoft Defender protection for a moment

Fix 4. Uninstall and reinstall the game from your Steam library

15 to 60 minutes, depending on the game's sizeRead the warningVerifying did not bring the file back, or the box returns right after a verify.

Verifying repairs files Steam knows about. A folder that was moved, copied in by hand, or mixed with leftover files from mods or another version can still load the wrong DLL. A clean installation leaves only what Steam itself puts there, including the matching steam_api.dll.

1. Right-click the game in your Steam Library and select Manage > Uninstall. Confirm.
2. Open steamapps\common in the same library and delete the game's folder if Steam left it behind, after saving anything you need.
3. Restart the PC.
4. Select the game in your Library and select Install. Pick the library folder and drive.
5. Let the download finish, then start the game from Steam before adding any mods.

• Low disk space or a failing drive. Downloads that stop halfway leave games incomplete. Make sure the drive has room for the full game, and check it with Check a disk for errors (chkdsk) if downloads keep failing.
• A game moved by hand. Steam Support describes how to move a library or a game properly. A game folder copied between drives without Steam knowing may lack files: reinstall it in the library Steam shows.
• A game shown as not installed. If Steam lists the game as uninstalled although the folder exists, Steam Support says starting the installation makes Steam recognise the existing files and download only what is missing.

Fix 5. Remove a copy of the game that did not come from Steam, and scan the PC

30 to 60 minutesRead the warningThe game is not in your Steam library: a repack, a crack, a trainer pack or a folder copied from elsewhere.

A non-Steam copy either has no genuine steam_api.dll or carries a replaced one. Antivirus programs remove the replacements because they are modified code from unknown authors. No legitimate fix makes such a file load, and the safe end is to remove it and check the PC.

1. Do not restore or allow the flagged steam_api.dll in Protection history. Select Remove on its entry.
2. Uninstall the game from Settings > Apps > Installed apps, or delete its folder if it had no installer: Uninstall a program or app in Windows
3. Run a Full scan in Windows Security, then a Microsoft Defender Antivirus (offline scan), which Microsoft says runs before Windows loads so persistent malware has a harder time hiding: How to scan for malware with Microsoft Defender
4. Open Protection history after the offline scan and read what it found.
5. If anything was found under a stealer, trojan or backdoor name, change the passwords of your important accounts from another, clean device.
6. Get the game from Steam or another official store. Its own files include the genuine DLL.

Users on Microsoft Q&A describe the typical end of this road: a decade-old cracked steam_api.dll suddenly blocked by Microsoft Defender, exclusions that do not help, and a file that cannot even be deleted. The answers there point to reinstalling and excluding, but the honest fix for a file Defender rates as a threat is to stop using it.

Fix 6. Start the game through a running Steam when the file is there but the API fails

5 minutesNo risksteam_api.dll is back, but the game now says Steam must be running, or SteamAPI_Init failed.

The DLL only forwards calls to the Steam client. Valve's documentation lists why the start of the Steamworks API fails: Steam is not running, Steam cannot tell which game this is, the game runs under another user or admin level than Steam, or the signed-in account does not own it.

1. Start Steam and sign in with the account that bought the game.
2. Start the game from the Steam Library, not from a desktop shortcut to its .exe.
3. If you set the game's .exe to Run as administrator, turn that off in its Properties > Compatibility, or run Steam the same way. Valve says the game and Steam must run under the same user context and access level.
4. In Steam, check that the game appears in your Library and is not a Family Sharing copy that the owner is using right now.
5. Restart Steam fully with Steam > Exit, then start it again and launch the game.

If the steam_api.dll error is still there: what to check and what to send

When the box survives the fixes for your case, collect facts before you change anything else. Four places hold them: the box itself, the game's folder, Protection history and the Windows Application log.

1. Write down the full text of the box, its title and which name it shows: steam_api.dll or steam_api64.dll.
2. List every copy of the DLL in the game's folder and its subfolders. Replace the path with the real one from Browse local files.

   dir /s /b "C:\Program Files (x86)\Steam\steamapps\common\GameName\steam_api*.dll"

3. Open Windows Security > Virus & threat protection > Protection history and note any entry with the game's path, its date and the detection name.
4. Open Event Viewer and go to Windows Logs > Application. Look for Application Error or Application Popup entries at the time of the box. They name the program and, for a crash, the faulting module.
5. Check that no copy of steam_api.dll sits in C:\Windows\System32 or C:\Windows\SysWOW64. If one does, somebody put it there by hand: remove it.

• What to send to the developer: the box text, the game's build or version, your Windows version, the dir result and whether Protection history shows the file. Post it in the game's Steam discussions or the developer's support page.
• What to send to Steam Support: only problems with Steam itself, such as downloads that never finish. Steam Support's help wizard is at help.steampowered.com.
• When it is the game, not your PC: the file is present, nothing is quarantined, other Steam games start, and the box appears right after a game update. Then the update shipped broken and the developer has to fix it.
• When it is a different problem: a box that names another file, such as a Visual C++ runtime or a DirectX file, has its own cause and fix.

How to keep the steam_api.dll error from coming back

The common thread is the source. A steam_api.dll that Steam installed with the game is the one file that fits that game. Anything that replaces it, whether a DLL site, another game or a crack, can only make things worse, and a missing genuine copy is always one verify away.

Frequently asked questions

What is steam_api.dll?

steam_api.dll is the Steamworks API library that Valve provides to game developers in the Steamworks SDK. A game that uses Steam features such as achievements, cloud saves, the overlay or multiplayer lobbies ships it next to its own .exe. 64-bit games use steam_api64.dll instead. Valve's documentation says developers must ship the file in the game's run-time directory. It is not part of Windows and not something the Steam client installs for all games, so each game has its own copy and Steam's Verify integrity of game files restores it.

Where is steam_api.dll located?

In the game's own folder, next to the game's .exe file. For Steam games that folder is under C:\Program Files (x86)\Steam\steamapps\common\ by default, one subfolder per game, or under steamapps\common in another Steam library you added. Some games keep the .exe and the DLL in a subfolder such as bin. The fastest way to find it is to right-click the game in your Steam Library and select Manage > Browse local files. It does not belong in System32 or SysWOW64.

Is steam_api.dll a virus?

The genuine file from Steam is not a virus. It is Valve's library and comes with games you buy. Copies with the same name are a different matter: cracks and Steam emulators replace the game's steam_api.dll with modified code, and antivirus programs detect many of those. Sometimes a genuine copy is flagged by mistake, which Steam Support calls a false positive. If the file came from Steam, restore it or verify the game's files. If it came with a cracked game, remove it and scan the PC as in Fix 5.

Can I download steam_api.dll or steam_api64.dll from a DLL site?

You should not, and you do not need to. Each game ships the build of steam_api.dll from the Steamworks SDK version its developer used, and Steam puts back that exact file when you verify the game's files. A download from a DLL site may be the wrong version, the wrong 32-bit or 64-bit build, or a modified file of unknown origin that loads inside the game with your rights. If the game is not from Steam, there is no genuine source for its steam_api.dll at all.

Why does Windows Defender keep deleting steam_api.dll?

Because modified copies of this file are common in cracked games, security software looks closely at it. If your copy is a crack, the detection is correct and you should not override it. If the game is from Steam, it may be a false positive. Restore the file from Protection history or verify the game's files, submit the file to Microsoft as a sample, and add an exclusion for that one game's folder as in Fix 3. Steam Support describes the same order: exclusion first, then verify.

Will reinstalling Steam fix steam_api.dll was not found?

Usually not. Reinstalling the Steam client replaces Steam's own program files, while steam_api.dll lives inside each game's folder in steamapps\common. The earlier version of this guide listed reinstalling Steam as the first fix, but it does not touch those folders. What restores the game's copy is Verify integrity of game files in the game's Properties, or reinstalling the game itself from your Library. Reinstall Steam only when Steam itself is broken and cannot start, update or verify.

Does regsvr32 steam_api.dll fix the error?

No. regsvr32 registers a DLL as a component in the Windows registry by calling a registration function inside it. Games do not find steam_api.dll through the registry: Windows looks for it in the game's folder when the game starts. Registering it would change nothing even if the file had such a function, and if the file is missing there is nothing to register. The earlier version of this guide suggested regsvr32. Use Fix 1 or Fix 2 to put the file back.

What does Steam API doesn't return the URL to download the file mean?

That message does not come from Steam or from steam_api.dll. It is shown by unofficial Steam Workshop downloader sites when Steam's public interface does not give them a download link for a Workshop item. Users report it for mods of games they do not own on Steam. The official way to get Workshop content is to subscribe to it in Steam, which needs the game in your library. This page is about the missing DLL; we do not help to get Workshop files for unowned games.

Does the steam_api.dll error look different on Windows 11?

No. Windows 11 shows the same System Error window as Windows 10: the code execution cannot proceed because steam_api.dll was not found, or the same with steam_api64.dll. The causes and fixes are identical on both, because the file belongs to the game and the antivirus behaviour is the same. The only difference you may notice is the look of Windows Security, where Protection history and Exclusions sit under Virus and threat protection on both versions. Windows 10 left support on 14 October 2025.