> 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/general/library-preparation-general-faq-list/000003453.md).

# BLT-PF usage FAQ for Illumina DNA PCR-Free

**Note**:The BLT-PF reagent is the bead linked transposome reagent used in the Illumina DNA PCR-Free workflow.

**Can 10 µl of BLT-PF be used (like in the integrated extraction protocol) for purified gDNA?**\
No, this will impact sequencing metrics.

**If saliva**/**blood input is quantified**, **can 15 µl BLT-PF be used instead? What would happen** (**in the Tagment Genomic DNA section of Reference Guide**)**?**\
This will increase the amount of DNA required for the integrated normalization. For some samples, this may negatively impact the self-normalization feature of the Illumina DNA PCR-Free method.

**Why is there a different amount of BLT-PF if using gDNA vs blood or saliva input?**\
This is intended to make sure that raw samples are normalized as they are processed through the workflow, allowing for utilization of the normalizing effect of the bead linked transposome.

**Should dried blood spots** (**DBS**) **be treated like gDNA** (**using 15 µl BLT-PF**) **or like blood**/**saliva** (**using 10 µl BLT-PF**) **in the Tagment Genomic DNA section of the Reference Guide?**\
Treat dried blood spots like blood/saliva samples, using 10 µl BLT-PF for each sample.

**What happens if the beads settle out of solution?**

Resuspend the beads and proceed as normal.

\
\
\ <br>

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