NXE2GOD vs Iso2God: On-Console Conversion vs PC-Side Conversion
NXE2GOD and Iso2God reach the same destination — a disc game as a Games On Demand (GOD) package that a modded Xbox 360 can run without the disc — from opposite directions. Iso2God works on a PC: it converts an ISO image file into a GOD package you then transfer to the console. NXE2GOD works on the console itself: it converts a game you already installed with the stock dashboard (an NXE install) into a GOD package in place. Choosing between them is mostly choosing where the game currently lives.
One requirement is shared and non-negotiable: both routes need a modded console (JTAG, RGH or a BadUpdate-class exploit). A GOD package carries an unlocked licence; a stock retail 360 only runs GODs it downloaded itself and NXE installs that still demand the disc. No converter changes that.
The short answer
| Iso2God (PC-side) | NXE2GOD (on-console) | |
|---|---|---|
| Runs on | A Windows PC (GUI fork); iso2god-rs adds Linux/macOS | The Xbox 360 itself, as homebrew |
| Input | An ISO image of the game (360 or OG Xbox) | An existing NXE disc install on the console’s storage |
| You need the disc? | No — you need a dumped ISO image | Yes, for the initial NXE install the conversion starts from |
| Output | A GOD package on the PC, then transferred (USB/HDD/FTP) | A GOD package created in place on the console |
| Padding control | Yes — None / Partial / Full modes in the GUI | No equivalent documented control; it converts the install as it stands |
| Best when | Your library is ISOs on a PC; you convert in bulk; you want FTP upload and metadata control | The game is already installed from disc on the console and you just want it disc-free |
Why NXE installs need converting at all
When a stock Xbox 360 installs a game from disc, it writes an NXE install — a package that is technically a near-twin of a GOD (both are SVOD containers) but signed differently (PIRS rather than LIVE) and locked to the installing console, with the disc required in the tray as a licence check. On a modded console that lock is pointless friction: the game is already on your hard drive, yet you still need the disc to start it.
NXE2GOD exists to remove exactly that friction. It re-packages the on-console NXE install as a GOD with an unlocked licence, so on a modded console the installed game launches without the disc — the standard route documented by the ConsoleMods wiki. No PC, no ISO, no transfer step: the conversion happens where the game already sits.
Why Iso2God still wins for library work
- Your source is an ISO, not a disc. NXE2GOD cannot start from an ISO file at all — it only converts installs that already exist on the console.
- Bulk and repeatability. Converting a library on the PC — with queues, padding choices and optional FTP upload in the GUI fork, or full scripting with iso2god-rs — beats installing discs one at a time (see GUI vs CLI workflows).
- Padding and size control. The GUI’s Partial/Full modes shrink packages before they ever reach the console’s drive; an on-console conversion works with the install as written.
- Metadata. The PC GUI shows and lets you edit name, Title ID, Media ID and thumbnail before converting.
- Original Xbox games. The PC tools convert OG Xbox ISOs to GOD as well; NXE2GOD’s world is the 360’s own disc installs.
An honesty note on versions
We do not print a version number for NXE2GOD on this page, because we could not verify one from a primary source — it is distributed through console homebrew channels rather than a canonical release page we can cite. Sites that state a precise “latest NXE2GOD version” without a source are guessing. What is documented, by the ConsoleMods wiki, is its role: the standard on-console route from NXE install to GOD on modded consoles.
Which should you use?
- Game already installed from disc on your modded 360, want it disc-free: NXE2GOD — nothing leaves the console.
- Library of ISOs on a PC: Iso2God / iso2god-rs, then transfer (USB, HDD or the GUI’s FTP upload).
- Both situations across a collection: use both — they produce the same kind of package and coexist happily on the same drive. Custom dashboards like Aurora scan GODs wherever they sit, whichever tool made them.
- You later need an ISO back from a GOD: neither tool — see God2Iso.
One last practical note: neither route touches the other route’s work — packages made on the PC and packages converted on the console sit side by side in the same Content layout.
What happens to saves, DLC and multi-disc games
A few household details apply whichever route you choose, because both produce the same kind of package. Your saves and profile are untouched by conversion — they live separately from the game package. Downloadable content is a separate matter from the base game: on the stock dashboard layout, DLC still has to sit under the console’s Content tree in the documented location even when the game itself was converted on the console; converting the game does not move or convert its DLC. For multi-disc games, custom dashboards such as Aurora and Freestyle Dash swap GOD discs automatically, while stock-dashboard-plus-XeXMenu setups rely on DashLaunch’s autoswap setting — worth knowing before you convert a two-disc game either way and wonder why disc two never loads.
Time and effort, honestly compared
For a single game already installed on the console, NXE2GOD is unbeatable: no dumping, no PC transfer, no re-copying gigabytes back. The cost was already paid when the NXE install was written from the disc. For anything at library scale the arithmetic flips — installing discs one by one on the console, then converting in place, serialises your whole collection through a single optical drive, while the PC route converts ISO after ISO in a queue (or a script, with logging) and can FTP the results back in bulk. There is also a resilience difference: a PC-side library of ISOs plus GODs is trivially backed up and re-converted with different settings years later, while an on-console-only library exists exactly once, on one ageing drive — one more reason the PC route, or at least a PC backup of its results, anchors most serious collections.
Frequently asked questions
Does NXE2GOD work on a stock Xbox 360?
No. It is homebrew — it only runs on a modded console — and the GODs it produces carry an unlocked licence that a stock console refuses anyway. The same is true of Iso2God’s output.
Can NXE2GOD convert an ISO on my PC?
No. NXE2GOD runs on the console and converts NXE disc installs that already exist on its storage. PC-side ISO conversion is Iso2God’s job.
Do I still need my game discs after using NXE2GOD?
That is the point of the conversion: on a modded console, the converted GOD launches without the disc in the tray. Keep your discs as your originals regardless.
What about Aurora’s disc-to-GOD script?
Aurora, the current custom dashboard, also offers an on-console Disc-to-GOD script — a neighbouring option in the same family as NXE2GOD. NXE2GOD remains the named, documented converter for existing NXE installs.
PC-side downloads and hashes are on the download page; the rest of the head-to-heads are in the Comparisons hub.