Univer 1.0: Six Editors, One Programmable Office SDK

Hey, developers! We've been working on this major release since April 2026. Today, we're ready to share it with you: Univer 1.0 is here.

The Univer Team started with spreadsheets and has focused on helping builders create the office editing experience they need within their own applications.

Over the past few months, improvements have focused on scrolling and calculation in large spreadsheets, pagination in long documents, rendering complex canvases, and preserving formatting and content when importing Office files.

This release includes Univer Docs and Univer Slides, which we promised from the start, as well as three previously unannounced editors: Univer Boards, Univer Bases, and Univer PDFs. Together with the continued development of Univer Sheets, these six editors cover spreadsheets, documents, presentations, whiteboards, structured data, and PDFs. You can integrate them into your product through a single SDK.

The editors share Univer's plugin and command systems, with Facade APIs for each type of content. Applications can combine the editors they need while using their own navigation, user accounts, and business data.

Try the editors in Univer Office, or follow the getting started guides to integrate them into your project.

What's new

If you're coming from 0.25, here's an overview of the main changes:

EditorWhat's changed in 1.0
Sheets · SpreadsheetsA reorganized formula engine, better Excel calculation compatibility and large spreadsheet performance, cross-workbook references, shapes linked to formulas, PivotCharts, and expanded pivot table and chart capabilities.
Docs · DocumentsBetter section and page layout in traditional mode, more columns and content blocks in modern mode, and support for tables of contents, footnotes, content controls, and formulas.
Slides · PresentationsRebuilt editing capabilities, with expanded support for masters and layouts, charts, tables, SmartArt, presenting, and file exchange.
Boards · WhiteboardsA new freeform canvas with shapes, connectors, mind maps, tables, charts, and Mermaid import.
Bases · Structured dataA new workspace built around fields and records, with multiple views, linked records, formulas, pivot views, and dashboards.
PDFs · PDF filesA new PDF viewer and editor with page management, text, tables, images, annotations, import, and export.

Univer Sheets

We reorganized the formula engine, bringing formula registration and calculation scheduling into a shared module used by Sheets, Bases, inline formulas in Docs, and shapes linked to formulas. Sheets also improves incremental calculation and shared formula lookup to reduce repeated calculations after cell edits.

Version 1.0 improves the handling of structured references, array formulas, implicit intersection, and Excel date systems to reduce differences in calculation results after importing workbooks. New 3D references can aggregate data across consecutive worksheets. For example, =SUM(Jan:Mar!B2) sums cell B2 across every worksheet from Jan through Mar in workbook order.

Formulas can now reference data in other workbooks. Once the source workbook is loaded in the same calculation environment, a summary sheet can calculate sales totals from Sales.xlsx:

text
=SUM('[Sales.xlsx]Data'!B2:B100)

Applications can also bind a source to a stable document ID. See cross-workbook references for details.

Shapes on a worksheet can be linked to formulas. For example, a shape can display total sales using =SUM(B2:B100). Its displayed result updates when the data changes and the formula recalculates. Shapes and connectors also respond to changes in the row and column structure, adjusting their positions and sizes according to their anchor settings.

Pivot tables gain date grouping, more layouts, and additional ways to show values, including percentages, differences, and running totals. New PivotCharts share field, filter, and sort settings with their linked pivot tables and update as the report's dimensions change.

For example, a sales report can aggregate data by month and region, show each region's percentage of the total, and display the results in a PivotChart.

Chart updates cover histograms, treemaps, sunburst charts, and gauge charts, along with multilevel category axes, control over hidden data, and SVG export. These features use a shared chart engine across the editors. Learn more in the chart guide.

Edit source data and charts in the same worksheet.Try the demo ↗

Univer Docs

Docs offers modern mode and traditional mode.

Modern mode is suited to knowledge bases, project notes, and online collaboration. Content flows down a continuous page without paper-based pagination. Combine text, images, and tables with columns and callouts to build product comparisons, guides, and team handbooks.

Modern mode: columns and comparison tables on a continuous page.Try the demo ↗

