> 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/guides/peptide-hplc-interpretation-guide.md).

# HPLC Interpretation Guide

| Field            | Value                                                              |
| ---------------- | ------------------------------------------------------------------ |
| **Document ID**  | RPL-GUIDE-HPLC-001                                                 |
| **Version**      | 1.0                                                                |
| **Publisher**    | RPL Peptide (Qingdao RPL Biotechnology Co., Ltd.)                  |
| **URL**          | <https://rplpeptides.com/guides/peptide-hplc-interpretation-guide> |
| **Last Updated** | July 2026                                                          |

***

## 1. Introduction

HPLC is the primary method for peptide purity determination. Understanding how to read and interpret HPLC data is essential for quality assessment.

## 2. Introduction to HPLC

High-Performance Liquid Chromatography separates components based on hydrophobicity. The C18 column retains peptides; the mobile phase gradient elutes them in order of increasing hydrophobicity.

## 3. Chromatogram Layout

X-axis: Time (minutes) Y-axis: UV absorbance (mAU) at 214 nm Main peak: The target peptide Small peaks: Impurities or degradation products

## 4. Retention Time (RT)

The time at which the peptide elutes. Used for preliminary identification. Can vary slightly between runs (±0.2 min). Should match reference standard RT.

## 5. Peak Area

The integrated area under each peak. Proportional to the amount of that component. Measured in mAU × minutes.

## 6. Main Peak

The largest peak in the chromatogram. Should be well-resolved from other peaks. Should have symmetrical shape. Tail factor: 0.8–1.5 is acceptable.

## 7. Impurities

Any peak other than the main peak. May include:

* Truncated sequences (earlier eluting)
* Oxidation products (earlier eluting)
* Deletion sequences
* Process-related impurities

## 8. Peak Integration

The software automatically integrates peaks. Key parameters:

* Slope sensitivity
* Minimum peak area
* Shoulder detection Manual integration may be needed for complex baselines.

## 9. Purity Calculation

Purity (%) = (Area of main peak / Sum of all peak areas) × 100 Example: Main peak = 985,000; Total = 1,000,000 Purity = 98.5%

## 10. Common Interpretation Errors

❌ Including injection peak (solvent front) ❌ Ignoring late-eluting peaks ❌ Poor baseline integration ❌ Comparing RT across different methods

## 11. Case Examples

Example 1: Clean chromatogram → One main peak, no significant impurities Example 2: Shoulder on main peak → Possible co-eluting impurity Example 3: Multiple small peaks → Multiple synthesis-related impurities

***

## Document Revision History

| Version |    Date   | Changes         |
| :-----: | :-------: | --------------- |
|   1.0   | July 2026 | Initial release |

***

© 2026 RPL Peptide

rplpeptides.com


---

# 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/guides/peptide-hplc-interpretation-guide.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.