Frequently Asked Questions

HowManyCookies is more than a recipe collection. It is a shared kitchen for finding and sharing recipes, preserving changes through Recipe Git forks, planning meals, and learning with other cooks through Blogs, Forums, community feeds, and Galleries.

You can browse public recipes, articles, discussions, policies, and FAQs without contributing. An account is needed for personal and community features such as saving recipes, creating forks, posting, messaging, Kitchen Houses, menus, calendars, and shopping lists. Create an account or sign in.

Start with the Recipe Book if you want something to cook. Visit the Blog to learn, the Forum to discuss techniques and substitutions, or the community feed to see what other cooks are sharing. If you get stuck, return to this FAQ or contact Customer Service.

A fork is a new recipe version connected to its starting recipe. It lets you change an ingredient, method, temperature, or timing without overwriting the original. Recipe Git keeps the lineage and records why the new branch exists. Browse recipes in the Recipe Book.

No. A fork creates a separate recipe branch. The original stays intact, while the fork records its own ingredients, directions, notes, commits, and future changes. Private or restricted recipes keep their access boundaries.

A commit is a saved checkpoint with a note explaining what changed. History makes experiments understandable: you can compare versions, follow the fork lineage, and decide which changes belong in your kitchen instead of guessing from a rewritten recipe.

It means the recipe does not yet have a reliable serving or batch quantity. HowManyCookies leaves scaling disabled when the yield is unknown so it does not pretend to calculate dependable amounts. Once a useful yield is confirmed, the recipe owner can record it. Sometimes a little mystery is part of the recipe. ;)

A tested label means the contributor represents that they physically prepared that version. It is not an independent guarantee from HowManyCookies, and an untested recipe is not automatically unsafe or bad. Read the complete recipe, its fork changes, and the Recipe & Food Safety policy before cooking.

The Bench is your working area for promising recipes. Save recipes there while deciding what to cook, testing an idea, or organizing a future menu. Open your Bench.

Build a menu in Menu Maker, place it on the Menu Calendar, then synchronize its ingredients with your Shopping List. You can edit and print the list before heading to the store.

A Kitchen House is a shared workspace for cooks who plan together. Its owner can invite collaborators to organize recipes, Bench work, menus, calendar assignments, and shopping tasks. Access and visibility remain limited to the people allowed into that Kitchen House. Open Kitchen Houses.

Use the Blog for longer explanations and stories, the Forum for focused discussions, the community feed for updates, and the Gallery for useful cooking images.

Your profile can show your display identity, selected profile answers, public recipes, Gallery albums, Blog posts, and community activity. Availability depends on your account and the visibility chosen for each feature. Review your profile fields in Edit Profile and account choices in Preferences.

Following helps you keep up with another cook’s public activity. Buddies are a mutual connection. Messages are private conversations between permitted members. Respect privacy: do not repost someone’s private message or restricted content without permission.

HowManyCookies uses a session cookie to keep visits and signed-in accounts connected, an optional remember-me cookie, and local browser storage for consent and interface preferences. Read the plain-language Cookie Policy and Privacy Policy for details.

No. Tags and notes are contributed information, and ingredients or manufacturing practices can change. Check packaging, account for cross-contact, use safe temperatures and storage, and consult a qualified professional when a medical or dietary need matters. Read Recipe & Food Safety.

First check this FAQ for the quickest answer. If you need a person, submit a ticket through Customer Service. Keeping the question in a ticket preserves replies, status, and history in one place.

Use the report or flag control beside the content when one is available. For account, privacy, security, or technical concerns, contact Customer Service. For urgent medical or safety emergencies, contact the appropriate emergency or professional service instead of waiting for a site reply.