> 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/3/advanced-topics/fretboard-diagrams/fretboard-diagrams-prior-to-version-31.md).
# Fretboard diagrams (prior to version 3.1)
**Note**: *This page applies to versions of MuseScore prior to 3.1 only. Users of MuseScore 3.1 and above should go to* [*Fretboard diagrams*](/3/advanced-topics/fretboard-diagrams.md)*.*
A range of **fretboard** (or **chord**) **diagrams** for the guitar are provided in the Fretboard Diagrams [palette](/3/basics/palettes.md) in the Advanced Workspace.
You can create a chord diagram for *any* fretted, stringed instrument by [editing](#edit-a-fretboard-diagram) an existing one. It can be saved to a [custom palette](/3/basics/palettes.md#customize-palette-contents) for future use if required.
## Add a fretboard diagram
To add a fretboard diagram to the score, use one of the following methods:
* Select a note in voice 1 and double-click a fretboard diagram from a [palette](/3/basics/palettes.md).
* Drag and drop a fretboard diagram from a palette to the desired position in the score.
As the cursor hovers over the chosen diagram within the palette, its name will appear as a **pop-up hint**.
## Edit a fretboard diagram
When a fretboard diagram is selected, it can be edited in the [Inspector](/3/basics/inspector.md) as follows:
* To adjust the **number of instrument strings**: Use **Strings**.
* To adjust the **fret position number**: Use **Offset**.
* To adjust how many frets to display (height-wise): Use **Frets**.
* To **place the finger dots**: Click on a fret to establish a dot; click again to remove the dot.
* **To create a barre or partial barre**: First make sure that the desired fret position is clear of black dots (click on a dot to remove it). Then, holding the Shift key, click on the string where you want the barre to begin. (Note: Only one barre can be applied per diagram; a partial barre must end on the first string).
* **To delete a barre**: Click on the black dot where the barre begins.
* **To Indicate open and mute strings** (if applicable): Click just above the diagram to toggle a string between:
* Open (**o**)
* Mute/unplayed (**x**)
* No indication.
* To adjust the size: Use the **Scale** property.
## To adjust a diagram's element properties
The **position** of a Fretboard Diagram can be adjusted using the keyboard arrows in [Edit mode](/3/basics/edit-mode.md); or with the X- and Y-offsets in the "Element" section at the top of the [Inspector](/3/basics/inspector.md).
**Visibility**, **Color** and **Stacking order** can also be adjusted from the "Element" section.
## To adjust a diagram's style properties
Certain default and global properties of Fretboard Diagrams (e.g. barre thickness, vertical position, scale, fret-number font-size and position) can be adjusted from the [Style](/3/formatting/layout-and-formatting.md#style-window) submenu: select **Format -> Style… ->** [**Fretboard Diagrams**](/3/formatting/layout-and-formatting.md#fretboard-diagrams). Some of these properties are subject to override via the [Inspector](/3/basics/inspector.md); but most affect all Fretboard Diagrams 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 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://handbook.musescore.org/3/advanced-topics/fretboard-diagrams/fretboard-diagrams-prior-to-version-31.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.