> 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/appian/get-started/guides.md). # Appian WebViewer Discover how to enhance your Appian environment with the Appian WebViewer Component Plugin. View, annotate, and manipulate documents seamlessly within Appian without compromising data security. Instal The Appian WebViewer Component Plugin wraps around the [Apryse WebViewer](/web/get-started/guides.md) UI and SDK to enable access to our flagship document processing JavaScript library in your Appian environment. Use it to view and annotate documents right in Appian without documents leaving the platform. Add it to your case management workflow to review documents or redact sensitive information from a document. Document manipulation is also available through the UI or through JavaScript APIs. The component can be added to any Appian interface you choose with lots of customization options available. ![](https://1373770520-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQBPkEFulYTrl1g37jENZ%2Fuploads%2Fgit-blob-8300a2b5bc08998a4bf9dad0c068d121e937c1b5%2F54252c4d2f82b8e21a62c4d295f3d3f7f6eb69f1-2522x1273.png?alt=media) {% hint style="info" %} **WebViewer is a client-side SDK** WebViewer does not send any data to our servers. All document processing is done on the client-side. This means that your documents never leave your Appian environment or browser. For server-side processing on Appian, check out the [WebViewer System Plugin](https://community.appian.com/b/appmarket/posts/apryse-webviewer-connected-system). {% endhint %} ## Install WebViewer in your Appian environment Review the [Appian Get Started guide](/appian/get-started/install.md) to learn how to install the components and set them up. There is also a YouTube video that will walk you through the steps. You can install WebViewer in Appian with the following plugins listed on the Appian AppMarket (both are required to run the solution): * [WebViewer Component Plugin - AppMarket Listing](https://community.appian.com/b/appmarket/posts/apryse-webviewer-component/) * [WebViewer System Plugin - AppMarket Listing](https://community.appian.com/b/appmarket/posts/apryse-webviewer-connected-system/) ## File Type Support WebViewer supports a multitude of file types for viewing and editing. Here are some of the most common file types that can be viewed and edited in Appian: * PDF, PDF/A * DOCX, XLSX, PPTX (MS Office software or licenses are **not** required) * JPG, PNG For a full list of supported file types, see our [file type support page](/web/what-is-webviewer/file-format-support.md). Please note that only the `Client only` column applies to Appian in this case. WebViewer Server and custom server solutions require additional server deployments to work alongside Appian. ## Browser Support WebViewer for Appian runs in all [Appian supported browsers](https://docs.appian.com/suite/help/24.2/System_Requirements.html#web-browsers). See our [browser support page](/web/what-is-webviewer/browser-support.md) for more details. ## How can we access WebViewer features in Appian? Our WebViewer JavaScript UI and SDK are wrapped in an Appian Component Plugin. The plugin exposes certain parts of the SDK through it's component properties. The component parameters execute the necessary JavaScript code on run time, depending on your configurations. TThis allows users without any prior coding knowledge to access and configure the features, appearance, and behavior of WebViewer. ![](https://1373770520-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQBPkEFulYTrl1g37jENZ%2Fuploads%2Fgit-blob-5486cca573d5550010722274a12ea59008e01133%2Fb0d9ba2f53d47f11a3bce17dd7ab3b49a7b6cfdb-1473x573.png?alt=media) You can check out the [component's list of configurable properties](/appian/get-started/component-properties.md). ### Looking to do more? Not finding what you need? Don't worry! We've got you covered. You can access the full WebViewer SDK through the Appian Component Plugin. This allows you to access and manipulate documents in Appian using JavaScript APIs. You can also customize the look and feel of the WebViewer UI to match your Appian interface. Check out our [Appian customization guide](/appian/customization/working-with-apis.md) to learn more. ## Related Blogs [Five Ways the Apryse WebViewer Plugin Enhances the Appian Case Management Solution](https://apryse.com/blog/webviewer-plugin-for-appian-5-benefits) - 1/17/24 [Unlock Native Document Viewing and Editing in Appian with Apryse WebViewer](https://apryse.com/blog/document-viewing-and-editing-in-appian-apryse-webviewer) - 9/16/23 [How to Streamline On-platform Redaction and Document Processing for Appian Case Management](https://apryse.com/blog/appian/add-document-processing-and-redaction-to-appian-case-management) - 10/26/22 [How to Add PDF Viewing and Editing in Appian Designer](https://apryse.com/blog/appian/view-and-edit-pdf-and-word-documents-with-appian) - 12/29/21 --- # 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/appian/get-started/guides.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.