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

# How to mitigate index hopping

**What is index hopping?**\
Index hopping is a specific cause of index misassignment. Index hopping can result in incorrect assignment of libraries from the expected index to a different index in a multiplexed pool, which may lead to misalignment and inaccurate downstream analysis results.

**Which factors impact index hopping?**

* Contamination of free adapters/index primers can lead to increased index hopping.
* The method of library preparation contributes to levels of index hopping. In general, PCR-free library preparation methods that only include adapter ligation generate libraries with higher levels of index hopping than methods that incorporate a PCR amplification step of the libraries.
* Libraries clustered on nonpatterned flow cells with traditional bridge amplification typically have lower rates of index hopping compared to libraries run on patterned flow cells that use exclusion amplification (ExAmp) cluster generation.

**Best practices to mitigate index hopping**:

* Prepare libraries with unique dual index kits, which allow index hopped reads to be bioinformatically removed.
* Remove free adapters from library preps. This may include additional bead clean-up or column clean-up if needed.
* Store libraries individually at -20°C. Do not store libraries as a pool.
* Pool libraries just prior to sequencing.

More details about index hopping are found in the white paper [Effects of Index Misassignment on Multiplexing and Downstream Analysis](https://www.illumina.com/content/dam/illumina-marketing/documents/products/whitepapers/index-hopping-white-paper-770-2017-004.pdf?linkId=36607862).

\
\
\ <br>

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