Ask what to stack with BPC-157 and the internet answers with a shortlist. BPC-157 plus TB-500 for healing, BPC-157 plus ipamorelin for recovery, maybe GHK-Cu or a growth-hormone blend if the page sells those too — each recommendation arriving with a combination dosing table, a synergy explanation, and a checkout link. What almost none of these pages mention is the fact that determines everything else: no human trial has ever tested BPC-157 together with any other peptide. Not with TB-500, not with GHK-Cu, not with ipamorelin, not with anything. BPC-157 on its own has more than 100 preclinical publications and zero published human efficacy trials — and every combination inherits that gap, then adds a second one on top.
There is a real scientific story underneath the shortlists, and this guide tells it properly. The pairings people search for are not random: they follow mechanistic-complementarity logic — BPC-157's angiogenesis and FAK-paxillin repair signaling paired with TB-500's actin-mediated cell migration, or with GHK-Cu's extracellular-matrix remodeling, or with growth-hormone secretagogues riding on the fact that GH stimulates collagen synthesis in human tendon and muscle connective tissue (Doessing et al., 2010, J Physiol, PMC2821728). And in 2026 the single most popular pairing finally got its first direct test — an exploratory rat tendon study that compared BPC-157, TB-500, and the combination head-to-head, and found the combination did not outperform either peptide alone (Biçer et al., Joint Dis Relat Surg, DOI 10.52312/jdrs.2026.2951).
This guide walks each pairing, grades what it aims at against what has actually been studied, then shows what PeptaHub's stack library records for each — three documented entries with per-component evidence levels, not vendor copy — and how to check any combination yourself with our stack checker tool.
This guide is educational only. It does not provide dosing, sourcing, or protocol instructions, and nothing in it should be read as a recommendation to combine BPC-157 with anything in humans.
Side-by-side comparison
| Compare | Pairing | What it aims at | Evidence grade |
|---|---|---|---|
| BPC-157 + TB-500 (the 'Wolverine stack') | The most discussed combination in recovery communities. Complementary logic: BPC-157 drives angiogenesis and FAK-paxillin repair signaling while TB-500 sequesters actin to speed repair-cell migration. Recorded in PeptaHub's stack library as 'The Wolverine Stack: BPC-157 + TB-500 for Healing'. | The one head-to-head animal test — 32 rats with transected, surgically repaired Achilles tendons, four groups including the combination — found TB-500 alone reached significance on load-to-failure and histopathology, BPC-157 was numerically positive, and the combined group 'did not confer additional benefits compared to either agent alone' (Biçer et al., 2026). | One exploratory combined rat study — negative for added benefit; no human data |
| BPC-157 + TB-500 + GHK-Cu (the 'healing stack') | Adds extracellular-matrix remodeling on top of the Wolverine pair: GHK-Cu activates metalloproteinases to clear damaged matrix and stimulates new collagen synthesis. Recorded in our library as 'Healing Stack: BPC-157 + TB-500 + GHK-Cu'. | No study has tested the trio together — or BPC-157 with GHK-Cu at all. GHK-Cu's human data are topical and dermal; injectable GHK-Cu has no published human pharmacokinetic or safety data. | Mechanistic reasoning only; no combined study |
| BPC-157 + GHK-Cu + epithalon (the 'anti-aging stack') | Longevity framing: each peptide assigned a different hallmark of aging — epithalon for telomere attrition, GHK-Cu for age-related gene expression, BPC-157 for declining tissue-repair capacity. Recorded in our library as 'Anti-Aging Stack: Epithalon + GHK-Cu + BPC-157'. | The library entry itself labels this stack speculative. Epithalon's telomerase evidence comes from cultured cells and a single research group's non-randomized human work on the related pineal extract, not the synthetic peptide. | Speculative; mechanistic only |
| BPC-157 + ipamorelin | The growth-hormone-side pairing. The rationale runs: GH stimulates collagen synthesis in human tendon and muscle connective tissue (Doessing et al., 2010, recombinant GH in humans), so a selective GH secretagogue might support connective-tissue repair alongside BPC-157's repair signaling. | No study has combined BPC-157 with any GH secretagogue. Ipamorelin's selectivity was characterized in swine (Raun et al., 1998); its one Phase 2 human trial (postoperative ileus) missed its primary endpoint. Our BPC-157 vs ipamorelin comparison page covers the head-to-head question. | Indirect human rationale (from rhGH, not secretagogues); zero combination data |
| BPC-157 + CJC-1295 or GH-secretagogue blends | Folded into 'recovery stacks' by clinics and content pages, usually via the same GH-collagen rationale. PeptaHub's library keeps these worlds separate: our growth-hormone stack entries (CJC-1295 + Ipamorelin) deliberately do not include BPC-157. | CJC-1295 has the best human pharmacology of any GH-releasing peptide — a randomized placebo-controlled trial showed multi-day GH and IGF-1 elevation (Teichman et al., 2006) — but it has never been trialed alongside BPC-157. | Clinic convention; no combination data |
| BPC-157 alone (the baseline everyone skips) | Over 100 preclinical publications across tendon, muscle, bone, gut, and nerve models; mechanisms include FAK-paxillin signaling (Chang et al., 2011) and VEGF/eNOS-mediated angiogenesis. | No published human efficacy trial exists for BPC-157 by itself. A Phase I safety study has been initiated but not reported. Every stacking question sits on top of this unsettled base. | Animal data only |
| Any BPC-157 combination in humans | No human trial has tested BPC-157 together with TB-500, GHK-Cu, ipamorelin, CJC-1295, or epithalon — for any indication, at any dose, by any route. | Any page publishing confident combination dosing tables or synergy percentages is describing something no study has measured. | No human data |
BPC-157 pairings people actually search for, what each aims at mechanistically, and the evidence grade for the combination itself. The grade column, not the pairing, is the answer.
Why every 'what to stack with BPC-157' answer online is a product list
The pages ranking for this question share a template: a headline promising the best BPC-157 stack, a synergy paragraph naming two or three peptides, a combination dosing table, and a path to purchase or consultation. The shortlist conveniently matches the seller's inventory. The synergy paragraph is always mechanistic — 'BPC-157 builds the vessels, TB-500 brings the cells' — and never cites a study of the combination, because until 2026 there was no study of the combination to cite. The dosing tables are the tell: precise microgram schedules for pairings that have never been through a single human trial, or any trial at all.
Start from the base of the pyramid instead. BPC-157 alone has an unusually deep preclinical literature — more than 100 publications, concentrated in but not exclusive to the Zagreb group that discovered it — and no published human efficacy data. That is the foundation. The first stacking question is therefore not 'which peptide pairs best' but 'what does it even mean to optimize a combination whose base compound has no human efficacy data'. Every layer added on top — TB-500, GHK-Cu, a secretagogue — adds a second compound with its own evidence profile and a combination that, with one recent exception in rats, has never been tested as a pair anywhere.
This is why honest stack content looks different from vendor content. A vendor page answers 'what to stack with BPC-157' with a recipe. An evidence-graded page answers it with a hierarchy: here is the mechanistic rationale people cite, here is what has actually been tested together, here is what our stack library records about each combination's community usage, and here is how to check the next claim yourself. The rest of this guide follows that structure.
BPC-157 + TB-500: the Wolverine stack meets its first combined study
The pairing: BPC-157, a stable gastric-juice-derived pentadecapeptide that promotes angiogenesis and activates the FAK-paxillin pathway governing cell adhesion and tissue remodeling (Chang et al., 2011, J Appl Physiol), alongside TB-500, the synthetic actin-binding fragment of thymosin beta-4 that keeps repair cells mobile by fueling actin polymerization at wound edges. The complementarity story is genuinely elegant — blood supply plus cell delivery, two independent bottlenecks in one healing cascade — and it made 'Wolverine stack' the most discussed peptide combination in the recovery and biohacking community. PeptaHub's stack library records it in full: goals, mechanism rationale, phased community protocol structure, and per-component safety notes, including the theoretical caution around angiogenesis in the context of existing tumors.
In 2026 the pair got something it had never had: a direct head-to-head test. Biçer et al. (Joint Diseases and Related Surgery, 2026;37(3):822-837, DOI 10.52312/jdrs.2026.2951) randomized 32 rats with transected, surgically repaired Achilles tendons to vehicle, BPC-157, TB-500, or the combination, dosed intraperitoneally for 30 days, then measured load-to-failure, Bonar and Movin histopathology scores, and collagen I/III staining. The results cut against the narrative: TB-500 alone reached statistical significance on load-to-failure and on both histopathology scores; BPC-157 was numerically positive but not significant on biomechanics; and the combined group did not differ from any single-agent group — the authors' own conclusion states that combined treatment 'did not confer additional benefits compared to either agent alone.'
One exploratory study in 32 rats does not settle anything — it is a single small-animal experiment, using intraperitoneal dosing rather than the subcutaneous routes community protocols describe, from one research team. But note what it is: more direct evidence about the BPC-157 + TB-500 combination than essentially every clinic page combined has ever cited, and its direction is 'no synergy observed'. The honest statement of where the Wolverine stack stands: strong mechanistic rationale, the deepest community following of any pairing, one small combined animal study that failed to show added benefit, and no human data of any kind. Our BPC-157 vs TB-500 comparison page covers how the two peptides differ when evaluated alone.
Adding GHK-Cu: the extracellular-matrix argument
The second most common answer to 'what to stack with BPC-157' adds a third mechanism. GHK-Cu is a naturally occurring copper-binding tripeptide that declines with age and drives coordinated matrix turnover — activating metalloproteinases that clear damaged extracellular matrix while stimulating synthesis of new collagen, elastin, and glycosaminoglycans. The reasoning, recorded in our healing-stack library entry, is that the Wolverine pair addresses blood supply and cell delivery but not tissue architecture: without proper matrix remodeling, healed tissue is disorganized and re-injury-prone. GHK-Cu is assigned that third bottleneck.
The evidence layer underneath deserves the same grading as everything else on this page. GHK-Cu is the one peptide in these stacks with a long human history — as a topical cosmetic ingredient, where decades of consumer use and an in-vitro fibroblast literature sit. But the human dermal evidence is weaker than reputation suggests (no large registered randomized trial of topical GHK-Cu has been published), and the injectable form that stacking implies has no published human pharmacokinetic, dose-finding, or safety data at all. The widely repeated '4,000 genes modulated' figure is transcriptomic screening data from cell lines, not a clinical effect. And no study — animal or human — has tested GHK-Cu together with BPC-157.
The longevity variant of this pairing swaps the repair framing for an aging framing. Our anti-aging-stack entry (epithalon + GHK-Cu + BPC-157) assigns each peptide a hallmark of aging: epithalon for telomere attrition, GHK-Cu for age-related gene expression, BPC-157 for declining repair capacity. The entry itself describes this framing as speculative, and the underlying evidence agrees: epithalon's telomerase findings come from cultured cells, with human data limited to a single Russian group's non-randomized studies of the related pineal extract. Mechanistic plausibility, honestly labeled, is the entire content of this pairing's evidence base.
The growth-hormone side: ipamorelin, CJC-1295, and the collagen rationale
A whole family of 'what to stack with BPC-157' answers points at GH secretagogues — ipamorelin most often, CJC-1295 alongside it. The biology behind the instinct is real and, unusually for this topic, human: Doessing et al. (J Physiol, 2010, PMC2821728) showed that recombinant growth hormone administration in humans stimulates collagen synthesis in tendon and skeletal-muscle connective tissue — without affecting myofibrillar protein synthesis. Growth hormone is connective-tissue medicine. From there the stack logic runs: a secretagogue that raises endogenous GH might support the collagen side of repair while BPC-157 handles signaling and vascularization.
The gap between that rationale and the evidence is where these pages lose their footing. Ipamorelin is a selective ghrelin-receptor agonist whose clean selectivity profile (no cortisol, ACTH, or prolactin elevation) was established in swine, not humans (Raun et al., 1998); its single Phase 2 human trial, in postoperative ileus, missed its primary endpoint. CJC-1295 has genuinely strong human pharmacology — a randomized, placebo-controlled trial showed multi-day GH and IGF-1 elevation after a single injection (Teichman et al., 2006, JCEM) — but efficacy trials for body composition or recovery have never been published for either compound. And critically: no study has paired any GH secretagogue with BPC-157 in any species. The chain of inference is rhGH-in-humans, to secretagogue-in-humans (unproven for repair), to secretagogue-plus-BPC-157 (unstudied) — three links, two of them untested.
PeptaHub's stack library handles this honestly by separation: our growth-hormone entries (the CJC-1295 + Ipamorelin stack, and the IGF-1 LR3 muscle-growth variant) do not include BPC-157, because no evidence basis exists for folding it in. Readers weighing this family of pairings can see the two sides side by side on our BPC-157 vs ipamorelin comparison page — different mechanisms, different evidence profiles, different regulatory statuses, and no combined data.
What PeptaHub's stack library actually contains
This is the part of the answer no vendor page can copy, because it is a structured record rather than a sales argument. PeptaHub's stack library contains exactly three entries that include BPC-157, each documenting what the community actually discusses — not what anyone should do. The Wolverine Stack: BPC-157 + TB-500 for Healing records the two-peptide repair pairing with its loading-then-maintenance phased structure and the angiogenesis-plus-cell-migration rationale. The Healing Stack: BPC-157 + TB-500 + GHK-Cu extends it with the matrix-remodeling third mechanism. The Anti-Aging Stack: Epithalon + GHK-Cu + BPC-157 applies the same format to the longevity framing. Every entry carries per-component evidence levels (all 'preclinical' for BPC-157 and TB-500, the strongest human data in any entry being GHK-Cu's topical record), mechanism text, safety warnings, and an explicit statement that no human trial has studied the combination.
Read the entries the way you should read any stack content: as ethnography of peptide community practice, with citations. The phased protocol tables document what community protocols look like — they are not schedules to execute, and the entries say so. The safety notes carry real weight regardless of evidence level: the theoretical concern about combining pro-angiogenic and tissue-growth-stimulating compounds in the context of existing or undiagnosed cancer appears on both BPC-157-containing healing entries, because it is the sharpest identified risk in an otherwise mild reported side-effect profile. And the evidence-level tags do the grading work up front — you can see at a glance that nothing in any BPC-157 stack has progressed past preclinical.
That is the differentiator worth internalizing. Any page can assert a best stack; a record library shows you what the stack is, where each part of the claim comes from, what the community's actual practice looks like, and where the evidence ends — and lets you check every field against a peptide profile or comparison page one click away.
How to pressure-test any BPC-157 combination yourself
You will meet BPC-157 stack recommendations for the rest of the peptide content era, so end with a procedure. First, the species test: does the page say which species its claims come from? The combination rationale on most pages is built from rat and mouse studies of individual peptides; if neither 'rat' nor 'mouse' appears near the synergy claim, the claim came from nowhere. Second, the combination test — the one specific to stack content: has the pair ever been studied together? For BPC-157 plus anything, the answer is 'once, in rats, in 2026, with no added benefit observed' for TB-500, and 'never' for every other partner. A page asserting synergy is asserting something no study has measured. Third, the incentive test: is there a protocol for sale, a consultation funnel, or an affiliate link within a scroll? Stacks are the highest-margin content in the peptide economy precisely because combinations justify bigger baskets.
Then use the tools built for exactly this. PeptaHub's stack checker lets you select a combination and see the component-level record for what you have chosen — evidence levels, mechanisms, and safety flags — instead of taking a stranger's word for synergy. The stack library pages document each recorded combination in full. For the pairing questions underneath the stack question, the comparison pages put the two compounds side by side: BPC-157 vs TB-500 for the healing pairing, BPC-157 vs ipamorelin for the GH-side pairing. And for the timeline expectations that stack marketing always implies, our guide to how long BPC-157 takes to work grades every onset claim by evidence layer; for the route questions that combinations raise, the BPC-157 oral vs injection guide does the same.
The graded bottom line on 'what to stack with BPC-157': the most common answer is TB-500, on strong mechanistic grounds and the thinnest possible combined-evidence base — one small rat study that found no added benefit from combining. The GH-side answers ride an elegant human collagen rationale through two untested links. The anti-aging answers are openly speculative. None of these judgments is a reason to combine anything — they are a map of what is known, so that the next confident stack page you read has to argue with the evidence instead of with your expectations.
Frequently asked questions
TB-500, in the combination communities call the 'Wolverine stack'. It is the most discussed recovery pairing in biohacking and sports communities, built on a mechanistic complementarity rationale: BPC-157 promotes angiogenesis and FAK-paxillin repair signaling while TB-500 upregulates actin-dependent cell migration. PeptaHub's stack library records it in full. Note that popularity tracks the elegance of the mechanism story, not combined-trial evidence — the pairing's only head-to-head study is a 2026 rat tendon experiment that found no added benefit from combining.
One, as of 2026. Biçer et al. (Joint Diseases and Related Surgery, 2026;37(3):822-837) randomized 32 rats with transected, repaired Achilles tendons to vehicle, BPC-157, TB-500, or the combination for 30 days. TB-500 alone reached significance on load-to-failure and histopathology scores; BPC-157 was numerically positive on biomechanics; and the combined group did not outperform either single agent — the authors state combined treatment 'did not confer additional benefits compared to either agent alone.' An exploratory single study, but more direct evidence than most pages citing the stack have ever referenced.
People do discuss it, and there is a human-adjacent rationale: recombinant GH stimulates collagen synthesis in human tendon and muscle connective tissue (Doessing et al., 2010). But no study has combined BPC-157 with any GH secretagogue in any species, ipamorelin's human evidence is thin (its one Phase 2 trial missed its primary endpoint), and CJC-1295's solid human pharmacology (Teichman et al., 2006) is single-agent only. PeptaHub's stack library deliberately keeps GH secretagogue stacks and BPC-157 separate for this reason; our BPC-157 vs ipamorelin comparison page lays out the two evidence profiles side by side.
No. No human trial has tested BPC-157 together with TB-500, GHK-Cu, ipamorelin, CJC-1295, or epithalon — for any indication. BPC-157 alone has over 100 preclinical publications but no published human efficacy trial (a Phase I safety study has been initiated, not reported). Any page publishing combination dosing tables, synergy claims, or 'what to expect' arcs for a BPC-157 stack is describing something no study has measured in any species except the single negative-for-synergy rat test of the TB-500 pairing.
Neither, in general. BPC-157 and TB-500 were both removed from Category 2 of the FDA's interim 503A bulk drug substances list on April 15, 2026, and neither can legally be compounded in the US today; a July 23, 2026 advisory committee vote recommended adding both to the 503A Bulks List, but the FDA decision is pending and rulemaking typically takes 12 to 24 months. The common stack partners do not share one status: ipamorelin and CJC-1295 remain on Category 2, and injectable GHK-Cu is queued for advisory review at a PCAC meeting the FDA has said will reconvene before the end of February 2027. For sport, BPC-157 is on the WADA Prohibited List for 2026 and TB-500 is prohibited under Section S2 — stacking changes nothing about either listing.
Run three tests and one tool. Species test: which animal model does each claim come from, with a citation? Combination test: has this specific pair ever been studied together? For BPC-157 pairings the answer is essentially never (the TB-500 exception found no added benefit), so any synergy claim is mechanistic reasoning presented as results. Incentive test: is there a protocol or consultation for sale within a scroll? Then use PeptaHub's stack checker to pull the component-level record — evidence level, mechanism, and safety flags — for the exact combination in front of you, and the BPC-157 stack-library entries to see how the community version is documented.