> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/web/release-notes/release-notes.md).
# Apryse Web SDK release notes
Explore Apryse Web SDK release notes for the latest updates to WebViewer, DOCX Editor, and Spreadsheet Editor, including new features, enhancements, and fixes.
## October 1, 2026
#### v12.2.0
This fall release expands built-in capabilities across the Apryse Web SDK while delivering faster performance in the workflows developers rely on most.
Highlighting now extends from WebViewer to DOCX Editor, while commenting is available in Spreadsheet Editor for the first time, bringing greater consistency to review workflows across editors. In addition, PDF editing, search and replace, and Architecture, Engineering, and Construction (AEC) workflows are optimized for faster, more responsive performance. These enhancements simplify development through a more consistent API experience across WebViewer, DOCX Editor, and Spreadsheet Editor, helping teams build richer document workflows with less custom code.
### WebViewer
#### Advanced stamp management and AEC workflow improvements
This release expands WebViewer's stamp capabilities and makes stamp libraries easier to manage at scale. Developers can now import PDF content as vector-based stamps, preserving fidelity across the PDF ecosystem and enabling the creation of reusable engineering and annotation symbol libraries without rasterization.
{% hint style="info" %}
**Availability:** Requires a WebViewer license and the [WebViewer Base Package](https://apryse.com/capabilities).
{% endhint %}
The stamp panel has also been redesigned to better support large collections. Custom and preset stamps are now separated, with search, filtering, and categorization tools that make it easier to find and organize stamps across projects. In addition, custom line and fill rendering, previously available only through APIs, is now exposed directly in the UI.
With these enhancements, developers can:
* Import PDF content as vector stamps while preserving PDF fidelity.
* Create and manage large stamp libraries with search, filtering, and categorization.
* Support vector, image, text, and raster-based stamps within the same workflow.
* Access custom line styles and fill patterns directly from the UI.
* Expose engineering-specific line types and hatch patterns for AEC workflows.
These improvements help AEC and engineering teams build richer markup workflows while reducing the need for custom implementations and workarounds.
For documentation details, see:
* [Configure PDF stamps with JavaScript](/web/annotation/stamps.md)
#### Faster PDF editing performance
This release improves the performance of PDF editing workflows powered by the `ContentEdit` APIs. Entering edit mode is quicker, typing is more responsive, and rapid editing operations are handled more consistently.
PDF editing is now faster and more responsive across common editing workflows. Improvements to the underlying `ContentEdit` APIs reduce startup overhead and streamline editing operations behind the scenes. As a result, entering edit mode is quicker, typing is more responsive, and rapid editing operations are handled more consistently.
{% hint style="info" %}
**Availability:** Requires a [WebViewer license](https://apryse.com/capabilities) and the [PDF Editing](https://apryse.com/capabilities#PDFEditing) add-on.
{% endhint %}
These optimizations deliver a faster, more responsive text and image editing experience while maintaining full compatibility with existing PDF editing workflows. No code changes are required.
With these enhancements, users can:
* Enter PDF editing mode faster.
* Edit text and images more responsively.
* Make rapid edits more reliably and consistently.
* Work more efficiently with large editing sessions.
The result is a faster, more responsive PDF editing experience that better matches the performance users expect throughout WebViewer.
For documentation details, see:
* [Edit text and images in PDFs using the WebViewer JavaScript library](/web/edit-page-content/text-edit.md)
#### Streamlined signing workflows
This release simplifies navigation between form fields in signing workflows, making it easier for users to move through documents and complete required actions.
{% hint style="info" %}
**Availability:** Requires a [WebViewer license](https://apryse.com/capabilities) and the [Digital Signature](https://apryse.com/capabilities#DigitalSignature) add-on.
{% endhint %}
Field navigation improvements reduce friction for teams building custom e-signature experiences on top of WebViewer. As more organizations bring signing workflows in-house, these enhancements provide a stronger foundation for guided signing experiences while maintaining full workflow control.
With these enhancements, developers can:
* Guide users through required signing fields more efficiently.
* Create smoother signing experiences with less custom navigation logic.
* Build custom e-signature workflows that are easier for end users to complete.
These improvements help organizations build streamlined signing experiences without relying on third-party e-signature platforms.
For documentation details, see:
* [Sign PDFs and manage signing workflows using JavaScript](/web/digital-signature/sign-pdf.md)
* [Use the digital signature tool in WebViewer](/web/digital-signature/signature-tool.md)
* [Work with PDF signature fields using JavaScript](/web/digital-signature/interacting-with-signature-field.md)
### DOCX Editor
#### Highlighting and faster search workflows
This release brings highlighting to DOCX Editor, extending another familiar WebViewer review capability across editors. Users can now highlight text using a dedicated toolbar tool and color palette without creating a full comment thread or tracked change.
{% hint style="info" %}
**Availability:** Requires a [WebViewer license](https://apryse.com/capabilities) and the [DOCX Editor](https://apryse.com/capabilities#DOCXEditor) add-on.
{% endhint %}
In addition, search and replace has been optimized to deliver better performance on long documents, making common editing and review workflows more responsive.
With these enhancements, users can:
* Highlight text using the same interaction pattern available in WebViewer.
* Flag content without opening a comment thread.
* Apply highlight colors consistent with Microsoft Word.
* Search and replace content more efficiently in large documents.
Together, these enhancements make DOCX Editor a more complete environment for review-heavy workflows while providing a more consistent experience across the Web SDK.
For documentation details, see:
* [Format text with DOCX Editor](/web/docx-editor/format-text.md)
* [DOCX Editor highlighting and shading FAQ](/web/get-started/faq/docx-editor-highlighting-and-shading-faq.md)
* [DOCX Editor search and replace FAQ](/web/get-started/faq/docx-editor-search-and-replace-faq.md)
* [Search and replace text within WebViewer, DOCX Editor, and Spreadsheet Editor](/web/search/search-replace.md)
### Spreadsheet Editor
#### Threaded comments for collaborative spreadsheet review
This release brings built-in commenting to Spreadsheet Editor, extending another core review capability across the Web SDK. Using the same Notes Panel already available in WebViewer and DOCX Editor, developers can now provide a consistent review experience across PDF, DOCX, and spreadsheet files.
{% hint style="info" %}
**Availability:** Requires a [WebViewer license](https://apryse.com/capabilities) and the [Spreadsheet Editor](https://apryse.com/capabilities#SpreadsheetEditor) add-on.
{% endhint %}
Comments and threaded replies can be attached directly to individual cells and managed through both the UI and API without modifying the underlying spreadsheet data. Existing workbook comments are preserved when files are opened in Spreadsheet Editor, including legacy Excel Notes, which automatically convert to threaded comments during import.
With these enhancements, developers can:
* Create, view, edit, and delete comments and threaded replies on spreadsheet cells.
* Access comments through the same Notes Panel used by WebViewer and DOCX Editor.
* Manage comments programmatically through a consistent API.
* Preserve existing workbook comments when importing spreadsheet files.
* Automatically convert legacy Excel Notes into threaded comments.
* Navigate directly to a commented cell from the Notes panel.
* Save comment changes back to the workbook.
These improvements eliminate the need for separate review experiences across file types and help maintain review context as content moves between applications. Teams can now provide a consistent commenting workflow across PDF, DOCX, and spreadsheet documents while preserving existing workbook feedback and collaboration history.
Comments also support review-heavy workflows where users need to provide feedback before finalizing a spreadsheet. By attaching discussions directly to cells and formulas, teams can validate calculations, flag sensitive data, and collaborate on spreadsheet content without altering the underlying document.
For documentation details, see:
* [Manage cell comments in Spreadsheet Editor](/web/spreadsheet-editor/manage-cell-comments.md)
To learn more about this release:
* View the [Changelog](/web/changelogs/v12-2-0.md) for more release information, including new APIs and bug fixes.
* Check [Downloads](/web/get-started/download.md) for the most recent versions of our products.
## July 8, 2026
#### v12.0
This summer release puts developers in control. New APIs expose core document capabilities directly to code, enabling applications to define how workflows behave and appear.
At the center are programmatic tracked changes in the DOCX Editor, which allow AI-suggested edits to flow in as tracked changes and be reviewed or resolved through a fully custom interface. WebViewer 12.0 reinforces this approach with a single unified UI and customization model, while the Spreadsheet Editor adds direct XLS/CSV support and API-driven chart interactions for greater control over data presentation.
### WebViewer
#### Unified UI and various platform improvements
This major release streamlines the WebViewer experience by retiring the [legacy UI](/web/ui-customization/legacy-ui/legacy-ui.md) and standardizing a single, unified customization framework with [Modular UI](/web/ui-customization/modular-ui/getting-started.md). Developers can use this [migration guide](/web/migration-guides/migrating-to-v11/migrating-to-v11-modular-ui.md) when transitioning existing implementations. By consolidating into a single supported UI platform, this release provides a clearer foundation for new integrations, reduces package size, and simplifies ongoing maintenance and customization.
{% hint style="info" %}
**Availability:** Requires a WebViewer license and the [WebViewer Base Package](https://apryse.com/capabilities).
{% endhint %}
To help teams transitioning from the legacy UI, this release also introduces a new `ToolGroupToggleButton` and Modular UI component that makes it easier to recreate a familiar legacy-style toolbar experience within Modular UI.
Alongside UI consolidation efforts, the release adds several highly requested enhancements, allowing developers to:
* Add date picker fields via the UI in the form builder mode.
* Customize annotation statuses in the comments panel via API, eliminating the need for UI forks.
* Automatically persist comments with autosave.
* Use multi-tab and multi-viewer modes in tandem for more flexible document workflows.
* Search and sort annotations by annotation numbering.
* Ensure XFDF stamp data aligns with the XFDF specification.
Finally, this release strengthens WebViewer’s security posture. The recommended Content Security Policy no longer requires `unsafe-inline` or `unsafe-eval`, making it easier to meet strict security standards.
We’ve further strengthened how we install and manage dependencies to better protect against supply chain risks, such as malicious package updates or compromised publishes. In practice, this means more predictable, locked-down installs in CI, verification of package sources, and tighter control over caches and lockfiles. The result is a more secure, consistent, and auditable build process.
For documentation details, see:
* [Migrating to V12 of WebViewer](/web/migration-guides/migrating-to-v12.md)
* [Migrating to Modular UI](/web/migration-guides/migrating-to-v11/migrating-to-v11-modular-ui.md)
* [Get started with WebViewer Modular UI](/web/ui-customization/modular-ui/getting-started.md)
### DOCX Editor
#### Programmatic tracked changes for DOCX Editor
This release introduces programmatic control over tracked changes in the DOCX Editor, enabling developers to manage change workflows entirely through code without relying on the editor UI.
{% hint style="info" %}
**Availability:** Requires a [WebViewer license](https://apryse.com/capabilities) and the [DOCX Editor](https://apryse.com/capabilities#DOCXEditor) add-on.
{% endhint %}
Previously, tracked changes were primarily driven through user interaction in the editor. With the new [TrackedChangeManager API](https://sdk.apryse.com/api/web/Core.Document.OfficeEditor.TrackedChangeManager.html), applications can now automate and scale document review workflows more effectively. Combined with newly exposed text navigation APIs and improved structured content handling, developers can build richer, more precise editing experiences. With these enhancements, developers can:
* Accept and reject tracked changes programmatically.
* Navigate to specific changes and retrieve change data directly from code.
* Improve reliability when copying and pasting structured document content.
These capabilities unlock automation scenarios such as AI-assisted review, batch document processing, and integration into larger document pipelines. Developers no longer need workarounds or custom forks to manipulate tracked changes at scale, enabling more streamlined and maintainable implementations.
While headless APIs in the market provide similar programmability, they often lack a full editing experience. Conversely, editor-first solutions typically limit programmatic access or require server-side components. This release brings both together, delivering deep programmability alongside Apryse’s high-fidelity, fully in-browser DOCX editing experience with no server dependency.
For documentation details, see:
* [Track changes with Apryse DOCX Editor](/web/docx-editor/docx-editor-tracked-changes.md)
* [Migrating to V12 of WebViewer](/web/migration-guides/migrating-to-v12.md)
### Spreadsheet Editor
#### Direct XLS/CSV file support and chart interactions
This release expands the Spreadsheet Editor’s capabilities by enabling direct loading of XLS and CSV files, with automatic conversion to XLSX on import while preserving the original file.
{% hint style="info" %}
**Availability**: Requires a [WebViewer license](https://apryse.com/capabilities) and the [Spreadsheet Editor](https://apryse.com/capabilities#SpreadsheetEditor) add-on.
{% endhint %}
Previously, spreadsheet workflows often required pre-processing to convert legacy XLS files or CSV exports into XLSX before use. The editor now handles this conversion seamlessly on load, simplifying integrations and reducing setup steps. In addition, chart interactions have been added to support in-browser manipulation via the UI or programmatically with the new APIs. With these updates, developers and users can:
* Open XLS and CSV files directly, with automatic conversion to XLSX on load.
* Export results as XLSX or PDF.
* Select, move, and resize charts directly in the browser.
* Leverage basic APIs for chart interaction to enable custom application workflows.
* Experience faster chart loading and improved responsiveness.
{% hint style="info" %}
**Limitations:** Saving back to XLS or CSV is not supported in this release. Chart creation, styling, and type changes are also not included.
{% endhint %}
These enhancements remove a key friction point in handling real-world spreadsheet data, which is often stored in CSV exports or legacy XLS formats. By eliminating the need for pre-conversion, developers can streamline ingestion pipelines and reduce integration complexity. At the same time, chart interactivity enables richer browser-based experiences for data-heavy applications, such as internal dashboards and document review tools.
For documentation details, see:
* [Spreadsheet Editor overview](/web/spreadsheet-editor/spreadsheet-editor.md)
* [Use view mode in Spreadsheet Editor](/web/spreadsheet-editor/view-mode.md)
* [Use edit mode in Spreadsheet Editor](/web/spreadsheet-editor/edit-mode.md)
* [Use charts in Spreadsheet Editor](/web/spreadsheet-editor/charts.md)
* [Listen to Spreadsheet Editor events](/web/spreadsheet-editor/events.md)
* [Migrating to V12 of WebViewer](/web/migration-guides/migrating-to-v12.md)
To learn more about this release:
* View the [Changelog](/web/changelogs/version-12/v12-0-0.md) for more release information, including new APIs and bug fixes.
* Check [Downloads](/web/get-started/download.md) for the most recent versions of our products.
## April 1, 2026
#### v11.12
This spring’s Web SDK update extends core review functionality across documents, text, and structured data. Enhanced side-by-side viewing support, newly added commenting in the DOCX Editor, and improved chart rendering within imported files in the Spreadsheet Editor enable users to compare, annotate, and refine content directly within their working environment.
### WebViewer
#### Enhanced side-by-side viewing
This release adds full editing capabilities to WebViewer’s multi-viewer mode, transforming it from a comparison‑focused tool into a fully interactive, side‑by‑side workspace.
{% hint style="info" %}
**Availability:** Requires a WebViewer license and the [WebViewer Base Package](https://apryse.com/capabilities).
{% endhint %}
Previously optimized for viewing and comparing multiple documents, multi-viewer mode now includes the complete set of WebViewer PDF editing tools across all supported file types. With enhanced side-by-side viewing, users can:
* Edit multiple documents directly within a single view.
* Set permissions independently across each viewer.
* Apply changes to PDFs, images, Microsoft Office documents, and more.
* Work with each document independently or simultaneously, consistent with standard WebViewer interactions.
These enhancements streamline key multi-document workflows by enabling users to review, compare, and edit content without switching contexts. Editing no longer interrupts comparisons, and users gain efficiency by remaining in a single workspace.
Since the [Compare](https://apryse.com/capabilities#Compare) add-on is powered by the multi-viewer, the latest enhancements further elevate and streamline Compare’s workflows, resulting in a more fluid and feature‑rich side‑by‑side review experience there as well.
For documentation details, see:
* [View Documents Side-by-side](/web/ui-customization/multi-viewer-mode.md)
* [Semantic Text Compare](/web/compare-files/semantic.md)
### DOCX Editor
#### Expanded review and approval with comment support
The DOCX Editor now supports comments, giving permission‑based users a way to provide contextual feedback directly within DOCX files.
{% hint style="info" %}
**Availability:** Requires a [WebViewer license](https://apryse.com/capabilities) and the [DOCX Editor](https://apryse.com/capabilities#DOCXEditor) add-on.
{% endhint %}
Comments work alongside tracked changes and approvals, enabling teams to collaborate without making direct edits to the document. With this new comment support, users can:
* Import existing comments from DOCX files.
* Add, edit, and delete comments while collaborating.
* Apply role‑based permissions for comment visibility and management.
Comment permissions mirror standard WebViewer [AnnotationManager permissions](/web/annotation/annotationmanager/permissions.md) for consistency and ease of use. The following table summarizes the details.
| **User** | **Permission** |
| -------------- | ----------------------------------------------------------------------------- |
| Read-only user | View all comments. |
| Standard user | Create comments and manage their own comment threads. |
| Admin user | Manage all comments, including editing or deleting threads created by others. |
This update supports review workflows that require feedback without altering content, adds clarity to suggested changes, and aligns DOCX Editor interactions with familiar WebViewer annotation UI patterns.
For documentation details, see:
* [DOCX Editor Overview](/web/docx-editor/docx-editor.md)
#### **Strikethrough formatting support**
In addition to comment support, this release introduces new strikethrough formatting capabilities in the DOCX Editor. Users can now apply strikethrough to text using either toolbar controls or keyboard shortcuts.
{% hint style="info" %}
**Availability:** Requires a [WebViewer license](https://apryse.com/capabilities) and the [DOCX Editor](https://apryse.com/capabilities#DOCXEditor) add-on.
{% endhint %}
With this enhancement, users can:
* Apply or remove strikethrough using `Ctrl/Cmd + S`.
* Click the new strikethrough icon in the toolbar to toggle the formatting.
* Use strikethrough to visually indicate content that is outdated, revised, or suggested for removal without deleting text.
This update expands the editor’s formatting toolkit and helps teams communicate edits and revisions more clearly during collaborative review workflows.
### Spreadsheet Editor
#### Native chart rendering and editing
The latest update adds support for XLSX files containing charts, including viewing, editing values, and saving changes in-app when using the Spreadsheet Editor add-on.
{% hint style="info" %}
**Availability:** Requires a [WebViewer license](https://apryse.com/capabilities) and the [Spreadsheet Editor](https://apryse.com/capabilities#SpreadsheetEditor) add-on.
{% endhint %}
The Spreadsheet Editor now renders existing standard charts from imported XLSX files with full fidelity. Once a spreadsheet is uploaded, users can modify associated cell data. All chart updates are preserved when the file is exported, ensuring no loss of formatting or configuration upon saving or sharing. With in‑app chart support, users can:
* View spreadsheet data and charts together in the same workspace.
* Modify chart data without switching applications.
* Maintain chart fidelity when exporting, sharing, or reusing spreadsheets in other systems.
For documentation details, see:
* [Spreadsheet Editor Charts](/web/spreadsheet-editor/charts.md)
To learn more about this release:
* View the [Changelog](/web/changelogs/version-11/v11-12-0.md) for more release information, including new APIs and bug fixes.
* Check [Downloads](/web/get-started/download.md) for the most recent versions of our products.
## January 7, 2026
#### v11.10
DOCX Editor now offers Input Method Editor (IME) keyboard support for documents to extend our existing IME support for search input and file name fields. IME allows users to enter complex characters and symbols, such as those used in Chinese, Japanese, and Korean languages, using a standard keyboard.
### DOCX Editor
#### Additional IME keyboard support for documents
We’re excited to announce IME keyboard support for Chinese, Japanese, and Korean languages for documents in our [DOCX Editor](/web/docx-editor/docx-editor.md). To use, [enable IME](/web/docx-editor/edit-docx-file.md#ime-keyboard-support) and select your preferred OS-level keyboard for input.
{% hint style="info" %}
**Availability:** Requires a [WebViewer license](https://apryse.com/capabilities) and the [DOCX Editor add-on](https://apryse.com/capabilities#DOCXEditor).
{% endhint %}
The benefits of using this feature include:
* You can type Chinese, Japanese, and Korean (CJK) naturally using OS keyboards and IMEs.
* Prevents garbled text, duplicated characters, or broken composition caused by improper IME handling.
* Reduces friction when switching between Latin and CJK input modes or mixed-language documents.
* Preserves typographic features like proper line breaking and word boundaries used by CJK workflows.
* Makes the editor usable for global teams in China, Japan, Korea, and CJK users anywhere Windows is used.
* Brings Windows behavior in line with macOS (where IME often “just works”), avoiding platform-specific bugs and support tickets.
* You can move between OSs without relearning input behavior.
* Properly handles IME candidate windows, caret positioning, and focus changes.
See the following documentation for developing this feature:
* [Enable DOCX Editing](/web/docx-editor/edit-docx-file.md)
* [Enable IME Keyboard Support](/web/docx-editor/edit-docx-file.md#ime-keyboard-support)
See our [latest Changelog](/web/changelogs/version-11/v11-10/v11-10-0.md) for more WebViewer release information, including new APIs and bug fixes.
Visit our [downloads page](/web/get-started/download.md) to access the latest versions of our products and get the latest features and functionality.
## October 8, 2025
#### v11.8.0
With the Fall release, WebViewer continues to deliver an increasingly consistent user experience across formats and expands out-of-the-box market coverage. All right-to-left (RTL) content is supported in WebViewer. Also, developers can quickly accommodate new global markets by providing localized, RTL viewing and document editing in the UI for Arabic, Hebrew, Persian, and Urdu.
Additionally, the DOCX and Spreadsheet Editors include new features so teams can work across document types efficiently. Review and collaboration are simpler with search and replace for the DOCX Editor and Spreadsheet Editor via the UI or programmatically with the new APIs.
From programmatic automation to in-editor precision tools to global-ready language support, we’re making editing better with every release.
### WebViewer
#### Right-to-Left (RTL) viewing and editing
Until now, content in RTL languages was difficult to handle because PDFs lack implicit text direction. Developers often had to build custom workarounds that still produced issues like reversed character order, inaccurate search results, or broken copy/paste.
{% hint style="info" %}
**Availability:** Requires a WebViewer license and the [WebViewer Base Package](https://apryse.com/capabilities).
{% endhint %}
We’ve now expanded the document viewing and editing experiences in WebViewer, including UI localization for Arabic, Hebrew, Persian, and Urdu, without additional engineering overhead. All other RTL languages benefit from these improvements as well.
Capabilities for RTL include:
* Modular UI RTL layout
* Arabic, Hebrew, Persian, and Urdu language localization in UI Natural Text Selection
* Improved Copy/Paste
* Search
* Both PDF and Office Viewing
* Consistent Page Manipulation
Benefits include:
* RTL users can interact with documents naturally.
* Reduces user frustration.
* Increases product usage and value.
* The correct character order, copy/paste, and search functionality are upheld.
* Text selection and highlighting are accurate.
* Content meaning and context are preserved.
* Eliminates the need for third-party tools and workarounds for developers.
See the following new documentation for developing these features:
* [RTL Language Support Overview](/web/ui-customization/localization/rtl-language-support.md)
* [RTL Language Support in DocumentViewer](/web/documentviewer/rtl-support.md)
### DOCX Editor
#### Programmatic text editing and in-editor search and replace
DOCX Editor now offers APIs for programmatic text editing and a new in-editor Search & Replace panel, giving developers the ability to automate bulk updates and end users the ability to make quick, precise changes to content.
{% hint style="info" %}
**Availability:** Requires a [WebViewer license](https://apryse.com/capabilities) and the [DOCX Editor](https://apryse.com/capabilities#DOCXEditor) add-on.
{% endhint %}
You can now automate structured updates like placeholder replacements, bulk corrections, or sensitive text removal, minimizing manual effort when generating or standardizing documents. With programmatic text editing through our APIs:
* Insert, delete, or replace text.
* Preserve existing document formatting, styles, and layout.
You can now enable fast, user-driven editing tasks directly within the editor during the document editing process. With UI search and replace:
* Use the new search and replace panel in the main menu of the UI.
* Replace a single instance or all instances of a word or phrase.
* Access search and replace by keyboard shortcut, if you prefer.
Benefits include:
* Faster updates due to programmatic text editing, keyboard shortcuts, and search and replace all.
* Every matching term, placeholder, or name is updated the same way throughout the file.
* Updates are made with awareness of DOCX formatting.
* Eliminates the need to manually review each section for missed or inconsistent changes.
See the following new documentation for developing these features:
* [Overview of Search in WebViewer, DOCX Editor, and Spreadsheet Editor](/web/search/search.md)
* [Search Text in WebViewer, DOCX Editor, and Spreadsheet Editor](/web/search/text-search.md)
* [Search and Replace Text within WebViewer, DOCX Editor, and Spreadsheet Editor](/web/search/search-replace.md)
* [APIs for Searching Text](/web/search/search-api.md)
### Spreadsheet Editor
Spreadsheet Editor introduces search and replace across cells, sheets, and workbooks, with support for regex, case sensitivity, and programmatic APIs.
{% hint style="info" %}
**Availability**: Requires a [WebViewer license](https://apryse.com/capabilities) and the [Spreadsheet Editor](https://apryse.com/capabilities#SpreadsheetEditor) add-on.
{% endhint %}
This release also adds:
* Undo/redo buttons.
* Image insertion.
* Keyboard shortcuts for a faster, more familiar editing experience.
With search and replace, you can:
* Search and replace text or numbers across all sheets in a workbook.
* Use advanced search options like regex and case-sensitive.
* See search results clearly in a panel and identified throughout the sheet.
* Move through results easily using next/previous.
* Replace one or all results at once.
* Use new APIs to run search and replace programmatically, especially for bulk updates.
Benefits include:
* Quick review of results identified in a sheet, or in the summary panel to see what’s being changed before committing to a replacement.
* Use Programmatic search and replace across large datasets using our APIs.
* Faster updates due to programmatic text editing and search and replace all.
* Every matching term, placeholder, or name is updated the same way throughout the file.
* Eliminates the need to manually review hundreds or thousands of rows that can result in missed or inconsistent changes.
See the following new documentation for developing these features:
* [Spreadsheet Editor Edit Mode](/web/spreadsheet-editor/edit-mode.md)
* [Overview of Search in WebViewer, DOCX Editor, and Spreadsheet Editor](/web/search/search.md)
* [Search Text in WebViewer, DOCX Editor, and Spreadsheet Editor](/web/search/text-search.md)
* [Search and Replace Text within WebViewer, DOCX Editor, and Spreadsheet Editor](/web/search/search-replace.md)
* [APIs for Searching Text](/web/search/search-api.md)
See our [latest changelog](broken://pages/4lIc3gW9ydcm06mY4pgg) for more WebViewer release information, including new APIs and bug fixes.
Visit our [downloads page](/web/get-started/download.md) to access the latest versions of our products and get the latest features and functionality.
## July 9, 2025
#### v11.6.0
In this release, we’ve extended editing and layout controls for DOCX Editor and Spreadsheet Editor, both add-ons to the Web SDK, bringing more sophisticated formatting, styling, and cell-level control into a single, browser-based experience. It’s a step forward in keeping users focused and productive within your application.
Our modular UI now meets WCAG 2.2 AA standards across WebViewer, DOCX Editor, and Spreadsheet Editor. This ensures your applications are accessible to users with motor or visual impairments, without requiring additional development effort.
### Spreadsheet Editor
#### Editing mode functionality
The Spreadsheet Editor interface uses an Excel-like layout users are used to seeing so it’s intuitive and easy to use. Building on our View Mode launch, Spreadsheet Editor now has edit mode functionality users can use for:
* **Cell Formatting**: Modify text size and color, fonts, border styles, cell colors, border colors, and text styling for bold, italic, underline, and strikethrough.
* **Formula and Function Support:** Execute standard mathematical operations, statistical calculations, date/time functions, and other common formulas.
* **Dynamic Data Manipulation:** Easily add, edit, and delete rows and columns. Seamlessly cut, copy, and paste data.
* **Cell Adjustments:** Merge cells and preserve formatting.
* **File Support:** Open and export files in .xlsx format.
{% hint style="info" %}
**Availability**: Requires a [WebViewer license](https://apryse.com/capabilities) and the [Spreadsheet Editor](https://apryse.com/capabilities#SpreadsheetEditor) add-on.
{% endhint %}
Editing capabilities in Spreadsheet Editor reduce reliance on third-party systems, multiple vendors, and file downloads for everyday spreadsheet tasks without compromising control, compliance, or security. Teams can format and calculate spreadsheet data directly, all with a similar look and feel to how they manipulate PDFs and DOCX files.
See the following new documentation for developing these features:
* [Spreadsheet Editor overview guide](/web/spreadsheet-editor/spreadsheet-editor.md)
* [Spreadsheet Editor basic setup guide](/web/spreadsheet-editor/basic-setup.md)
* [Spreadsheet Editor view mode guide](/web/spreadsheet-editor/view-mode.md)
* [Spreadsheet Editor edit mode guide](/web/spreadsheet-editor/edit-mode.md)
### DOCX Editor
#### Layout editing support
DOCX Editor now has a new layout tab users can use for:
* **Margin Editing**: Adjust the top, bottom, left, and right margins of a document’s body on a section-by-section basis. The Margin menu offers standard preset values, and you can also set custom values within it.
* **Column Page Layout Editing**: Adjust the number of columns and their width and spacing. You can apply the configurations you set to each section. You can also set uneven columns through custom settings.
Now, you can make more complex documents that jump from one section to the next with different layouts. DOCX Editor preserves text flow and section logic to ensure documents remain true to their original form, no matter how complex the layout.
{% hint style="info" %}
**Availability:** Requires a [WebViewer license](https://apryse.com/capabilities) and the [DOCX Editor](https://apryse.com/capabilities#DOCXEditor) add-on.
{% endhint %}
The benefits of margin and column editing include:
* Professional formatting and branding across documents, from proposals to reports.
* Compliance with legal and industry standards, especially for industries like legal, education, and government that often have strict formatting guidelines.
* Text that isn’t cramped and has enough white space around content, improving overall readability.
* More balanced, organized document layout.
DOCX Editor eliminates dependency on using other apps and file downloads without compromising security, control, or compliance. Companies can format and write directly within the same interface they’re already using for PDF files.
### Accessibility updates
Our modular UI now meets WCAG 2.2 AA standards across WebViewer PDF Editor, DOCX Editor, and Spreadsheet Editor, which ensures your applications are accessible to those with motor impairments, visual limitations, or cognitive disabilities without requiring additional development effort.
Here’s everything you get for a consistent, accessible UI with default behavior that enables developers to embed accessible in-browser document experiences without needing to build a custom solution from scratch:
| **Accessibility Category** | **Apryse Product Feature** |
| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Visual Accessibility | High Contrast Ratios: Text and UI meet or exceed 4.5:2 contrast ratios.
Screen Reader Compatibility: NVDA, VoiceOver, and JAWS supported with ARIA labels and semantic structure.
|
| Motor Accessibility | Full Keyboard Navigation: From UI interactions to page navigation, every action is accessible via keyboard, with logical tab order and visible focus indicators.
ARIA Role Support: Interactive UI elements are semantically correct or mapped to appropriate ARIA roles for better operability.
|
| Cognitive Accessibility | Predictable Layouts and Actions: Toolbar and menu structures remain consistent across sessions.
Focus Management: Modals, menus, and form inputs automatically redirect focus, which helps users stay oriented.
|
| Developer Assistive Tools | **Modular UI Framework:** Allows teams to customize UI while retaining accessibility. |
On June 28, 2025, the European Accessibility Act made effective the requirement that digital products and services comply with WCAG 2.1 AA standards [for certain industries](https://www.levelaccess.com/compliance-overview/european-accessibility-act-eaa/). Our accessibility update exceeds the WCAG 2.1 AA baseline.
We recommend that customers review their usage of our Web SDK solutions to ensure that their own applications remain compliant. Product and accessibility teams should test against the updated criteria and are encouraged to [contact us](https://apryse.com/support) with any questions or concerns.
See our [latest Changelog ](broken://pages/4lIc3gW9ydcm06mY4pgg)for more WebViewer release information, including new APIs and bug fixes.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.apryse.com/web/release-notes/release-notes.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.