ROS Legacy

File size

ROS Legacy file size

Mirae Labs mark
Official publisher mark from roslegacy.net.

ROS Legacy file size is the one hardware fact Mirae Labs has actually shipped: installer bytes, not a CPU or GPU sheet. Windows is 8,251,115,387 bytes (about 7.68 GiB) for ROSLegacy_Install_202609251811.zip from dl.roslegacy.net/full. Android is 108,574,372 bytes (about 103.5 MiB) for RoS-Legacy-2026091811.apk from dl.roslegacy.net/android/apk. iOS has no file. No RAM, CPU, or GPU floor is printed on the operator site. Until roslegacy.net prints CPU, GPU, and RAM rows, plan around the zip and APK lengths and leave extra free space for unpacking rather than chasing unofficial spec charts. Keep that gap visible so a fan GPU chart does not look official. Confirm the filename before you spend the download on a decoy host. Plan disk around three layers on Windows: the zip, the unpack, and the installed client. On Android, leave room after the 103.5 MiB APK for first-launch data. No official RAM line exists to pair with those numbers. Two facts: zip and APK.

Measured installer sizes

Platform
Windows
Stable URL
https://dl.roslegacy.net/full
Resolved host
edge.roslegacy.net
Filename
ROSLegacy_Install_202609251811.zip
File size
8,251,115,387 bytes (about 7.68 GiB)
Status
live
Platform
Android
Stable URL
https://dl.roslegacy.net/android/apk
Resolved host
cdn.mobile.roslegacy.net
Filename
RoS-Legacy-2026091811.apk
File size
108,574,372 bytes (about 103.5 MiB)
Status
live
Platform
iOS
Stable URL
iOS — Coming Soon
Resolved host
—
Filename
—
File size
—
Status
coming-soon

Windows storage

  1. Plan disk around the zip first. 8,251,115,387 bytes is the compressed download. Extraction needs a second block of free space, and the installed client needs a third. A drive with only 8 GB free will not finish the unpack. The resolved host is edge.roslegacy.net. If a site lists “4 GB RAM minimum” or a GTX 1050 line, that line did not come from roslegacy.net.
  2. The official site also does not list a 32-bit versus 64-bit requirement, a DirectX version, or a supported Windows build. Those gaps are real. Use a current 64-bit Windows machine as a practical baseline because that is what the Open Beta audience is already running, and keep the measured zip as the only number you can defend.
  3. Think in three layers: zip, unpack, install. The zip alone is already 7.68 GiB. A disk with 20 GB free is a safer starting point than a disk that only matches the zip. No official RAM or VRAM line exists to pair with that number, so storage is the only planning figure on this page.
  4. A drive with only 8 GB free will not finish the unpack.

Android storage

  1. The APK is 108,574,372 bytes. That is the download, not the unpacked game data after first launch. Leave extra space on internal storage so the client can write additional assets. The resolved host is cdn.mobile.roslegacy.net. Last-modified on the object was 18 September 2026, which is a file date, not a phone spec.
  2. There is no official Android API-level chart, no listed RAM floor, and no supported-device table. If a phone cannot sideload APKs from the browser, you cannot use this Open Beta yet. Google Play is not an alternate size source because there is no Play listing.
  3. 103.5 MiB is small next to the Windows zip, but first launch can still write extra data. Keep internal storage from filling to zero. There is no official list of supported Android versions. If the OS blocks sideload APKs and you cannot enable the browser source, this Open Beta has no Play Store fallback.
  4. Keep internal storage from filling to zero after first launch.

What Mirae Labs has not published

  1. No CPU model, no GPU model, no RAM floor, no recommended settings, no iOS storage figure. The marketing page talks about sprawling maps and dozens of weapons without attaching those claims to hardware. Until a spec table appears on roslegacy.net, treat any detailed requirements graphic on social media as unofficial.
  2. If you cannot run the client after a correct install, the next checks are account and connectivity, not a missing GPU string. See sign-in and server status. For host verification, see safe files.
  3. Hardware guesses from other wikis are not copied here; only installer bytes are.

iOS has no installer size

  1. Because the chooser disables iOS and dl.roslegacy.net/ios returns 404, there is no byte count to report. Do not use an IPA size from another ROS project as a stand-in. When Mirae Labs enables the iOS row, this desk should pick up a new host record with a real length.
  2. JSON-LD still naming iOS as a platform does not create a file. The chooser is the shipping control. Watch that row, not the schema block, for the day a size exists.
  3. No IPA means no iOS storage number. Using another revival’s IPA size here would mix projects. When the chooser enables iOS, a new host row with a real length should appear next to Windows and Android. Until then, iPhone players can create a Mirae ID but cannot install this client.
  4. Leave iPhone users on the Mirae web ID until that row enables.
  5. When the chooser enables iOS, a new host row with a real length should appear.
  6. A 256 GB laptop with 10 GB free may download the Windows zip and still fail extraction, so clear space first. On Android, the APK is small next to the zip, but first launch can still write extra assets onto internal storage.
  7. iPhone players can still create a Mirae ID on the web forms, but they cannot install this client until the chooser enables the iOS row and a real byte length appears.
  8. Using another revival’s IPA size here would mix projects, so this desk reports no iOS figure.