Playnite

An open source video game library manager and launcher with support for 3rd party libraries like Steam, Epic, GOG, EA App, Battle.net and others. Includes game emulation support, providing one unified interface for your games.

Screenshots are available at the Homepage

If you find Playnite useful please consider supporting the lead developer Josef Nemec on Patreon.

Features

See the Homepage for the list of features.

Download

Grab the latest installer or portable package from the download page. Playnite will automatically notify you about a new version upon release.

Requirements: Windows 10 or 11

FAQ, Known Issues, user manual

Can be found here

Questions, issues etc.

If you find a bug please file an issue and if relevant (crashes, broken features) please attach a diagnostics package, which can be created from inside the "About Playnite..." submenu.

Biggest community around Playnite currently gathers on our Discord server and Reddit.

Privacy Statement

Playnite itself doesn't store any user information and you generally don't need to provide any information to import installed games. All game library data is stored locally on your PC.

Account connection process depends on how a library plugin is implemented, but is usually done via official login web forms and only the web session cookies or tokens are stored, the same way when you login to those services via the web browser.

Add-ons

Playnite can be extended with plugins (written in .NET languages), PowerShell scripts and user interface themes.

See the extensions portal for more information about how to make these addons.

Translations

We use Crowdin to manage localization, please join our project if you want to submit translations:

https://crowdin.com/project/playnite

Proofreading changes to original English strings can be submitted by creating pull request for LocSource.xaml file.

Code Contributions

Pull requests are generally on pause because majority of code base is being rewritten for Playnite 11. Smaller "safe" changes for P10 might get accepted based on what they and if they come with test coverage. If you plan to work on bigger changes, please discuss it first in related issue or on Discord, thank you.

Please ask in the related issue first before starting implementing something to make sure that nobody else is already working on it. If an issue doesn't exist for your feature/bug fix, create one first.

Regarding code styling, there are only a few major rules:

• private fields and properties should use camelCase (without underscore)
• all methods (private and public) should use PascalCase
• use spaces instead of tabs with 4 spaces width
• add empty line between code block end } and additional expression
• always encapsulate the code body after if, for, foreach, while etc. with curly braces:

if (true)
{
    DoSomething();
}

DoSomethingElse();

instead of

if (true)
    DoSomething();
DoSomethingElse();

Branches

• master - default branch representing state of currently released build.
• devel - development branch containing latest changes. All pull requests should be made against devel branch.
• devel* - development branches for specific features/versions.

Roadmap

Playnite is currently being rewritten from scratch for next major version release 11. The work is being done in private repository until beta release, after which the code will be release in this repository under the same license as current version 10 release. There is no list of planned changes and new features for version 11.

Development

See the wiki for info about building and setting up the development environment.

Others

This program uses free code signing provided by SignPath.io, and a free code signing certificate by the SignPath Foundation