Food Photos for Restaurant Email Campaigns
Restaurant email food photos should make one offer easy to understand on a small screen. Choose a real dish you currently sell, show the standard serving, and pair the photograph with a clear menu link and live text. A useful image does not have to show the whole menu or depend on AI editing.
Start with the email template your restaurant actually uses. Its content-block width, mobile stacking, and image handling determine the useful crop and pixel dimensions. There is no universal restaurant-email ratio, file-weight limit, or loading-time guarantee.
Choose the photograph around the campaign
Decide what the recipient should do before selecting images: view a seasonal dish, browse a catering menu, or reserve a table. Use one main photo as a starting layout, then add supporting images only when they help explain that offer.
| Placement | What to show | What to verify |
|---|---|---|
| Main offer | One actual dish or the complete advertised bundle | The serving and included sides match the offer text. |
| Supporting option | A relevant side, drink, or alternative | A paid add-on is labeled rather than implied to be included. |
| Catering or event image | The relevant tray or service format | The image and copy explain quantities and availability. |
Do not imply that a limited-time item is available after its end date. Ask the kitchen to confirm the current recipe and serving before capture; the seasonal photo workflow covers retirement as well as launch.
Size for the actual content block
A landscape image can keep the offer text near the main photo, while a square image may fit a supporting column. These are design choices to test, not email-client requirements.
For a block displayed 600 pixels wide, a 1200-pixel source is one possible high-density starting point. It can still look soft if the capture is blurred, and extra pixels can increase transfer size. A narrower mobile block may need less. Confirm the template's own recommendations rather than exporting every image at a fixed size.
Mailchimp's image recommendations distinguish its legacy 600-pixel templates from 660-pixel templates in the new builder. This is provider-specific guidance, checked 2026-10-10; it does not establish a maximum width for all email systems.
Judge the image by its pixel dimensions, displayed size, compression, and actual appearance. Changing a DPI metadata label alone does not make a web image smaller or sharper.
Separate slow images from Gmail message clipping
A heavy hosted image can load slowly, but its file weight is a different issue from the email's underlying message code. Mailchimp's Gmail clipping explanation says Gmail clips messages larger than 102 KB of message code. Reducing a remotely hosted JPEG alone does not prove that code is below the limit.
Use your email builder's preview and a received test message to check both concerns:
- Inspect the actual image file weight and its appearance after compression.
- Keep the message structure and live text concise; remove redundant copied formatting where appropriate.
- Confirm the footer, offer terms, and unsubscribe control remain available in the received email.
- Test with image downloads disabled. The dish name, offer, and action should still make sense.
JPEG is a practical starting format for photographic email assets. Check your provider and target clients before choosing another format. DishVivid downloads JPEG; it does not generate email HTML, JPEG fallbacks, or a guaranteed file size.
A five-step kitchen-to-email workflow
1. Photograph the advertised serving
Prepare the camera, light, and background before the dish arrives. Ask for the normal recipe, standard portion, included sides, and usual service vessel. Use soft side light and compare a raised angle with an overhead frame; choose the view that explains this dish.
Leave enough surrounding space for the intended content block, then test that crop. A fixed percentage of empty border cannot guarantee a fit for every template.
2. Make a restrained manual edit
Open a JPEG, PNG, or WebP up to 20 MB in DishVivid Studio. Manual brightness, contrast, saturation, and crop adjustments run in the browser and need no account. Try the stock sample first if you want to learn the comparison and download steps; the sample is not a customer case or AI demonstration.
Inspect pale plate rims and dark ingredients while making small adjustments. There is no dedicated manual white-balance, temperature, highlights, shadows, denoise, or sharpening control. Fix a strong color cast or missed focus at capture or in suitable external software rather than expecting these sliders to repair it.
3. Review any optional AI separately
AI is optional, requires sign-in and available edits, and can change food or scene details. Check your account and current pricing before generating. Each generated candidate uses an edit; this guide does not promise a free allowance or a successful payment.
Compare a candidate with the original and the real serving. Reject added garnishes, enlarged proteins, changed sides, or implausible sauce texture. Approve an accurate candidate before export. A prompt asking for fidelity is not proof that fidelity was preserved.
4. Download, then prepare the template asset
Complete the dish checks and download the JPEG. Original retains the selected image's dimensions; Delivery wide is 1600 × 900, Delivery classic is 1500 × 1200, and Social square is 1200 × 1200. These are editor choices, not email specifications.
If your template needs 1200 × 675 or another custom size, resize or compress in another suitable tool. Inspect the final crop and actual weight after that step. Keep the untouched capture separately and organize the approved export in your own photo library; manual downloads are not automatically saved to an account library.
5. Add text and test the destination
Add accurate alternative text in the email builder. For a linked image, consider its destination and any adjacent link text so the complete control has a useful accessible name. Alt text is not written into the email by DishVivid.
Link the image and a visible text button to the relevant menu item, menu category, or reservation page. Verify the destination on a phone in the state a recipient will see. The ordering system may require item options, sign-in, or additional checkout steps; do not promise one-tap checkout.
Hypothetical weekend-special layout
Suppose a bistro promotes its current pappardelle special. This is a planning example, not a customer campaign or measured sales result.
The operator chooses one landscape photograph of the standard pasta serving and writes the dish name, actual price, availability window, and a link to that item. A second square image shows an optional side with its separate price. Both photographs are reviewed against the kitchen's current preparation.
The team downloads a reviewed JPEG, prepares the custom template size externally, and sends itself a test. If the side block stacks awkwardly on mobile, it removes that block or changes the layout. No illustrative file size or sending time establishes how fast the recipient's email will load or whether an order will follow.
Common failures to check
| Failure | Practical correction |
|---|---|
| The plate becomes tiny in a wide table spread | Test a single-dish frame at the actual mobile block size. |
| The image looks sharp on desktop but soft on a phone | Check the capture, pixel dimensions, template scaling, and provider processing. |
| A link opens an unrelated homepage | Use the relevant destination and verify availability, options, and back navigation. |
| The photo implies included extras | Match the base offer or label optional items clearly in live text. |
| AI changes the recipe | Reject the candidate and use the reviewed manual edit or recapture. |
| The menu changes after scheduling | Recheck the offer and photograph before the send; retire expired assets. |
Pre-send checklist
- The photo shows a current dish and the normal serving.
- The final crop keeps the offer's important components visible.
- The received email is readable on desktop and mobile, including with images off.
- Compression and template scaling preserve useful detail.
- Image and text links reach the correct current destination.
- The footer and provider-managed unsubscribe control remain available.
- The original, approved export, and offer dates are recorded separately.
Begin with one real offer and one photograph. Review it in DishVivid Studio, prepare any template-specific size externally, and compare actual campaign clicks and completed orders in your own systems. Photo editing alone does not establish a conversion or revenue improvement.