> ## Documentation Index
> Fetch the complete documentation index at: https://akron-cdb9eaf4.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage .akr setups

> Back up, reset, and maintain directly configured Akron setup state.

Akron setup state covers the options, bindings, StartPos slots, and scoped tool settings that you can export into `.akr` packs. Use setup packs to back up direct configuration or share a focused group of settings.

## Start from current settings

Configure Akron directly, then export the current settings as a setup pack once they match the state you want to preserve. Organize setups around visible tool groups and scoped packs.

## Maintain setups

<Steps>
  <Step title="Start from a baseline">
    Export a fresh baseline before changing individual tools.
  </Step>

  <Step title="Change one tool group at a time">
    Configure overlay behavior, HUD tools, StartPos tools, visual settings, and interop separately to easily identify configuration issues.
  </Step>

  <Step title="Export a pack">
    Export an `.akr` setup pack when the setup is stable.
  </Step>

  <Step title="Use scoped imports">
    Import only the section you need when applying shared StartPos, Keybinds, Auto Kill, Auto Deafen, Recorder, Audio, or HUD packs.
  </Step>
</Steps>

## Reset strategy

Use reset actions when your setup state has drifted too far from its intended baseline. Prefer exporting a setup pack first if it contains map-specific StartPos slots or carefully tuned binds.

## Clean setup hygiene

* Keep state-changing tools out of submitted-run setups.
* Check suboptions, not only parent rows.
* Avoid importing whole setup packs from untrusted sources into submitted-run setups.
* Use [Clean vs cheat classifications](/concepts/clean-vs-cheat) when deciding where a setting belongs.