> For the complete documentation index, see [llms.txt](https://docs.chromaticsffxiv.com/chromatics-4/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chromaticsffxiv.com/chromatics-4/getting-started/beta-releases.md).

# Beta Releases

Chromatics uses a two-channel release model. Most people should stick with the **stable** channel, which is the default. If you'd like to help test new features and fixes early, you can opt in to the **beta** channel.

## What to expect from betas

Beta releases contain the latest features, fixes, and performance improvements, but they haven't finished testing yet. That means:

* Features can still change between beta builds.
* You'll occasionally hit bugs that aren't in the stable release.
* Your feedback directly shapes what ships to everyone else.

Your settings, layers, and palettes are safe across beta builds - they use the same format as the stable release.

## Opting in

You can switch to the beta channel from inside the app:

1. Open **Settings → Advanced**.
2. Turn on **Opt in to beta releases**.
3. Click **Check for Updates**.

Chromatics will check both the stable and beta update feeds and install whichever version is newest.

To go back to the stable channel, turn the setting off. You'll stay on the current build until the next stable release overtakes it.

## Reporting feedback

The best place to report beta feedback is our Discord, in the **#beta-releases** channel.

[![](https://discordapp.com/api/guilds/334196655131721741/widget.png?style=banner2)](https://discord.gg/sK47yFE)

When reporting a bug, it's very helpful to include:

* The Chromatics version (shown at the top of the Console tab).
* Your device(s) and vendor software versions.
* A short description of what you were doing when the issue happened.
* Logs if possible - **Settings → Advanced → Collect Logs** bundles everything useful into a ZIP you can drop in Discord.