Photo vs No Photos: What Works Best on Digital Restaurant Menus
Photos help most on a digital menu when a dish is unfamiliar, hard to describe or worth upselling, and they hurt when the image is poor, doesn't match the plate that arrives, or makes the page slow to load. For most restaurants the best answer is neither all photos nor none: it is a few good photos on the items that benefit, and clear, appetizing text for everything else.
This guide walks through the real trade-offs, offers a simple way to decide item by item, and gives practical advice on shooting and sizing photos for phone screens. It is general design guidance. Whether a given platform supports dish photos, and how, is something to confirm with your provider before you plan your shoot.
When photos on a digital menu help
Photos earn their place when words struggle. A dish with a local or regional name that a visitor has never heard of, a cuisine that is new to many of your guests, or a plate whose presentation is the point (a sharing platter, a layered dessert, a cocktail with a garnish) all become clearer in one glance. In a city that welcomes visitors from many countries, a picture can answer the question a guest would otherwise ask the waiter.
They can also support upselling. A guest scrolling past a photographed dessert or shared starter is more likely to notice it than a line of text among thirty others. The picture acts like a small display window: it draws the eye to the items you most want to sell, especially high-margin ones.
Photos can also cut repeated questions about what a dish looks like, how big the portion is or what comes on the side, freeing your team for actual service.
When photos hurt more than they help
A bad photo is worse than no photo. Dim, yellow, blurry or obviously stock images signal carelessness and make the dish look less appetizing than a good description would. If you cannot take or commission a decent picture, leave the item as text.
The photo must also match what arrives. If the menu shows a generous, artfully arranged plate and the kitchen sends something smaller and plainer, the guest feels misled, and that disappointment sticks to the whole meal. Photograph the dish as your kitchen actually plates it on a normal busy evening, and re-shoot when the recipe or the plating changes.
Speed matters too. Large images make a page slow on mobile data, especially in a busy dining room where many phones share the same signal. A guest staring at a blank screen may give up and ask for paper. And in fine dining, photos can flatten a menu whose appeal is restraint and discovery, where a well-written description does more than a picture.
Deciding item by item
Rather than debating the whole menu, sort dishes into three groups. The first group needs a photo: signature dishes, unfamiliar items, sharing plates and anything you want to push. The second could use one: dishes with a strong visual identity that you can photograph well. The third stays text-only: familiar staples, simple drinks, sides and anything that changes weekly.
Consistency matters more than volume. A menu with twelve well-lit photos in the same style feels considered; a menu with photos on a third of the items, each shot differently, feels patchy. Use the same light, angle, background and crop across the set, and add photos gradually as you can take them to the same standard.
A text-only menu is a legitimate choice, not a compromise. Good descriptions that name the main ingredients, cooking method and flavor do a great deal of work, and they load instantly.
Shooting and preparing photos for phone screens
You do not need a studio. Window light, a plain table as background and a modern phone camera are enough. Shoot from straight above for flat dishes such as pizza and salads, and from a slight angle, roughly the height of a seated guest's eyes, for anything with height like burgers or desserts. Shoot the plate as served, without props that will not appear at the table.
Then shrink the files. A photo straight from a phone camera can be several megabytes, far more than a small phone screen needs. Resize images to roughly the width they will be displayed at, save them in a compressed format such as JPEG or WebP, and aim to keep each one well under a megabyte, and often much smaller. Use the same aspect ratio for all photos so the layout doesn't jump around as images load.
Always test on a real, mid-range phone over mobile data, not just on your office wifi. If the menu feels sluggish there, your photos are too heavy or there are too many of them on one screen.
Checking what your platform supports and whether it works
Before planning any shoot, confirm with your provider whether the platform supports dish photos, how many images per item it allows, how they are stored and delivered, and whether they load progressively. Do not assume that every QR menu tool handles images the same way. If you are considering ChargeM3, ask the team directly about image options for your menu.
Once you have photos live, watch the results instead of trusting instinct. ChargeM3's analytics dashboard shows order trends and best-sellers, so you can see whether items you changed are selling differently over a few weeks. Combined with easy menu updates, which let you add, edit or remove items in minutes, you can treat the menu as something to refine gradually rather than a fixed document.
Frequently Asked Questions
Should a digital restaurant menu have photos?
It depends on the dishes. Photos help with unfamiliar dishes, sharing plates and items you want to upsell, but they hurt when the image quality is poor, when the plate doesn't match the picture, or when they slow the page down. A mix of a few excellent photos and clear text elsewhere works for most restaurants.
Do photos make a QR menu load more slowly?
They can. Large image files take longer to download on mobile data, especially when many guests share a weak signal. Resizing images to the size they are displayed at, compressing them and limiting how many appear at once keeps the menu fast.
Should fine-dining restaurants use photos on their digital menu?
Often not. Fine dining tends to rely on restraint, surprise and well-written descriptions, and photos can give away the plate or feel out of tone. Text only, or one or two carefully shot images, usually suits the atmosphere better.
How large should menu photos be?
Resize each photo to roughly the width it will appear at on a phone, compress it as JPEG or WebP, and keep the file well under a megabyte, often much smaller. Use the same proportions for all photos so the layout stays stable. Test on a mid-range phone over mobile data.
Does every QR menu platform support dish photos?
No, support varies between providers. Before planning a photo shoot, ask your provider whether dish photos are supported, how many per item are allowed and how they are delivered to the guest's phone.
Ready to modernize your restaurant?
See a live demo of the menu experience or check the full pricing details.
Questions? Get in touch
[email protected] · +359 88 401 1730 · Sofia, Bulgaria
Related articles
- Restaurant Menu Design Psychology: Colors, Layout, and SalesPractical menu design principles for colors, contrast, hierarchy and highlighting, with honest limits on what design can and cannot do for sales.
- Restaurant Menu Planning 101: Step-by-Step for BeginnersA beginner-friendly, five-step guide to planning a restaurant menu, from concept and kitchen limits to costing, layout and testing with real sales.
- How Restaurant Menu Design Affects Customer Ordering DecisionsWidely used menu design ideas, from visual hierarchy to price anchoring, and how a digital menu lets you adjust them in minutes.
Read this article in Bulgarian