> For the complete documentation index, see [llms.txt](https://docs.kouch.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kouch.dev/getting-started/first-run-setup.md). # First-run setup The five steps Kouch walks you through the first time: your Emulation folder, extra disks for games, Black or White, and your emulators. The first time Kouch starts, it walks you through five steps. Nothing on your disks changes until the last one, where you see everything Kouch is about to do and confirm it. The dots at the top show where you are: **Main folder**, **More disks**, **Look**, **Emulators** and **Ready**. | To | Controller | Keyboard | | --------------------------- | ------------------- | ---------------------- | | Choose the highlighted card | **A** | **Enter** | | Go to the next step | **Start** or **RB** | **M** or **Page Down** | | Go back a step | **B** or **LB** | **Esc** or **Page Up** | | Leave setup for later | **Y** | click **Set up later** | You can also click any button, including the ones in the bar at the bottom. ## 1. Pick your main Emulation folder ![The first step: one card per disk, with the recommended one picked](https://3008865259-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiaV8VKDYJngjWWkPZx0Q%2Fuploads%2Fgit-blob-fc704cc7d082feda58933b975f1d033f404c0279%2Fsetup-1-main-folder.png?alt=media) This is Kouch's home. Your emulators, saves, your own system files and art live here, plus a `roms` folder for games. Each disk gets a card with its name, its type (SSD, hard disk, USB drive, SD card, network drive, or internal storage on a handheld) and how much space is free. Kouch marks the disk it suggests as **Recommended** and picks it for you. Press **A** on another card to choose that one instead. * **Folder name** is `Emulation` unless you change it. The line below shows the full path Kouch will create, for example `D:\Emulation`. * **Already have an Emulation folder?** Its disk shows **Emulation folder found**. Choose it and leave **Use the existing Emulation folder** on. Kouch then uses that folder as it is and only adds what's missing. {% hint style="info" %} Kouch never touches files that are already there. It creates folders, and it only changes an emulator's settings after showing you, in the last step. {% endhint %} ## 2. More disks for games? ![The second step: other disks, each marked "roms only"](https://3008865259-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiaV8VKDYJngjWWkPZx0Q%2Fuploads%2Fgit-blob-3078cc3147d65accb26168ac04a31c7d3968064e%2Fsetup-2-more-disks.png?alt=media) If your games are spread over more than one disk, add the others here. Press **A** on each disk you want. Kouch creates a `roms` folder on each one and **never puts saves or system files there**, so a game disk can be unplugged safely. No other disks? Press **Start** to skip. ## 3. Pick a look ![The third step: Black or White](https://3008865259-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiaV8VKDYJngjWWkPZx0Q%2Fuploads%2Fgit-blob-09757097cccf406657dcad14eefee7b36241aff1%2Fsetup-3-look.png?alt=media) Choose **Black** or **White**. Black is easiest on OLED screens. The change shows straight away, and you can change it any time from quick access (**Select**) or **Settings › Display**. ## 4. Emulators ![The fourth step: the emulators Kouch already knows](https://3008865259-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiaV8VKDYJngjWWkPZx0Q%2Fuploads%2Fgit-blob-b4509836513634bb36b3de8cc1914819997e811a%2Fsetup-4-emulators.png?alt=media) Kouch starts the emulators you add. It never includes one itself. This step lists the emulators Kouch already knows. To add one now, **drop its `.kod` file on the Kouch window** or open a `kouch://` link. You can also do it any time later from **Settings › Emulators › Import profile**. See [Add an emulator](/emulators/emulators/add-an-emulator.md). ## 5. Ready to set up ![The last step: everything Kouch will do, before it does it](https://3008865259-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiaV8VKDYJngjWWkPZx0Q%2Fuploads%2Fgit-blob-4363acf26bc1a6439efd2ece6744ada551b559d0%2Fsetup-5-ready.png?alt=media) This page lists **everything Kouch will do**. Nothing has changed yet. Depending on your disks you'll see: | Group | What it means | | ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Create** | New folders Kouch will make. | | **Already there, kept as is** | Folders that exist. Kouch leaves them alone. | | **Emulator settings Kouch will point at these folders** | Emulator config files Kouch will update so the emulator saves into your Emulation folder and reads your controllers from Kouch. Each file is backed up first. | | **Kouch data moving into the new folder** | Things Kouch had stored elsewhere, such as emulators it installed earlier. | | **Your own folders to move yourself** | Folders Kouch found but won't move for you. | | **Left where they are** | Folders whose new place already has files, so Kouch doesn't mix them. | | **Game folders no emulator uses yet** | Folders in `roms` that none of your emulators play yet. They'll show up once you add an emulator for them. | Press **Start** (**Set up**) to go ahead. When it's done you'll see **All set**. Press **A** on **Done**. ## What's in your Emulation folder | Folder | What goes in it | | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `roms\` | **Your games**, one folder per system. There's one on every disk you added. | | `bios\` | **Your own system files** for an emulator that needs them. You add them yourself: drop them onto Kouch, or copy them in. Kouch only places what you give it; it never syncs, sends or packs what's inside. | | `saves\` | Saves, save states, screenshots and settings. Each Steam account gets its own. | | `storage\` | Big data an emulator keeps, plus downloaded art. | | `emulators` | Emulators Kouch installed for you. | | `mods` | Mods you've added. | | `tools` | Kouch's own helpers. | ## Set up later Choose **Set up later** (**Y**) to skip the wizard. Kouch goes to Home and shows **Set up your Emulation folder** with a **Set up now** button, so you can come back to it. The wizard won't open by itself again. You can also run it any time from **Settings › Storage › Run setup again**. ## After setup Kouch shows three quick tips: how to join with a controller, how to open the Quick Menu in a game, and where the themes are. Press **A** on **Got it**. You can see them again from **Settings › About › Show the tips again**. Next: [Your first game](/getting-started/your-first-game.md). --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.kouch.dev/getting-started/first-run-setup.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.