While most restaurants focus on perfecting recipes, they often ignore how those dishes should actually look on the plate. The result? Your signature risotto looks completely different depending on who's cooking that day. Visual recipe documentation transforms inconsistent plating into reliable presentation standards.
Why presentation photos are crucial
Your chef makes a beautiful risotto. The next day your sous-chef makes the same dish, but it looks completely different. Different garnish, different portion size, different color. To the guest, it seems like a different dish.
⚠️ Note:
Inconsistent presentation costs you an average of 15-20% of your returning guests. They no longer know what to expect.
A photo and clear description in your recipe prevents these problems. Everyone knows exactly what the dish should look like.
Dishes that always need a photo
Signature dishes: Your top dishes that you're known for. These should always look the same.
- Best-selling main courses
- House specialties
- Seasonal dishes that return
- Dishes above €25 (guests expect more)
? Example:
Bistro The Golden Spoon has 3 signature dishes:
- Beef tenderloin with truffle sauce (€32) - photo + garnish description
- Sea bass with roasted vegetables (€28) - photo + plating arrangement
- Homemade ravioli (€24) - photo + sauce distribution
Result: every guest gets the same beautiful plate, regardless of who's cooking.
Complex dishes that need explanation
Dishes with many components: The more parts, the greater the chance of mistakes.
- Dishes with 5+ ingredients on the plate
- Composed salads
- Desserts with multiple elements
- Tapas and sharing plates
? Example:
Caesar salad with grilled chicken - without a photo things go wrong:
- How much chicken per plate? (150g)
- Where does the chicken go? (on top or to the side)
- How much dressing? (2 tablespoons)
- Parmesan shaved or grated?
With a photo everyone knows exactly how it should be.
Seasonal dishes and rotating menus
Dishes that are off the menu for a few months and then return always need a photo. Otherwise your team forgets what they looked like. After managing kitchen operations for nearly a decade, I've seen too many "returning favorites" become completely different dishes because nobody remembered the original plating style.
- Summer dishes with seasonal vegetables
- Winter stews
- Holiday menus
- Specials that return regularly
Desserts and appetizers
Desserts: Here guests expect perfection. A sloppy tiramisu or collapsed cake ruins the whole experience.
Appetizers: The first thing the guest sees. If this doesn't look good, they immediately think the rest won't either.
? Example:
Chocolate cake with red berries:
- Photo shows: 12cm slice, 3 raspberries, mint leaves
- Description: "Powdered sugar lightly dusted, not overdone"
- Sauce: "Coulis in drops around the plate, not over it"
This way every slice looks professional.
What you DON'T necessarily need to photograph
Not every dish needs a photo. Save time by skipping these:
- Simple dishes with 1-2 components
- Standard side dishes (fries, rice, salad)
- Soups (unless special garnish)
- Dishes you're removing from the menu soon
How to take good recipe photos
Timing: Photograph the dish right after it's plated, before it goes to the guest.
Lighting: Use daylight or good kitchen lighting. No flash.
Angle: Shoot from slightly above, the way the guest sees it when placed in front of them.
⚠️ Note:
Update your photos at least once a year. Dishes evolve and your presentation keeps improving.
Storing recipe photos digitally
Store photos digitally where everyone can find them. Not on someone's phone, but in a system the whole team can access.
Tools like KitchenNmbrs let you store photos directly with the recipe. That way everyone always has the right reference at hand.
Related articles
How do you determine which dishes need a photo?
Make a list of your dishes
Write down all the dishes on your current menu. Divide them into categories: appetizers, main courses, desserts. Also count how many components each dish has.
Determine priority per dish
Give each dish a score: signature dish (high priority), complex dish (medium), simple dish (low). Focus first on your top 5 best-selling dishes.
Plan photo sessions per week
Photograph 2-3 dishes per week during the quiet service. Start with your signature dishes and work your way down. Within a month you'll have all important dishes documented.
✨ Pro tip
Document your top 8 signature dishes with photos during your next slow Tuesday lunch service. You'll have 2 hours of uninterrupted time to perfect each plate and capture the exact presentation standards your team should hit every service.
Calculate this yourself?
In the KitchenNmbrs app you can do this in just a few clicks. 7 days free, no credit card.
Was this article helpful?
Frequently asked questions
Do I need to photograph all dishes?
How often should I update recipe photos?
Can I just take photos with my phone?
Where should I store the photos?
What if my team doesn't use the photos?
Should I photograph dishes that change seasonally?
How detailed should the written description be alongside photos?
What's the biggest mistake restaurants make with recipe photos?
kennisbank.ingredients_in_article
Sources consulted
- EU Verordening 852/2004 — Levensmiddelenhygiëne (2004) — Official source
- EU Verordening 853/2004 — Hygiënevoorschriften voor levensmiddelen van dierlijke oorsprong (2004) — Official source
- EU Verordening 1169/2011 — Voedselinformatie aan consumenten (2011) — Official source
- NVWA — Hygiënecode voor de horeca (2024) — Official source
- NVWA — Allergenen in voedsel (2024) — Official source
- Codex Alimentarius — International Food Standards (2024) — Official source
- FSA — Safer food, better business (HACCP) (2024) — Official source
- BVL — Lebensmittelhygiene (HACCP) (2024) — Official source
Food Standards Agency (FSA) — https://www.food.gov.uk
The HACCP standards shown in this application are for informational purposes only. KitchenNmbrs does not guarantee that displayed values are current or complete. Always consult the FSA or your local authority for the latest regulations.
Written by
Jeffrey Smit
Founder & CEO of KitchenNmbrs
Jeffrey Smit built KitchenNmbrs from 8 years of hands-on experience as kitchen manager at 1NUL8 Group in Rotterdam. His mission: give every restaurant owner control over food cost.
kennisbank.more_in_category
Related questions
Explore more topics
All your recipes in one place, forever
Recipes in heads, on notes, in folders — that doesn't work. KitchenNmbrs centralizes all your recipes with costs, allergens, and portions. Try it free for 14 days.
Start free trial →