Traditional mode is suited to reports, contracts, and printed documents. Sections, headers and footers, and pagination controls let you set up different page layouts for individual sections. A table of contents generates entries from headings and updates page numbers, while footnotes and endnotes hold references and explanations. Tables spanning multiple pages, list numbering, and text and image layout have also been improved.

Traditional mode: arrange formal documents using pages, margins, and pagination.Try the demo ↗

New content controls support text, checkboxes, dates, lists, and repeating sections. You can mark fields in business templates, control which content is editable, or let users add repeated line items while preserving the rest of the template.

Docs also adds LaTeX math expressions and inline formulas that can be calculated. Find and replace, word count, outline navigation, and paste formatting options have also been improved.

Integrate Exchange to import and export DOCX files.

Univer Slides

We reworked the Slides editing workflow: create pages, apply masters and layouts, edit text and shapes, insert tables and charts, and start presenting. Alignment guides, layer controls, and editable SmartArt are also part of the editing tools.

The same content can be created and modified through Facade APIs. For example, an application can generate a presentation from sales data, let users adjust the text and layout, and then export it as PPTX through the file conversion service.

Edit the text, images, and page layouts of a brand pitch in Slides.Try the demo ↗

Univer Boards

Boards provides a freeform canvas for flowcharts, architecture diagrams, mind maps, and discussions. Use shapes and connectors to describe relationships, organize content in containers, or import existing Mermaid diagrams and continue editing them on the canvas.

Map the steps and responsibilities of equipment lending with shapes and connectors.Try the demo ↗

Univer Bases

Bases is built for structured data that changes over time. The same set of project tasks can be entered in a grid, organized by status on a kanban board, or scheduled in a calendar or Gantt view. Views share the same records. Linked records and record hierarchies describe relationships, while pivot views and dashboards summarize the data.

Tickets grouped by status, with linked customer records and work logs.Try the demo ↗

Univer PDFs

PDFs supports viewing and editing PDFs, managing pages, and adding text, images, tables, and annotations, with export and printing options. The imported source document and editing data are stored separately.

See the PDF editing guide for features and integration details.

Embedding and editing across documents

Version 1.0 supports embedding one type of Univer document inside another while retaining its native editing capabilities. For example, users can still edit cells and enter formulas in Sheets embedded in a Docs document. A board embedded in a Slides page also retains its shape and connector editing tools.

Embedded documents can also appear in workbook tabs, slide page lists, or the table lists in Bases. For example, you can add a Docs tab to a workbook to write notes about a report. Switching to that tab makes the Docs menus and editing tools available.

Embedded documents are linked to their hosts by reference. Each keeps its own data model and is saved separately by the application. See the embedding guide for supported locations, editor combinations, and integration details.

Mobile editing for touchscreens

Mobile support in 1.0 covers Sheets, Docs, Slides, Boards, and Bases. Toolbars, property panels, and content navigation have been reorganized for smaller screens, with updates to touch gestures and layout behavior when the on-screen keyboard opens.

  • Sheets: Improved cell selection, editing, and formula input, with mobile panels for advanced features such as charts and pivot tables.
  • Docs: Touch text selection, pinch-to-zoom, and mobile formatting tools, plus mobile interfaces for images, links, and comments.
  • Slides: A page list, canvas editing, and mobile presentation mode, with tap and swipe gestures for moving between slides.
  • Boards: Drag and pinch gestures to pan and zoom the canvas, with bottom panels for inserting and configuring shapes, connectors, and other objects.
  • Bases: Navigation organized around editing records and switching tables and views, with touch-friendly field inputs, filters, and sorting panels.

Use each editor's mobile UI plugins when integrating these interfaces. Desktop and mobile editors use the same data models.

Performance improvements

Sheets reduces repeated rendering and calculation. Scrolling reuses the existing image and incrementally draws areas entering the viewport. Bulk paste and formula updates also do less repeated work. Improvements to incremental calculation and shared formula lookup help limit recalculation to the data affected by an edit.

Docs prioritizes the content being read and edited. Long documents can be laid out progressively, starting with pages near the current editing position before continuing with the rest. Local edits reuse existing layout results where possible. Applications can also configure a layout Worker to move layout processing to a background thread.

