# Playnite Extensions Collection: a shelf of add-ons for a game library manager > The Playnite Extensions Collection is a set of extensions for Playnite, the open-source game library manager, and it is the work of one developer who makes them for the love of it and keeps them free. The collection covers the gaps in the base application, with tools for cooperative feature detection, cover collages, display configuration, Game Pass browsing, engine tagging, metadata loading for custom themes and a second-class game watcher for GOG. **darklinkpower/PlayniteExtensionsCollection** — Collection of extensions made for Playnite. - Repository: https://github.com/darklinkpower/PlayniteExtensionsCollection - Stars: 569 · Forks: 57 - Language: C# - License: MIT - Published: 2026-10-22 · Updated: 2026-10-22 · Language: en - Canonical page: https://hysenlabs.com/projects/darklinkpower-playniteextensionscollection ## What the collection is The Playnite Extensions Collection is a set of extensions developed to enhance and customise the experience in Playnite, which is an open-source game library manager. The repository is a single person's work, and the README is unusually direct about the arrangement: I create Playnite extensions and themes for the love of it, always free for the community. The project is a collection rather than a library or a framework. There is no API here, no plugin interface of its own and no shared runtime. What there is, is a shelf of separate add-ons, each of which plugs into Playnite's own extension mechanism and each of which solves one narrow problem. That distinction matters for how you evaluate it. Extensions like this are not a coherent system; they are a menu. You install the ones that match a problem you have, and the value of the collection is that somebody has already written them rather than that they build on each other. The primary language is C#, the licence is MIT, the default branch is master, and the recent releases are 2026.08.08_82cc5fd7 from 2026-08-09, and two from 2026-06-29. The release names carry a date and a commit hash, which is a pattern used when a build is produced from a snapshot rather than a tagged version, and it fits a collection where each extension is versioned on its own schedule. The last push was on 2026-08-31 with the project not archived, and the repository has a Crowdin badge for translations, a Ko-fi badge, and a link to the issue tracker. The repository layout confirms the collection structure: a source/ directory holding the extension projects, manifests/ for the per-extension metadata, references/ for shared files, screenshots/ for the images used in the README, and a crowdin.yml at the root for the translation pipeline. ## How the extensions are distributed and installed Installation has two routes, and both go through Playnite rather than through a download page of the project's own. Option A is to click the Link of the extension in the README table, which takes you to the addon entry in the Playnite database, and then click the Download button in that entry. Option B is to download directly from Playnite in the addons browser. Both routes end in the same place, which is the addons browser inside Playnite, and that is the point of the design. Extensions are distributed through Playnite's own database rather than as loose downloads, so a user gets the extension from the same place they get the updates, and the version tracking is handled by the host application rather than by the extension author. This also explains the table structure in the README. Every row has an Icon column, a Name, a Description, a Database link and a Help link, and the Database link points at a playnite.link addons URL with a specific identifier in the fragment. The identifier is a GUID, which is what Playnite uses to track an addon. The Help column is worth noting because it is not always present. Several rows say N/A, and for those the instructions live in the Playnite forums instead, which the Usage section confirms: usage varies depending on the extension functionality, but in general, and you should refer to each extension thread in the Playnite forums for the specific instructions. So the documentation model is split in two. Some extensions have a wiki page in the repository, reachable from the Help link, and the rest are documented in forum threads. That is a pragmatic arrangement for a collection maintained by one person, since a forum thread is much quicker to write and update than a wiki page per extension, but it does mean the extensions without a Help link need more digging. The issue tracker link in the README points to a different repository, PlayniteScriptExtensions, rather than to the collection repository itself. That is a small detail but a useful one to know before you report a problem: the issue tracker for these extensions lives elsewhere. ## A tour of the Generic extensions The README lists the extensions under a Generic heading, and the names describe the gaps in the base application that they fill. Cooperative Modes Importer detects and adds features that indicate the cooperative features in games, so a game with local co-op gets tagged as such. That is metadata Playnite does not import on its own, and it is the kind of field that a library management app would want to filter on. Covers Collage Maker creates and exports customizable game cover collages from your library, which is a sharing-oriented extension rather than a management one. Details to Grid View Converter converts the layout in Details View to Grid View of supported Desktop Mode themes, which is a theme compatibility fix rather than a feature. Display Helper offers functionality to configure your displays when starting games, so a game can be launched on a specific screen or at a specific resolution. That is a real convenience on a multi-monitor desk. Extra Metadata Fullscreen Mode Helper adds support for the Extra Metadata Loader extension usage in certain Fullscreen Mode themes, and Extra Metadata Loader itself adds functionality to support logos and videos media in compatible custom themes. So there is a family here: one extension loads logos and videos, and another makes that work in the fullscreen themes that would otherwise ignore it. Filter Presets Quick Launcher offers diverse functionality to quickly launch Filter presets from the top panel, the sidebar or from Playnite's Search keyboard launcher. It is about making the filtering system faster to use, which is a sign the author spends time in the app rather than only writing for it. Game Engine Checker adds a tag with the name of the engine used by the game, is compatible with PC games available on GOG or Steam, and gets the information from PCGamingWiki. That is a nice piece of engineering: rather than storing a database of engines, it queries an existing public one and turns the answer into a Playnite tag. Game Media Tools is intended as a library maintaining tool and to make it easier to handle game media in your library. As its name suggests, it works on the game library itself rather than adding new data from outside, which makes it the odd one out in the list. ## The extensions that reach outside the library Several extensions in the list do something more than reorganise what Playnite already knows, and they are the reason to look at this collection rather than at a single-purpose tool. Game Pass Catalog Browser browses the Game Pass catalog in Playnite and adds its games to your library. It has a Help page. It is doing two things at once, presenting a subscription catalogue in a familiar interface and pushing entries into your library, which is the direction every catalogue integration tends to move in. Game Relations detects and displays other games in your library related to the game currently displayed, using their metadata in supported themes. So the relation is inferred from the metadata you already have rather than from a hardcoded list, which means it works for series, remasters and editions as long as Playnite knows about the connection. GOG Second Class Game Watcher detects games with missing features or issues on GOG, and adds tagging and display options in Playnite. The extension surfaces GOG's missing features and issues as tags you can filter on. It is the same technique as Game Engine Checker, applied to a different public data source. Extra Metadata Loader, mentioned earlier, is the extension that pulls logos and videos into a library. That is a different class of thing from the rest, because it requires the custom themes to have somewhere to put the media, which is why there is a separate helper for the fullscreen themes. Taken together, these extensions share a pattern. Each one takes a fact or a capability from somewhere else, the store metadata, the Game Pass catalogue, PCGamingWiki, GOG's feature list, and makes it a Playnite tag, a filter or a field. The library is the centre, and these are the feeds that enrich it. The theme-related extensions, Details to Grid View Converter and Extra Metadata Fullscreen Mode Helper, work the other way round. They adjust how an existing theme renders rather than adding data, which is a different kind of contribution, and one that a user of a custom theme may need more than a user of the default one. ## The project around the extensions, and how to contribute The repository is more than a list of extensions, and the surrounding structure is what makes it workable. The crowdin.yml at the root and the Crowdin badge in the README header point at a translation pipeline. The Translations section of the README asks for help to translate the extensions into different languages through the project's Crowdin page. So localisation is a first-class part of the project rather than something done ad hoc by translators pulling the source, which is a considerable amount of work for a project of this size, since each extension has its own strings. The Tips and donations section explains the economics. The author makes the extensions and themes for the love of it and they are always free, and while donations are not expected they are appreciated, with a Ko-fi link. Every extension being free is a deliberate choice, and the reason given is the love of it rather than a business model, so the probable outcome is that they stay free. The Contribution Guidelines section in the table of contents is a promise the README does not fill in. The Questions, suggestions and issues section points people at opening a new issue on the PlayniteScriptExtensions repository. The manifest directory is worth understanding because it explains how a Playnite extension is packaged. Playnite extensions have a manifest that declares the extension's identity, its version, its author, and which files are included, and having a manifests/ directory with one manifest per extension means the packaging metadata is versioned alongside the code rather than being typed into a web form on the addons database. It also means a change to a manifest is a reviewable commit. So the shape of the project is: one repository, one author, a set of independent C# extension projects under source/, a manifest per extension, screenshots for the documentation table, and a Crowdin pipeline for the strings. The release naming with a date and a commit hash suggests the whole collection is built and shipped together rather than each extension being released separately, which is consistent with everything sharing one versioning scheme and one installation path. ## Conclusion Adopt the Playnite Extensions Collection if you already use Playnite and want the small gaps in the base application filled, particularly the cooperative feature detection, the display configuration on launch, the Game Pass catalogue browsing, the engine tagging from PCGamingWiki and the GOG feature watcher. Do not expect a coherent framework, because this is a shelf of independent add-ons from one developer rather than a system with a shared runtime, and check the Playnite forums for an extension's specific usage if its row in the table has no Help link, since the documentation is split between the repository wiki and forum threads. Before you commit, install through Playnite's own addons browser rather than a loose download, so version tracking stays with the host application, and note that issue reports go to the PlayniteScriptExtensions repository rather than to this one. ## FAQ ### What is the Playnite Extensions Collection? It is a set of Playnite extensions developed to enhance and customise the experience in Playnite, the open-source game library manager. The collection is written in C#, MIT licensed, and every extension is free, with the author stating they make them for the love of it and asking for donations rather than charging. ### How do I install a Playnite extension from this collection? Either click the Link of the extension in the README table to reach the addon entry in the Playnite database and click Download there, or download directly from Playnite in the addons browser. Both routes go through Playnite's own addons system, so updates are handled by the host application. ### What does the Game Engine Checker extension do? It adds a tag with the name of the engine a game uses, works with PC games available on GOG or Steam, and obtains the information from PCGamingWiki. The GOG Second Class Game Watcher works the same way, detecting games with missing features or issues on GOG and adding tagging and display options. ### What are the theme-related extensions in the collection? Details to Grid View Converter converts the layout in Details View to Grid View in supported Desktop Mode themes, and Extra Metadata Fullscreen Mode Helper adds support for the Extra Metadata Loader extension in certain Fullscreen Mode themes, while Extra Metadata Loader itself adds support for logos and videos media in compatible custom themes. ### Can I help translate the Playnite extensions? Yes. The repository uses Crowdin, with a crowdin.yml at the root and a badge linking to the project page, and the README asks for help to translate the extensions into different languages through that page. Issues and suggestions can be raised on the PlayniteScriptExtensions repository. ## Sources - [darklinkpower/PlayniteExtensionsCollection on GitHub](https://github.com/darklinkpower/PlayniteExtensionsCollection) - [Issues](https://github.com/darklinkpower/PlayniteExtensionsCollection/issues) - [License: MIT](https://github.com/darklinkpower/PlayniteExtensionsCollection/blob/master/LICENSE) - [README](https://github.com/darklinkpower/PlayniteExtensionsCollection/blob/master/README.md) - [Releases](https://github.com/darklinkpower/PlayniteExtensionsCollection/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/darklinkpower-playniteextensionscollection