> 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/rna-library-prep/library-preparation-rna-library-prep-reference_material-list/000002864.md).

# Types of small RNA and the need for a separate small RNA kit

This article discusses the various types of small RNA and why a separate small RNA library preparation kit is required to sequence them.

**Most common types of small RNA:**

| **Abbreviation** | **Name**              | **Length**                          | **Description**                     |
| ---------------- | --------------------- | ----------------------------------- | ----------------------------------- |
| miRNA            | microRNA              | 18-25 nt                            | Inhibit translation of mRNA         |
| siRNA            | small interfering RNA | 20-25 nt (longer has been reported) | Cleave mRNA                         |
| piRNA            | Piwi-interacting RNA  | 24-31 nt                            | Silence transposons in the germline |

**Why is a separate small RNA kit required?**\
The small RNAs are too small to be captured by the Total RNA and mRNA library preparation kits. Library fragments generated from such small RNAs are not faithfully retained during bead clean-up steps.

**For Illumina solutions for small RNAs, see**:

* [Illumina miRNA Prep Kit](https://www.illumina.com/products/by-type/sequencing-kits/library-prep-kits/illumina-mirna-prep.html)
* [TruSeq Small RNA Prep Kit](https://www.illumina.com/products/by-type/sequencing-kits/library-prep-kits/truseq-small-rna.html)

\
\
\ <br>

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