SuperDoc Editor
Understand how SuperDoc edits DOCX files before you add the Editor to your application.
SuperDoc adds DOCX editing to your web application. People work in a document editor while your application controls where files come from, where they are saved, and which workflows surround them.
Keep DOCX as the document
A DOCX is a package of XML parts, relationships, and assets. An HTML-first editor converts that package into another format for editing, then reconstructs a DOCX for export.
SuperDoc takes a different path. It reads the document's OOXML package into editable state and writes changes back to OOXML without converting the document to HTML. The browser DOM is a rendered view, not the document format.
| Approach | Editing model | DOCX output |
|---|---|---|
| HTML-first editor | Converted HTML | Reconstructed from HTML |
| SuperDoc | OOXML-backed document state | Changes written back to the package |
Fit the Editor into your application
The browser Editor mounts inside your application and needs no SuperDoc server to render or edit a document. Your application chooses the document source, storage, authentication, and collaboration provider.
People edit through the browser UI. Application code can use the Document API against the same open document. For server-side automation and agent workflows, SuperDoc provides headless tools built on the same OOXML-backed model.
SuperDoc is open source under AGPLv3. A commercial license is available for proprietary applications. See Licensing for the requirements of each option.
What changed in v2?
SuperDoc v1 used ProseMirror as its authoritative browser editing model. V2 uses an OOXML-backed document model across browser and headless workflows. If you already use v1, start with Migrate from v1.
Open your first document
Follow the Quickstart to install the Editor, open a DOCX, make an edit, and export the result.