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

# Input recommendations for Illumina Rapid RNA Kits

**Are there any changes to the RNA input quantity or quality that the Rapid RNA kits support vs non-Rapid?**

Yes, Illumina Rapid mRNA and Illumina Rapid RNA Prep with Enrichment workflows support lower input amounts (down to 1 ng of high quality input) compared to their non-Rapid versions. For traditional RNA-seq workflows, clean-up steps following cDNA synthesis or ligation may lose a significant amount of the sample library. Illumina Rapid workflows eliminate those clean-up steps, resulting in more diverse and complex mRNA libraries for detection of low abundance transcripts and supporting lower input amounts.

**Note**: Illumina Stranded Total RNA already supports down to 1 ng of input, therefore the lower end of the input recommendation for Illumina Rapid Total RNA is still also 1 ng.

The required input quality (ie, RIN or DV200) are unchanged compared to the non-Rapid versions. See the respective Product Documentation RNA Input Recommendations section for input recommendation details for each Illumina Rapid RNA product.

\
\
\ <br>

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