One place to install, update and get back to Spira

September 24, 2026

The Launcher brings the game, Studio, Hooks and Spira Reforged into one place. Version 1.0.11 adds the active Spira Reforged content card; these first full notes also cover the install tools, optional save backups and everyday settings already available.

Highlights

Spira Reforged now has an active install and update card. The first published content package is 0.1.0 and requires Launcher 1.0.11 or newer.
Install, update and open FFX Mod Studio directly from the Launcher. The editor has its own version, separate from the Launcher and the other products.
Windows x64 and Linux x64 packages are available. Optional cloud save backups offer manual backup and restore on both platforms. Windows also supports automatic backups after a Launcher-started session, disabled until you opt in.

What's included

Spira Reforged in the catalog. Check its available version and use the card to install or update the managed content package. You no longer need to treat it as a Coming Soon entry.
Studio from download to launch. The main Studio action checks its state, installs it when missing, updates it when necessary and opens an installed current copy. Windows and Linux use their respective Studio packages.
Hooks management. The catalog provides install, update, refresh and recovery states for FFX Hooks. The Hooks package remains beta, and its catalog version can differ from the newer manual downloads on GitHub; the Launcher does not automatically install every experimental GitHub release.
Choose your game installation. Use detected installations or select the game folder manually, then launch Final Fantasy X from the Launcher. If you use a custom Steam library, check that the selected folder is the one you actually play from.
Optional cloud backups. Create an account or sign in to browse stored saves, make a manual backup, restore a chosen backup or remove copies you no longer need. Signing in alone does not upload your saves.
Backups after play on Windows, when you ask for them. Automatic backup requires your save-upload consent, a signed-in session and the end of the exact game session started by the Launcher. It is off by default. Linux currently offers manual backup and restore instead of automatic post-session uploads.
Control how much you keep. Backup retention settings let you manage older copies rather than accumulating them indefinitely. Manual restore remains a separate action that you choose explicitly.
Separate platform downloads. Windows offers an MSI installer as well as ZIP packages. Linux has an x64 ZIP package and its own update feed. The website's main bootstrap download currently points to the Windows installer.

Improvements

Clearer product states. Installation, update, download progress, confirmation and retry states help you see what the Launcher is doing. A product's version belongs to that product, so an editor update does not imply a new Launcher version.
Checked downloads. The Launcher checks release metadata and package integrity before using supported downloads. Studio downloads are limited to the official release assets, reducing the chance of installing an unrelated or incomplete file.
Restore with verification. A cloud backup is downloaded to a temporary file and checked before replacing the selected destination. The Launcher verifies the expected size and checksum instead of trusting an unfinished download.
Launcher self-updates. An update banner lets you install an offered Launcher update. Its updater includes automatic recovery for failed update operations; there is no separate screen for freely selecting an older Launcher version.
Your setup stays with you. The selected game folder, theme, language and backup preferences are saved locally. Choose from the interface's Portuguese, English, Spanish, French, Italian, German, Japanese, Korean and Chinese options.
Keep different tasks separate. Opening the game, opening Studio, installing mod content and uploading a save are distinct actions. You can use the local Launcher without turning on cloud backups.

Known issues

The Spira card can still show Beta in Launcher 1.0.11. Its released configuration selects that channel, even though the same 0.1.0 content is also published on stable. The label does not indicate a different 0.1.0 package in the feeds checked for these notes.
Windows binaries are not code-signed. Windows may show an Unknown Publisher or SmartScreen warning. Package integrity checks and a signed update feed are not the same thing as a Windows publisher signature.
Linux has a separate package. A published Linux build does not guarantee that every Windows integration, overlay or mod combination behaves identically under Proton. Use the package for your platform and follow the relevant game setup instructions.
Cloud backups depend on the online service and your consent. Automatic post-session backup is Windows-only in this release and is not triggered by a game session you start outside the Launcher. Linux users can back up and restore manually.
Keep local save copies as well. Restore replaces the destination you select, and the Launcher is not a substitute for a personal backup of saves or a heavily customized mod setup.

