> 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/docx-editor/docx-editor.md).

# Apryse DOCX Editor Overview

Embed native Word editing into your app with Apryse DOCX Editor—part of the Web SDK Office suite. Supports JavaScript frameworks like React, Angular, Vue, Nuxt.js, or Next.js.

{% hint style="info" %}
**Requirements**

*These packages are required to use these features in production. Trial keys have unlimited access to all features*

<a href="https://apryse.com/capabilities#DOCXEditor" class="button primary">Package: DOCX Editor</a><a href="/web/get-started/readme.md" class="button primary">Web SDK</a><a href="https://showcase.apryse.com/office-editor" class="button primary">Live demo</a>
{% endhint %}

The DOCX Editor is an add-on to the Apryse Web SDK, enabling native in-browser and desktop editing of Word documents. Combined with WebViewer’s [PDF editing capabilities ](/web/what-is-webviewer/overview.md)and the [Spreadsheet Editor](/web/spreadsheet-editor/spreadsheet-editor.md), it gives developers a complete set of tools for embedding rich document editing into their applications.

The DOCX Editor integrates easily with JavaScript frameworks like React, Angular, Vue, Nuxt.js, or Next.js, using a simple DOM element to host the component and supports document creation, editing, and review workflows without third-party dependencies.

{% hint style="info" %}
The DOCX Editor add-on is currently not supported on mobile browsers.
{% endhint %}

DOCX Editor eliminates dependency on using other apps and file downloads without compromising security, control, or compliance. You can format and write directly within the same interface you're already using for PDF files.

## Overview video

See the functionality DOCX Editor offers in our DOCX Editor Overview video.

{% embed url="<https://www.youtube.com/embed/QrmJQgbkxJs?si=RWTv04Xuv34uznH9>" %}
An overview of DOCX Editor
{% endembed %}

## How It Works

The Apryse DOCX Editor is an add-on component of WebViewer, to the Apryse Web SDK. When configured for Office editing, it enables full creation and editing of Word documents directly on the client side, performing all operations in memory. You can load DOCX files from local storage or a remote URL, such as an AWS S3 bucket, and save your changes as a DOCX file after editing.

Editing capabilities include:

* Font and text formatting.
* Viewing, Reviewing, and Editing toggle.
* Paragraph alignment.
* Margin and column formatting.
* Break, table, and image insertion.
* Search and replace.
* Comments, giving permission‑based users a way to provide contextual feedback directly within DOCX files, enabling teams to collaborate without making direct edits to the document.

<figure><img src="https://3532544125-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX9YnTSKIHvV7m0A36LbO%2Fuploads%2Fgit-blob-0b82f2cb2b6ab6d278d90d4a98e51ec28e5ea2fb%2Fa2bdfcedee8daad9e68862715ec881dc355df921-1440x1064.png?alt=media" alt="The Home ribbon for the DOCX Editor"><figcaption><p>The Home ribbon for DOCX Editor</p></figcaption></figure>

<figure><img src="https://3532544125-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX9YnTSKIHvV7m0A36LbO%2Fuploads%2Fgit-blob-d6049aedd4f6e040b6222cf90d9bc50a321a0324%2F2cbb06685384143d82278b5e6c837860776dc2ee-1440x1064.png?alt=media" alt="The layout ribbon of DOCX Editor"><figcaption><p>The Layout ribbon for DOCX Editor</p></figcaption></figure>

<figure><img src="https://3532544125-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX9YnTSKIHvV7m0A36LbO%2Fuploads%2Fgit-blob-58bab4316435d0eb8639d9fac754d3f1dd18b2ee%2F0c379a98f46652967b84cbad0fcedf668e1f84c9-1440x1064.png?alt=media" alt="The Insert ribbon for DOCX Editor"><figcaption><p>The Insert ribbon for DOCX Editor</p></figcaption></figure>

## Get Started

See our documentation on how to enable DOCX Editor in your application that's been integrated with WebViewer.

* [Enable DOCX Editing in WebViewer](/web/docx-editor/edit-docx-file.md)

## Related Resources

* [How to Embed DOCX Editor in React Using Apryse WebViewer](https://www.youtube.com/watch?v=tC2W1XAa3Ec\&t=2s)
* [How to Embed DOCX Editor in Next.js Using Apryse WebViewer](https://www.youtube.com/watch?v=aggPBQ72TqQ)
* [How to Embed DOCX Editor in Angular Using Apryse WebViewer](https://www.youtube.com/watch?v=19tN_cx6g3U\&t=2s)
* [Building a Powerful Docx Editor in JavaScript Framework](https://apryse.com/blog/docx-editor-in-javascript)
* [Create and Edit Word DOCX Documents in Any Web Application](https://apryse.com/blog/webviewer/create-edit-word-docx-document-in-web-app)
* [How to Embed DOCX Editor Into Your React Web App](https://apryse.com/blog/webviewer/how-to-embed-docx-editing-in-react)


---

# 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/docx-editor/docx-editor.md?ask=<question>&goal=<user_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.
