> For the complete documentation index, see [llms.txt](https://guide.strikepack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.strikepack.com/horizon/strikepack-horizon-app-guide/shooter-studio-guide/5-profile-backup-and-restore.md).
# 5 - Profile Backup & Restore
Profile Backup & Restore
STRIKEPACK HORIZON™ Gaming Adapters
{% hint style="info" %}
**Shooter Studio** features a significantly redesigned **Profiles** system that can be customized for virtually any First Person Shooter (FPS) or Third Person Shooter (TPS) game.
Think of **Game Profiles** as your own custom **GAMEPACKS**—built, customized, saved, and shared for the games you play.
{% endhint %}
{% embed url="" %}
Watch Video on YouTube
**In the video above,** you'll learn how to **Backup Your Profile** to a **Text File** (.txt) from within the **STRIKEPACK HORIZON** app. You can then **Restore Your Profile** whenever you need to, or even **Share Game Profiles** for your **Favorite Games** with **Other Gamers Online**.
* A Profile .txt file contains a complete snapshot of the profile's data taken at the time of the backup. This includes all Weapons, Loadouts, Accessibility Macros, and Settings.
**Written Steps:**
{% stepper %}
{% step %}
First, enter the **Profile** that you want to backup.
***
{% endstep %}
{% step %}
Next, **tap** the :gear-complex: **Gear** button in the top-right corner to go to the **Settings** screen.
***
{% endstep %}
{% step %}
Under **Data Management**, **tap** **Save** to open your Smartphone's **Share** menu.
***
{% endstep %}
{% step %}
Save the text file to your phone or cloud storage for safekeeping (e.g. iCloud®, Google Drive™). Remember to do this often to keep your efforts backed up and easily recoverable!
***
{% endstep %}
{% step %} **Tap** the **X** to head back to the **Profiles** screen.
***
{% endstep %}
{% step %} **Tap** the :plus: **Plus** button to create a **New Profile** to test importing the profile .txt file you just saved. This is also how you would import a game profile that someone has shared online.
***
{% endstep %}
{% step %}
Enter this newly created blank profile.
You'll be met with the **Initial Setup** screen. Instead of starting over, **tap** :file-arrow-up: **Import Existing Profile**. Find and select the Profile .txt file that you want to import. In this case, the backup you just saved.
***
{% endstep %}
{% step %}
**Selective Restore** allows you to select which parts of the profile you want to overwrite. In this case, you're restoring to a blank profile, so you may as well leave it all checked. When you're ready, **tap** **Overwrite Selected**.
{% endstep %}
{% endstepper %}
***
:hands-clapping: **And just like that, the Profile is imported and the restoration of your backup is complete!**
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://guide.strikepack.com/horizon/strikepack-horizon-app-guide/shooter-studio-guide/5-profile-backup-and-restore.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
**tap** the :gear-complex: **Gear** button in the top-right corner to go to the **Settings** screen.
***
{% endstep %}
{% step %}
Under **Data Management**,