> 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-reference_material-list/000003741.md).

# Manual denaturation of libraries on the NextSeq 1000/2000

Manual denature and dilution is recommended for low concentration libraries that are unable to meet the recommended loading concentration and volume as stated in the [NextSeq 1000 and NextSeq 2000 Product Documentation](https://support-docs.illumina.com/IN/NextSeq10002000/Content/IN/FrontPages/NextSeq10002000.htm).

The NextSeq 1000/2000 [Denature and Dilute Libraries Guide](https://support-docs.illumina.com/IN/dnd-wizard/Content/dnd/landing.htm?ins=nextseq1k2k) contains:

* Recommended final loading concentrations (what is loaded into the cartridge after denaturation and dilution) and corresponding starting library concentrations.
* Instructions for Manual Denature and Dilution

To optimize loading for libraries that have not been validated by Illumina:

* For XLEAP-SBS reagents, see Knowledge Base Article: [NextSeq 1000/2000 Loading Optimization for XLEAP-SBS](https://knowledge.illumina.com/instrumentation/nextseq-1000-2000/instrumentation-nextseq-1000-2000-reference_material-list/000008693.md)
* For Standard SBS reagents, see Knowledge Base Article: [NextSeq 1000/2000 Loading Optimization for Standard SBS](https://knowledge.illumina.com/instrumentation/nextseq-1000-2000/instrumentation-nextseq-1000-2000-reference_material-list/000002435.md)

**Run Setup for Manual Denature and Dilution**

Onboard Denature and Dilution is enabled by default on the NextSeq 1000/2000. There are two methods to disable the onboard denaturation and dilution in the system.

**Option 1:** Set Denature and Dilute Preferences from Settings.\
This will change the default denature and dilution strategy for all runs. This is preferred if all runs on the system are to be manually denatured and diluted.

1. From the control software menu, select **Settings**.
2. Choose whether to automatically denature and dilute libraries onboard the instrument.
   * To disable denature and dilute libraries automatically onboard the instrument, **uncheck** the **Denature and Dilute On Board** checkbox.

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-bd05c272838b990fc5bd1a546c38a997321b604f%2Fimage1.jpg?alt=media)

**Option 2**: Confirm of Change Setting in Run Review Screen.\
If performing manual denature and dilute for a single run, modify the setting within the run review screen during the run setup.

1. From the Run Review screen, disable manual denature and dilution.

* Example:

  ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-ed4a85887de5023137ab071b530e93c06ccd5e1e%2Fimage2.jpg?alt=media)

The runparameters.xml file will indicate if denature and dilution were performed onboard or off instrument.

| Run Parameters Setting           | Strategy                                           |
| -------------------------------- | -------------------------------------------------- |
| \<SkipObdd>**false**\</SkipObdd> | On Board Denature and Dilution preformed (default) |
| \<SkipObdd>**true**\</SkipObdd>  | On Board Denature and Dilution omitted             |

\
\
\ <br>

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