XGD2 vs XGD3 Explained: XGD1, XGD2, XGD3 and XSF Disc Formats
XGD2 vs XGD3 is, at heart, a before-and-after story: XGD2 is the launch-era Xbox 360 disc format, and XGD3 is its 2011 successor, which gave developers roughly an extra gigabyte of data on each disc — about 8.13 GB in total against the roughly 7 GB class of XGD2. For Iso2God conversion, the practical news is reassuring: the modern converter iso2god-rs detects and accepts XGD1, XGD2, XGD3, and XSF images, so the format on your disc rarely decides whether a conversion is possible.
These letters get thrown around in forums as if they were quality grades or copy-protection settings you can toggle. They are neither. They are successive generations of the Xbox Disc (XGD) layout — the physical and logical format a game was mastered in — and which one you have is fixed by when and how the game was produced. This page walks the generations in order, states only what contemporary sources support, and finishes with what each format actually means at conversion time.
If you have an XGD3 image in front of you and a problem to solve, the dedicated walkthrough is the XGD3 Iso2God guide. All of the converters mentioned are on the download page.
The four names, in era order
| Format | Era and platform | What defines it |
|---|---|---|
| XGD1 | Original Xbox generation. | The first Xbox Game Disc format: the layout of original-Xbox game discs. Iso2God’s whole lineage, back to the original tool, handles original-Xbox images as well as 360 ones. |
| XGD2 | Launch-era Xbox 360. | The standard Xbox 360 disc format from the console’s early years, in the roughly 7 GB class. Most of the back catalogue an Iso2God user meets is XGD2. |
| XGD3 | Xbox 360 from 2011. | The successor format that added roughly 1 GB of usable data per disc (about 8.13 GB total), delivered alongside a dashboard update, and carried new anti-piracy checks. |
| XSF | Recognised by the modern converter’s detection code. | iso2god-rs detects and accepts XSF images alongside the three XGD generations. Our sources document its convertibility, not a marketing history, so this page claims nothing more than that. |
XGD1: the original Xbox format
XGD1 is where the family starts: the game disc format of the original Xbox. It matters to an Iso2God reader for one concrete reason — the conversion lineage never dropped it. The original Iso2God converted original-Xbox ISOs as well as Xbox 360 ones, and iso2god-rs still parses original-Xbox executables (XBE files) alongside Xbox 360 ones (XEX files) when it reads an image. An original-Xbox image in your collection is not an edge case the tools forgot; it is a supported input with its own GOD content type in the package header.
XGD2: the launch-era standard
XGD2 is the Xbox 360’s launch-era disc format and the default mental model for the console’s library: a game mastered into a layout in the roughly 7 GB class, with images padded out to the full mastered size. That padding behaviour is an XGD2-era fact of life that still shapes workflows today — it is why a small game’s ISO still occupies about the full disc size, and why padding removal in Iso2God exists at all. The settings side of that story is in the best padding settings per game.
XGD3: the 2011 step up
XGD3 arrived in 2011 as the format’s mid-generation revision. Contemporary reporting of Microsoft’s own statements put its benefit plainly: it “gives developers an extra 1 gigabyte of data on each disc” — roughly 8.13 GB in total, against the roughly 7 GB class of XGD2. Those figures come from contemporary Microsoft statements reported at the time, not from an official specification sheet, so this page prints them as approximations, which is what they are.
XGD3 reached consoles through a dashboard update, and it also carried new anti-piracy checks — the larger layout was not the only change Microsoft shipped in it. For a modern reader, the anti-piracy context explains why XGD3 generated so much era-specific discussion about drives and burning. That discussion belonged to the disc-burning workflow of the time. It is not part of the ISO-to-GOD workflow: converting an image you already have does not involve a burner, and this page deliberately makes no claims about that separate path.
XSF: the fourth name in the detector
XSF appears in this story in exactly one verified place: the format detection in iso2god-rs, which recognises XGD1, XGD2, XGD3, and XSF images. That is genuinely useful to know if a tool reports your image as XSF — the modern converter accepts it — and it is all our primary sources support. Rather than invent a history for the name, this page leaves it there: detected, accepted, converted.
What the format means for conversion
- Convertibility is not the issue. iso2god-rs reads all four image types and parses both XEX (Xbox 360) and XBE (original Xbox) executables for Title ID and title. The Windows GUI lineage likewise covers Xbox 360 and original-Xbox images.
- Size expectations shift with XGD3. An XGD3 library budgets roughly a gigabyte more per padded game than an XGD2 one. The worked planning examples are in the GOD library storage guide.
- Padding behaviour still applies. XGD3 images are padded layouts too, so the None / Partial / Full decision, and its documented exceptions, apply in the same way.
- The output is the same GOD format. Whatever the input generation, the result is a Games On Demand (SVOD) package: a header plus a
.datafolder of part files, playable on a modded console or in an emulator. The format comparison with extracted games is in GOD packages versus XEX folders.
What this page does not claim
Precision has limits here, and honesty about them is part of the explainer. Our sources do not support printing exact sector counts or security-sector offsets for these formats, and claims of that kind circulating elsewhere were not verified against a primary source in this session, so they do not appear. Likewise, nothing about special burning hardware belongs in a conversion guide. What is verified — the eras, the approximate sizes, the 2011 arrival and anti-piracy context of XGD3, and the converter’s detection list — is enough to make every decision an Iso2God user actually faces.
The console rule, once more
Disc format does not change playback requirements. A GOD package converted from any of these image types carries an unlocked licence and needs a modded Xbox 360 (JTAG, RGH, or a BadUpdate-class exploit), or an emulator such as Xenia on PC — whose own format support is covered in the Xenia GOD format guide. A stock retail console will not run the result, whatever generation disc it came from.
Frequently asked questions
What is the difference between XGD2 and XGD3?
XGD3 is the 2011 successor to the launch-era XGD2 format. It gave developers roughly an extra gigabyte per disc — about 8.13 GB total versus the roughly 7 GB class of XGD2, both approximate — arrived through a dashboard update, and carried new anti-piracy checks.
Can Iso2God convert XGD3 games?
Yes. The modern converter iso2god-rs detects and accepts XGD1, XGD2, XGD3, and XSF images. For XGD3-specific issues, see the dedicated XGD3 guide linked at the top of this page.
What is XGD1?
The original Xbox’s game disc format, and still a supported input: the Iso2God lineage converts original-Xbox images as well as Xbox 360 ones.
Does an XGD3 game take more storage than an XGD2 game?
At padded disc size, roughly a gigabyte more per game, approximately. After padding removal, a GOD package reflects the game’s actual content, so the gap depends on the game rather than the format label.
More explainers and conversion walkthroughs are collected on the Tutorials hub.