Game Decompilations List: 691 Projects in One README

By Indie Kings | October 29, 2026

Updated October 29, 2026: SamidyFR/Game-Decompilations is a single README that links 691 game decompilation projects in alphabetical order, with 689 unique repository URLs and 18 links pointing somewhere other than GitHub. The repository has 750 stars, 46 forks, 15 contributors and 18 open issues, was created on July 10, 2025, and merged its newest change on October 29, 2026.

Image: a card catalogue, a fitting metaphor for an alphabetical index of projects, via Wikimedia Commons.

One file, 691 links

The list does exactly one thing and does it at scale. Open the README and you get a heading, a short set of notes, a date, and then hundreds of lines, each one a game title in brackets followed by a link to a repository. There are no categories, no console groupings, no progress percentages and no descriptions. It is an index in the oldest sense: a way to find a project when you already know the name of the game.

The README is upfront about how to use it. The tip is to press Ctrl+F and search, because the list is long and alphabetical. That single instruction explains the design. A reader looking for a specific title can jump straight to it, and a reader who wants to browse is expected to scroll. The absence of structure is a limitation and also a kind of honesty: the list does not pretend to rank projects or judge their quality, it only records that they exist and where they live.

The numbers are larger than they first appear. Of the 691 entries, 689 point to unique URLs, which means two repositories are listed twice. One is blackgamma7/aidyn, which appears once as Aidyn Chronicles: The First Mage and once as Aidyn Chronicles. The other is sonicretro/skdisasm. Those duplicates are a small defect in a list this size, and the README already asks readers to help fix duplicates through its contributing guide, so the maintainer knows the problem exists.

Eighteen links do not point at GitHub. Those entries include assembly source files hosted on fan wikis, project pages and other archives. The proportion is telling: about 97 percent of the projects in the list live on GitHub, which reflects how completely the decompilation scene has standardized on git repositories, pull requests and continuous integration. A project that is not on GitHub is now the exception, and often it is an older disassembly that predates the convention.

What counts as a decompilation here

The list uses the word decompilation loosely, and that is worth understanding before using it. Some entries are matching decompilations in the strict sense: source that compiles back into the original binary. Others are disassemblies, which produce readable assembly rather than C. Others are reimplementations or source ports that reconstruct game logic without matching the original instructions. A few are browsers or rewrites that share almost nothing with the original code beyond the design.

Examples make the range clear. The list includes Ace Combat 6 under a repository named AC6_recomp, Ambermoon under Ambermoon.net, Wipeout under a project called wipeout-rewrite, and Zuma Deluxe under CircleShootApp. Each of those is a legitimate preservation or reconstruction effort, and none of them is a byte matching decompilation of the original executable. The list also includes 3D Maze, a playable reconstruction of an early maze game, and Zone of the Enders 3, which is the Guy Savage minigame from Metal Gear Solid 3 rather than a standalone release.

That breadth is a feature for a general audience and a problem for a researcher. Someone who wants a project they can build into an identical ROM has to check each candidate, because the list does not distinguish matching decompilations from ports. The README says as much in its notes: some decompilations are unfinished and need to be checked before downloading, and the list is a work in progress with more projects still missing. Those two sentences are the only quality guidance offered, and they are accurate.

Seven entries carry a warning symbol. The list includes AI-flagged projects at the end, marked with the same symbol used by other curated lists to disclose AI involvement. That convention has spread through the scene over the past two years as matching projects argued about whether generated code belongs in a decompilation. Including the flag without excluding the projects is a pragmatic choice: readers get the information and make their own decision, and the list stays a record rather than an endorsement.

The alphabetical ordering creates some odd adjacencies. Aidyn Chronicles sits next to Air Traffic Chaos and Aironauts. Zone of the Enders sits at the end next to Zuma Deluxe. A console-based index would group those games more usefully, but it would also require judgment calls about which platform a project targets, and many projects target several. Alphabetical order avoids that argument entirely, at the cost of browseability.

A website generated from a README

The repository is not only a README. It is an HTML project, and its commit history shows an automated step that regenerates index.html from README.md. That means the list exists in two forms: the Markdown source that contributors edit through pull requests, and a static page that readers can open without visiting GitHub. The site is the public face, and the README is the database.

The contribution flow is conventional and healthy. A contributor adds a line, opens a pull request, and the maintainer merges it. The two most recent merges, both dated October 29, 2026, add Fallout 1 through pull request 127 and BattleTanx: Global Assault for the PlayStation through pull request 124. A bot commit then regenerates the HTML. That sequence, human edit, review, merge, generated output, is exactly what a list like this needs, because it keeps the source of truth in a text file that anyone can diff.

The project has 46 forks and 18 open issues against 750 stars. The fork count suggests people copying the list to adapt it, perhaps for their own regional or platform-specific indexes. The open issues are likely a mix of missing projects, broken links and duplicate reports, which is the maintenance load of any link collection. Fifteen contributors over fifteen months is a modest but steady group, and the fact that the newest merges are still arriving suggests the list has not been abandoned.

There is no license file. For a list of links that is less consequential than for a codebase, since the entries point elsewhere and the underlying projects carry their own terms. It still means the README text itself has no explicit grant for reuse. Anyone building on the list should treat it as a reference rather than a dataset with clear terms, which is a small but real gap for a resource that other tools might want to consume.

The date line reads Last Updated: October 21st, 2026, while the repository received merges on October 29. That eight day lag is a reminder that a hand maintained date field drifts. The commit history is the reliable record, and it shows activity continuing past the stated date. For readers deciding whether the list is current, the answer is yes, with the caveat that the visible date is not automatically regenerated the way the HTML is.

Project card

FAQ

What is this repository?
A single README that indexes 691 game decompilation, disassembly and reconstruction projects in alphabetical order, with a generated HTML version.

Does it host the projects?
No. It hosts links. Every project has its own repository, license and build instructions elsewhere.

How do I find a specific game?
Open the README and use Ctrl+F, which the README itself recommends because the list is long.

Are all entries matching decompilations?
No. The list mixes matching decompilations, disassemblies, reimplementations and source ports, and it does not label which is which.

What does the warning symbol mean?
It flags a project with disclosed AI involvement. Seven entries carry it.

Can I contribute?
Yes. The repository has a contributing guide and a credits file, and additions arrive through pull requests.

Bottom Line

This is the most useful single page in the decompilation scene precisely because it does not editorialize. Six hundred and ninety one links, alphabetically sorted, with a Ctrl+F tip at the top and an automated HTML mirror, is a better research tool than a curated list that hides half its candidates. The loose definition of decompilation is the main weakness: a reader cannot tell a byte matching build from a browser remake without clicking through, and two repositories appear twice. As a starting point for finding whether a game has been taken apart, it has no real rival at this scale.

Sources

• GitHub SamidyFR/Game-Decompilations README, entry list, notes, contributing guide and date line, accessed October 29, 2026
• GitHub API metadata for SamidyFR/Game-Decompilations, stars, forks, contributors, issues and commit history, accessed October 29, 2026
• Link counting performed on the README as retrieved on October 29, 2026, including duplicate URL checks

Related: RecompStore: A Homebrew App Store for Jailbroken PS5 Recomps | Cubyz: Zig Voxel Sandbox Rebuilt From Java With 3.7k Stars