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

# Library quantification and manual normalization of Nextera XT libraries

The Nextera XT protocol provides two methods for normalizing final libraries, bead-based normalization and manual normalization. This article focuses on manual normalization, and best practices for quantification.

After the Nextera XT PCR cleanup step, the library is double stranded DNA and can be **quantified using a fluorometric method**, **such as Qubit or PicoGreen**.

Bioanalyzer traces or qPCR are not acceptable methods for quantifying Nextera libraries.

* Although a Bioanalyzer trace is recommended for assessing final library size, it is not accurate for quantification due to the broad library size distribution of Nextera XT libraries.
* qPCR is appropriate only for libraries with a narrow size range. qPCR uses single-sized standards which are not representative of Nextera XT libraries, and a qPCR standard is not available for the broad size distribution of Nextera XT libraries.

Quantify samples with Qubit or PicoGreen, and omit the bead-based normalization steps of the protocol if planning to manually normalize the libraries.

For manual normalization:

1. Calculate the molarity of each library using the Qubit quantification values and the average fragment length from the Bioanalyzer.
2. Prepare dilutions of each library to the same nanomolar concentration (C1V1 = C2V2)
3. Pool equal volumes of each normalized library (5 µl of each, for example)

See [Best practices for manually normalizing library concentrations](https://knowledge.illumina.com/library-preparation/general-library-prep/library-preparation-general-library-prep-reference_material-list/000001252.md) for more information.

**Note:** Consult the denature and dilution protocol for the instrument that will be used for the most appropriate recommendations for next steps.

\
\
\ <br>

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