> 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/general/instrumentation-general-reference_material-list/000005603.md).
# Instrument washes required for Illumina sequencing platforms
**Background**\
Many different factors contribute to a successful sequencing run. One important aspect is to make sure that the fluidics lines are thoroughly flushed between sequencing runs to prevent any salt accumulation. It is also important that the fluidics systems are well maintained when the instrument is idle.
For some Illumina sequencing platforms, including the iSeq 100, MiSeq i100 Series, and NextSeq 1000/2000 Series, instrument washes are not required. These systems use sequencing cartridges that contain contain the pumps, valves, and all other fluidics components needed for sequencing, and the cartridges are discarded after each run.
This article outlines the types of washes required, the time needed to complete the wash, and how frequently the respective washes should be performed for all Illumina sequencing instruments.
**Note:** Water and other chemicals used should be lab grade.
**MiSeq system**\
Instructions for performing the wash procedures can be found in the [MiSeq System Guide](https://sapac.support.illumina.com/sequencing/sequencing_instruments/miseq/documentation.html).
**MiniSeq and NextSeq 500/550 systems**\
Instructions for performing the wash procedures can be found in the [MiniSeq System Guide](https://sapac.support.illumina.com/downloads/miniseq-system-guide-1000000002695.html), [NextSeq 500 and NextSeq 550 Sequencing System Guide](https://support.illumina.com/downloads/nextseq-500-550-systems-product-documentation.html).
**NovaSeq 6000 system**\
Instructions for performing the wash procedure can be found in the [NovaSeq 6000 System Guide](https://sapac.support.illumina.com/downloads/novaseq-6000-system-guide-1000000019358.html).
**NovaSeq X Series systems**\
Instructions for performing the wash procedure can be found in the [NovaSeq X Series Product Documentation](https://support.illumina.com/downloads/novaseq-x-novaseq-x-plus-product-documentation.html).
\
\
\
| |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #5603), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000005603%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/general/instrumentation-general-reference_material-list/000005603.md?ask=&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.