Xenia GOD Format Guide: Opening GOD Packages in Xenia Canary

The current answer to the Xenia GOD format question is simpler than most guides suggest: current Xenia Canary loads GOD packages directly, alongside ISO images and extracted default.xex folders. You no longer have to convert every GOD package back to an ISO before the emulator will touch it — although that older route still exists, and in some situations it is still the useful one.

Xenia is a research emulator for the Xbox 360, not a finished commercial product, and it is actively maintained: the Xenia Canary repository was still receiving pushes on 23 October 2026, the day this guide was checked. That maintenance pace is exactly why older advice goes stale. A guide written when Canary could not open a GOD package will confidently send you through a conversion step that current builds have made optional.

This page presents both routes, dated, so you can tell which one your build needs. For the reverse conversion itself, see converting GOD to ISO with God2Iso. The tools are linked from the download page.

What Xenia Canary accepts today

Input	Open it directly in current Canary?	Notes
Xbox 360 ISO image	Yes	The straightforward starting point if you still have the original image.
Extracted game folder (default.xex)	Yes	Point the emulator at the extracted executable; useful for installs you extracted yourself.
GOD package	Yes, in current Canary	Older guides route this through God2Iso first — see the dated comparison below.
Extension-less STFS / XBLA-style files	Listed as loadable	The same container family GOD packages are built from.

That list is the reason the GOD question keeps changing. GOD is a Secure Virtual Optical Disc (SVOD) container: a header file plus a folder of data part files. An emulator that understands that container can open the package as it stands. An emulator build that only understands disc images cannot, and needs the package rebuilt into an ISO first.

How to open a GOD package in Xenia Canary, step by step

1. Use a current Xenia Canary build. The direct-GOD behaviour described here is the current behaviour; an old build is the most likely reason it will not work.
2. Keep the GOD package complete. A GOD conversion produces a header file and a matching .data folder of part files (Data0000, Data0001, and so on). Moving or copying only the header leaves the emulator with nothing to read.
3. Open the package from the emulator’s file dialog and select the GOD header file for the game.
4. If the build refuses the package, fall back to the dated route below rather than re-converting the game from scratch. Your GOD package is probably fine; your emulator build is probably old.

Keep that completeness point in mind when you tidy a library. Deleting a .data folder because it “looks like leftovers” deletes the game. The structure is explained in depth in GOD packages versus XEX folders.

The older route, dated: GOD first, then God2Iso, then Xenia

Older Xenia guides, and plenty of forum answers copied from them, give a three-step chain: take the GOD package, run it through God2Iso to rebuild an ISO, and open that ISO in the emulator. God2Iso (raburton/god2iso) does exactly that one job — GOD to ISO — and its last release, v1.0.5, is from 19 April 2023, when it became open source under CC BY-SA 4.0.

That route was correct for the emulator builds those guides were written against. It is not wrong today; it is just no longer the mandatory first step for a current Canary build. Presenting both matters because readers arrive with both kinds of build installed, and because a page that silently deletes the old route leaves those readers with a package their emulator genuinely cannot open and no explanation.

When converting GOD to ISO still helps

• Your emulator build does not accept GOD packages. Older builds, and builds other than current Canary, may still need an ISO. God2Iso is the standard rebuild tool for that case.
• Another tool in your chain only accepts ISO. Extractors, inspection tools, and older utilities were often written against disc images only. Rebuilding an ISO gives them something they understand.
• You want to extract the game’s files. An ISO is the practical intermediate step toward an extracted folder, and extracted default.xex folders are themselves a format current Canary opens.
• You are archiving in one format. If your whole library standard is ISO images, converting a stray GOD package keeps the archive uniform — a housekeeping choice, not a compatibility requirement.

The full reverse workflow, including the verified God2Iso download, is in the God2Iso guide. Note the direction carefully: Iso2God and iso2god-rs convert ISO to GOD. God2Iso converts GOD back to ISO. They are different tools doing opposite jobs, and iso2god-rs has no GOD-to-ISO mode.

GOD on a PC versus GOD on a console

Do not confuse the two playback routes for the same package. On a PC, Xenia is the route, and no console is involved. On real hardware, a GOD package produced by Iso2God carries an unlocked licence and requires a modded Xbox 360 — JTAG, RGH, or a BadUpdate-class exploit. A stock retail console will not run it, and no emulator setting changes that. Choose the route first, then follow the instructions for that route.

If your goal is the console rather than the emulator, read how the Aurora dashboard handles GOD packages and keep your padding choices conservative using the per-game padding guide.

Troubleshooting a GOD package that will not open

1. Check the build date first. Update to a current Canary build before suspecting the package.
2. Check the package is complete. Header file present, matching .data folder present, part files inside it.
3. Try the ISO route as a diagnostic. Rebuild an ISO with God2Iso and open that. If the ISO opens, the game data is intact and the problem was format support in your build.
4. Re-convert from the source ISO only as a last resort, at Partial padding, using a tool from the download page.

Builds and platforms to know about

Xenia’s main project is Windows-first. Xenia Canary, the experimental build line most guides mean when they say “Xenia” today, also ships a Linux AppImage alongside its Windows archive, which is why current GOD support should be judged on a Canary build rather than on an old master-branch snapshot. The master Xenia project and Canary are related but separate repositories with separate release rhythms; a limitation you read about in one is not automatically a limitation of the other. When a guide does not say which build it tested, treat its format claims as undated — which, for GOD support, usually means out of date.

Frequently asked questions

Can Xenia play GOD files?

Current Xenia Canary can load GOD packages directly, as well as ISO images and extracted default.xex folders. Older builds may need the package rebuilt into an ISO with God2Iso first.

Is Xenia still maintained?

Yes. Xenia describes itself as a research project, and the Canary repository was receiving pushes on 23 October 2026. Expect a research emulator’s rough edges, not a finished product’s polish.

Do I need God2Iso if I use Xenia?

Not with a current Canary build and a complete GOD package. Keep God2Iso for older builds, for tools that only accept ISO images, and for getting from a GOD package toward extracted files.

Can I convert a GOD package with iso2god-rs instead?

No. iso2god-rs converts ISO to GOD only. It has no GOD-to-ISO mode and does not take XEX-folder input. The reverse direction is God2Iso’s job.

More guides are collected on the Tutorials hub.