Transpose sheet music online by semitones, target key, or instrument profile. Keep the original score, create a new revision, and review range and spelling.
BetaChoose semitones, a target key, or a transposing-instrument profile, then compare the new revision with the untouched source.
Transposition uses music21 when configured and keeps a deterministic TypeScript fallback; complex enharmonic spelling and clef comfort still require review.
The current implementation supports semitone, target-key and transposing-instrument modes.
Short product demo
Watch the actual workflow
Short product demo: transposing a score into a new revision
Workflow
How this path works
The public page leads into the authenticated app workflow when users are ready to process a score.
01
Open a score project
Use any project with a current Score JSON revision created from MusicXML, OMR, Jianpu, MIDI, or Score JSON import.
02
Choose the transposition mode
Move by semitones, choose a target key, or create a written part for Bb, A, Eb, or F instruments.
03
Check the resulting range
Optional voice and instrument range profiles report low/high notes and write warnings into the new revision.
Product detail
What to expect
Revision-based workflow
Change the sheet music key without overwriting the source: every transposition creates a new version so teachers and arrangers can compare results.
Exports regenerate from the model
Jianpu, MusicXML, MIDI, rendered PDF/images, and practice audio can be generated again from the transposed revision.
Transpose for singers and instruments
Change the sheet music key for a vocal range, or create written parts for common transposing instruments while preserving the source revision.
Common errors
Where this workflow usually fails
The interval moves in the wrong direction
Symptom: The new score is higher when the singer or instrument needed a lower key.
How to fix it: Confirm up/down direction and preview the lowest and highest resulting notes before export.
Concert pitch is confused with written pitch
Symptom: A Bb, Eb, F, or A instrument part sounds in the wrong key.
How to fix it: Use the instrument profile and verify one known written-to-sounding pitch before processing the whole part.
Correct pitches use awkward spelling
Symptom: The notes sound right but contain hard-to-read double accidentals or uncomfortable clefs.
How to fix it: Review enharmonic spelling, key signature, clef, and range; musical readability still needs human judgment.
Accuracy statement
What is reproducible and what needs judgment
The pitch interval transformation is deterministic for structured notes, and the downloadable example is checked note-for-note. That does not make every notation choice automatically optimal: enharmonic spelling, octave placement, clef changes, vocal tessitura, and instrument range remain musical decisions.
Test and review checklist
Verify the first and last notes against the chosen interval.
Check the new key signature and all accidentals.
Play the result and inspect the full range before distributing parts.
Workflow comparison
Choose the workflow that fits the task
This compares workflow categories, not the overall superiority of any brand. Product scope and capabilities change over time.
Workflow
Best for
Tradeoff
ScoreTransposer browser workflow
Non-destructive revisions, target-key/instrument modes, range checks, and regenerated exports.
Final spelling and part readability still need review.
Traditional notation editor
Manual engraving adjustments after transposition.
The operation may involve more setup and manual comparison with the source revision.
Static PDF pitch-shift workflow
Changing playback audio without needing editable notation.
It does not create a trustworthy structured score or instrument part.
FAQ
Questions about Transpose Sheet Music Online
Practical limits and the expected workflow for this score tool.
What input does Transpose Sheet Music Online accept?
Use any project with a current Score JSON revision created from MusicXML, OMR, Jianpu, MIDI, or Score JSON import.
Can I edit the result after conversion?
Yes. Successful imports become Score JSON revisions that can be corrected, transposed, played, and exported from the score workspace.
What should I check before relying on the result?
Transposition uses music21 when configured and keeps a deterministic TypeScript fallback; complex enharmonic spelling and clef comfort still require review.
Related workflows
Continue with the same score project
These pages use the same MusicXML and Score JSON source instead of sending the score through disconnected converters.
Current real product captures/videos, self-authored native-format samples, automated file-signature and SEO tests, plus the manual checks listed on this page.
