> 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/000005604.md).

# How to Replace a NextSeq 500/550 Air Filter

On newer versions of NextSeq 500/550 instruments and on older instruments that have received an air filter retrofit, the instrument displays a notification to change the air filter every 90 days. This is the user's responsibility to replace air filters as part of routine maintenance.

NextSeq Air Filter Catalog #: **20063988**

**How to Change Air Filter**

The instructions are also available in the [NextSeq 500 and NextSeq 550 Sequencing System Guide](https://support.illumina.com/downloads/nextseq-500-550-systems-product-documentation.html)

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-3b1ef958c8b77b947e818cefe99776c283405978%2Fimage1.png?alt=media\&token=03998374-6489-45a2-9068-65c796babda7)

1. Remove air filter from package. Write date of install on frame.
2. On back of instrument, press down on top of filter tray to release the tray.
3. Grasp the top of the filter tray and pull up to lift the tray completely out of the instrument.
4. Remove and discard the older air filter.
5. Insert the new air filter into the tray.
6. Slide the filter tray into the instrument. Push down on the top of the filter tray until it clicks into place.

**Note:** The air filter can be inserted the wrong way. There are arrows pointing the correct direction and there is a warning sign present indicating it must not be visible when inserted correctly.

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-ac886d4f30b128b500541e51a139afb45b13b93c%2Fimage2.png?alt=media\&token=abf451da-c049-4782-b307-f6803f78394b)

\
\
\ <br>

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