Bad Cook Club
Bad Cook Club turns whatever sits in your fridge into a single AI-generated recipe, shaped by three quick constraints: cooking time, appetite and dietary needs. Free, no account required — but the generator no longer works.
What is Bad Cook Club?
Bad Cook Club is a single-purpose web app that turns a list of ingredients into an AI-generated recipe. Its name is its pitch: the opening screen asks bad at cooking? and answers join the club.
The whole product is four questions across five screens, one button each. You type what you have, in a field that seeds itself with a random example drawn from around seventy-eight pre-written combinations such as Beef, Onion, Red Wine, Garlic, Tomato Sauce. You pick 10, 20 or 30 minutes. You pick a filling portion or a lighter one. You add any dietary constraint in free text, with vegetarian, gluten free... offered as the example. The browser then assembles a single instruction along the lines of i have {ingredients}. Create a new {duration} recipe {appetite}, {constraints}. and sends it to a serverless endpoint.
The output format is dictated to the model rather than left open, and that shapes the result more than anything else: a title, a description under ten words, an ingredient list with no quantities at all, and instructions as separate lines of under forty words each, capped at 250 tokens. You get a plausible dish and a sequence of steps, but no amounts, no temperatures and no per-step timings — an odd omission for a tool that names beginners as its audience.
A second page gathers the last five hundred recipes generated by everyone who has used the site. There is no sign-up, no account, no payment and no announced usage limit. The footer holds one link, to a weekly newsletter.
The build is a client-rendered React and Vite application, and generation ran through a serverless function calling OpenAI — established by the error the site's own endpoint returns.
As of 11 August 2026 the tool does not work. The generation endpoint answers with an HTTP 500 carrying the provider message You have no credits remaining, reproduced twice, and the database behind the recipe gallery no longer resolves: it has been deleted, not merely interrupted. The site still loads and says nothing about any of this. The domain was registered in February 2023 and runs until February 2027.
What it does
- Generate an original recipe from a free-text list of ingredients
- Constrain the result to 10, 20 or 30 minutes of cooking
- Choose between a filling portion and a lighter one
- Add dietary constraints such as vegetarian or gluten-free
- Return a title, a short description, an ingredient list and step-by-step instructions
- Browse recipes generated by other visitors
- Subscribe to a weekly newsletter
When to use Bad Cook Club / When not to
A quick filter to help you decide if Bad Cook Club is the right fit.
When to use Bad Cook Club
- Home cooks staring at a half-empty fridge with no idea what to make
- Students on a tight budget who cook from whatever is already in the cupboard
- Anyone who wants a meal idea in under thirty minutes without trawling recipe blogs
- People who refuse to create yet another account just to get one suggestion
- Readers who enjoy a blunt, self-mocking tone rather than earnest food writing
When not to use Bad Cook Club
- Anyone who needs a working tool today, since recipe generation is currently down
- Cooks who need quantities, temperatures or yields, all of which the output deliberately omits
- People managing allergies or medical diets, as nothing checks that the recipe respects what was entered
- Professional kitchens and anyone planning menus at scale
- Businesses and privacy-conscious users, given that the site publishes no terms, no privacy policy and names no operator
How to use Bad Cook Club
A typical end-to-end flow, from setup to results.
- Open the site — there is nothing to install and no account to create
- Start the flow from the opening screen
- Type the ingredients you actually have into the free-text field; leaving it empty triggers a scolding alert
- Pick a cooking time of 10, 20 or 30 minutes
- Choose a filling portion or a lighter one
- Add dietary constraints in free text, or leave the field alone
- Trigger the generation and wait a few seconds
- Read the result: title, description, ingredients, steps
- Run through the flow again for a different recipe, as there is no way to save one
- Open the recipes tab to browse what other visitors generated
Pros & Cons
Pros
- Completely free, with no account, no card and no sign-up wall
- Extremely short path: four questions and nothing optional to configure
- Starts from what you already own rather than from a recipe catalogue
- Takes both available time and dietary constraints into account
- Distinctive, self-mocking voice that is rare in this category
- Asks for no personal data and shows no cookie banner
- Public gallery lets you judge the output before typing anything
Cons
- Recipe generation is down: the endpoint returns an error and the model provider's credits are exhausted
- The recipe gallery has lost its database and can no longer display anything
- No ingredient quantities, by deliberate design of the format requested from the model
- No temperatures and no per-step cooking times
- Output capped at 250 tokens, so recipes are very short and unsuited to anything elaborate
- Crude and self-contradicting appetite control, offering over 500 against under 600 calories
- No terms, no privacy policy, no contact and no identifiable operator
Pricing & Plans
The tool is entirely free. There is no pricing page, no paid tier, no payment path and no account to create, so there is no lowest price point to quote and no free trial to begin. No usage limit is advertised. The weekly newsletter linked in the footer is likewise free.
Data, GDPR & hosting
A consolidated view of how Bad Cook Club handles your data.
GDPR overview
There is no mention of the GDPR anywhere on this site — none at all. It publishes no privacy policy, no cookie banner and no consent mechanism. It names no data protection officer, no Article 27 representative in the European Union and no contact address of any kind. No data processing agreement is offered and no list of sub-processors is published, although the code reveals four in use: OpenAI for generation, a hosted database for storage, Vercel for hosting and analytics, and beehiiv for the newsletter. Technical traces point to United States infrastructure. For a visitor in the European Union this means no stated legal basis, no retention rule, no stated right of access or erasure, and nobody to address a request to.
Who owns the data?
No terms and conditions, no privacy policy and no legal notice exist anywhere on this site, so ownership of what you type and what you receive is simply undefined. No company, person or postal address is named, and there is no account, so nothing is tied to an identity. What the published code does show is this: the ingredients you entered were sent through the site's own serverless endpoint to OpenAI, and each generated recipe was written into a third-party hosted database and then displayed publicly on the site's recipes page. That is observable behaviour, not a commitment made by anyone.
Reuse rights
Nothing on the site grants or restricts reuse. With no terms of service there is no licence, no attribution requirement and no stated limit on what you may do with a generated recipe. In practice the results were treated as public: every recipe was stored and republished in the site's own gallery for anyone to read, without warning and without any way to opt out. Treat the output as unowned and unwarranted — usable in all likelihood, but backed by no permission and no guarantee from anyone.
Data retention & training
Hosting summary
The site states nothing about where data is hosted: no country, no region, no provider, no residency commitment and no choice of location. Everything that follows is inferred from technical traces rather than declared by the operator. The domain resolves to an address geolocated in the United States, on an anycast range consistent with a Vercel front end, and the page loads Vercel's analytics script. Generated recipes were written to a hosted database project whose region was never published and which has since been deleted. Generation itself was delegated to OpenAI, whose infrastructure the site does not document. In short, the operating jurisdiction appears to be the United States, but none of it is committed to in writing and there is no mechanism to request a different region.
Things to keep in mind
Risks and trade-offs to weigh before adopting Bad Cook Club.
- The tool is out of service and nothing on the site says so: you can complete the entire flow and simply get nothing back
- No operator is identifiable — no company, address, email or form — so there is no one to contact and no recourse of any kind
- No terms, no privacy policy, no mention of the GDPR and no stated minimum age
- Generated recipes were published on a public page without prior warning, carrying whatever text had been typed in
- Dietary constraints are passed to the model but never verified, a real hazard for anyone with an allergy
- A recipe with no quantities and no temperatures invites a beginner to improvise on food safety, which is precisely where beginners get hurt
- Treating a generated recipe as nutritional or medical guidance would be a mistake: it is a text prediction, not advice
Setup & Integrations
Technical difficulty
None. There is nothing to install, nothing to configure, no API key to supply and no account to create — a browser is enough, though JavaScript is mandatory since the application renders entirely on the client. The flow is four guided questions, so there is no learning curve at all. One caveat outweighs all of this: with the generation service no longer responding, no amount of correct setup produces a result.
Deployment
Supported languages
Behind Bad Cook Club
Resources
All the official URLs gathered for verification and reference.
Frequently asked questions
What does Bad Cook Club do?
Do I need an account?
Is it free?
Does the tool still work?
Which AI model does it use?
Do the recipes include quantities?
Can I specify an allergy or a diet?
Are my recipes private?
Who runs the site?
Is there a mobile app or a public API?
Should you pick Bad Cook Club?
Bad Cook Club had a good idea and knew exactly how small it wanted to be. Starting from the fridge rather than from a catalogue is the right instinct, and the execution matched it: four questions, nothing optional, no sign-up wall, and a voice with more personality than most of this category manages.
The limits were built in from the start. Capping the model at 250 tokens and explicitly forbidding quantities produces something that reads like a recipe without being usable as one — no amounts, no temperatures, no timings. For a tool that names bad cooks as its audience, that is a strange place to economise. The appetite control never quite made sense either, offering a choice between over 500 and under 600 calories.
What settles it is that the tool no longer runs. The generation endpoint returns an error saying the model provider's credits are exhausted, and the database that fed the public gallery has been deleted outright. Neither is a passing outage, and the site tells visitors none of it: the questions still appear, the button still waits, and nothing comes back.
Behind it all there is nobody to ask. No company, no name, no address, no email, no terms and no privacy policy — while the recipes people generated were quietly published on a page anyone could read.
Read it as what it is: a 2023 side project, competently built and cheaply abandoned, whose shopfront stays lit because the domain is paid up until February 2027 and the newsletter still answers. Worth a look as a design sketch. Not worth sending anyone to as a working tool.
- Choosing a selection results in a full page refresh.
- Opens in a new window.