Guide
How to import MusicXML into Finale.
MusicXML is how scores travel between notation programs. If a colleague sent you a .musicxml, .xml, or .mxl file — or you converted a scan into one — here is what Finale does with it, and what to check once the document is open.
The import, step by step
- Check what you have. MusicXML arrives as .musicxml, .xml, or compressed .mxl. Finale reads all three. Leave the extension exactly as it is.
- Bring the file in from the File menu. In current versions, MusicXML comes in through the File menu — either File › Open or File › Import › MusicXML, depending on your version. Both routes produce the same result: a new Finale document built from the file.
- Answer the import prompts. Finale may ask which document settings or template to base the new score on. A standard default template usually gives a cleaner page than trying to reproduce the source formatting.
- Check the staves and the first system. Confirm staff order, instrument names, clefs, key signature, and time signature on the opening system of every part before you start editing.
- Save as a Finale document. Save in Finale's own format so your edits and page layout persist, and keep the MusicXML as the source file you can bring in again.
Finale converts on the way in: the result is a new Finale document, not a live link back to the MusicXML. Re-importing an updated file therefore produces a new document rather than updating the one you have been editing — worth knowing before you invest an hour in layout.
What comes across reliably
The musical substance transfers well. Expect notes and rests with correct pitches and durations, key and time signatures, clefs including mid-staff changes, multiple layers or voices on a staff, ties and slurs, dynamics and hairpins, articulations, tempo markings, repeat structure, and lyrics attached to the right syllables. Staff names and grouping generally survive, which is what matters most on an ensemble score.
What does not transfer is the page. MusicXML can describe how the source looked, but Finale re-sets note spacing, system breaks, and page turns against its own document settings. A score that filled five pages elsewhere may fill four or six here. That is expected, not a failure.
What usually needs cleanup
- Beaming. Beam groups are commonly re-derived from the time signature, so beaming that crossed beats in the source may need regrouping.
- Tuplet grouping. Durations are usually correct while bracket visibility, number placement, and nested tuplets need adjusting.
- Layout and formatting. Measure layout, staff spacing, and the vertical position of expressions are recomputed. Update the layout once across the document rather than measure by measure.
- Expressions and text. Titles, composer lines, rehearsal marks, and technique text can land in the wrong category or style, which affects both appearance and playback.
- Specialised notation. Percussion mapping, custom noteheads, figured bass, guitar notation, and heavily edited historical music are the first things to inspect.
Troubleshooting
The file will not open. Check the extension first — it must be .musicxml, .xml, or .mxl. Files sent by email or chat frequently arrive with the extension stripped, doubled, or changed to .txt. Rename it correctly and try again. A .mxl is a zip container; if something expanded it in transit, point Finale at the uncompressed .musicxml inside.
The score opens but the parts are garbled. Staves in the wrong order, music on the wrong instrument, or a piano split oddly across two staves almost always reflects the part assignments in the file rather than the import. Compare the staff list against the original score; correcting assignments at the source beats moving music between staves afterwards.
Bars hold the wrong number of beats. That is a content fault in the file and will appear the same way in any program that reads it. Find the measures and fix the durations there.
The document is empty. Usually an empty or truncated file. Check the file size before assuming Finale is at fault.
Starting from a PDF or a scan instead
If what you actually have is a printed part, a PDF, or a photo of a page, you need MusicXML before any of this applies. StaveWave converts scans and PDFs into MusicXML, then walks you through a bar-by-bar check that spotlights the measures it was unsure about on your original page — so recognition errors are caught before they reach Finale, where they are much harder to spot. It is an online service that runs in the browser, with nothing to install.
Start at PDF to MusicXML. If you already have MusicXML and want a print-ready engraved edition rather than an editable document, the engraving service computes the layout and returns PDF, MusicXML, and MIDI.