About ForkChop

Most recipe apps ask what you want to eat. ForkChop asks what's in your kitchen and finds things you can cook right now, plus things you're only one or two ingredients short of. Missing the parsley is different from missing the chicken, so it treats them differently.

• Free-text resolution. Type “2 chicken breasts”, “cilantro”, “tomatos” — a staged parser turns each into a canonical ingredient, tolerating amounts, plurals, dialect swaps and typos.
• Ingredient importance. Each recipe ingredient is tagged core, normal or optional. Missing a core ingredient sinks the match; missing a garnish barely moves it.
• Staples are assumed. Salt, oil, water and a handful of others are never reported as missing.
• Strict allergen filter. A recipe containing a flagged allergen — even in an optional garnish — is removed entirely.
• Local first, then wider. A hand-curated corpus is searched first; Spoonacular only when the local results are thin. External recipes flow through the same filters and ranking as local ones.

• A payment processor. Checkout hands off to the store's own site.
• A medical or nutrition tool. Allergen filtering is a convenience over ingredient data, not a substitute for reading a label.
• A social network. There are no follows, no comments, no public profiles.
• An advertising business. There are no ads, no third-party trackers, no data sales.

Next.js and TypeScript, Supabase for accounts and data, Tailwind CSS for the design. Deployed on Vercel. The recipe corpus is bundled with the app; wider search uses Spoonacular, barcode lookups use Open Food Facts. Voice input uses the browser's built-in speech recognition — no third-party service is contacted through us.

Signed out, your pantry stays in your browser. Signed in, it's stored against your account and protected by row-level security. We don't use analytics or advertising trackers. The privacy policy is short and code-accurate.