Open source video game library manager and launcher with support for 3rd party libraries like Steam, GOG, Origin and Uplay. Including game emulation support, providing one unified interface for your games.
Screenshots on Homepage
Steam, Origin, GOG, Uplay support
Import games from Steam, Origin, GOG and Uplay services including games that are not installed. You can also import Windows Store (UWP) games.
Console Emulation support
Import console games and run them through emulators.
View options
Choose from 3 different view options.
Custom games
Add any game or program with custom launch options.
Automatic Update
Application automatically updates to new version.
Portable installation
Run Playnite without need to install, with ability to run from any place, with option to configure database location for automatic sync via service like DropBox or Google Drive.
"Big Picture" mode with controller support
Fullscreen mode managed with controller.
UI Customization
Full support for skins and custom color pallets.
Add additional launch options for legacy games
To help managing and launching older games. Features like limit CPU cores, CPU speed fix, compatibility flags, automatic installation of 3d party wrappers etc.
Plugin support
Add additional functionality through easy scritping or fully fledged C# plugins.
Playnite doesn't store any user information and you don't need to provide any information to import installed games. Login is required only for full library import of GOG and Origin games and in that case only web session cookie is stored, the same way when you login to those services via web browser.
What about Defender SmartScreen installer warning?
Windows may display security dialog regarding executable securty. This is mainly due to fact that installer is not digitally signed, however it's completely safe to use. More information is in issue #80
Grab latest installer or portable package from releases page. Playnite will automatically notify about new version when released.
Requirements: Windows 7, 8 or 10 and .Net 4.6
If you find a bug please file an issue and if relevant (crashes, broken features) please attach diagnostics package, which can be created via from "About Playnite..." menu.
General discussion lives on Reddit and you can also ask a question directly on Discord or follow @AppPlaynite for updates.
Solution will properly load only in Visual Studio 2017 because it contains ASP.NET Core project with .csproj project configuration, which is not supported in 2015. Otherwise there are no other requirements to build from VS, all references should be downloaded from NuGet.
To build from cmdline run build.ps1 in PowerShell, script builds Release configuration by default into the same directory. Script accepts Configuration, OutputPath, Setup, Portable and SkipBuild parameters.
NSIS 3+ with NsProcess plugin is required to build installer. To build installer run build script with -Setup parameter:
.\build.ps1 -Setup
Portable zip package can be built when using -Portable parameter.
Playnite runs in development environment without extra configuration with exception of Steam library import and auto-update features.
Requires simple web server serving update.json file with information about available version. URL with update.json has to be configured in app.(Debug|Release).config file, UpdateUrl key.
Example file:
{
"stable" : {
"version" : "0.70.0.0",
"url" : "https://localhost/build/PlayniteInstaller.exe"
}
}
In order to download information about full Steam library (installed games can be imported without this), Steam API has to be used with proper API key obtained from Valve. Since API access comes with some limitations (1 request per second and 100k requests per day), Playnite doesn't directly access Steam API, but uses caching service. This also prevents distribution of API keys to end users.
To deploy caching service in development environment, you must do following:
- Build PlayniteServices project, either manually from VS, using buildServices.ps1 script or via
dotnet publish - Create configuration file with Steam API key called apikeys.json inside service folder
- Deploy project to web server or run it directly via
dotnet .\PlayniteServices.dll - Configure root endpoint inside app.(Debug|Release).config file, ServicesUrl key.
apikeys.json example:
{
"Steam" : "25SSE201224DEE54F732DDDC2BA21690C"
}