Get in touch.

What we can help with

Most messages fall into one of four categories. Bug reports — if a conversion gives you a wrong number, or the tool breaks on a specific input, tell us exactly what you entered and what you expected to see. Feature requests — we're always looking for gaps: missing units, unsupported ingredient types, or workflow improvements that would make the tool more useful. Conversion questions — sometimes a recipe uses an unusual unit (a "wineglass" of cream, a "knob" of butter) that the tool can't handle directly; ask and we'll point you in the right direction. Partnerships — if you run a food publication or app and want to discuss embedding the converter, use the Other subject line and give us a brief overview of what you have in mind.

Response time

We typically reply within one to two business days. Bug reports with clear reproduction steps get prioritized — the faster we can reproduce the issue, the faster it gets fixed. Feature requests go into a running backlog; we may not respond to every one individually, but we read them all and they genuinely shape what gets built next.

What to include in your message

A few details that speed things up considerably:

• —For bugs: the exact ingredient text you pasted, the scale factor you used, and the output you got versus what you expected.
• —For conversion questions: the original recipe line, the ingredient name, and whether you're converting for cooking or baking — precision matters more in baking.
• —For feature ideas: the specific use case, not just the feature name. "I make a lot of bread" is more useful than "add a bread mode."