> 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/spreadsheet-editor/spreadsheet-editor.md).
# Spreadsheet Editor - Overview
Apryse Spreadsheet Editor delivers Excel-like XLSX editing in the browser—part of the Web SDK Office suite.
{% hint style="info" %}
**Requirements**
*These packages are required to use these features in production. Trial keys have unlimited access to all features*
Package: Spreadsheet EditorWeb SDKLive demo
{% endhint %}
Spreadsheet Editor is part of the Apryse Web SDK’s Office editing suite, offering client-side access to viewing and editing of spreadsheet files with a familiar, Excel-like interface. It provides developers a complete set of tools for embedding rich spreadsheet editing into their applications. Used alongside the [DOCX Editor](/web/docx-editor/docx-editor.md) and WebViewer’s [PDF editing capabilities ](/web/what-is-webviewer/overview.md), it completes a full set of in-app document editing capabilities for developers.
Spreadsheet Editor integrates easily into any JavaScript framework like React, Angular, Vue, Nuxt.js, or Next.js using a simple DOM element to host the component. It preserves the structure and integrity of template-based, compliance-intensive, and formula-driven content.
Using Spreadsheet Editor reduces reliance on third-party systems, multiple vendors, and file downloads for everyday spreadsheet tasks without compromising control, compliance, or security.
{% hint style="info" %}
The Spreadsheet Editor add-on is currently not supported on mobile browsers.
{% endhint %}
## How it works
When configured for Office editing, Spreadsheet Editor enables full creation and editing of Excel documents directly on the client side, performing all operations in memory. You can load XLSX, CSV, and XLS files from local storage or a remote URL, such as an AWS S3 bucket. When loading CSV and XLS files, the editor automatically converts these file types to XLSX. After editing, save your changes as an XLSX or PDF file.
Viewing capabilities include:
* Navigation mirrors spreadsheets in a standard grid format.
* View formulas within a cell and the calculated results.
* View/navigate across multiple sheets.
* Search across a workbook.
* View existing floating objects: standard charts, text boxes, shapes.
Editing capabilities include:
* Cut, copy, and paste content.
* Cell styling (text size, text color, font, background color, borders).
* Cell adjustments (insert + delete rows/columns, merge/unmerge cells, text wrapping).
* Cell formatting.
* Formula editing.
* Rename, add, or delete sheets.
* Insert images.
* Undo and redo actions.
* Search and replace across a workbook.
* View, edit, and save charts.
* Export files in XLSX or PDF format.
The following diagram includes all the default UI components structured in the Spreadsheet Editor.
## Get started
See our documentation on how to enable Spreadsheet Editor in your application that's been integrated with WebViewer.
* [Enable Spreadsheet editing in WebViewer](/web/spreadsheet-editor/basic-setup.md)
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.apryse.com/web/spreadsheet-editor/spreadsheet-editor.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.