Scans convert best when clean
Sharp staff lines, good contrast, and minimal skew produce better results. StaveWave profiles your upload first and prepares only what that source needs.
Scan to MusicXML
Scan sheet music online and export editable MusicXML.
Scan or photograph a score. StaveWave reads it, validates every measure, and walks you through the uncertain bars before export.
Optimized for scan sheet music to MusicXML, scanned sheet music converter, image to MusicXML, sheet music scan app workflows with reviewable MusicXML output.
Scan to MusicXML benefits
Every measure gets validated
Rhythm, structure, and a render-versus-scan comparison check each bar. The score check groups findings by cause so you can fix the pattern instead of chasing individual warnings.
Edit with proof
Fix notes right on the notation with the scan pinned alongside. An in-editor beat ruler turns green when a bar sums correctly.
Processing stack
The recognition and validation layers behind each export.
StaveWave shows the recognition engines, specialist passes, validation checks, and quality gates involved so users can see what checked the score before trusting the MusicXML.
Recognition passes
Independent recognition passes read the score and create MusicXML candidates.
StaveWave compares independent readings of the notation and keeps disagreements visible instead of treating one reading as automatically correct.
Review checks
Review checks compare the original page with the rendered result.
Visual, corpus, and notation checks inspect weak spots, compare the original scan against the rendered transcription, and flag suspicious measures or suggested fixes.
Specialist checks
Specialist checks look for notation mistakes that matter in editing.
Focused passes review pitch, rhythm, text, structure, articulation, and style so the output needs less cleanup in Sibelius, Dorico, MuseScore, Finale, or another editor.
Quality gates
Release gates decide whether the export is ready or blocked.
Validation, consensus, visual comparison, audio checks, plausibility scoring, and audit evidence must run. If a required component fails, the job reports a blocking error.
Workflow
How StaveWave analyzes the upload.
Capture or scan the score
Use 300+ DPI for printed scores. Phone photos work if the lighting is even and the page is flat.
Upload and review
Submit the file. StaveWave validates the source, runs recognition, and flags uncertain measures.
Export verified MusicXML
Export the file for Sibelius, Dorico, MuseScore, Finale, or any standard notation app.
Questions
What to know before uploading.
These answers match the structured data search engines receive for this page.
What resolution should I scan at?
300 DPI or higher works well for most printed scores. 600 DPI is useful for dense notation or small print. The score check will flag measures where scan quality affected recognition.
Can I use a phone photo instead of a scanner?
Yes, if the lighting is even and the page is flat. Avoid shadows, use good contrast, and shoot straight-on. The score check will show you which measures need attention.
How do I scan a bound book?
Flatten the page as much as possible to reduce skew and shadows near the spine. A flat, high-resolution scan of the full page works best. StaveWave accepts multi-page files up to 50 pages.
Can it read handwritten notation?
StaveWave is optimized for printed notation. Some clean handwritten manuscripts work, but irregular note heads and non-standard spacing increase recognition errors. The score check will flag uncertain measures for review.
What if the scan is unclear?
The score check will point to measures where uncertainty arose. You can re-scan if quality was the issue, or edit the uncertain bars manually in your notation app.
Ready to convert