Iso2God Padding Explained: None vs Partial vs Full
Iso2God padding explained in one sentence: a retail Xbox 360 ISO is padded up to the full mastered disc layout even when the game itself is small, and the None, Partial and Full modes decide how much of that filler the converter strips when building the GOD package. Partial is the safe default — Full saves the most space but breaks specific games, and None is the fallback those games need.
Why a small game ships as a ~7 GB ISO
A game disc is mastered to a fixed layout. The game files occupy their positions, and the remaining sectors are filled — zeroed or padded out — so the image always spans the whole layout. Period documentation puts it bluntly: Xbox 360 ISOs are zeroed out to 7 GB or so no matter how big the game actually is. XGD2-era images sit in that roughly 7 GB class; XGD3, the 2011 successor format, added about another gigabyte of usable space per disc. The practical consequence: the ISO on your hard drive is mostly not game. It is game plus air, and padding removal is the act of throwing the air away while keeping every byte the game can actually address.
The three modes, precisely
| Mode | What it removes | Resulting size | Risk profile |
|---|---|---|---|
| None | Nothing. The converted layout stays byte-faithful to the source image. | Largest GOD — close to the padded source. | Safest. The mode a game needs when its installer or engine expects the padded layout. |
| Partial | Some padding. The conservative strip built into the GUI workflow. | Noticeably smaller than None, larger than Full. | The recommended default. Documented as the required mode for games that break under Full. |
| Full | All padding it can identify. Also the mode behind the GUI’s rebuilt-ISO output. | Smallest GOD, or a shrunken rebuilt ISO. | Highest savings, highest risk. Some games fail outright; never apply it blindly to a whole library. |
Two savings side effects matter beyond disk space: a smaller GOD also transfers faster over USB and FTP, and a library of Partial/Full conversions is what makes a large collection fit a console drive at all. The honest trade is always the same — space now versus the small chance a given title needed its padding.
The space math, worked generically
Padding math needs no invented per-game numbers — it follows from the layout. Imagine three games whose real file data totals 2 GB, 4 GB and 6 GB, each mastered into the same roughly 7 GB padded image:
| Real game data | Padded ISO | Air inside the ISO | What removal can save at most |
|---|---|---|---|
| 2 GB | ~7 GB | ~5 GB | Up to ~5 GB — small games gain the most. |
| 4 GB | ~7 GB | ~3 GB | Up to ~3 GB. |
| 6 GB | ~7 GB | ~1 GB | Up to ~1 GB — big games were never mostly padding. |
That ceiling is why reports of savings vary so wildly between titles, and why Full versus Partial matters most for small games: on a 2 GB game, the difference between stripping some padding and stripping all of it is measured in gigabytes; on a near-full disc, all modes converge. Judge a mode by the title in front of you, not by library averages.
iso2god-rs –trim is a different, narrower feature
Do not map the GUI modes onto the command-line tool. iso2god-rs offers --trim (equivalent to --trim=from-end, and the default) or --trim=none. From-end trimming only cuts unallocated space from the end of the image — it never reaches into the middle of the layout the way Full padding removal does. For many games the practical saving is similar, because much of the air sits at the end, but the features are not interchangeable: when a per-game note specifies a GUI padding mode, that note is about the GUI’s modes. The CLI side is covered fully in the iso2god-rs guide, and the GUI controls are in How to Use Iso2God.
Counter-example 1: Tetris – The Grand Master Ace needs Partial
The r4dius fork maintainer’s own per-game notes document that Tetris – The Grand Master Ace breaks when padding is set to remove everything, and must be converted with Partial. This is the canonical proof that Full is not a universal default: a real, named title fails under it, and the fix is not a different tool or a re-dump — it is one dropdown changed before conversion. Treat any guide that says ‘always use Full’ as unreliable on that evidence alone.
Counter-example 2: Wolfenstein: The New Order Disc 1 keeps its padding
ConsoleMods’ documentation records the stricter case: Wolfenstein: The New Order’s Disc 1 is an installer disc whose first GOD conversion requires the padding left intact. In GUI terms that means None for that disc — Partial is not conservative enough when the installer itself reads the padded layout. Multi-disc releases concentrate most padding traps, because install discs behave differently from play discs; see Multi-Disc Games with Iso2God before converting any two-disc release.
A decision routine that avoids both traps
- Default every new title to Partial in the GUI, or default –trim in iso2god-rs.
- Before converting an install disc or the first disc of a multi-disc set, check for a per-game note; if one says keep padding, use None (or –trim=none) for that disc only.
- If a Full conversion fails to launch or install, reconvert the same ISO with Partial before suspecting the dump — padding is the cheapest variable to change.
- Record the mode that worked next to the game in your library notes; padding knowledge is per-title and worth keeping.
Applying this in each tool
In the Windows GUI, the mode is the padding dropdown you set per queue entry before pressing Convert — the exact clicks are walked through in How to Use Iso2God. In iso2god-rs, the choice is the –trim flag on the command line: default from-end trimming for ordinary titles, –trim=none for a title whose note says to keep its layout. Both tools, with every verified binary and checksum, are collected on the download page, so the mode decision is the only real choice left once your download is verified. A useful habit when a library grows: keep a plain text note per game recording the tool, the mode and whether the result launched — three lines per title that will save a full reconversion experiment every time you revisit that game on a new drive or a second console.
Frequently asked questions
Does padding removal change the game itself?
No game file is altered: padding is filler between and after real data. Removal changes the layout the data sits in, which is exactly why most games never notice and a few layout-sensitive installers do. The game data, and the hashes protecting it inside the GOD, are about the real content.
Why does the GUI offer a rebuilt ISO with Full removal?
Because a shrunken ISO is useful in its own right — for archiving, for emulator workflows, and as an intermediate step. Choosing ‘rebuilt ISO only’ or ‘GOD plus rebuilt ISO’ with Full removal produces that stripped image instead of, or alongside, the GOD package.
If Partial is safe, why does None exist?
Because ‘safe default’ is not ‘universally safe’. Wolfenstein: The New Order Disc 1 needs its padding intact, and a byte-faithful None conversion is also the right diagnostic baseline when a title misbehaves under every other mode.
Which mode makes games load faster?
Padding mode is about size and compatibility, not loading speed. Its performance effect is indirect: smaller packages copy to the console faster. More conversion guidance lives in the Tutorials hub.