Boards and Slides reduce unnecessary updates in complex canvases. Improvements cover large scenes, rendering during dragging, and shape cache reuse. Presentation thumbnails are also scheduled for updates based on visibility.

Other UI improvements include the Ribbon layout, dark themes, and RTL support. Comments, permissions, and version history now cover more editors, and snapshot comparison APIs help applications show differences between revisions.

Office file compatibility

Exchange in the Server SDK imports XLS / XLSX spreadsheets, DOC / DOCX documents, and PPT / PPTX presentations. After editing, they can be exported as XLSX, DOCX, and PPTX respectively. Spreadsheets also support CSV and TSV import and export.

Compatibility improvements include:

  • Spreadsheets: Better handling of Excel date systems, formula caches, and references, along with improved chart, pivot table, and formula compatibility.
  • Documents: Improvements to sections, pagination, list numbering, borders, and text and image layout.
  • Presentations: Better preservation and editing of PPTX text, shapes, backgrounds, and charts.

File conversion can also run directly in Node.js for batch processing and background jobs. See the Server SDK file conversion guide and the import and export guides for Sheets, Docs, and Slides.

Univer Office SDK: Easier integration

Working with the Web SDK has shown us how much flexibility a plugin architecture brings to frontend integration. This release introduces the Server SDK and AI SDK to bring that extensibility to backend modules and agents within your product, so they can be adapted to your application's requirements.

SDKRole in your application
Web SDKEmbed editors in your interface and connect them to your application through plugins, themes, and Facade APIs.
Server SDKIntegrate collaboration and file conversion with your backend, using your existing identity, permissions, storage, and deployment setup.
AI SDKProvides TypeScript capabilities for building an Office CLI, allowing agents and automation to read, modify, and inspect content.

In a reporting application, the Server SDK handles Excel file conversion while the Web SDK provides the spreadsheet editor. Agents within the product use the AI SDK to read data, update formulas, generate charts, and perform visual inspections of the results.

Upgrading from 0.25

Maintenance policy for 0.25

The 0.25 series will receive security updates only, for one year from the release of Univer 1.0. Upgrade to 1.0 for new features and other improvements.

Version 1.0 includes API cleanup and package changes. When upgrading an existing project, start by checking these areas:

  1. Runtime requirements and build formats. The Web SDK compilation target has moved from Chrome 70 to Chrome 88. The supported baseline is Chrome / Edge 88, Firefox 90, Safari 14.1, and Electron 12. Presets no longer include UMD builds, so projects loading them through script tags need to switch to a module-based build.
  2. Legacy Facade calls. Deprecated APIs have been removed. For example, replace createUniverSheet(), getActiveUniverSheet(), and getUniverSheet() with createWorkbook(), getActiveWorkbook(), and getWorkbook() respectively. Migrate legacy event hooks to addEvent().
  3. Import and export. Exchange APIs are now separated by product. For example, spreadsheet imports use importSheetToSnapshotAsync() from @univerjs-pro/sheets-exchange-client/facade in place of importXLSXToSnapshotAsync(). Check plugin registration and service configuration as well. See the import and export guide.
  4. Advanced features and custom extensions. Facade APIs for Docs, charts, and shapes have changed. Version history now combines shared modules with product plugins, and some formula services and types have moved to engine-formula. Projects that register plugins manually or use lower-level services should check imports, parameters, and return values against the current feature guides and API reference.
  5. Custom code execution. Uniscript has been removed. Custom formula registration no longer supports sending function source code over RPC and deserializing it remotely. Trusted functions needed in a Worker should be deployed with the Worker code and registered in the environment where they run.

Keep the versions of interdependent Univer packages aligned, then use representative documents to check editing, saving, undo, import and export, and collaboration. Projects using a single editor can continue to install only the features they need.

Start building

Thank you to everyone who contributed code, reported issues, improved the documentation, and shared feedback. Your input helped shape the features in this release.

Join us on GitHub. We look forward to seeing what you build with Univer 1.0.

© 2026 DreamNum Co., Ltd.