AnyPS5 Workbench on Windows: source ZIP to a separate converted-game folder

The key checkpoint: Select a supported source snapshot, your own prepared game and a separate output. Conversion success and a successful gameplay test are two different checkpoints.

Before you start

Use the recorded versions and the supported inputs listed in the original notes below.
Compare the last successful checkpoint before choosing a fix.
Keep original files, relevant logs and a known working setup when testing changes.

Resources from this video

Links, downloads & documentation

Every original URL from the video description is collected here, including recorded releases, setup discussions and related videos. Use the version-specific notes when following a recorded build.

01Get Workbenchhttps://drive.google.com/file/d/1zBZyXSL615M7AOCoJQfg9JyWAlZz-2n9/view?usp=sharing 02Official AnyPS5 sourcehttps://github.com/boykopovar/AnyPS5 03Usage and runtime layouthttps://github.com/boykopovar/AnyPS5/blob/main/docs/user/USAGE.md 04Build instructionshttps://github.com/boykopovar/AnyPS5/blob/main/docs/dev/BUILD.md 05Game bring-up reportshttps://github.com/boykopovar/AnyPS5/discussions/categories/game-bring-up

Watch the complete video

Open this video on YouTube ↗. Screenshots below link to their exact recorded moments.

Walkthrough 01

Extract the complete Workbench app

Video reference 1:05 ↗

The Workbench download is linked in the resources section. Extract the entire app ZIP into a folder, keep its files together, and open Any PS Five Workbench dot exe. You don't need Python or developer tools already installed just to open the app. Keep an internet connection available for the initial setup, and leave enough disk space for the build files and another copy of your game. The screen is arranged in three parts: Source snapshot, Game input, and Windows output.

We'll go through them in that order.

Open AnyPS5 Workbench — recorded frame — 1:05 in the video · Open AnyPS5 Workbench. Select the screenshot to open this point in the original video.

Walkthrough 02

Choose a supported source snapshot

Video reference 2:22 ↗

First, open the official Any PS Five GitHub page linked in the resources section. On the Code tab, open the green Code menu and choose Download ZIP. This gives you a snapshot of the source on the selected branch. Save that ZIP, then select it with Browse ZIP under Source snapshot. Here, you can see the source ZIP I've selected. You can also see a Download latest source option in Workbench, but I'm showing the GitHub ZIP route in this recording.

This is the part that lets you try a supported source snapshot without waiting for it to be packaged into a Windows release.

Select your prepared game folder — recorded frame — 2:22 in the video · Select your prepared game folder. Select the screenshot to open this point in the original video.

Walkthrough 03

Select and identify your prepared game

Video reference 3:07 ↗

Next, under Game input, click Folder and choose your prepared game folder. Use a dump of the game you own, with its executable, modules and assets kept together. Workbench needs usable, decrypted game data; it doesn't decrypt an encrypted package. If your prepared game is in a supported ZIP, the ZIP button is the alternative. I'm selecting the folder route here. Click Find games and check the title it detects. Mine is Hollow Knight: Silksong.

If you selected a collection folder, choose the game you actually want from the list before continuing.

Output folder and CPU options — recorded frame — 3:07 in the video · Output folder and CPU options. Select the screenshot to open this point in the original video.

Walkthrough 04

Keep converted output separate

Video reference 4:21 ↗

Under Windows output, choose where the converted game should go. Use a short folder path with enough free space, separate from your original game folder. My output location is already selected here. There's also an Intel CPU compatibility option. Use that option for an Intel processor; I'm using an AMD processor, so I leave it off. It isn't a frame-rate boost setting. I'll leave Fixed base at its default and Build jobs on Auto. With the source, detected title and output checked, click Convert to Windows.

You don't need to run Build engine only first for this route.

Conversion complete, output files and launch — recorded frame — 4:21 in the video · Conversion complete, output files and launch. Select the screenshot to open this point in the original video.

Walkthrough 05

Wait for conversion and test the result

Video reference 5:18 ↗

Now Workbench verifies the inputs, prepares the build tools, builds the matching engine, and converts and packages the game. The first build can take time because it may need to download and compile dependencies. Later attempts can reuse cached files. Watch the stage name and the log on the right to see what it's doing. I'm accelerating this waiting period in the video; the conversion itself is not instant. Let it finish until the status says Windows EXE created.

That confirms the conversion completed. The next check is whether the game actually runs. Open the output folder and you can see what was created. Play dot exe sits beside the app zero folder, the libs folder, fonts, and the supporting files. Keep this package together when you move it; copying just the executable can leave it without the files it needs. Back in Workbench, click Run converted game. That launch route also captures a run log, which is useful if something goes wrong.

Give the first launch time to initialize. Here we reach the Team Cherry logo, then the Silksong title screen, and then the opening area. Here is the result at normal speed. The game is responding to my inputs, movement is working, and the recording has game audio. The frame counter changes during the run, so treat it as an on-screen reading from this test, not a promised frame rate for your PC.

Gameplay and original game sound — recorded frame — 5:18 in the video · Gameplay and original game sound. Select the screenshot to open this point in the original video.

Walkthrough 06

Retest revisions and keep useful logs

Video reference 6:38 ↗

When you want to test a newer supported source snapshot, choose its ZIP and convert again. Workbench builds the matching files for that snapshot, instead of mixing a new executable with old system libraries. Updating the Workbench app or downloading a new source ZIP does not automatically update a game you've already converted. Keep the earlier working output until you've tested the new one. And if upstream changes its build requirements beyond what Workbench supports, the frontend may need an update too.

If your attempt fails, first separate a build problem from a launch problem. If the app never reaches Windows EXE created, use Open log and check the reported download, source or build error. If it creates the executable but the game crashes or renders incorrectly, check the game's compatibility report and the exact source version being tested. A newer source snapshot can help a particular game, but it doesn't guarantee that every game will work.

Workbench also has an Export community report option for sharing captured diagnostics after you review them. We aren't going through that separate reporting workflow in this demonstration.

Build errors, launch errors and logs — recorded frame — 6:38 in the video · Build errors, launch errors and logs. Select the screenshot to open this point in the original video.

If your result differs

Situation	Next useful check
The process stops at a different checkpoint	Record the exact message, current build and last successful stage. Compare that stage with the matching video section.
A setting is selected but the result differs	Repeat the same scene and change one option at a time. A menu target does not establish measured performance.
A newer release changes the interface	Check the linked release notes and instructions. This companion preserves the recorded route and its limitations.

Search This Blog

ItsOOGWAY