Skip to main content

How to Save Your Fleet in Xterium — Protecting Your Fleet from Attacks

Xterium Fleet Save Guide: How to send a fleet on a mission with the right timing so it returns after an enemy attack, why a fleet is invulnerable while in flight, which missions are suitable, and common save mistakes.

5 min Updated 2026-06-18 Guides Verified by the Xterium team
On this page
  1. Why Does the Save Work?
  2. Step 1. Spot the threat early
  3. Step 2. Send the fleet on a timed mission
  4. Which missions are suitable for a save file?
  5. Don't forget the resources
  6. Common Save Errors
  7. Related Resources
  8. Frequently Asked Questions

"Save" (hiding) your fleet is the number one survival skill for a newbie in Xterium. As long as your fleet is parked on a planet, it can be destroyed by an attack. As long as it’s in flight—it can’t. “Save” is the ability to send your fleet into flight at the right moment so that it returns after the attack has passed. Below is how and why this works.

Why Does the Save Work?

A fleet is invulnerable while in flight: you can only attack targets on a planet or moon. So the task is simple—by the time the enemy fleet arrives, your own fleet must be in the air. The attacker will arrive at an empty planet and leave empty-handed.

Step 1. Spot the threat early

A save begins with early warning. Keep an eye on incoming flights and use intelligence—the “Espionage and Intelligence”] mechanic explains how to see who is flying toward you and what they’re carrying. The sooner you spot them, the smoother the save will be.

Step 2. Send the fleet on a timed mission

The key strategy: Send your fleet on a mission so that its flight time is longer than the time it takes for the attack to arrive. That way, the attack will hit an empty planet, and your fleet will return later. Flight time depends on speed—see the mechanics section “Fleet Speed, Time, and Consumption”].

Which missions are suitable for a save file?

Any mission where the fleet returns on its own is suitable: deploying or redeploying to one of your own planets, transporting to an ally, or holding a position. Adjust the range and speed so that the return trip takes place after the attack. Mission types are explained in the guide “All About Missions”].

Don't forget the resources

Not only the fleet but also resources are saved: anything left on the planet beyond what is protected by the vault will be looted by the attacker. Load resources onto your fleet before saving. For details on how looting and vault protection work, see the “Vaults and Looting” section.

Common Save Errors

  • The flight was too short—the fleet returned before the attack and was destroyed. Allow plenty of time.
  • They forgot about the resources—they saved the fleet, but the resources were plundered.
  • A last-minute save—we didn't have time to figure it out. Spot the threat early (Step 1).
  • Relying on defense instead of saves—defense helps, but it doesn't hold up well against major attacks. For more details, see the guide “How Not to Lose Your Fleet” and the section Defense.

Frequently Asked Questions

Why does the save function work at all? A fleet in flight is invulnerable—you can only attack targets on a planet or moon. If your fleet is in the air, the attacker will arrive at an empty planet.

How do you calculate a save correctly? Send the fleet on a mission so that its flight time is longer than the time it takes for the attack to arrive. Then the attack will hit an empty planet.

Which missions are suitable for a save file? Any mission from which the fleet returns on its own: a deployment to one of its own planets, a transport mission to an ally, or a defensive mission.

Should resources be saved along with the fleet? Yes. Anything left on the planet that isn't protected by the vault will be looted by the attacker, so load your resources onto your fleet before saving.

Put your knowledge into practice?

Registration is free. 30 seconds to the game.

Start playing for free

The Xterium knowledge base is maintained by the project team; data is verified against the game engine. About the project and team →