# What Is MusicXML? The Format for Editable Scores

MusicXML explained from the spec: what a .musicxml or .mxl file stores, how it differs from MIDI and PDF, version 4.0, and which programs open it.

Canonical: https://pianotosheetmusic.com/blog/what-is-musicxml
Published: 2026-10-22 · Author: Antoine Duno (https://pianotosheetmusic.com/about)

If you've been handed a .musicxml or .mxl file, or a transcription tool offered you one next to a PDF, it's the file that lets you change the music. A PDF is a picture of a score and a MIDI file is a recording of keys being pressed. MusicXML is the score itself, written as text that any notation program can read.

> **Quick answer**
>
> **MusicXML** is an open file format for **exchanging digital sheet music between programs**. It stores notation as XML text: pitches with their **spelling** (E-flat is not D-sharp), note **durations and types**, **clefs, key and time signatures**, ties, lyrics, text and much of the **layout**. Files end in **.musicxml** (plain) or **.mxl** (zip-compressed). The current version is **MusicXML 4.0** (June 2021), maintained by the **W3C Music Notation Community Group**; it is not a formal W3C Standard. Open it in **MuseScore Studio, Sibelius** or other notation software to edit, transpose or reprint a score.

## MusicXML at a glance

Facts from the MusicXML 4.0 specification and its tutorial on w3.org, read on 16 September 2026.

| | |
|---|---|
| **What it is** | "A standard open format for exchanging digital sheet music" |
| **Designed for** | Sharing sheet music files between applications, and archiving them |
| **Underlying format** | XML text |
| **File extensions** | .musicxml (uncompressed), .mxl (compressed, zip-based) |
| **Media types** | application/vnd.recordare.musicxml+xml (uncompressed); application/vnd.recordare.musicxml (compressed) |
| **Current version** | 4.0, Final Community Group Report, 1 June 2021 |
| **Maintained by** | W3C Music Notation Community Group |
| **Status** | "Not a W3C Standard nor is it on the W3C Standards Track" |
| **Support** | "Over 250 applications" as of the 4.0 publication date |
| **First version** | 1.0, released January 2004 |

## What a MusicXML file stores

The specification's tutorial describes the format's aim as "a universal format for common Western music notation, similar to the role that the MP3 format serves for recorded music." It also explains the design in one line that matters for anyone choosing between file types: "MusicXML consists of two main types of elements." One set represents "how a piece of music is notated", for display on screen or in print. The other represents "a sonic realization of the score", used for MIDI playback.

That dual role is what separates it from the other two score files you meet.

| | MusicXML | MIDI | PDF |
|---|---|---|---|
| Note pitches | Yes, with spelling | Yes, as numbers only | Only as shapes on a page |
| Rhythms as notation (quarter, dotted half) | Yes | No, as timings | Only as shapes |
| Clefs, key and time signatures | Yes | Key and time only | Only as shapes |
| Beams, ties, articulations as written | Yes | No | Only as shapes |
| Editable in notation software | Yes | After import and cleanup | No |
| Plays back | Yes, in software | Yes | No |

Our [MIDI vs MusicXML vs PDF](/blog/midi-vs-musicxml-vs-pdf) guide goes through which one to use for which job. In short: keep the MusicXML, share the PDF, use the MIDI for sound.

## What's inside: one bar, explained

A MusicXML file is readable text. Here is a one-bar example we wrote for this page, following the structure the tutorial teaches: a dotted half note on the E-flat above middle C, in E-flat major, in 3/4.

```xml
<score-partwise version="4.0">
  <part-list>
    <score-part id="P1">
      <part-name>Piano</part-name>
    </score-part>
  </part-list>
  <part id="P1">
    <measure number="1">
      <attributes>
        <divisions>1</divisions>
        <key><fifths>-3</fifths></key>
        <time><beats>3</beats><beat-type>4</beat-type></time>
        <clef><sign>G</sign><line>2</line></clef>
      </attributes>
      <note>
        <pitch><step>E</step><alter>-1</alter><octave>4</octave></pitch>
        <duration>3</duration>
        <type>half</type>
        <dot/>
      </note>
    </measure>
  </part>
</score-partwise>
```

What each piece means, from the tutorial:

- **score-partwise** is the root. The score is organised as parts, each made of measures. There is also a **score-timewise** layout, measures made of parts, but the tutorial notes that "most of today's MusicXML applications use the \<score-partwise\> format."
- **part-list** is the header naming every part. Each **part** must refer back to one of those ids.
- **divisions** sets the unit for durations "in terms of divisions per quarter note". With 1 division per quarter, a dotted half lasts 3.
- **fifths** is the key signature's position on the circle of fifths: negative for flats, positive for sharps. Three flats is -3.
- **beats** and **beat-type** are the top and bottom of the time signature.
- **pitch** splits the note into **step** (E), **alter** (-1 for flat) and **octave** (4, the octave starting at middle C).
- **type** and **dot** say how the note is written, separately from **duration**, which says how long it lasts.

One detail shows the design thinking. The tutorial says the pitch element needs **alter** "even if the accidental is already in the key signature". The pitch records what sounds; the key signature records what's printed. That separation is why a MusicXML file can be transposed or re-engraved without losing the spelling.

## .musicxml or .mxl?

Both contain the same notation. The tutorial explains that plain MusicXML files "can be very large - much larger than the original music notation application files, or corresponding MIDI files", which held back its use for distributing sheet music. MusicXML 2.0, released June 2007, introduced the compressed format, which the tutorial says "reduces MusicXML file sizes to roughly the same size as the corresponding MIDI files".

An .mxl file is a zip archive. Inside, a file at **META-INF/container.xml** points to the main MusicXML file, and since version 3.1 a small uncompressed **mimetype** file comes first so programs can identify it. The 4.0 specification also allows images, a PDF rendition and separate parts in the same archive.

Most programs open either. If one refuses, try exporting the other form. Our short guide to MusicXML vs MXL covers when each is the better choice.

## Versions, and who looks after it

The version history on w3.org dates each release:

| Version | Released | Notable change |
|---|---|---|
| 1.0 | January 2004 | First release |
| 1.1 | May 2005 | Page, system and staff layout; credits on the first page |
| 2.0 | June 2007 | Compressed .mxl files |
| 3.0 | August 2011 | Standard instrument sounds for playback |
| 3.1 | December 2017 | Licensed under the W3C Community Final Specification Agreement; .musicxml recommended over .xml |
| 4.0 | June 2021 | Score and parts in one .mxl; concert-pitch scores; Nashville numbers and Roman numerals in chord symbols |

The specification is published by the W3C Music Notation Community Group, and it is careful about what that means: "It is not a W3C Standard nor is it on the W3C Standards Track." Community groups, the W3C's own page notes, "are proposed and run by the community" and "do not necessarily represent the views of the W3C Membership or staff." Calling MusicXML "the W3C standard" is a common shorthand, and it's wrong.

The format is still being worked on. The group's page describes it maintaining MusicXML and the SMuFL music font specification, and developing a newer format under the working title MNX. Its progress posts from September 2026 describe roadmap work towards a MusicXML 4.1 release. For now, 4.0 is what programs read and write.

## Opening a MusicXML file

Any current notation program will do. MuseScore Studio's handbook puts it simply: you can convert a MuseScore file to MusicXML "and it will open in Sibelius, Finale, or any other compatible scorewriter; and vice versa." Our guide to importing MusicXML into Sibelius covers that program's options.

The same handbook is honest about the limit: "MusicXML faithfully reproduces the notes and instrumentation, but, nevertheless, it is usually necessary to do some clean-up work to make the transferred score look exactly the same as the original." Its import settings deal with page layout, system and page breaks, fonts, and text that arrives as plain staff text. The notes come across; the page layout often needs a pass.

A text editor opens MusicXML too, as the example above shows, but you'd only edit it that way to fix something a program can't.

## Why it matters when you transcribe a recording

A transcription is a draft, whoever or whatever makes it. The PDF shows you the draft. The MusicXML lets you fix it: correct a wrong note, respell an accidental, move a note to the other staff, add fingering, then print a clean PDF from your corrected version.

That's why Piano to Sheet Music delivers a MusicXML file with every piece, alongside the engraved PDF and a MIDI file, for $4.99 per piece with no subscription. If you want to see what a transcription of your own playing looks like in MuseScore, you can [try it here](/transcribe).

It matters for submissions too. Exam boards and competitions usually want a PDF, but the corrections they ask for are made in the notation file. If you're preparing coursework, our guide to A-Level Music composition score requirements covers what the boards ask for; keep the MusicXML alongside whatever you submit.

## Frequently asked questions

### What is a MusicXML file?

A MusicXML file is sheet music stored as text in XML, so notation programs can exchange it. The specification calls it a standard open format for exchanging digital sheet music, designed for sharing between applications and archiving. It records notes with their spelling, clefs, key and time signatures, and much of the layout, not just the sound.

### What is the difference between MusicXML and MIDI?

MIDI records a performance and MusicXML records notation. The MusicXML tutorial points out that MIDI stores a pitch as a single number, while MusicXML splits it into step, alteration and octave, so E-flat and D-sharp stay different. MusicXML also stores clefs, beams and written note values that MIDI has no place for.

### What program opens a MusicXML file?

Most notation software. MuseScore Studio's handbook says a MusicXML file exported from MuseScore will open in Sibelius, Finale or any other compatible scorewriter, and vice versa. The MusicXML 4.0 specification says the format was supported by over 250 applications when it was published in 2021.

### What is the current version of MusicXML?

MusicXML 4.0, published by the W3C Music Notation Community Group in June 2021. The group's September 2026 progress posts describe work towards a MusicXML 4.1 release. Version 4.0 added ways to store a score and its parts in one compressed file, concert-pitch scores, and Nashville numbers and Roman numerals in chord symbols.

### Is MusicXML a W3C standard?

No, and the specification says so directly: it is not a W3C Standard nor on the W3C Standards Track. MusicXML 4.0 is a Final Community Group Report, published by the W3C Music Notation Community Group under the W3C Community Final Specification Agreement. In practice it is the common exchange format for notation software.

### Does MusicXML keep the exact look of my score?

Not exactly. MuseScore Studio's handbook says MusicXML faithfully reproduces the notes and instrumentation, but some clean-up is usually needed to make a transferred score look the same as the original. Expect page layout, system breaks and text styles to need attention after import, and the notes themselves to arrive intact.

## Sources

- [W3C Music Notation Community Group: MusicXML 4.0, Final Community Group Report](https://www.w3.org/2021/06/musicxml40/)
- [MusicXML 4.0 tutorial: introduction](https://www.w3.org/2021/06/musicxml40/tutorial/introduction/)
- [MusicXML 4.0 tutorial: "Hello World" in MusicXML](https://www.w3.org/2021/06/musicxml40/tutorial/hello-world/)
- [MusicXML 4.0 tutorial: the structure of MusicXML files](https://www.w3.org/2021/06/musicxml40/tutorial/structure-of-musicxml-files/)
- [MusicXML 4.0 tutorial: the MIDI-compatible part of MusicXML](https://www.w3.org/2021/06/musicxml40/tutorial/midi-compatible-part/)
- [MusicXML 4.0 tutorial: compressed .mxl files](https://www.w3.org/2021/06/musicxml40/tutorial/compressed-mxl-files/)
- [MusicXML version history: 1.0](https://www.w3.org/2021/06/musicxml40/version-history/10/), [1.1](https://www.w3.org/2021/06/musicxml40/version-history/11/), [2.0](https://www.w3.org/2021/06/musicxml40/version-history/20/), [3.0](https://www.w3.org/2021/06/musicxml40/version-history/30/), [3.1](https://www.w3.org/2021/06/musicxml40/version-history/31/), [4.0](https://www.w3.org/2021/06/musicxml40/version-history/40/)
- [W3C Music Notation Community Group home page and progress posts](https://www.w3.org/community/music-notation/)
- [MuseScore Studio Handbook: working with MusicXML files](https://handbook.musescore.org/file-management/working-with-musicxml-files)

Sources checked 16 September 2026.