MChartier / Playnite

Open source video game library manager with support for 3rd party libraries like Steam, GOG, Origin, Battle.net and Uplay. Including game emulation support, providing one unified interface for your games.

Playnite

Open source video game library manager and launcher with support for 3rd party libraries like Steam, GOG, Origin, Battle.net and Uplay. Including game emulation support, providing one unified interface for your games.

Screenshots on Homepage

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

Features

See homepage for list of features.

Download

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

Portable version requires Microsoft Visual C++ 2013 Redistributable (x86) to be installed manually.

Extensions

Playnite can be extended with plugins (written in .NET languages) or by scripts (PowerShell and IronPython are currently supported).

See extensions portal for tutorials and full API documentation.

Known Issues

List of known issues and solutions can be found on wiki.

Privacy Statement

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, Origin and Battle.net games and in that case only web session cookie is stored, the same way when you login to those services via web browser.

Questions, issues etc.

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.

Contributions

Translations

See How to: Translations wiki page.

Themes

See How to: Themes wiki page.

Code Contributions

Please ask in an issue first before starting with implementation to make sure that nobody else is already working on it. If the issue doesn't exists 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
• always encapsulate with brackets:

if (true)
{
    DoSomething()
}

instead of

if (true)
    DoSomething()

Roadmap

You can see planned version with their features in projects overview.

Development

See wiki about building and settings up development environment.