steam-library-bridge build you intend to use.steam-library-bridge versions, CLI flags or achievement behaviour. Every bridge-specific value below is marked check the documentation — verify it against the project's own README before running anything.
C:\Program Files (x86)\Steam). Launching Steam and the game at the same privilege level matters — see Troubleshooting.Pre-flight checklist:
steam-library-bridge README (check the documentation for its current install and import commands)What to do: find the exact .exe (or Linux binary) for every game you want in Steam, and find your Steam numeric account folder. Epic and GOG games are started by a small executable inside the game's install folder, not by the launcher itself — pointing Steam at the launcher only opens the launcher.
Why: Steam shortcuts store an absolute path. If the path is wrong or points at the launcher, the entry opens a store page or an empty window instead of the game. The numeric account folder (userdata\<SteamID3>) is where Steam keeps per-account shortcut and artwork data, so you need its name before you copy anything.
Example: list the Steam account folders and the Epic manifest-free game directories.
$steam = "C:\Program Files (x86)\Steam"
Get-ChildItem "$steam\userdata" -Directory | Select-Object -ExpandProperty Name
Get-ChildItem "C:\Program Files\Epic Games" -Directory | Select-Object -ExpandProperty Name
Get-ChildItem "C:\Program Files (x86)\GOG Galaxy\Games" -Directory | Select-Object -ExpandProperty Name
Expected output: an 8-digit folder name such as 123456789 from the first command, then one line per installed game, e.g. Fortnite, Cyberpunk 2077. If userdata is empty, Steam has never been started under this Windows account — start Steam once and rerun.
How to check: run the path through the shell to confirm the file exists:
Test-Path "C:\Program Files\Epic Games\Fortnite\FortniteGame\Binaries\Win64\FortniteLauncher.exe"
Expected output: True. False means you copied the wrong segment of the path — open the game folder in Explorer, right-click the executable, Copy as path, and paste it.

What to do: run the bridge to import the launcher libraries, then add anything it missed with Steam's native dialog, and finally attach custom artwork.
Part A — run the bridge. Launch the tool with its import command; the exact flag and executable name are not specified in this guide's source material — check the documentation (--help is the portable way to discover them):
steam-library-bridge --help
Expected output: a usage block listing the available subcommands. Run the import subcommand it prints; on success the tool writes new entries into shortcuts.vdf and Steam shows them under Library → your category after a client restart.
Part B — add anything by hand. In Steam: Games → Add a Non-Steam Game to My Library… → Browse, select the executable from Step 1, Add Selected Programs. For an emulator, select the emulator executable and put the ROM path in Properties → Shortcut → Launch Options — Steam appends those arguments to the target path, which is why the emulator receives the ROM as if you had typed it on the command line.
Example: for a GOG title, the target is the game's own binary, and the launch option might be a windowed flag:
Target: C:\Program Files (x86)\GOG Galaxy\Games\Cyberpunk 2077\bin\x64\Cyberpunk2077.exe
Launch options: -window-mode exclusive
Flags differ per game — use only flags the game itself documents.
Part C — covers. Right-click the new entry → Manage → Set custom artwork, then pick Grid, Hero, Logo and Capsule images from your art folder. This is the reliable path: Steam copies the files into userdata\<SteamID3>\config\grid\ for you. If you prefer to place files manually, use that folder and the file-name prefix Steam assigns to the entry — confirm the current naming scheme in the documentation before bulk-copying dozens of files.
How to check: open Library, switch the filter to All or your custom category, and confirm each entry shows the artwork you set. Then verify the shortcut file exists:
Get-ChildItem "$env:ProgramFiles(x86)\Steam\userdata\*\config\shortcuts.vdf" | Select-Object FullName, Length
Expected output: at least one shortcuts.vdf with a non-zero length. A 0-byte file means Steam has no non-Steam shortcuts at all — repeat Part A/B.

