# Godot PCK Explorer treats the PCK container as something you can edit, not just read

> GodotPCKExplorer is a viewer and editor for Godot Engine's PCK files that can explore, extract, create, patch, merge and split them, supports Godot 3 and 4 including encrypted packages, and ships as a Windows UI app and a cross platform console tool.

**DmitriySalnikov/GodotPCKExplorer** — Small program for exploring and extracting files from the Godot Engine PCK

- Repository: https://github.com/DmitriySalnikov/GodotPCKExplorer
- Stars: 563 · Forks: 57
- Language: C#
- License: MIT
- Published: 2026-10-22 · Updated: 2026-10-22 · Language: en
- Canonical page: https://hysenlabs.com/projects/dmitriysalnikov-godotpckexplorer

## The container, not the project

Godot PCK Explorer is described as a small program for exploring and extracting files from the Godot Engine PCK, and the README puts it more precisely: a viewer and editor for Godot Engine's PCK files with the ability to extract content and create new packages. It supports Godot 3 and 4.

The distinction between the PCK and the Godot project is the whole scope of the tool. A PCK is the archive Godot produces when you export a project, and a developer working inside the Godot editor has no need to look inside one. The people who do need to look inside one are the ones shipping a game with custom assets, building a mod, or trimming a build down.

That also explains the feature list, which is much more than a viewer. The tool can explore existing PCK files, regular or embedded. It can extract content from a PCK file. It can create new PCK files, or embed the folder as a PCK into any other files. It can patch PCK files and replace some of their contents with new files from the folder. It can merge an existing PCK into other files. It can change the version of an existing PCK. It can extract a whole embedded PCK, remove an embedded PCK, and split files with an embedded PCK into two separate files. And it supports encrypted Godot 4 PCK.

The project is written in C#, the licence is MIT, and the recent releases are 1.6.0 from 2025-09-21, 1.5.3 from 2025-03-16 and 1.5.2 from 2025-01-02.

## Embedding, merging and splitting, which is the unusual part

Most archive tools let you read and write an archive. This one treats the container as a thing you can graft into other files, and that is where the interesting behaviour lives.

Embedding is the first of those. The tool can embed the folder as a PCK into any other files, and it can extract a whole embedded PCK, remove an embedded PCK, and split files that contain an embedded PCK into two separate files. So a game executable with a PCK appended to it can be taken apart and put back together, which is a real capability rather than a convenience.

Merging is the second. Merging an existing PCK into other files means combining archives rather than just concatenating bytes, so the tool has to understand the index structures it is merging and keep them consistent.

Patching is the third, and it is the one that changes the format rather than just the contents. Patching a PCK replaces some of its contents with new files from the folder, keeping the rest. In Godot 4.4, support for removing files in PCK patches was added, and this program supports that feature. The mechanism has a visible side effect: files with the Removal flag will have .@@removal@@ in the name when extracted, and the .@@removal@@ is removed from the name and converted back into the Removal flag when packing.

That marker is a design decision worth understanding. Because a removal is not a file, it cannot be represented by an empty file, so the tool has to smuggle the information through the filename and then translate it back on the way in. It is a small hack that keeps the round trip lossless, and it is the kind of detail that tells you the author has thought about round trips.

## user:// paths survive the round trip, in a folder called @@user@@

The other piece of format knowledge the tool preserves is the user:// path prefix, and the way it handles it is the most user visible of the special cases.

PCK Explorer supports paths with the prefix user://. When extracting, files with the user:// prefix are placed in the folder @@user@@. When packing, files from @@user@@ will have the user:// prefix added back.

So the two special names, @@user@@ and .@@removal@@, are the visible consequences of two things the format does that a plain folder listing cannot express. user:// is a virtual location rather than a path on disk, and a removal is a marker rather than a file. The tool handles both by translating them to and from plain directory names at the boundary, and it does it symmetrically, so an extract followed by a pack returns the same archive.

That symmetry is the property that makes the tool usable for the actual job, which is editing a shipped package. If a round trip lost the user:// prefix or dropped removals, then explore, extract, edit, repack would silently corrupt the archive, and the tool would be unusable for anything beyond inspection.

The screenshots in the README show a main window, a pack window, a pack window with patching, and a change version window, which is a reasonable picture of the four workflows: look, build, patch, and retarget an archive at a different Godot version.

## Installing it and running the console for the first time

The distribution is unusual enough to be worth spelling out, because it changes what you install.

The program is available in two versions. The UI version supports only Windows and requires the installation of the .NET Desktop Runtime. The Console version supports Windows, Linux and macOS.

The console version is not a stripped build, it is the same functionality exposed differently, because the README says all these features are also available via the console, and you just write GodotPCKExplorer.Console.exe with -h to get help.

On top of that there are two build flavours per platform, which arrived in version 1.4.2. The native version is a standalone program that does not require anything extra to run. The dotnet version requires .NET 9 to work, and its download should be prompted when you run the .exe files in Windows if it has not been installed previously. The .NET Desktop Runtime is required to use the UI versions of the program.

On Linux and macOS, you just need to install the .NET Runtime, and you run it with the command `dotnet GodotPCKExplorer.Console.dll [some arguments]`. The README links to the .NET 9 download page.

