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

# Input DNA requirements for TruSeq DNA PCR-Free library preparation

**Why are different input amounts used to generate 350 bp and 550 bp TruSeq DNA PCR-Free libraries?**\
The input recommendations were tested and validated to yield appropriate final yields for sequencing. Illumina recommends 1 µg input for the 350 bp target insert size and 2 µg for the 550 bp target insert size. In order to generate sufficient nanomolar concentration of libraries for sequencing with the larger 550 bp insert length, 2 μg of input DNA is required, due to the longer insert size compared to the 350 bp workflow.

**Can the input DNA quantity be reduced?**\
Illumina does not support or recommend input amounts lower than 1 μg for a 350 bp insert size or 2 μg for a 550 bp library. It is possible that reducing the amount of input material may fail to generate enough library to successfully proceed with sequencing.

If sufficient input DNA is not available, consider using [TruSeq DNA Nano](https://www.illumina.com/products/by-type/sequencing-kits/library-prep-kits/truseq-nano-dna.html), which includes a PCR amplification step, or [Illumina DNA PCR-Free Prep](https://www.illumina.com/products/by-type/sequencing-kits/library-prep-kits/dna-pcr-free-prep.html), which offers greater flexibility in DNA input requirements.

\
\
\ <br>

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