gdsdecomp: recovering Godot projects from PCK, APK and EXE files
Godot reverse engineering tools
At a glance
- What is it?
- GDRE Tools is an MIT-licensed C++ toolkit that decompiles GDScript, extracts PCK archives and rebuilds a Godot project directory. It covers Godot 2.x, 3.x and 4.x, and the command line is where most of the real work happens.
- Who is it for?
- Use gdsdecomp when you need to read your own shipped build, audit a Godot title you have permission to inspect, or recover a project whose source is gone. Do not use it as a way to lift assets from someone else's game, and do not expect it to produce a build-ready tree: bytecode recovery depends on the engine version, and the README does not promise that a recovered project compiles unchanged.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 32 days ago.
- What is it written in?
- Mainly C++, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- GDRETools/gdsdecomp4,462 ★ · +243
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| GDRETools/gdsdecomp | 4.2k | 4.5k |
243 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What gdsdecomp recovers, and who needs it
A shipped Godot game is not a folder of .gd and .tscn files. The exporter packs resources into a PCK archive, converts imported assets into engine-specific formats, and compiles scripts to bytecode. If the source tree is lost, the build is the only copy left. gdsdecomp exists for that situation. The README lists its scope plainly: full project recovery, a PCK archive extractor and creator, a GDScript batch decompiler, and a resource text/binary batch converter.
The full recovery path is the ambitious one. According to the README it loads resources from an APK, PCK or embedded EXE, decompiles all GDScript, recovers the original project file, converts imported resources back to their original import formats, converts auto-converted binary resources back to text, and recreates plugin configuration files. That is a pipeline, not a single command, and each stage can fail on its own.
Who is this for? Developers who shipped a build and then lost or corrupted the repository. Studios doing a code audit of a contracted Godot deliverable. People studying how a particular Godot game is structured. The tool supports Godot 4.x, 3.x and 2.x projects, which matters because bytecode formats changed across those lines.
How the recovery pipeline actually works
The repository layout tells you the architecture. There are separate top-level directories for bytecode, crypto, exporters, plugin_manager, standalone and gui, plus a bytecode_generator.py and a prepop_cache.py at the root. The bytecode directory is the interesting one: GDScript bytecode is not stable across engine releases, so the tool needs a definition for each revision it supports.
The README notes that --compile, which compiles GDScript files to bytecode, requires --bytecode.
There is also a godot-mono-decomp directory in the repository. The README does not describe what that component does in detail.
Installing gdsdecomp and running a first recovery
The README points to the releases page on GitHub as the place to get binaries. On Windows there is a Scoop route, which the README gives as two commands: add the games bucket, then install the package.
scoop bucket add games
scoop install gdsdecompThe README does not document a Linux or macOS package; outside Windows you download a release or compile from source by cloning the repository into Godot's modules subfolder as gdsdecomp and rebuilding the engine.
The GUI path is the shortest: open the application, pick "Recover project..." from the "RE Tools" menu, or drag a PCK or EXE onto the window. For anything scriptable, use headless mode. The README's usage line is:
gdre_tools --headless <main_command> [options]A first real use is to look before you extract. Listing the archive is cheap and tells you whether the file you have is the one you think it is:
gdre_tools --headless --list-files=<GAME_PCK/EXE/APK>The README says --list-files lists all files in the specified PCK, APK or EXE and exits, and that it can be repeated. Once the listing looks right, run the full recovery:
gdre_tools --headless --recover=<GAME_PCK/EXE/APK/DIR>Include and exclude globs filter what gets recovered; the README notes they only match files actually present in the project PCK or directory.
Where gdsdecomp runs into trouble
The README's Limitations section says support has yet to be implemented for converting 2.x models (dae, fbx, glb, etc.) and GDNative or GDExtension scripts.
Include and exclude globs are the other trap. They only match files that are actually in the project PCK or directory, not source files that were never shipped: if a project contains res://main.gdc but not res://main.gd, an include glob of res://main.gd recovers nothing, while res://main.gdc recovers res://main.gd.
Finally, the README says to edit a recovered project with the same Godot tools version the original game was compiled in; the recovery log states which version was detected.
gdsdecomp against a plain PCK extractor
The obvious alternative is a bare PCK extractor: a small tool that unpacks the archive and stops there. The difference is what you get at the end. An extractor leaves you with the packed forms of the resources and the compiled .gdc scripts. gdsdecomp's recovery path is designed to go further, converting imported resources back to their original import formats and auto-converted binary resources back to text, then recreating the project file and plugin configuration files.
That is a real difference in output, and it comes with a cost in surface area: the command line also covers extraction, file listing, compiling and decompiling. If all you need is a file listing or a raw dump, a minimal extractor is easier to reason about. If you need a project directory that Godot can open, the conversion stages are the whole point.
The other comparison is to the engine itself. gdsdecomp is built as a Godot engine module: the README says to clone it into Godot's modules subfolder and rebuild the engine from the project's own Godot fork, so it is an engine build rather than a from-scratch reimplementation of resource handling.
Licence, maintenance and what an upgrade costs you
The repository is MIT licensed, with a LICENSE file at the root. For most users that means you can use, modify and redistribute the tool, including in commercial work, provided the licence text and copyright notice travel with it. That is the general shape of MIT; it is not legal advice, and if you are redistributing gdsdecomp inside a product you should read the LICENSE file yourself rather than take a summary.
Maintenance is visible in the release history. The most recent push to the repository was on 2026-10-14, and the same date carries the v2.8.0-beta.2 release. Before that came v2.7.4 on 2026-10-11 and v2.8.0-beta.1 on 2026-10-10. The current line is a beta, with a stable 2.7.4 sitting just behind it. That is a normal pattern for a tool that has to track engine changes.
The upgrade cost is the part to think about before you depend on this. Bytecode definitions are versioned against engine revisions, so a new Godot release can require a new gdsdecomp release before your target decompiles. If your workflow assumes a specific Godot version, pin the gdsdecomp release alongside it rather than tracking the latest beta.
Building a patched PCK and translating an existing release
Recovery is only half the tool. The README lists a PCK archive extractor / creator and a resource text <-> binary batch converter among the module features, and the command line includes --extract to unpack a PCK, APK or EXE and --compile to compile GDScript files to bytecode, which requires --bytecode.
Editorial conclusion
Use gdsdecomp when you need to read your own shipped build, audit a Godot title you have permission to inspect, or recover a project whose source is gone. Do not use it as a way to lift assets from someone else's game, and do not expect it to produce a build-ready tree: bytecode recovery depends on the engine version, and the README does not promise that a recovered project compiles unchanged. Before trusting a recovery, run --list-files on the archive to confirm the file set, then check the recovered project.godot against the engine version you intend to open it with.
Frequently asked questions
How do I decompile a PCK file with gdsdecomp?
Run gdre_tools --headless --recover=<GAME_PCK/EXE/APK/DIR> to perform full project recovery, which decompiles the GDScript as part of the run. The README also documents --decompile to decompile GDC files to text.
Can Godot games be decompiled?
The README states that gdsdecomp supports decompiling Godot 4.x, 3.x and 2.x projects, and that full project recovery decompiles all GDScript scripts. Compiled scripts are matched to a bytecode revision, so support depends on the engine version the game was built with.
How do I open a PCK file in Godot Engine?
gdsdecomp does not describe opening a PCK directly in the editor. Its documented routes are full project recovery, which rebuilds a project directory from the archive, or --extract, which unpacks the PCK, APK or EXE without the conversion stages.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/gdretools-gdsdecomp)Star history chart for your README
[](https://hysenlabs.com/projects/gdretools-gdsdecomp)Was this useful?