Dorico export workflow

Dorico to editable sheet music

Export selected Dorico flows or layouts as MusicXML, preview the result locally, and continue with a verified editable score while preserving the original Dorico project.

Honest conversion route

Dorico projects contain flows, layouts, engraving settings, and playback data that a web importer cannot reproduce from .dorico directly. Select the needed flows in File → Export → MusicXML, then open the exported MXL or XML file below.

Accepted after export: .musicxml, .xml, or .mxl. Native .dorico files are not accepted.

Open MusicXML exported from Dorico

Choose the flow or layout export you intend to edit. The original .dorico project is not a supported browser input.

Open MusicXML

Parsing and engraving run locally in your browser. This tool does not upload the score.

Local · zero Token

Drop a .musicxml, .xml, or .mxl file here

or choose one file from this device · instant preview up to 2 MB

Source-specific workflow

From Dorico to a checked editable score

The preview is an import test, not proof of perfect fidelity. Complete these steps before treating the converted document as a new source of truth.

  1. 1

    Choose Dorico flows and layouts deliberately

    In Dorico choose File → Export → MusicXML, select compressed or uncompressed XML, then select the flows to export. If layouts must remain separate, enable separate layout files before choosing the destination.

  2. 2

    Preview one exported file at a time

    Open the resulting .mxl or .xml file below. Local normalization and engraving expose the actual interchange result before it enters an editable document.

  3. 3

    Verify semantic and visual differences

    Check player-to-staff assignments, flow titles, condensing results, divisi, custom playing techniques, percussion, and overrides made in Engrave mode. Then continue with the checked score.

What fidelity really means for this route

First confirm musical meaning, then inspect application-specific engraving and playback. A clean preview can still need deliberate editorial correction.

Usually carried

  • Core notes, voices, tuplets, lyrics, dynamics, articulations, and playing directions
  • Players represented as parts and staves, instrument changes, keys, meters, and transpositions
  • Selected flows and many notation properties supported by the MusicXML export

Verify carefully

  • Condensing, divisi, extra players, percussion kits, and complex instrument changes
  • Engrave-mode offsets, custom paragraph styles, music fonts, and page templates
  • Flow headings, layout-specific content, custom playing techniques, and repeat behavior

Not promised

  • Dorico project structure as one editable project with all flows and layouts linked
  • Playback templates, expression maps, mixer state, endpoint setups, and sampled sounds
  • Complete Engrave-mode overrides or guaranteed reproduction of Dorico spacing

Questions before you convert

Can NotationAI open a .dorico project?

No. Export MusicXML from Dorico first. The native project coordinates flows, layouts, engraving, and playback in ways that are not represented by a single interchange file.

Should I export flows or layouts separately?

Choose based on the editing task. Export the exact flows you need, and use separate layout files when part-specific or soloist material needs independent review.

Does MusicXML preserve Dorico condensing?

Do not assume it does. Condensing is a layout process tied to Dorico’s players and rules. Verify the resulting staves and voices against a reference PDF before editing.

Related input routes