Embedded Word editing removes the download, edit, and upload loop from your
product. A user opens a .docx, changes it in your interface, and saves the
result to your application.
Try the embedded editor
Edit the sample document or open your own Word file:
DOCX Editor processes the document in the browser. Your application controls where the original and edited files are stored.
For agent workflows, the editor exposes two separate layers. The editing API lets your tools read and change the document. The composable UI lets users inspect and control those changes.
Plan the document flow
An embedded editing workflow has four parts:
- Your application loads DOCX bytes from a file picker, database, or object store.
- The editor reads Office Open XML (OOXML) and renders editable pages.
- The user or your automation changes the open document.
- Your application saves the returned DOCX bytes as a new version.
This flow keeps your product responsible for authentication, storage, version history, autosave, and access controls.
The loading and saving guide shows the browser file lifecycle. The core architecture explains how OOXML becomes an editable document and returns to DOCX.
Choose the integration surface
Use the adapter that matches your interface:
- React Word editor covers components, refs, and saving.
- Vue DOCX editor covers Vue 3, template refs, loading, and saving.
- Nuxt DOCX editor covers the client-only component and Vite setup.
- Programmatic editing API covers server jobs and open-editor automation.
- DOCX editing API for AI agents covers custom tools and agent interfaces.
- Contract redlining API covers AI SDK tools and user-reviewed proposals.
- Tracked changes and comments cover review workflows.
The React and Vue adapters use the Apache 2.0 license. Review features and programmatic editing use commercial licenses.
Check the fit for your application
DOCX Editor works on the Word document structure instead of using HTML as an
intermediate format. This approach suits products that must return editable
.docx files with their document structure intact.
The packages do not provide your storage, permissions, approval workflow, or agent model. Your application supplies those systems.
If you build contract software, see Word document editing for legal applications.
Explore common document requirements
Check Word fidelity before you select a document workflow. It lists supported structures and round-trip behavior.
Use content controls for structured fields inside Word documents. Use custom styles when your application owns the document style system. The Pro overview explains the commercial review and extension features.