Padding Removal Broke Your Game? How to Reconvert It Safely
If a game worked as a full image but misbehaves after conversion with Full padding removal, the padding setting is the prime suspect — and the fix is simple: reconvert the same ISO with Partial (or, for one documented installer case, with padding left intact). Full removal is a space-saving option, not a universal default, and a small number of games are documented to depend on the padding it strips away.
This is not a defect in your copy or your console. It is a known characteristic of how some games were built, recorded by the people who maintain the tools. Below are the cases, why they happen, and the exact way back to a working game. For the full background on the three modes, read our padding explained guide alongside this page.
What Full padding removal actually removes
Retail disc images are padded to the full mastered layout: an ISO of a small game still occupies roughly the full disc size, because unused and padding sectors fill out the layout. Iso2God’s three modes treat that padding differently. None keeps the layout byte-faithful. Partial removes some padding and is the safe default in the GUI workflow. Full removes all of it — the smallest output, and also the mode the GUI uses to rebuild a shrunken ISO.
The catch is that “padding” is defined by layout, not by whether a particular game ever reads those regions. Most games never notice. A few do — because an installer measures the image, a loader expects data at fixed offsets, or a check treats the padded layout as part of the disc’s shape. For those games, Full removal produces a package that converts cleanly, copies fine, and then fails in play, which is why the setting is so often blamed last.
The two documented cases
| Game | Documented behaviour | Setting that works | Source of the note |
|---|---|---|---|
| Tetris – The Grand Master Ace | Breaks when padding is set to remove all of it | Partial | The r4dius fork maintainer’s per-game compatibility notes |
| Wolfenstein: The New Order – Disc 1 | The installer requires the padding left intact for its first GOD conversion | Keep padding (None) for Disc 1 | ConsoleMods wiki guidance |
Treat these two as the proven examples of a general principle rather than as the only games in the world that care. They are the cases with a documented source behind them, which is why we name them specifically — and why any site claiming Full removal is always safe for every game is overstating what anyone actually knows.
The fix: reconvert, do not patch
- Go back to your original ISO. You cannot “add padding back” to a finished GOD package — the conversion is where the choice is made.
- In Iso2God, set padding removal to Partial and convert again. For the Wolfenstein: The New Order Disc 1 installer case, use None so the padding stays intact.
- Replace the old package on the console completely — header file and .data folder together — rather than mixing parts from the two conversions. Mixing parts across conversions is a route to the corruption errors described in our corrupted content guide.
- Test the game past the point where it previously failed: for Tetris TGM Ace, into actual play; for an installer disc, through the install step it performs for the other discs.
How to choose next time
- Default to Partial. It saves meaningful space over None and avoids the known Full-removal failures.
- Use Full when space is tight and the game is known to tolerate it — and keep the source ISO until you have tested the result in play, not just to the title screen.
- Use None for installer discs and for any game that misbehaved under other settings. The space cost is real but a working game is the point.
- One game at a time when experimenting. Batch-converting a whole shelf on Full and testing later makes it impossible to tell which games care.
Our companion page on the best padding settings per game collects the per-game and per-situation recommendations in one place, including multi-disc notes — several two-disc games, for example, are documented in the fork maintainer’s notes as working best with Disc 1 handled as extracted install content and Disc 2 as the GOD. If a conversion will not complete at all, that is a different fault tree: see the conversion errors guide.
A note on iso2god-rs and trimming
If you converted with iso2god-rs, its --trim option is a narrower thing than the GUI’s padding modes: it only drops unallocated space from the end of the image. It is not Full padding removal, and it should not be described — or blamed — as though it were. A game failing after an rs conversion with default settings is unlikely to be a padding case; work through the corrupted-content and conversion-error checks instead. The rs workflow is covered in our iso2god-rs guide.
Frequently asked questions
Can I fix a Full-removal game without reconverting?
No. Padding is removed during conversion, and the finished GOD package cannot have it put back. Reconvert the original ISO with Partial — or None for the Wolfenstein: The New Order Disc 1 installer case — and replace the whole package on the console.
Which games break with Full padding removal?
Two cases are documented in sources we can point to: Tetris – The Grand Master Ace, which the fork maintainer’s notes say needs Partial, and Wolfenstein: The New Order Disc 1, whose installer needs padding intact. Others may exist; that is why Partial is the sensible default.
Is Full padding removal ever the right choice?
Yes — for the many games that tolerate it, it gives the smallest package and the fastest transfers. Just keep the source ISO until the converted game is tested in play, so reconverting with a safer setting costs you nothing but time.
Does iso2god-rs Full-trim cause the same problem?
The rs --trim option only removes unallocated space from the end of the image; it is not the GUI’s Full padding removal. See the Troubleshooting hub for the whole troubleshooting series, and our download page for the tools themselves.
Symptoms that point at padding (and symptoms that do not)
Padding problems have a recognisable shape. The game typically converted without errors, copied completely, and appears in the library — the failure shows up in behaviour: an installer that will not complete, a game that stops at a particular point, or content that behaves as though part of the disc is not there. That pattern — structurally fine, functionally wrong — is what separates a padding case from a corruption case, where the console refuses the package outright after its hash check.
Just as useful is knowing what padding does not explain. A game missing from the library is a placement problem. A package the console calls corrupted is a completeness or licence problem. A conversion that crashed halfway never produced a package to argue about. Each of those has its own guide in this series, linked throughout this page, and reaching for the padding setting in those cases only adds a variable. But when a game worked from its full image and broke only after a Full-removal conversion, you have the cleanest possible evidence: one setting changed, and changing it back is the fix.
Finally, keep notes as you build your library. A single line per game — title, padding setting used, tested or not — turns future conversions from experiments into routine, and it is exactly the kind of record the per-game recommendations on our best padding settings per game page are built from.