Why convert MusicXML to MNX?
MusicXML is how scores move between most notation applications. MNX is the working format used by Viritura. This converter reads the musical structure in a MusicXML file, maps supported notation into MNX, and reports source details that need review.
How MusicXML and MNX differ
MusicXML is XML designed first for exchange between notation programs. Its structure uses an ordered stream of notes and directions. MNX uses JSON and makes several musical relationships explicit: voices are sequences, notes sounding together belong to one event, and objects such as ties and slurs can point to their destinations.
Chords
MusicXML writes chord notes as adjacent note elements and marks the later notes as part of the chord. MNX places the notes together in one event, with one duration and rhythmic position.
Voices
MusicXML can move its reading position backward to begin another voice. MNX stores simultaneous voices as separate sequences within the measure.
Tuplets
MusicXML describes tuplet timing on notes and uses start and stop notation for the visible group. MNX represents a tuplet as a container with its own content and rhythmic relationship.
Layouts
MusicXML carries print and positioning information for reconstructing an exported score. MNX can define layouts separately from source parts, allowing the same music to be arranged in more than one form.
MusicXML has broad support and remains the safer choice for exchange between existing notation applications. MNX has a more direct shape for many relationships and is intended to be usable as a working document, but it is still a draft with a much smaller software ecosystem.
What carries into MNX
The converter handles the basic structure needed to keep working on a score: parts and staves, notes and rests, chords, multiple voices, tuplets, ties, slurs, lyrics, clefs, key and time signatures, tempo, repeats, and common articulations. It also maps supported transposing instruments and multi-staff parts.
Some source details do not have a standard MNX equivalent. With Viritura extensions enabled, supported details can be retained in _x.viritura data. The Extensions and import limitations panel above is the maintained feature list. It separates extension-backed details, incomplete mappings, and source details that are not preserved.
Choose the output you want
Viritura extensions
Leave extensions on when the destination is Viritura and retaining supported source-specific notation matters. Turn them off to produce strict MNX output.
Stem directions
Keep explicit MusicXML stems to follow the source, or ask Viritura to recompute them from voice and pitch. Stemless and double-stemmed events need review.
Tempo text
Keep the numeric metronome value visible, or retain it for playback while written tempo text leads the printed result.
Review before you continue
Preview shows whether the converted score looks right. Diagnostics list details omitted or approximated for the selected file. MNX Output shows the generated document itself with live MNX Schema validation.
A valid MNX document can still differ from the source. Use the preview and diagnostics together before treating the conversion as finished.
Common questions
What is an MXL file?
An .mxl file is compressed MusicXML. It contains the same kind of notation data as an uncompressed MusicXML document, packaged into a smaller file for sharing.
Can the converter open Finale files?
It cannot open Finale .mus or .musx files directly. Export the score from Finale as MusicXML 4.0 or compressed MusicXML, then open that exported file here.
Will the MNX score look exactly like the original?
Not necessarily. Pitches, rhythms, and basic score structure often transfer more reliably than individually positioned items. Review the preview and diagnostics before treating the result as finished.
Does conversion upload my score?
No. Conversion and preview run locally in the browser. Your files stay on your device.