---
title: "Manage campaign history"
description: "Rename, trash, restore, reset, or permanently remove local Stellaris campaigns safely."
---

> Stellaris Companion documentation
> Complete index: https://galacticfilingcabinet.com/llms.txt

# Manage campaign history

Campaign History organizes the local records Stellaris Companion builds from your saves. Open it from **Settings → Game Data → Campaign History** or select **Manage campaigns** from Chronicle.

## Everyday organization

- Search by campaign, empire, or internal save identifier.
- Rename a campaign without changing its source save.
- Select unused campaigns with no story or recorded events.
- Move one campaign—or several unused starts—to Trash.
- Restore a trashed campaign later.

The currently loaded campaign cannot be moved to Trash or permanently deleted. Load a different campaign first if you need to remove it.

## Choose the right removal action

| Action | Removes | Keeps | Reversible? |
| --- | --- | --- | --- |
| Move to Trash | The campaign from the active list | Local history and Chronicle data in Trash | Yes |
| Clear Chronicle | Generated Chronicle writing | Campaign snapshots, events, and other history | Yes, with Restore Chronicle |
| Delete permanently | The campaign's local history and Chronicle | Any separately published story | No |
| Remove online story | The published website copy | Local campaign history | No |

Use **Clear Chronicle** when the extracted campaign history is useful but you want Chronicle to start its writing again. Use permanent deletion only after checking the campaign name, dates, snapshots, and publication status.

## Local history and published stories are separate

Deleting local campaign history does not remove a Chronicle that was already published. Campaign History lists published stories that no longer have local history so you can open or remove them separately.

Removing the online story deletes the public copy; it does not delete local saves, snapshots, or Chronicle text.

## Upgrading an existing archive

Version 1 creates and verifies a safety backup before upgrading an older campaign-history database. If that backup cannot be completed, the upgrade pauses and leaves existing Chronicles unchanged.

Check available disk space and permissions for the app-data folder, then reopen Stellaris Companion. Do not delete the existing database while resolving an upgrade warning.

For the full storage boundary, read [privacy and data flow](/docs/how-it-works/privacy-and-data-flow).

Source: https://galacticfilingcabinet.com/docs/chronicle/manage-campaign-history/index.mdx