> 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/get-started/faq/mime-types.md).

# MIME types

If you see a 404 for files on your server but you're very sure that the files are there then you may need to set MIME types for certain file extensions used by WebViewer.

If you see a 404 for files on your server but you're very sure that the files are there then you may need to set MIME types for certain file extensions used by WebViewer. With IIS you will generally need to do this and the process may vary slightly depending on your server.

Regardless of the documents that you're loading you'll need to add the MIME type for json files (`application/json`) so that the UI text is loaded. If you see buttons or labels in the UI with names like `controlbar.fullScreen` then that means the json file wasn't loaded successfully.

## XOD

You'll need to add `xod` with a MIME type of `application/octet-stream` or `application/vnd.ms-xpsdocument`

## PDF and Office

| Extension | MIME Type                |
| --------- | ------------------------ |
| res       | application/octet-stream |
| mem       | application/octet-stream |
| wasm      | application/wasm         |
| json      | application/json         |


---

# 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/get-started/faq/mime-types.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.