> 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/albums.md).

# Albums

## Overview

**Warning: The Album feature has been disabled in 3.x. It may come back in 5.x.**

The Album Manager allows you to prepare a list of multiple scores and save the list as an album file ("\*.album"), print all the scores as one long print job with consistent page numbers, or even join the scores into a single new MSCZ score. This is ideal for preparing an exercise book or combining multiple movements of an orchestration.

To open the Album Manager, go to **File -> Album...**

<figure><img src="/files/S3krwTdv5hfLQ47Fomfj" alt="Album Manager"><figcaption></figcaption></figure>

## Create album

1. To create a new album, click the **New** button. Fill in a title in the "Album Name:" box at the top.
2. To add scores to the album, click **Add Score**. A file selection dialog will appear and let you choose one or multiple scores from your file system. Click **OK**.
3. The scores you add will appear in a list in the Album Manager. You can rearrange their order by selecting a score and clicking the **Up** or **Down** button.

## Load album

If you have previously created an album, you can open it through the Album Manager by clicking the **Load** button. A file selection dialog will appear to let you load the .album file from your file system.

## Print album

To print an album as if it were a single document, click **Print Album**. The scores loaded into the Album Manager are printed in the order they are listed in with the correct page numbers, ignoring the page number offset values in **Layout -> Page Settings... -> First page number** for all but the first score. As the album is printed in one print job, double-sided printing (duplex printing) also works as expected.

## Join scores

To combine multiple scores into a single .mscz file, click **Join Scores**. The scores are combined in the selected order into one single score. If not already present, [line-](/3/formatting/breaks-and-spacers.md) and [section breaks](/3/formatting/breaks-and-spacers.md#section-break) are added to the last measure or [frame](/3/formatting/frames.md) of each score in the combined file.\
All style settings are taken from the first score; different style settings from subsequent scores are ignored.

All the scores should have the same number of parts and staves for this to work correctly, ideally with the same instruments in the same order. If the scores have the same total *number* of instruments but not the same ones, or not in the same order, then the instrument names from the first score will overwrite ones from subsequent scores. If some of the scores have fewer instruments than the first score, then empty staves will be created for those sections. **Any part or staff that is not present in the first score will be lost in the joined score.**

## Save album

Upon clicking the **Close** button, you will be prompted to save your album as a .album file. This file is not the same as a [joined score](#join-scores); it simply consists of the list of scores. Album files can be loaded into the Album Manager as described [above](#load-album).


---

# 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/albums.md?ask=<question>&goal=<endgoal>
```

`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.
