Iso2God Windows Setup: Complete Install and First Conversion Guide

On Windows you have two solid routes: the r4dius GUI v1.6.0 — a quality-of-life fork of the classic Iso2God interface, and the best choice for most people — or the iso2god-rs command-line tool if you prefer scripting and batch work. This page sets up the GUI completely: download, checksum verification, the .NET Framework note, and a first-conversion checklist you can follow in order. Linux and Mac users have native builds instead — see the links at the end.

Everything here starts from our download page, which links to the upstream GitHub releases. This site is an unofficial fan resource. And the console rule applies to every route: converted GOD packages need a modded Xbox 360 (JTAG, RGH or BadUpdate-class) or the Xenia emulator — not a stock retail console.

What you are installing, honestly labelled

The GUI on our download page is the r4dius fork, release v1.6.0 (26 January 2026). It is a decompilation-based quality-of-life mod of the original Team 360h v1.3.6 program — its own binary says exactly that, and states it is not supported by Team 360h. That honesty is a feature: the original 2010 program is closed-source freeware with no surviving trustworthy download, so no site can offer you a verifiable original binary. The fork is the GUI that can actually be downloaded from its maintainer’s GitHub and checked with a checksum. Fork additions include multi-ISO selection and drag-and-drop, a choosable FTP destination path, options to delete the source ISO or GOD after conversion or upload, corrected game names from its bundled game lists, a resizable window, and support for original Xbox Redump images.

Step 1 — Download and verify

1. Download the r4dius fork v1.6.0 zip from the upstream GitHub release — 562,728 bytes.
2. Unzip it anywhere you like; there is no installer. The folder contains Iso2God.exe plus the bundled xextool.exe helper and the two game-list CSV files the program uses for title lookup — keep them together in the same folder.
3. Verify the zip before unzipping if you want full assurance: its SHA-256 is 7288a31b884332d6436c9fb00e4573b58ea53062b21cbd3b828d8af651d759ac. We computed this locally and it matches the digest recorded by GitHub for the release asset. In PowerShell, Get-FileHash on the zip prints the value to compare.

Step 2 — The .NET Framework note

The GUI is a .NET Framework Windows Forms program (the fork project targets .NET Framework 4.8.1). Most current Windows 10 and Windows 11 installs already carry a compatible .NET Framework, and the program will simply open. If Windows instead reports that a .NET Framework is missing or the application fails to start, install the current .NET Framework 4.8.x runtime from Microsoft, then launch the program again. No other runtime, driver or codec pack is part of this setup, and nothing in the zip needs to be installed system-wide — the program runs from its folder.

One practical note: because the program is a small unsigned community build, Windows SmartScreen may show its standard prompt for unrecognised apps on first launch. Your protection in this workflow is provenance, not a prompt in either direction: a zip whose SHA-256 matches the value above is byte-identical to the file the maintainer published on GitHub.

Step 3 — First conversion checklist

1. Launch Iso2God.exe from the unzipped folder (with xextool.exe and the CSV files still beside it — the program uses them to extract and look up title metadata).
2. Click Add ISO and choose your Xbox 360 or original Xbox ISO. You can add several, or drag and drop them, and process a queue disc by disc — for multi-disc games, queue each disc separately.
3. Review the entry: check the game name, Title ID and Media ID shown, and the thumbnail. If the name is wrong, edit it before converting — it becomes part of the finished package.
4. Choose padding removal deliberately (see the next section): None, Partial or Full.
5. Choose the output format: GOD package, GOD plus a rebuilt ISO, or a rebuilt ISO only.
6. Set the output folder, then click Convert and let the queue finish without moving the source ISO mid-conversion.
7. Check the result: a GOD header file plus its .data folder of part files. Keep the pair together.
8. Transfer it: copy both to Content\0000000000000000\<TitleID>\00070000\ for the stock dashboard layout on a modded console, place it in any scanned folder for Aurora or Freestyle Dash — or use the GUI’s built-in FTP settings to upload it to the console directly.

For the click-by-click walkthrough with screenshots described step by step, continue to how to use Iso2God after this setup is done.

Choosing padding removal

Mode	What it does	When to use it
None	Keeps the disc layout byte-faithful, padding included	When a game is known to need its padding, or for a first safe conversion
Partial	Removes some padding	The safe general default — and the documented requirement for Tetris – The Grand Master Ace, which breaks with full removal
Full	Removes all padding; also how the GUI rebuilds a shrunken ISO	For maximum space saving on games with no known padding sensitivity

Smaller packages take less console storage and transfer faster, but Full is not universally safe. The clearest counter-example besides Tetris: Wolfenstein: The New Order Disc 1 acts as an installer and needs its padding left intact for its first GOD conversion, per console-modding documentation. When in doubt, convert with Partial first and only re-convert tighter if you need the space.

The command-line alternative: iso2god-rs on Windows

If you convert in batches or want identical behaviour across Windows, Linux and Mac, use iso2god-rs for Windows — a single .exe (1,129,984 bytes, SHA-256 1459fcf8ff5a89e039b02c68c06b006b7a036f3b1ca237c2d7e03d61bd211d47, verified against GitHub). Usage is one line — iso2god-x86_64-windows.exe game.iso output-folder — with --dry-run, --trim (end-trimming only) and -j thread options. Know its scope: ISO to GOD only, no GUI, no folder input, no FTP. Our iso2god-rs guide covers it fully. Note its version quirk too: the v1.8.1 binary reports itself as 1.8.0 when asked — that is a known, verified quirk of the release, not a wrong download.

After setup

Set up on another system as well? The same rs tool runs natively on Linux and Mac. For the big picture see which Iso2God version to use, the Version History and the Platforms hub.

Frequently asked questions

Do I need to install Iso2God, or does it run from the folder?

It runs from the folder. Unzip the r4dius fork release, keep Iso2God.exe together with xextool.exe and the game-list CSVs, and launch it. There is no installer and nothing is added system-wide.

Which .NET version does the Windows GUI need?

It is a .NET Framework Windows Forms program; the fork project targets .NET Framework 4.8.1. Most Windows 10/11 systems already have a compatible framework. If Windows reports it missing, install Microsoft’s .NET Framework 4.8.x runtime and launch again.

Is the GUI the original 2010 program?

It is a decompiled quality-of-life fork (r4dius v1.6.0) of the original Team 360h v1.3.6 — the fork’s own binary states this and notes it is not supported by Team 360h. No trustworthy download of the untouched original survives, which is why the verifiable fork is the GUI we link.

Which padding mode should a beginner pick?

Partial. It saves meaningful space and is the documented safe choice for sensitive titles such as Tetris – The Grand Master Ace. Avoid Full until you know a game tolerates it, and leave padding intact entirely for installer discs such as Wolfenstein: The New Order Disc 1.