A complete Word editing experience in the browser

An embeddable Word editor, built-in AI agent and JavaScript and TypeScript SDK. Documents open, edit and save locally, without Microsoft Word, a document server or a required UI framework.

Browser editor

Word processing, inside your application

Familiar Word tools in the browser: a ribbon, paginated pages, direct editing, clipboard support and undo and redo. Documents retain their margins, sections, headers, footers and page numbers.

Loading, layout, editing and export run locally, without document uploads or an office service. The editor works embedded in your application or as a standalone browser application.

Commands, fonts, styling and editing modes are configurable. The editor UI is MIT-licensed; its underlying SDK requires a commercial license for production use.

Editor features and customization

Document tools

Text and page formatting
Text and paragraph styles, lists, columns, page breaks, sections, headers, footers and multilingual editing.
Rich document content
Tables and merged cells, images, shapes, charts, equations, hyperlinks, bookmarks, footnotes and tables of contents.
Review and forms
Comments, tracked changes, comparisons and form controls, with viewing, editing, review and form-filling modes.
Word and PDF output
Save edits as DOCX or export rendered pages as PDF, with documented compatibility and export limits.

Built-in AI agent

An assistant that works with the document

Alongside the editor, the AI agent answers document questions, finds content and makes requested changes through the document APIs.

AI assistance is optional. Your application provides the model backend and controls document access. Ordinary editing works independently.

Agent capabilities and integration

Connected to the editor

Document context
The agent reads content and structure, navigates to relevant passages and uses that context for answers and edits.
Edits in the document
Changes appear in the editor, with change notifications and undo history. Users can inspect and undo edits.
Application-controlled AI
Your backend keeps credentials on the server and sends prompts and required document context to your provider. Model usage is billed separately.

JavaScript and TypeScript SDK

Programmatic access to the document

The SDK creates, reads, edits, renders and exports documents independently of the editor. Typed APIs cover paragraphs, tables, styles, sections, forms and review information.

The SDK supports the editor, Canvas viewer or your own interface. Node.js and HTTP entry points support backend and combined deployments. Server rendering and PDF export require Chrome or Chromium.

SDK API reference

Document operations

Creation and editing
Create or load Word documents, modify text, formatting and supported elements, and save as DOCX.
Templates and forms
Populate bindings, repeated sections, conditional content and images. Define fields, validate answers and extract structured results.
Content extraction
Read headings, paragraphs and tables as structured data or Markdown, without rendering. Source references link content to document locations.
Review and collaboration
Comments, revisions and comparisons, plus optional shared editing with presence and peer cursors through your own service.

Integration

One package for the editor

Editor includes the SDK and Canvas dependencies and works with plain JavaScript, React, Vue, Angular, Svelte and other frameworks.

This example creates a blank document with the ribbon. Your application handles storage, authentication and saving. Dispose the editor when removing its host.

Evaluation requires no account or license key. Rendered pages and PDF exports carry an evaluation watermark.

Editor integration guide
Terminal
npm install @onodocs/editor
main.js
import { createEditor } from "@onodocs/editor";
const host = document.createElement("div");
host.style.height = "80vh";
host.style.minHeight = "24rem";
document.body.append(host);
const editor = createEditor({ container: host });
await editor.newDocument();

Licensing

Commercial SDK, open-source editor UI

The editor UI has public MIT-licensed source. SDK, Canvas and Agent are commercially licensed. Production use of the embedded editor requires an OnoDocs license.

Per-application licenses include unlimited developers, end users and documents. Covered releases remain usable indefinitely, with one year of updates and email support. Renewal is optional.

Pricing and license scope

Evaluation and compatibility

Full SDK evaluation has no registration or time limit and includes a watermark. A 30-day watermark-free trial is available.

The compatibility guide covers supported Word features and limits for complex content, editing and exports. The editor above accepts your own documents.

Technical details

What runs in the browser, and what needs a backend?

Single-user loading, editing, rendering and export run in the browser. AI needs a model backend; shared editing needs a collaboration service. Backend processing is optional.

Which Word files are supported?

OnoDocs opens .docx, .docm, .dotx and .dotm without executing macros, and saves as DOCX. Older .doc and .dot files, RTF and PDF inputs are unsupported.

How are fonts handled?

Rendering uses available fonts or application-supplied files licensed for web distribution. Matching fonts helps preserve line breaks and pagination. See the font configuration guide.

What does PDF export preserve?

PDFs include searchable text, links, bookmarks and tagged structure for supported content. Graphics use vectors where possible; visible text is rasterized. PDF/UA certification is not claimed. See the export guide.