Highlights

Spira Reforged now has an active install and update card. The first published content package is 0.1.0 and requires Launcher 1.0.11 or newer.

Install, update and open FFX Mod Studio directly from the Launcher. The editor has its own version, separate from the Launcher and the other products.

Windows x64 and Linux x64 packages are available. Optional cloud save backups offer manual backup and restore on both platforms. Windows also supports automatic backups after a Launcher-started session, disabled until you opt in.

What's included

Spira Reforged in the catalog. Check its available version and use the card to install or update the managed content package. You no longer need to treat it as a Coming Soon entry.

Studio from download to launch. The main Studio action checks its state, installs it when missing, updates it when necessary and opens an installed current copy. Windows and Linux use their respective Studio packages.

Hooks management. The catalog provides install, update, refresh and recovery states for FFX Hooks. The Hooks package remains beta, and its catalog version can differ from the newer manual downloads on GitHub; the Launcher does not automatically install every experimental GitHub release.

Choose your game installation. Use detected installations or select the game folder manually, then launch Final Fantasy X from the Launcher. If you use a custom Steam library, check that the selected folder is the one you actually play from.

Optional cloud backups. Create an account or sign in to browse stored saves, make a manual backup, restore a chosen backup or remove copies you no longer need. Signing in alone does not upload your saves.

Backups after play on Windows, when you ask for them. Automatic backup requires your save-upload consent, a signed-in session and the end of the exact game session started by the Launcher. It is off by default. Linux currently offers manual backup and restore instead of automatic post-session uploads.

Control how much you keep. Backup retention settings let you manage older copies rather than accumulating them indefinitely. Manual restore remains a separate action that you choose explicitly.

Separate platform downloads. Windows offers an MSI installer as well as ZIP packages. Linux has an x64 ZIP package and its own update feed. The website's main bootstrap download currently points to the Windows installer.

Improvements

Clearer product states. Installation, update, download progress, confirmation and retry states help you see what the Launcher is doing. A product's version belongs to that product, so an editor update does not imply a new Launcher version.

Checked downloads. The Launcher checks release metadata and package integrity before using supported downloads. Studio downloads are limited to the official release assets, reducing the chance of installing an unrelated or incomplete file.

Restore with verification. A cloud backup is downloaded to a temporary file and checked before replacing the selected destination. The Launcher verifies the expected size and checksum instead of trusting an unfinished download.

Launcher self-updates. An update banner lets you install an offered Launcher update. Its updater includes automatic recovery for failed update operations; there is no separate screen for freely selecting an older Launcher version.

Your setup stays with you. The selected game folder, theme, language and backup preferences are saved locally. Choose from the interface's Portuguese, English, Spanish, French, Italian, German, Japanese, Korean and Chinese options.

Keep different tasks separate. Opening the game, opening Studio, installing mod content and uploading a save are distinct actions. You can use the local Launcher without turning on cloud backups.

Known issues

The Spira card can still show Beta in Launcher 1.0.11. Its released configuration selects that channel, even though the same 0.1.0 content is also published on stable. The label does not indicate a different 0.1.0 package in the feeds checked for these notes.

Windows binaries are not code-signed. Windows may show an Unknown Publisher or SmartScreen warning. Package integrity checks and a signed update feed are not the same thing as a Windows publisher signature.

Linux has a separate package. A published Linux build does not guarantee that every Windows integration, overlay or mod combination behaves identically under Proton. Use the package for your platform and follow the relevant game setup instructions.

Cloud backups depend on the online service and your consent. Automatic post-session backup is Windows-only in this release and is not triggered by a game session you start outside the Launcher. Linux users can back up and restore manually.

Keep local save copies as well. Restore replaces the destination you select, and the Launcher is not a substitute for a personal backup of saves or a heavily customized mod setup.