> For the complete documentation index, see [llms.txt](https://docs.rplpeptides.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rplpeptides.com/docs/glossary/analytical-terms/impurity.md).

# Impurity

## Definition

An impurity is any substance present in a peptide sample that is not the target peptide. Impurities are detected and quantified during HPLC analysis and reported on the Certificate of Analysis.

## Overview

Impurities in peptide samples arise from the synthesis process (truncated sequences, deletion peptides), handling/storage (oxidation products, aggregation), or formulation (residual solvents, counter-ions). The type and level of impurities directly impact product quality.

## Technical Explanation

**Common Impurity Types:**

| Type                | Source                               | Example                      |
| ------------------- | ------------------------------------ | ---------------------------- |
| Truncated Sequences | Incomplete coupling during SPPS      | Missing C-terminal residues  |
| Deletion Peptides   | Failed coupling at specific residues | Missing internal amino acid  |
| Oxidation Products  | Exposure to air/light                | Methionine sulfoxide         |
| Acetylated Species  | Side reaction during cleavage        | N-terminal acetylation       |
| Dimer/Aggregate     | Intermolecular interaction           | Two peptide molecules joined |
| Residual Solvents   | Incomplete lyophilization            | Acetonitrile, TFA            |
| Water               | Hygroscopic absorption               | Moisture content             |

**Impurity Reporting:**

* Each impurity ≥0.1% is typically reported individually
* Total impurities = 100% − Main peak purity (%)
* Impurities identified by RRT (Relative Retention Time)

## Importance in Peptide Documentation

The impurity profile is as important as the purity value itself. A product with 98% purity but containing a toxic impurity is less desirable than one with 97% purity and only harmless truncation impurities. Detailed impurity data demonstrates comprehensive quality control.

## Related Terms

* [Purity](/docs/glossary/analytical-terms/purity.md)
* [HPLC](/docs/glossary/analytical-terms/hplc.md)
* [Peak Area](/docs/glossary/analytical-terms/peak-area.md)
* [Retention Time](/docs/glossary/analytical-terms/retention-time.md)
* [COA](/docs/glossary/quality-control/coa.md)
* [Specification](/docs/glossary/quality-control/specification.md)

## Frequently Asked Questions

**Q: What is an acceptable impurity level?** A: For research-grade peptides, total impurities ≤2% (purity ≥98%) is standard. Higher purity (≥99%) is available for sensitive applications. Individual impurities are typically ≤0.5% each.

**Q: Are all impurities harmful to research?** A: Not necessarily. Truncation peptides (shorter fragments) may be biologically inert. However, some impurities (oxidation products, reactive by-products) could interfere with experimental results. Full impurity characterization is always recommended.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.rplpeptides.com/docs/glossary/analytical-terms/impurity.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.