Univer Office SDK: Embed Editable Spreadsheets and Docs in Your App
Official artwork from the Univer repository. An editable spreadsheet is a surprisingly large product feature. Once users can change cells, you inherit formulas, selection, undo and redo, copy and paste, keyboard navigat
Official artwork from the Univer repository.
An editable spreadsheet is a surprisingly large product feature. Once users can change cells, you inherit formulas, selection, undo and redo, copy and paste, keyboard navigation, formatting, persistence, and file compatibility. Building all of that from scratch is rarely a good use of an application team's time.
Univer is an open-source Office SDK that lets developers embed spreadsheet and document experiences into their own web products. It is worth watching because it is not just a static grid: its plugin architecture, application-facing APIs, and headless workflows make it possible to connect an editor to the rest of a product.
Why it is trending now
In the GitHub Trending TypeScript snapshot collected on November 16, 2026 at 06:57 UTC, dream-num/univer appeared at position one with 988 stars gained that day. That is a dated snapshot, not a promise about tomorrow's ranking. The project also tagged v1.5.1 on November 16. The preceding v1.5.0 release, published November 14, added dedicated chart sheets, stacked line charts, error bars, editable Board layout improvements, and formula-calculation memory improvements.
The useful signal is the combination of a current trending position and a fresh release with concrete editor capabilities. This is an established project gaining attention, not a brand-new repository.
What Univer actually provides
Univer is best understood as an application framework for office-like editing surfaces. Its open-source foundation includes Sheets and Docs functionality, while the wider product family and commercial packages cover additional workflows.
The architecture is modular:
- Presets assemble a useful set of plugins for a common editor configuration.
- Plugins provide capabilities such as rendering, formulas, sheets, documents, and UI.
- Facade APIs give application code a stable way to work with workbooks, worksheets, ranges, and commands.
- Commands and undo data let related features participate in one coherent edit history.
- Headless usage lets Node.js processes reuse content models and plugins without mounting the browser editor.
That last point matters. A product can use the same workbook model for a visible editor, an automated import job, a report generator, or an assistant that updates a value after a user approves the change.
Official Sheets preview from the Univer README.
Build a first spreadsheet
The current README quick start uses a bundler such as Vite and the Sheets Core preset. It requires a browser container with a height.
pnpm add @univerjs/presets @univerjs/preset-sheets-core
Add the editor container:
<div id="app" style="height: 100vh"></div>
Then initialize the preset:
import { UniverSheetsCorePreset } from '@univerjs/preset-sheets-core'
import UniverPresetSheetsCoreEnUS from '@univerjs/preset-sheets-core/locales/en-US'
import { createUniver, LocaleType, mergeLocales } from '@univerjs/presets'
import '@univerjs/preset-sheets-core/lib/index.css'
const { univerAPI } = createUniver({
locale: LocaleType.EN_US,
locales: {
[LocaleType.EN_US]: mergeLocales(UniverPresetSheetsCoreEnUS),
},
presets: [
UniverSheetsCorePreset({
container: 'app',
}),
],
})
univerAPI.createWorkbook({})
This creates an editable spreadsheet using the open-source packages. The application-facing API can then populate a range, read calculated values, or save a workbook snapshot. The official README demonstrates a quotation sheet with quantity, unit price, and formula-driven totals. It also shows how to wait for the formula engine's lifecycle stage before making edits.
Two implementation details are easy to miss:
- Keep coordinated
@univerjs/*packages on the same version. Mixing release lines is a common source of dependency and runtime problems. - In a React or Vue component, retain the instance returned by
createUniverand dispose it when the component unmounts. Do not initialize a new editor on every render.
The installation guide and lifecycle guide cover framework-specific setup.
Where it fits
Univer is a good candidate when editing is part of the product rather than a separate export step:
- A CRM can let sales teams edit quote assumptions and see totals recalculate.
- A finance product can provide a spreadsheet-like planning surface over application data.
- An education platform can let instructors create and update structured grade sheets.
- An operations tool can let users edit a workbook while application code validates and persists the result.
- An agent-enabled product can expose a narrow set of Facade operations after a human approves the proposed change.
The important design decision is to keep persistence and authorization in your application. A workbook snapshot is not a substitute for your database's access-control model.
Trade-offs and alternatives
Univer is not a drop-in Microsoft Excel replacement. A spreadsheet editor is only one part of office compatibility. Importing and exporting complex XLSX files, server-side collaboration, and some advanced capabilities are separate product areas or commercial packages. The open-source quick start explicitly does not require a commercial license or Server SDK, but that does not mean every product capability is included under the same terms.
The core repository uses Apache-2.0 licensing; review the license of each package you plan to ship, especially commercial extensions. Also check the API stability policy before depending on internal extension points.
Choose based on the job:
| Option | Better fit |
|---|---|
| Univer | An editable office surface with formulas, commands, plugins, and app integration |
| AG Grid | A high-performance data grid inside an application, not a full office editor |
| Handsontable | A spreadsheet-like grid when its commercial model and feature set fit |
| SheetJS | Reading, writing, and transforming spreadsheet files without building an interactive editor |
If you only need to generate an XLSX export, a file-processing library is simpler. If users need to work inside a rich spreadsheet UI, Univer is much more relevant.
Watch the SDK integration demo
The maintainers link to this integration walkthrough from the official README:
What to check before adopting it
Prototype the exact operations your users need: formulas, copy and paste, large sheets, keyboard navigation, persistence, import/export, and mobile behavior. Test the version you intend to deploy rather than relying on a demo. For v1.5.1, read the release page and the v1.5.0 notes before upgrading; the v1.5.1 tag itself does not provide a detailed change summary.
The project is also useful to study even if you do not adopt it. Its preset and plugin boundaries show how a complex editor can be assembled without forcing every application to load every feature.
Would you embed a spreadsheet directly in your product, or keep spreadsheet work in a separate tool and exchange files? Try the official demo and compare the integration cost with your current workflow.
Sources and further reading
- GitHub repository
- Official documentation
- GitHub Trending TypeScript snapshot
- v1.5.1 release
- v1.5.0 release notes
- Installation and lifecycle guides
Written by Shaswat Raj ยท LinkedIn ยท StackShade on YouTube
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes โ full credit and traffic to the original publisher.
