Video+Game · Development preview

Your Xbox collection.
One Mac workspace.

Organize Xbox files. Prepare disc backups. Review transfers. Keep checked backups. Orbit 360 brings the workflow together on Mac.

Development preview · Apple silicon · macOS 14 or later

Orbit 360 app iconA Rule Mobile development preview
6dedicated workspaces
4Disc Studio operations
SHA-256complete file comparisons

Keep the whole workflow in view

Six workspaces. Clear responsibilities.

Start with the files you already keep on your Mac, external storage, or a mounted NAS. Register source folders. Choose an exact game variant. Review each destination before you copy.

01 / LIBRARY

Find the exact copy.

Browse registered folders. Compare files. Keep disc images, extracted games, mods, and multi-disc variants distinct.

02 / STORAGE

Know the destination.

Inspect detected drives, mounted folders, shares, and supported disk images. Review drive identity and available space.

03 / DISC STUDIO

Prepare a separate output.

Convert Xbox 360 ISO to GoD. Extract a supported image. Rebuild an XISO. Create an XISO from a folder.

04 / SAVES & PROFILES

Inspect the details.

Read supported profiles, game history, and packages. Keep profile inspection separate from changing ownership or progress.

05 / ARTWORK

Recognize your collection.

Browse covers in Shelf, Grid, or Cover Focus. Prepare Aurora jackets and inspect the front, spine, and back.

06 / CONSOLE TOOLS

Record the real result.

Prepare reviewed setup files and shortcuts. Keep console test notes. Preview FTP names through a separate connection.

From source to console

Prepare. Review. Copy. Check.

A completed conversion answers one question. A verified copy answers another. A real console test answers the next. Orbit 360 keeps those milestones separate.

  1. Prepare

    Create the required playable layout in a separate output. Keep the original disc image.

  2. Review

    Confirm the exact variant, destination, space, and conflicts before the job starts.

  3. Copy and verify

    Wait for transfer and independent destination readback. Check the final result.

  4. Test on console

    Record launch, menu, play, save, and reload results separately. Leave untried steps marked Not tried.

“Copied and verified” describes the transfer. Your console, dashboard, and game configuration determine the next step. Orbit 360 records your console observations alongside the exact game copy.

Formats carry different jobs

Keep the format. Choose the right path.

A title name does not tell the whole story. Orbit 360 distinguishes disc images, extracted folders, and packages before it routes the work.

  • ISO → GoD: prepare a new Xbox 360 package and its matching data parts.
  • Extract: unpack a supported, readable XDVDFS image into a new folder.
  • Rebuild XISO: create a compact standard XISO while retaining its file contents.
  • Create XISO: build a standard XISO from a folder.
ISO file illustration

Disc images

Prepare supported images before transfer. Disc Studio creates separate outputs.

XISO file illustration

Standard XISO

Use the supported XDVDFS path. Keep compressed formats and unreadable full dumps outside this workflow.

GoD packages

Keep the package header and matching .data parts together as one complete set.

Extracted folders

Keep the launcher with its companion files. Track each prepared or modified variant separately.

Keep the files and the evidence

Back up selected content. Check it again.

Choose eligible games, apps, saves, profiles, or DLC. Create a checked backup on your Mac or mounted NAS. Keep its receipt with the files.

Run Check Files again when you need a fresh result. Complete SHA-256 comparisons examine file contents. Names, dates, and sizes alone do not establish a match.

DRIVE SETS

Save a selection. Keep variants exact.

Build a Drive Set for the games you want together. Orbit 360 saves your exact variant choices without duplicating the game files.

Recall the selection, resolve changed or missing sources, then review the destination. A Drive Set stores choices; it does not run automatic copies or sync.

A receipt records a check. Keep the backup payload too. A selected-content backup copies files; it does not create a sector-by-sector clone of the physical drive.

Hardware remains part of the workflow

Connect. Identify. Review.

Use a compatible transfer cable for an Xbox hard-drive enclosure, or a suitable USB-to-SATA connection for supported bare drives. Confirm the drive identity and capacity each session.

Xbox hard-drive enclosureXbox hard driveMatch the enclosure and cable.
Xbox hard-drive USB transfer cableReview the connectionCheck the attached medium.
SATA solid-state driveSATA HDD or SSDUse a suitable adapter or cradle.
Connection illustrations show different hardware paths. An adapter name can identify the cable rather than the attached drive. Orbit 360 asks you to review the selected destination before copying.

Artwork with structure

Give every side its place.

Build Aurora artwork from a full jacket. Choose fit or fill. Review the crop. Keep front covers, full jackets, and package thumbnails as separate outputs.

The cover browser offers Shelf, Grid, and Cover Focus. Turn a case to inspect its spine and back. A front-only image keeps a plain rear.

900 × 600 pixels. One full jacket carries the back, spine, and front. This diagram explains the output layout; it does not show app UI.

Current development scope

Build 38, in plain terms.

This page previews the workflow documented in the Build 38 user manual. Rule Mobile has not announced a public download or release date.

Mac requirements
The supplied Build 38 supports Apple silicon Macs running macOS 14 or later. Preparation and staging require free local storage.
Source locations
Register Mac folders, external storage, and mounted NAS folders. Keep the original files in their source locations.
Backups
Back up selected eligible content. Build 38 does not create full backups from physical drives.
Disk images
Inspect supported images and export copies. Build 38 does not mount them in Finder.
FTP
Test a connection and preview names. Build 38 does not transfer game files through FTP.
Profiles and artwork
Inspect profiles and achievements without editing progress. Prepare local thumbnail packets; Build 38 does not publish edited headers directly to physical drives.
Console results
Record your own launch, play, save, and reload observations. File checks do not establish console compatibility.

A few useful answers.

Does Orbit 360 keep another copy of my entire library?

Registering a source folder adds that location to the Library. It does not duplicate the files. A Drive Set stores exact game selections. Copy, preparation, and backup jobs create their own reviewed outputs.

Can I use a mounted NAS?

Yes. The documented workflow uses mounted NAS folders for source files, prepared outputs, and selected-content backups. Some preparation jobs stage files locally before publishing and verifying the output, so keep space available on your Mac.

What does “Copied and verified” tell me?

It confirms the transfer and independent destination readback for that job. Test the game on your actual console next. Record each result in Game Check: direct launch, menu, play, save, and reload.

Can I download the preview?

This page introduces the Build 38 workflow. Rule Mobile has not announced a public download or release date.

The collection deserves a clear workflow.

Explore Orbit 360’s six workspaces, exact variant selections, and separate file and console checks. Have a workflow question? Contact Rule Mobile.

Explore the workspaces ↑