> For the complete documentation index, see [llms.txt](https://knowledge.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.illumina.com/instrumentation/nextseq-1000-2000/instrumentation-nextseq-1000-2000-faq-list/000007863.md).

# Common Questions Related to Sequencing Analysis Viewer (SAV) software and the NextSeq 1000/2000

Sequencing Analysis Viewer (SAV) is a free software used to assess the performance of sequencing runs, and can be downloaded from the Illumina website: [Sequencing Analysis Viewer](https://emea.support.illumina.com/sequencing/sequencing_software/sequencing_analysis_viewer_sav/downloads.html)

### **Can the Sequencing Analysis Viewer software be installed on the NextSeq 1000/2000 instrument itself?**

This is dependent on what Operating System (OS) is installed on the instrument:

* **NO** - If the system OS is CentOS 7 with NextSeq Control Software (NCS) v1.7.x or earlier
* **YES** - If the system OS is Oracle Linux 9 with NCS v2.x.

**The v3.0 Sequencing Analysis Viewer software is compatible with Linux, will that version work onboard the NextSeq 1000/2000 instrument?**

While SAV v3.0 has a Windows, Mac, and Linux version, the current Linux version is only compatible with Enterprise Linux versions (EL8+). The NextSeq 1000/2000 currently has two OS versions. The older CentOS 7 (with NCS v1.7.x and older) that is EL7 and is **not compatible**.

The newer OS version is Oracle Linux 9 (with NCS 2.x) that is EL9 **is compatible.**

**What version of SAV should I use to view NextSeq 1000/2000 data?**

Both SAV v2.5.12 and SAV v3.0 can successfully parse NextSeq 1000/2000 data to be viewed in the software.

SAV v2.5.12 is compatible with Windows computers only.

SAV v3.0 is compatible with Windows, Mac, or Linux computers.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #7863), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000007863%20-%20Instrumentation%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |


---

# 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://knowledge.illumina.com/instrumentation/nextseq-1000-2000/instrumentation-nextseq-1000-2000-faq-list/000007863.md?ask=<question>&goal=<endgoal>
```

`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.