So the practical decision is: on Windows with a graphical workflow, take the native UI build and install nothing; on Linux or macOS, take the console build and have the .NET Runtime available. The single sentence of the README, that the native version requires nothing extra to run, is the reason most people will pick it.

The first run is the help output. The README says all of these features are also available via the console, and that you just write `GodotPCKExplorer.Console.exe -h` to get help. So the practical first use is to download the build for your platform, run that command, and pick an operation from the list: explore an existing PCK, extract from it, create a new one, or patch an existing archive with files from a folder.

The download itself is a binary release rather than a build. The README says the binaries of the latest version are available on itch.io or on the GitHub Releases page.

## Where Godot PCK Explorer is the wrong tool

Three cases, and the first one is the most common misunderstanding.

If you are developing a Godot game rather than shipping one, this tool does nothing for you. It operates on exported PCK archives, not on the project directory. The assets in your project are edited in the Godot editor, and the export is regenerated from there. Reaching for a PCK tool at that stage is like unzipping a jar to edit source.

The second is the encryption case, and it is a boundary rather than a bug. The tool supports encrypted Godot 4 PCK, and the repository also includes a PCK Bruteforcer in a Bruteforcer/ directory, which the README links as part of the project. The support is scoped to Godot 4 encrypted packages, and the README does not describe the key handling, the limits of the search, or what the bruteforcer does when it cannot succeed. If your use of encrypted archives involves anything beyond your own content, you need to read that code before relying on it.

The third is that the tool does not change the format. Changing the version of an existing PCK is a supported operation, and it is the one that most looks like a shortcut, so it is worth being clear about what it is: it rewrites the version marker in a container. It does not make a Godot 3 archive load in Godot 4, because the contents still have to be in a format the newer engine understands. The version field is not the compatibility.

And a practical one for the console build: it takes arguments and produces output, but the README does not document a scripting interface, so anyone planning to automate large numbers of packages should check the tests/ directory and the Core/ directory to see what is actually reusable.

## A small project, funded by donations, still shipping releases

The Support section is a Boosty donation link and a USDT TRC20 address, which tells you this is an independent tool maintained by one person rather than a company product.

The repository layout backs that up. There is an Explorer/ directory, which is the Windows UI, a Core/ directory, which is the shared library, a Bruteforcer/ directory, a Tests/ directory, a HexEditorStructures/ directory, and an Images/ directory holding the screenshots used in the README. The solution file is GodotPCKExplorer.sln, with a Directory.Build.props for shared build settings and a version.txt holding the version number.

The presence of a separate Core/ directory is the interesting structural choice. Splitting the format handling out from the Windows Forms interface is what allows the same logic to be driven from the console build on Linux and macOS, and it is what makes the code testable independently of a UI.

The builds are released as binaries on itch.io and on the GitHub releases page, with the version in version.txt matching the release tags. The repository is not archived and the last push was on 2026-06-13, so the project is being worked on, and the release numbering shows steady, roughly quarterly progression through 2025.

For a tool that touches the format of a shipped game, that combination of a permissive licence, a separated core, tests and consistent releases is a reasonable basis for trusting it with your own archives.

## Conclusion

Adopt Godot PCK Explorer if you ship Godot games and need to inspect, repack, patch or embed PCK archives, including building game-specific packages for modding or for shipping a trimmed asset set. Do not adopt it if your work is inside a Godot project rather than on its exported archives, since it operates on the built packages, not on the project. Before you rely on it, check which of the two download builds suits your platform, and note that the UI version needs the .NET Desktop Runtime while the console version runs on Windows, Linux and macOS with the plain .NET Runtime.

## FAQ

### What can Godot PCK Explorer do?

It is a viewer and editor for Godot Engine PCK files: explore existing PCK files, regular or embedded, extract content, create new PCK files, patch contents, merge an existing PCK into other files, change the version of an existing PCK, extract, remove or split embedded PCK, and it supports encrypted Godot 4 PCK.

### Which platforms does Godot PCK Explorer run on?

The UI version supports only Windows and requires the .NET Desktop Runtime, while the Console version supports Windows, Linux and macOS. From version 1.4.2 there are native builds that require nothing extra to run and dotnet builds that require .NET 9.

### How does Godot PCK Explorer handle the user:// path prefix?

When extracting, files with the user:// prefix are placed in the folder @@user@@, and when packing, files from @@user@@ get the user:// prefix back. The same round trip logic applies to the .@@removal@@ marker used for files with the Removal flag.

### Where can I download Godot PCK Explorer?

Binaries of the latest version are available on itch.io or on the GitHub Releases page. The repository also includes a PCK Bruteforcer in the Bruteforcer/ directory, and the project is MIT licensed.

## Sources

- [DmitriySalnikov/GodotPCKExplorer on GitHub](https://github.com/DmitriySalnikov/GodotPCKExplorer)
- [Issues](https://github.com/DmitriySalnikov/GodotPCKExplorer/issues)
- [License: MIT](https://github.com/DmitriySalnikov/GodotPCKExplorer/blob/master/LICENSE)
- [README](https://github.com/DmitriySalnikov/GodotPCKExplorer/blob/master/README.md)
- [Releases](https://github.com/DmitriySalnikov/GodotPCKExplorer/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/dmitriysalnikov-godotpckexplorer