> 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/library-preparation/dna-library-prep/library-preparation-dna-library-prep-faq-list/000003444.md).

# Denature and dilution FAQ for Illumina DNA PCR-Free

**Which Denature & Dilute protocol should be followed for NovaSeq 6000 and for other supported instruments? If protocol A/standard protocol, is NaOH added twice? (Once during the library preparation protocol (HP3 reagent) and then again during the denature & dilute protocol)**

Use the standard denature and dilution protocol (using NaOH) for instruments where denaturation is performed before loading the library on the instrument. Use the onboard denaturation protocol for instruments that support onboard denature and dilute.

While NaOH is used during the library preparation, it is still required to perform NaOH denaturation prior to sequencing to prevent the formation of any secondary structures.

**Do libraries need to be heat shocked/heat treated to make sure they are single stranded?**\
No. NaOH denaturation will resolve any secondary structures. Additional heat denaturation is not required.

**If denaturation prior to clustering was omitted**, **will the data be okay? What is the performance impact?**\
This method of clustering is not supported. However, because Illumina DNA PCR-free generates single stranded DNA (ssDNA) libraries, the libraries may still cluster and generate high quality data, though this cannot be guaranteed. It is possible to see lower quality, lower data output (lower cluster density or percent occupancy), or run failure.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                              |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #3444), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000003444%20-%20Library%20Preparation%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/library-preparation/dna-library-prep/library-preparation-dna-library-prep-faq-list/000003444.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.
