BPC-157 vs TB-500
People rarely actually pick between these two — the more common question is how they differ and why they're so often paired. There's even a combined entry in the library.
Side by side
| BPC-157 | TB-500 | |
|---|---|---|
| Class | Peptides | Peptides |
| Form | Injection | Injection |
| Half-life | — | — |
| Storage | — | — |
| Dose units | mcg, mg | mg, mcg |
| FDA status | Not FDA-approved | Not FDA-approved |
Facts from the Stack compound library. See the full pages: BPC-157 · TB-500.
How they differ
Origin
BPC-157 is a synthetic fragment of a protein found in gastric juice. TB-500 is a synthetic fragment of thymosin beta-4. Different parent molecules, different proposed mechanisms.
Half-life & dosing rhythm
Their pharmacokinetics differ, which is why people who run both often log them on separate schedules. A per-compound dose log keeps two overlapping cadences straight.
Reconstitution & storage
Both ship lyophilized and are reconstituted with bacteriostatic water, and both are typically refrigerated after mixing — so the reconstitution calculator and an opened-vial date apply to each.
Regulatory status
Neither is approved for human use anywhere. Their inclusion in the library is documentation, not endorsement.
Tracking either one
Whichever you log, the workflow is the same in Stack: add it once, set the schedule, and let the app handle reminders, supply projection and an "in your system" curve from the half-life. Run both? Group them into one protocol you can pause together.
Track your stack in Stack
Free, private, no account. Doses, schedules, supply and trends in one quiet app.
Get the appLast reviewed 2026-06-11