> For the complete documentation index, see [llms.txt](https://handbook.musescore.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.musescore.org/en_gb/customization/appearance.md).

# Appearance

## Overview

To change the appearance of MuseScore

1. From the menu, select **Edit→Preferences...** (Mac: **MuseScore→Preferences...**);
2. In the `Appearance` tab, select the desired option described below.

   <figure><img src="https://3437726813-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhlQyZtOnJ5I68XsXPBVv%2Fuploads%2Fgit-blob-8170b4ab5f665180e26b0f55200c910058857ab1%2Fpreferences_appearance.png?alt=media" alt="Dialog: Edit / Preferences / Appearance"><figcaption></figcaption></figure>

## Theme and Colours

The following options are available to change the colours of MuseScore. The display changes immediately so options can be tested without closing the dialog. The changes apply to all open instances of MuseScore (see [Windows](/en_gb/customization/toolbars-and-windows.md#toolbarsandwindows-windows))

* Light or Dark Theme
* Select "Follow system theme" if you want MuseScore to change themes from light to dark, or dark to light, when the system theme changes
* Enable high-contrast
* Accent colour options
* Background - the colour behind the score (not the colour of palettes and other program items) can be changed to a solid colour or a Wallpaper image.
* Paper - the colour of the score itself can be changed to a solid colour or a Wallpaper image.
* Invert Score - swaps the colour of score elements with the Paper colour

## Fonts

To change the font face and text size for Menu and Palette elements:

1. From the menu, select **Edit→Preferences...** (Mac: **MuseScore→Preferences...**);
2. In the `Appearance` tab, select the font options.

This does not affect and text elements in the score.


---

# 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://handbook.musescore.org/en_gb/customization/appearance.md?ask=<question>&goal=<user_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.