Comparison Tables
A comparison table puts two or more peptides side by side so their differences are obvious at a glance. This page explains how to read one and how to build one — the attributes that matter and why. For the finished comparisons on this wiki, see Stacks & Comparisons.
The core columns
A useful peptide comparison usually has one row per peptide (or one column per peptide) covering these attributes:
| Column | What it captures | Why it matters |
|---|---|---|
| Class / mechanism | What family it belongs to and how it acts (e.g. GHRH analog, ghrelin mimetic, GLP-1 agonist, healing peptide) | Two peptides in the same class are more interchangeable; different classes are often combined, not substituted |
| Primary use / goal | What people actually use it for (fat loss, recovery, GH support, sexual health) | Aligns the comparison to your goal rather than the molecule in isolation |
| Evidence strength | How well-supported the claims are (approved / clinical / preclinical / anecdotal) | Separates proven from speculative; see Evidence Grading Explained |
| Approx half-life | Roughly how long it stays active | Drives dosing frequency; see Half-Life Reference Chart |
| Legal / regulatory status | Approved drug, prescription, research-use-only, banned in sport, etc. | Determines availability and risk; see Regulatory & Legal Status |
You can add columns as needed — typical dose, route (subQ/IM/oral), common side effects, or cost — but the five above are the backbone of any honest comparison.
How to read a comparison table
- Start with class. If two peptides share a class and mechanism, the comparison is about which is better at the same job. If they differ, it is about which job you are trying to do.
- Weight by evidence, not hype. A claim graded “approved” or “clinical” carries far more weight than “anecdotal.” Don’t let a long benefits list outweigh a weak evidence column.
- Match half-life to lifestyle. A once-weekly long-half-life peptide and a thrice-daily short one can target the same goal very differently in practice.
- Check legal status last but never skip it. Two otherwise-similar options can differ sharply in whether they are an approved drug, prescription-only, or research-use-only.
How to build one
- Pick a fair axis. Compare like with like — same goal (e.g. fat loss) or same class (e.g. GH secretagogues). Comparing a GLP-1 agonist against a healing peptide tells you little.
- Pull each cell from the individual peptide page so the numbers stay consistent and sourced. Carry the evidence grade through; don’t flatten everything to a single “works/doesn’t.”
- Mark uncertainty. Where a value is approximate or poorly characterized (e.g. BPC-157 and TB-500 half-lives), say so rather than implying false precision.
- Keep it scannable. One attribute per column, short cells, and a one-line takeaway underneath.
Comparisons on this wiki
See the full set in Stacks & Comparisons, including side-by-sides such as BPC-157 vs TB-500, Semaglutide vs Tirzepatide, Tirzepatide vs Retatrutide, Sermorelin vs CJC-1295, MK-677 vs Ipamorelin, and Semaglutide vs Retatrutide.
Educational information only — not medical advice. See Disclaimer.