> 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-500-550/instrumentation-nextseq-500-550-reference_material-list/000003084.md).

# Thumbnail image information on the NextSeq 500/550

On the NextSeq 500/550, thumbnail images are disabled by default to prevent Real Time Analysis (RTA) from running slowly.

* Enabling thumbnail images can aid in troubleshooting.

**Thumbnail images location:**

* File Path: D:\Illumina\ NextSeq Control Software Temp\\

**Thumbnail images nomenclature:**

* \[Run\_Folder]\Thumbnail\_Images\L00\[X]\C\[Y.1] ]
  * X refers to the lane number
  * Y refers to the cycle number.\
    eg, Temp\[Run\_Folder]\Thumbnail\_Images\L00\[4]\C\[25.1] (Lane 4, Cycle 25, tiles 01)
* Saves thumbnail images only for tiles 01, 06, and 12.
* **Flow cell**
  * 4 Lanes
  * 2 Surfaces (1 = top, 2 = bottom)
* **Swaths**
  * Mid Output flow cell = 1 swath
  * High Output flow cell = 3 swaths
  * 6 sections (six cameras)
* **Tiles represented in two digits**
  * Mid Output flow cell: 144 tiles (4 lanes x 1 swath x 3 sections x 12 tiles)
  * High Output flow cell: 432 tiles (4 lanes x 3 swaths x 3 sections x 12 tiles)
  * Both flow cell tiles are numbered 01--12
* **Thumbnail file naming format**: s\_\[lane]*\[tile numbering]*\[channel].jpg
* **Tile numbering format**: \[Surface]\[Swath]\[Section]\[Tile]
  * Example:
    * s\_2\_21206\_green.jpg
      * lane 2
      * bottom surface
      * swath 1
      * section 2
      * tile 06
      * green channel

**References:**

* [Two-Channel SBS Technology](https://www.illumina.com/science/technology/next-generation-sequencing/sequencing-technology/2-channel-sbs.html)
* [NextSeq 500/500 Sequencing Systems Product Documentation](https://support-docs.illumina.com/IN/NextSeq_550-500/Content/IN/FrontPages/NextSeq-550-500.htm) (section **Thumbnail files**in Sequencing Output files)
* For further information, see for Knowledge Base article [How to turn on thumbnails for troubleshooting on the NextSeq 500/550](https://knowledge.illumina.com/instrumentation/nextseq-500-550/instrumentation-nextseq-500-550-reference_material-list/000002085.md)

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #3084), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000003084%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 by asking a question.

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

```
GET https://knowledge.illumina.com/instrumentation/nextseq-500-550/instrumentation-nextseq-500-550-reference_material-list/000003084.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.
