KitchenCalc / guide

Tell us what would make the kitchen easier

Questions, corrections, and thoughtful feature requests are welcome.

Kitchen tools improve when real cooks point out the awkward edge cases. If a label is unclear, a conversion assumption needs explaining, or a calculator would save you time every week, send a note. KitchenCalc is built for practical cooking rather than abstract math, so examples from your actual recipe are especially helpful. Include the units, ingredient, and result you expected when you are reporting a possible issue.

This site does not have a server-side email form. The contact form below prepares a message in your device’s default email application using a mailto link. You can review the recipient, subject, and message before sending. If the email application does not open, use the plain email link instead. No message is stored by this static website, and no account is needed to contact the project.

Feature requests are easiest to evaluate when they describe the cooking decision, not only the name of a new calculator. For example, tell us whether you need a yeast conversion by type, an air-fryer adjustment by temperature, or a storage guide organized by food and refrigerator time. The planned tools list reflects the kinds of requests that fit the site’s free, focused direction.

For urgent food-safety questions, consult a qualified local authority or current public-health guidance rather than relying on a general calculator. KitchenCalc can help with measurements and arithmetic, but it is not a substitute for professional advice. We read feedback for clarity and usefulness, and we may use general suggestions to improve the public tool without publishing personal details.

Send a note

This static site does not send email directly. Submit below to open a ready-to-review message in your email app, or use hello@kitchencalc.example.

Uses your email app because this static site does not send email directly.

Reference table

Best messageWhat to include
Bug reportPage, input values, expected result, and what appeared.
Feature requestThe cooking decision the tool should support.
CorrectionSource, unit system, and why the current value seems wrong.
General noteThe recipe context and your preferred units.

Worked example

Example: “On the cups-to-grams page, I selected rolled oats, entered 2 cups, and expected the result to explain that 90 g per cup is ingredient-specific.”

Frequently asked questions

Does the contact form send email?

It opens your email app with a prepared mailto message. The static site itself does not send or store messages.

Can I suggest a new calculator?

Yes. Explain the use case, units, and any regional differences you want the tool to handle.

Related KitchenCalc tools