> For the complete documentation index, see [llms.txt](https://intuitem.gitbook.io/ciso-assistant/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://intuitem.gitbook.io/ciso-assistant/features/evidence-preview.md).

# Evidence preview

View attachment content without downloading it

Most evidence attachments can be read directly in CISO Assistant, without downloading them first. This matters during an audit review, where you may be checking dozens of attachments in a row.

## Where to find it

Open an evidence and scroll to the attachment card below the details — the preview is rendered under the attachment name, next to the **Download** button. The same card appears on an individual evidence revision, so you can inspect what a past version actually contained.

Evidence tables show the **file name** rather than a preview. Previews are deliberately rendered on the detail page only: a thumbnail in a table row is too small to read, and rendering one per row would download every attachment on the page.

## Supported formats

| Type         | Formats                                                           | Rendered as                              |
| ------------ | ----------------------------------------------------------------- | ---------------------------------------- |
| Spreadsheets | `.xlsx`, `.csv`                                                   | Interactive table with one tab per sheet |
| Documents    | `.docx`                                                           | Formatted document                       |
| Markdown     | `.md`                                                             | Formatted text                           |
| Plain text   | `.txt`, `.log`, `.json`, `.yaml`, `.yml`, `.toml`, `.xml`, `.eml` | Raw text                                 |
| Images       | `.png`, `.jpg`, `.jpeg`, `.gif`, `.webp`, `.svg`                  | Image                                    |
| PDF          | `.pdf`                                                            | Embedded document viewer                 |
| Video        | `.mp4`, `.mov`                                                    | Player with controls                     |

Anything else — including legacy Office formats (`.doc`, `.xls`, `.ppt`) and OpenDocument files (`.odt`, `.ods`) — shows **No preview available.** and can still be downloaded.

### Spreadsheets

Spreadsheet previews keep the formatting that makes a workbook readable: cell fills and font styling, borders, merged cells, column widths, frozen header rows, and number formats — so a currency column still reads as currency and a date still reads as a date. Where a workbook has several sheets, each one gets a tab above the preview; hidden sheets are skipped.

Formulas display their last calculated value, exactly as a spreadsheet application shows them on open. Charts, embedded images and pivot tables are not rendered — download the file to see those.

### Documents

Word documents keep headings, bold and italic text, lists and tables. Links are shown as plain text rather than clickable links, and remote images are not loaded — a preview never reaches out to an external server, so opening a supplier's document cannot signal back to whoever sent it.

## Size limits

Large files are not rendered in full, to keep the page responsive:

* Text and Markdown files above 5 MB, and documents and spreadsheets above 10 MB, show **File is too large to preview. Download it to view its content.**
* Long files are cut off at 5 000 lines; spreadsheets at 2 000 rows, 100 columns and 50 sheets per file. When that happens the preview shows **Preview truncated. Download the file to see everything.**

In both cases the attachment itself is untouched — **Download** always gives you the complete file.

## Related

* [Evidence](/ciso-assistant/concepts/compliance/evidence.md)
* [Evidences from clipboard](/ciso-assistant/features/evidences-from-clipboard.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://intuitem.gitbook.io/ciso-assistant/features/evidence-preview.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.