Peptide guides

The guides published here all sit at the intersection of math and workflow: how to reconstitute a vial without making unit errors, how to convert a dose between milligrams and syringe units, and how to keep an honest log of doses, vials, and outcomes over time.

What the guides explicitly do not cover is medical advice. There are no protocol recommendations, no efficacy claims, no 'best peptide for X' rankings, and no suggestions about who should or shouldn't use any particular molecule. Those decisions belong with a qualified clinician — the guides exist to make sure that whatever decision is made, the math and the logging behind it are clean.

Each guide is written in plain English, with worked examples where the math gets dense, and a set of FAQs at the bottom that address the questions most newcomers hit on day one. None of the guides assume prior pharmacology knowledge.

Every guide opens with a quick-answer box — a one or two sentence summary you can read in five seconds and walk away with the gist. Below that is a 'last updated' date so you know how recent the content is, then the long-form body.

The body is organized into short, anchored sections so each heading is something you can link directly to. If a friend is stuck on the units conversion, you can send them the section anchor instead of the whole article.

FAQs sit at the bottom of every guide and double as Schema.org FAQPage data, which means search results often surface them directly. The questions are real ones from forums and emails, not synthetic SEO bait.

Guides are for the first time — when you're trying to understand why the math works the way it does, what a unit on a syringe actually represents, or how to label a vial so future-you doesn't have to redo any of the arithmetic.

Calculators are for the hundredth time — when you already understand the math and just want a clean number for today's dose. The four calculators on this site each take the same underlying formulas and present them with different inputs, depending on what you already know.

Most people bounce back and forth: read a guide, run the math in the matching calculator, save the resulting unit count to the vial label, then never re-derive it for the rest of the vial's life.

Peptide Pilot, the iPhone app behind this site, is built around the same primitives the guides describe: vials with a fixed concentration, doses logged against a vial, sites rotated automatically, and a weekly summary that surfaces what changed.

Reading a guide is enough on its own — there is no upsell hidden in the body copy. But if you find yourself opening the same calculator three times a week and writing the result on a sticky note, that's the moment a tracking app starts to pay for itself in saved time and fewer forgotten doses.

Every guide ends with the same offer: keep using the calculators and guides for free, or move the recurring math into the app so it's done once and reused forever. Both paths are first-class.

Start with the reconstitution guide. It establishes the vial, the diluent, and the concentration you'll be working with for everything else, and it walks through the worked example most people will reuse for their own vials.

Move next to the milligrams-versus-units guide. It explains why two people on the same dose can see different numbers on their syringes, and it makes the unit conversion second nature so the calculators feel like a sanity-check rather than a black box.

Finish with the tracking guide. By this point you've done the math; the question becomes how to keep doing it without redoing it every week. The tracking guide explains the workflow that makes the math disappear into the background.

There are no protocol templates anywhere in the guides. No 'starter cycles,' no 'best stack for fat loss,' no week-by-week dose ramps. Those are clinical decisions, and even the very best plain-English explanation of one is still a clinical decision dressed up as content. Putting them in a guide would actively harm readers, so they are simply not here.

There are no efficacy claims either. The guides do not say a peptide will work, will produce a specific result, or will outperform another peptide. The math layer the guides cover is real and useful; predictions about biological outcomes belong with the people who can examine you in person and review your full history.

Lastly, there are no rankings of suppliers, brands, or sources. Pointing readers toward a particular vendor would be both irresponsible and a moving target. The guides stay focused on the parts that do not change with the supplier — the units, the formulas, and the workflow.

Every guide carries a 'last updated' date at the top. When the underlying math, the supplies people commonly use, or a piece of frequently-asked terminology shifts in a meaningful way, the guide is rewritten and the date moves forward. Older revisions are not preserved publicly, because for a 'how the math works' page the goal is one canonical current version rather than a changelog.

Reader feedback drives most updates. When the same question shows up in three different emails or forum threads, that is a signal that the guide is missing a section, and a fresh block is added. The FAQs at the bottom of each guide are explicitly seeded from real questions, not from search-term lists.

If something in a guide reads as wrong, ambiguous, or out of date, the support email in the footer is the fastest way to flag it. Corrections that hold up to a quick fact-check usually land in the next revision within days, not weeks.

Every guide on this site is published as plain-English education about peptide math and tracking workflow. None of it constitutes medical advice, a diagnosis, a treatment plan, or a recommendation for any specific peptide, dose, frequency, or supplier. Decisions about whether a peptide is appropriate for any particular person belong with a licensed clinician who can review that person's full medical history.

The forbidden-verb list is enforced editorially. Words like 'recommend,' 'prescribe,' 'safe,' 'cure,' and 'treat' do not appear in any guide because each one implies a clinical judgement the site is not in a position to make. When you see those words missing in a place where they would feel natural, that is on purpose — the math holds up regardless of whether a particular use case is appropriate.

Every guide also closes with the same disclaimer block linking to the full health disclaimer and terms of use. Reading that block once is worthwhile context for everything else on the site. Nothing about the calculators or the tracker overrides clinical judgement; they are tools that take the friction out of the math so the conversations with a real professional can focus on the parts that actually matter.

The single most useful piece of feedback is 'this section was confusing because…' followed by a concrete example. Vague feedback is hard to act on; specific feedback usually leads to a same-week edit. The support email in the site footer routes directly to the people who write the guides.

Suggested topics for new guides also land through the same channel. The current backlog is shaped by which questions show up most often, so flagging a recurring confusion in a forum or in conversation is one of the fastest ways to influence what gets written next.

Finally, if a calculation result on the site does not match a result you trust from another source, the discrepancy itself is the most valuable thing you can send. Two calculators returning different unit counts for the same inputs almost always means one of them is making an assumption the other is not — and surfacing that assumption is exactly what makes the next iteration of the guide more useful for everyone.

The guides on this hub and the per-peptide reference pages under /peptides cover overlapping territory on purpose. A guide explains a concept once, in plain English, with the assumption that the reader has not seen it before. A reference page applies that same concept to a single molecule, with the assumption that the reader has a vial in front of them and wants the math worked out for that specific product. Reading both is rarely redundant — the guide builds intuition, and the reference page collapses that intuition into a few seconds of arithmetic.

Where a guide and a reference page would otherwise repeat the same sentence verbatim, the reference page links back to the guide instead. That keeps the per-peptide pages focused on what is genuinely peptide-specific — the typical vial size, the typical dose, the common reconstitution mistakes for that molecule — rather than re-deriving the unit-conversion formula on every page. The same pattern works in reverse: when a guide needs an example, it points at a representative reference page rather than inventing a hypothetical vial.

If you find yourself reading a guide and wishing it had more concrete numbers, the right next click is almost always a reference page. If you find yourself reading a reference page and wishing it explained the math more slowly, the right next click is almost always the matching guide. The cross-links at the bottom of every page exist for exactly that round-trip.