ScriptScore

Design pillars

Engraving, editing, accessibility, and professional output guide every layout rule, toolbar decision, and release — with ARIA-ready patterns shipped now, not parked for later.

Engraving
Spacing, beams, dynamics, and page balance are the product. Publisher-grade notation is the reason ScriptScore exists.
Editing
Fast, precise score work: selection, entry, revision, and rehearsal-friendly changes without fighting the interface.
Accessibility
Music is for everyone. Legible type, contrast, motor-friendly controls, and ARIA-ready structure so more musicians can read, hear, and write the score.
Professional output
Print-ready pages, consistent house style, and interchange that respects the gig, the publisher, and the studio downstream.

One license, two ways to work

Web application

ScriptScore runs in the browser today: fast iteration, shared projects, and a gallery of real interface captures as we ship production builds.

Desktop application

The Professional standalone is part of the same buy-once roadmap: offline-ready engraving on your machine, not a separate subscription tier.

Open interchange, built in

Production focus: bring existing notation into ScriptScore without a walled garden or subscription upsell.

MusicXML
MusicXML import and export is a core production goal so scores can move between ScriptScore, publishers, and other notation tools. We will describe support only for versions and features that ship and are tested.
Scores from other editors
Many editors (including the open-source MuseScore desktop app) export MusicXML. ScriptScore is being built to ingest that interchange path first; native project formats are evaluated separately.

MusicXML is a trademark of its respective owner. MuseScore is a trademark of its respective owner. ScriptScore is not affiliated with, sponsored by, or endorsed by those parties.