pepdex
← Back to peptides
Comparison

BPC-157 vs TB-500

BPC-157 vs TB-500 for healing: which to pick, and why most users run them together as the canonical healing stack.

№ 001
BPC-157
HealingEvidence: Limited

Think of BPC-157 as a healing accelerator for connective tissue. Most users run it for stubborn tendon, ligament, or gut problems where regular rehab has stalled. You inject a tiny amount under the skin once a day for 4-6 weeks, take a break, then reassess.

Onset
50
Documentation
55
Side intensity
64
Popularity
95
№ 002
TB-500
HealingEvidence: Limited

TB-500 is a fragment of a natural healing protein your body already makes. It's used for chronic injuries that won't resolve on their own — old shoulder issues, lingering tendon pain. You usually pair it with BPC-157 for a stronger combined effect.

Onset
50
Documentation
55
Side intensity
64
Popularity
70
Side-by-side
Field
Left
Right
Category
Healing
Healing
Half-life
~4 hours sub-q
~2-3 days
Route
Subcutaneous (oral for gut)
Subcutaneous or intramuscular
Schedule
Daily
Loading 2x/wk → maintenance 1x/wk
Cycle length
4-6 weeks on, 4 weeks off
8-12 weeks total
Dose
200-500 mcg sub-q daily, ideally injected near the injury site.
Loading: 2-2.5mg twice weekly for 4-6 weeks. Maintenance: 2-2.5mg weekly for 4-8 weeks.
FDA
Not FDA approved for any indication.
Not FDA approved for any indication.
WADA
Banned (S0 – Non-Approved)
Banned (S2)
Natty?
Not natty
Not natty
Prescribed
Not prescribed in conventional medicine. Some compounding pharmacies and longevity clinics offer it off-label.
Not prescribed in conventional medicine.
Top side effects
Mild injection-site irritation; Lightheadedness in first few doses; Transient appetite changes
Mild fatigue during loading; Injection-site soreness; Brief head-rush at injection

Which one should you pick?

Pick BPC-157 if lifters with nagging tendon or joint pain or anyone recovering from a soft-tissue injury.

Pick TB-500 if anyone with a chronic soft-tissue injury that won't resolve or lifters running bpc-157 for synergy.

Note: these two are commonly stacked together rather than chosen between. See the entries for the canonical protocol.

Full entry
№ 001 BPC-157 →
Full entry
№ 002 TB-500 →