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

# When and how to quantify Illumina DNA PCR-Free libraries

Can **libraries still be manually quantified and normalized if over 300 ng is used (saturating input)?**\
Yes, libraries can be quantified when input DNA is over the saturation point. For pooling, pool 9 µl or more per sample to mitigate pipetting variability.

**If the BLT-PF is self-normalizing at saturating conditions, why is a quantification after pooling still recommended?**\
This is because user to user and experiment to experiment variation is higher than sample to sample variation. Quantification is also required to calculate how to dilute libraries to the starting loading concentration.

**Can qPCR quantification be used for Hybex workflow?**\
Yes, KAPA qPCR is suitable for all input amounts, but is required for low DNA input (<300 ng).

**Should Qubit or qPCR quantification be used for saliva/blood/dried blood spots?**

* Either qPCR or single-stranded (ssDNA) Qubit quantification can be performed.

**Is it possible to omit the final pool quantification?**

No, libraries must be quantified prior to sequencing.

\
\
\ <br>

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