What to do: start every imported game from Steam, one at a time, and confirm three things: the game window appears, the Steam overlay responds, and the artwork survives a Steam restart.
Why: a shortcut can look correct in the library and still fail at launch — usually because the launcher requires its own client to be running, or because the entry points at a file that was moved by an update. Restarting Steam proves the change was written to disk, not just held in memory.
Example: get the app ID of an entry so you can build a direct launch URL. Create a desktop shortcut first (right-click entry → Manage → Add desktop shortcut), then read its target:
$lnk = (New-Object -ComObject WScript.Shell).CreateShortcut("$env:USERPROFILE\Desktop\Cyberpunk 2077.lnk")
$lnk.TargetPath
Expected output: a URL of the form steam://rungameid/<appid> — for example steam://rungameid/2345678901. That number is the ID Steam uses for the entry's artwork and shortcuts, so keep it.
How to check: success looks like all of the following on screen:
1. The game window opens within the time the game normally needs, with no Steam error dialog.
2. Pressing Shift+Tab opens the Steam overlay on top of the game.
3. After Steam → Exit, relaunching Steam shows the same custom cover on the entry.
If the game runs but the overlay never appears, that is a privilege mismatch, not a broken import — see Troubleshooting.
One honest limitation: Steam achievements are tied to a Steamworks application ID. A non-Steam shortcut, including one created by steam-library-bridge, has no such ID, so Steam will not display achievements for these titles. Achievement tracking for Epic and GOG games stays in their own launchers; for emulated games it stays in the emulator's achievement service. Whether the bridge adds any achievement bridging is check the documentation — do not assume it without a line in the project's README confirming it.
Problem. The entry opens a dialog instead of the game.
Failed to start game (missing executable).Test-Path "<full path>". If it returns False, open the game folder, copy the new executable path, then right-click entry → Properties → Target and paste it. Re-add the shortcut if the field is greyed out, then re-apply artwork.Problem. The game runs but Shift+Tab does nothing.
Get-Process steam, "EpicGamesLauncher" -ErrorAction SilentlyContinue | Select-Object Name, Id
Expected output: both processes listed. If one is missing, it was started under a different account context — close everything and relaunch both from the same desktop session.
Problem. Covers vanish after restarting Steam.
userdata folder. If two Steam accounts have signed in on this PC, each has its own userdata\<SteamID3>\config\grid directory, and only the active account's copy is read.Get-ChildItem "$env:ProgramFiles(x86)\Steam\userdata" -Directory | ForEach-Object { $_.FullName + "\config\grid" }
Expected output: one path per Steam account. Copy your files into each, then set the artwork again from the client UI so Steam rewrites its own metadata. For locating stray files across drives, Windows indexing helps — see How to Use AI-Powered Search in Windows 11.
You now have Epic, GOG and emulated titles launching from one Steam library, each with a custom cover and a working overlay. Next, group them into a Steam collection (Library → right-click a collection → Add games) and re-run the bridge import after each new launcher install, since new titles are not picked up automatically.
Do non-Steam games get Steam achievements?
No. Steam achievements require a Steamworks application ID, and non-Steam shortcuts do not have one; achievement progress stays with the game's own launcher or the emulator.
Does adding a game to Steam re-download it?
No. Steam only stores a path to the executable; the files stay where Epic, GOG or your emulator installed them. Removing the shortcut never deletes game data.
Can I move a game to another drive after adding it?
Yes, but you must update the shortcut path afterwards (Properties → Target), otherwise the launch fails with Failed to start game (missing executable).
Why does the overlay work in one game and not another?
Usually a privilege mismatch between Steam and the game process, or a game running in a mode that blocks overlay injection. Start both at the same privilege level and retest before assuming the import is broken.
Status: practical guide. Some statements come from vendors; verify in your environment.
Time to complete: about 30 minutes for 3–4 games (launchers already installed). Difficulty: Intermediate.
Machine data: Citation Map JSON · JSON-LD · Semantic Embeddings — separate stage.
| Entity | Type | Role |
|---|---|---|
| добавить игры epic в steam | тема/инструмент | упоминается в заголовке, TL;DR или разделах гайда |
| steam-library-bridge | тема/инструмент | упоминается в заголовке, TL;DR или разделах гайда |
| как добавить сторонние игры в steam | тема/инструмент | упоминается в заголовке, TL;DR или разделах гайда |
| обложки для игр в steam | тема/инструмент | упоминается в заголовке, TL;DR или разделах гайда |
| эмуляторы в steam | тема/инструмент | упоминается в заголовке, TL;DR или разделах гайда |
| Windows | платформа/технология | упоминается в заголовке, TL;DR или разделах гайда |
| Linux | платформа/технология | упоминается в заголовке, TL;DR или разделах гайда |
| Android | платформа/технология | упоминается в заголовке, TL;DR или разделах гайда |
No independent confirmation is provided; source claims and editorial conclusions are separated below.
| Source | Type | Role |
|---|---|---|
| No external links | — | — |
Cite as: AI Release. Как добавить игры Epic Games, GOG и эмуляторов в Steam с обложками и достижениями: настройка steam-library-bridge. ai-release.org.