Nexus Mods Acquires SteamDB Operation
The deal pairs SteamDB's long archive of game builds and update history with Nexus Mods' mod ecosystem, aimed at the common failure where a silent Steam update breaks mods that depend on a specific game version.
Key Facts
- Nexus Mods announced on September 2, 2026 that it will take over operation of SteamDB.
- SteamDB was founded in 2013 by xPaw and Marlamin.
- xPaw ran SteamDB nearly alone after Marlamin left and said he experienced burnout.
- SteamDB's free features will remain free, with no ads planned and no Nexus Mods account required.
- Nexus Mods plans to use SteamDB's game build and update history for mod compatibility checks, though the plan is at concept stage.
Reporting from 3 sources: Denfaminicogamer, Automaton, Game Spark.
Nexus Mods announced on September 2 that it will take over operation of SteamDB, the third-party database that tracks player counts, price history, and update information for games on Steam. SteamDB was founded in 2013 by xPaw and Marlamin. After Marlamin left the project, xPaw ran the site nearly alone, and he said the workload and mental burden grew as Steam itself expanded, leaving him close to burnout. He began looking for a partner in January 2026. SteamDB will remain a separate service with its own name, brand, and community. Features currently free will stay free, no ads are planned, personal data will not be sold, and a Nexus Mods account will not be required. The browser extension will keep being maintained. Nexus Mods said it will invest in SteamDB's infrastructure, security, and scalability, and it is considering using SteamDB's game build and update history to help mod managers check whether mods remain compatible with current game versions. That plan is at the concept stage. xPaw will support the transition for several months.
xPaw said he could not accept letting the site decline or shutting it down, and he chose Nexus Mods because of its two decades of work in the game community. Nexus Mods addressed monetization directly in a FAQ, saying SteamDB needs to earn revenue but that it has no plan to run ads, and it rejected the idea of enshittification, describing the term as an owner degrading a product while extracting value.
The company cited silent game updates as the most common cause of broken mods, giving the example of a setup that worked the night before and then failed after Steam patched a game at 3 a.m., removing the version that 200 mods depended on. It also floated version pinning, where a collection could state a required game version such as Skyrim 1.6.1170, and installation verification that distinguishes a clean install from a silently broken one.
SteamDB has relied on donated Steam keys for game file tracking, and Nexus Mods said it will fund that itself going forward. An API for developers and publishers is planned for the future.
Synthesized by Yomimono from the 3 cited sources below, including Japanese-language reporting where cited, then editorially reviewed before publishing.