> 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/miniseq/instrumentation-miniseq-reference_material-list/000002032.md).

# Enabling saving Thumbnail Images on the MiniSeq

Thumbnail Images on the MiniSeq may be useful when troubleshooting run quality issues or for determining clustering efficiency. By default, the setting to save Thumbnail Images is **not enabled** on the MiniSeq, as these images increase run folder size and can cause runs to crash due to the increased strain on the hard drive. However, if users would like to enable the saving of thumbnail images for diagnostic purposes, follow the guidance below.

1. Close MiniSeq Control Software (MnCS).
2. Locate the following file:
   * Windows 7:
     * C:\Illumina\MiniSeq Control Software\InstrumentShell.MiniSeqControlSoftware.Options.cfg
   * Windows 10:
     * C:\ProgramData\Illumina\MiniSeq Control Software\InstrumentShell.MiniSeqControlSoftware.Options.cfg
       * **The ProgramData folder may be hidden.** To unhide files, select the View tab in the File Explorer window and ensure that "Hidden items" is checked.
3. Make a copy of the file, rename it to "InstrumentShell.MiniSeqControlSoftware.Options.BACKUP.cfg", and save it as a backup.
4. Open the original file and locate this line:
   * ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-96aeb3d3330105b3015ae65d8a5a3c19c6a90391%2Fimage1.jpg?alt=media\&token=fed72624-f2dc-4b09-96d1-408cd5620988)
5. Change **false** to **true**, and make sure that no additional characters or spaces are added or deleted.
6. Save the changed file.
7. Power cycle the instrument following the instructions in [How to Power Cycle the MiniSeq](https://knowledge.illumina.com/instrumentation/miniseq/instrumentation-miniseq-reference_material-list/000002010.md).

* After following the steps above, the next run will save Thumbnail Images for each cycle.
* To disable Thumbnail Images, follow the above steps and change the argument back from **true** to **false** in step 5.

**Additional considerations:**

* Thumbnail Images will only be saved for Tiles 1 and 6 if this setting is enabled.
* Enabling this option does not retroactively add Thumbnails Images to past runs.
* When saving is enables, the Thumbnail Images are saved to:
  * \[Run Folder]\Thumbnail\_Images\L001\C\[X.1] where X refers to the cycle number.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #2032), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000002032%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/miniseq/instrumentation-miniseq-reference_material-list/000002032.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.
