> 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/appendix/upgrade-from-musescore-1x-or-2x.md).
# Upgrade from MuseScore 1.x or 2.x
## How to upgrade MuseScore
Download and install the latest version from the [download](https://musescore.org/en/download) page as described at [Installation](/3/getting-started/download-and-installation.md).
Installing MuseScore 3 won't uninstall 1.x nor 2.x —all three versions can coexist peacefully and can even be used in parallel. So this isn't really an upgrade but an installation of a new and different program.
## Opening 1.x or 2.x scores in MuseScore 3
MuseScore 3 significantly improved the typesetting quality to make scores attractive and easier to read. Improvements cover many items such as beam slope, stem height, layout of accidentals in chords and general note spacing. However, this means that sheet music made with MuseScore 1.x or 2.x looks slightly different from sheet music made with 3.x.
It also means that scores saved with 3.x won't open with 1.x nor 2.x.
To prevent you from accidentally overwriting your 1.x or 2.x scores, 3.x treats them as an import, which means:
* The score gets marked as being modified, even if you haven't changed anything
* On exiting MuseScore you're asked to save the score (as a result from the above)
* MuseScore uses the "Save As" dialog to save it, not the "Save" dialog
* MuseScore uses the score's title to create a default filename rather than taking the old filename
## Relayout
If you did not manually adjust the layout of a 1.x or 2.x score, then MuseScore uses the 3.x typesetting engine to layout the score. If you *did* touch the layout of the 1.x or 2.x score, the individual adjustments you may have made should remain after opening it in MuseScore 3.x, but due to slight changes in the surrounding layout they may still not appear correct in context. If you wish to reset even manual adjustments to use the 3.x typesetting engine throughout, select the complete score with the shortcut Ctrl+A (Mac: Cmd+A) and reset the layout with Ctrl+R (Mac: Cmd+R).
**Note**: When you open a 1.x or 2.x file in MuseScore 3, it will ask you if you want to reset the layout to the defaults.
## Getting the sound from MuseScore 1.x
While the sound in 2.x/3.x has been much improved, you may still prefer the sound from MuseScore 1.x. In that case, you can get the 1.x sound in 3.x by downloading the 1.3 SoundFont and add it in 3.x. You can do this in two steps:
1. [Download the 1.3 SoundFont named TimGM6mb](/3/sound-and-playback/soundfonts-and-sfz-files.md#list-of-downloadable-soundfonts-and-sfz)
2. [Install and use the TimGM6mb SoundFont in 2.0](https://musescore.org/en/node/50721)
---
# 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/appendix/upgrade-from-musescore-1x-or-2x.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.