A coffee roast timer tracks roast time milestones—start, first crack, and drop—so you can repeat a great batch on purpose.
You’re halfway through a roast, listening hard, and first crack finally starts—then your phone buzzes, you glance away, and suddenly you’re guessing when to drop. A roasting timer fixes that kind of “lost moment.” Not by turning roasting into spreadsheets, but by capturing a few high-leverage timestamps (start, first crack, drop) so you can repeat what worked—and change what didn’t—on the very next batch.
What a coffee roasting timer really tracks
A timer makes the key moments repeatable. Time the milestones you can act on, then change one thing next roast.
The three phases you’ll time (drying, Maillard, development)
Most roasts move through drying (green → yellow), Maillard/browning (sweet aromas build), and development (first crack → drop). That “post-crack” window is why many timers emphasize it (stages of coffee roasting).
Milestones worth a button press (first crack, second crack, drop)
- Start: when the roast begins (charge/start, based on your setup).
- First crack: the first steady pops you’re confident about.
- Drop: when you end the roast and start cooling.
Rule of thumb: if first crack is fuzzy, mark it when it’s clearly rolling, then note “1C faint.”
Your timer isn’t grading your roast—it’s giving you a clean “before/after” so tasting notes mean something.
Set up your timer before you charge the beans
Great timers feel boring mid-roast because you decided the basics up front. Pick a simple “drop idea” before heat starts—then you’re free to listen and steer.
Many tools use the same workflow—Start → First Crack → Drop—then show quick math like development % (free roasting timer tool). If you roast a lot, that same log can live in coffee roasting software like Cropster, Roastu, or Roastabout.
What to pre-fill (60 seconds)
- Coffee: name/origin.
- Batch: green weight.
- Target: light / medium / darker.
- Notes: where you’ll log one tasting line.
The “lap button” backup method
- Single tap: press once and keep roasting.
- Label it: note “late tap” if you’re unsure.
- Use confidence: mark 1C when pops become steady.
Heat safety: Keep cords, sleeves, and hands away from hot surfaces and moving parts.
Roast Timer Calculator (Start → First Crack → Drop)
Keyboard: Tab, then Enter/Space. “Mark” enables after Start.
Ready. Press Start, then mark First Crack and Drop.
Timing milestones during the roast (without overthinking it)
Your job is to roast—not babysit the clock. Tap once, keep moving, and write a two-word note if the moment was messy.
What to do when first crack is faint or delayed
If you hear a single “pop,” wait. When pops become steady, mark first crack and keep your focus on aroma and pace.
Quick sanity checks (interruptions, noise, missed taps)
| Milestone | What you notice | What you tap | Why it matters |
|---|---|---|---|
| Start | Beans hit heat; roast is underway | Start | Total time anchors every comparison |
| First crack | Pops become steady; aroma lifts | Mark First Crack | Starts the development window |
| Drop | You end roast and begin cooling | Mark Drop | Sets development time + DTR |
Development time ratio (DTR): the one number most timers optimize for
DTR (sometimes called RDT) is the share of roast time that happens after first crack. It’s a guardrail—then you let taste decide. Use DTR to stay consistent, not to chase perfection.
How to calculate DTR in 10 seconds
DTR = (Drop − First Crack) ÷ (Drop − Start) × 100. The math stays the same even when your targets change (calculate DTR percentage (2026)).
Quick example: Start 0:00, First Crack 8:30, Drop 10:30 → development 2:00 → DTR ≈ 19%.
Picking a starting target (light vs. medium)
Pick one target range for a week, then adjust by taste. A commonly discussed benchmark is to avoid development running too short or too long as total roast time shifts (Rao’s DTR benchmark).
Too short (often)
- Sharp: sour-leaning, thin acidity.
- Green: grassy/pea-like finish.
Too long (often)
- Flat: muted acidity; “brown” flavors dominate.
- Dry: papery or ashy bitterness.
Turn your timer notes into repeatable roasts
The timer becomes powerful when you pair it with what it tasted like. Write one tasting line, then make one timing change—that’s how you learn fast.
A simple roast log (what to keep, what to ignore)
Keep the basics: coffee name, batch weight, Start/1C/Drop, dev time, DTR, and one tasting note. Paper, spreadsheet, or roasting software—same fields.
| Date | Coffee | Green (g) | Start | 1C | Drop | Dev | DTR | Tasting note |
|---|---|---|---|---|---|---|---|---|
| — | — | — | 0:00 | — | — | — | — | Example: sweeter; next time drop 10–15s sooner |
| — | — | — | 0:00 | — | — | — | — | — |
Troubleshooting by taste (tie it back to timing)
- Grassy/sour: try a slightly longer development or slow the roast a touch before 1C.
- Ashy/dry: drop earlier and cool faster.
Advanced notes (keep this out of your main workflow)
If you later add probes or curves, keep these milestone timestamps anyway. If you’re using Cropster Roasting Intelligence, map its markers to the same Start/1C/Drop moments for clean comparisons.
