Google Business Image Size Guide for 2026

You upload a beautiful dish photo to Google. On your phone it looked sharp, balanced, and appetizing. Then it shows up in Google Search or Maps with the plate edge cut off, the garnish missing, or the whole image looking soft.

That isn't a small design issue. For restaurants, google business image size affects how people judge your food before they ever tap your menu, request directions, or place an order. A cramped crop can make a premium dish look careless. A blurry upload can make fresh food look stale.

Restaurant owners usually run into the same problem. They focus on taking a better photo, but Google applies its own templates, crops, and compression. If the image isn't prepared for those rules, the platform makes the decision for you.

Table of Contents

• Why Your Google Business Images Get Cropped
  • Google optimizes for layout, not your hero shot
  • Cropping hurts restaurants more than most businesses
• Google Business Image Size Quick Reference
  • Google Business Profile Image Specifications 2026
  • What each image type does
• Core Profile Images Logo and Cover Photo
  • Logo rules that keep your brand readable
  • Cover photos need room to breathe
• Google Post Image Specifications
  • The format that holds up best
  • What works in practice
  • Why restaurants should care more than other local businesses
• Menu and Product Image Guidelines
  • The overlooked problem is mobile cropping
  • Compose defensively, not artistically
  • What usually translates well on mobile
  • Menu photos should sell one decision
• Optimizing Image Quality and File Size
  • JPG or PNG for restaurant images
  • A simple pre-upload workflow
  • What usually goes wrong
• Image SEO Best Practices for Local Search
  • Name files like a local business, not a camera roll
  • Add useful descriptions when you upload
  • Keep metadata practical
• From Phone to Profile A BeauPlat Workflow
  • Step 1 Capture for flexibility
  • Step 2 Clean the image before styling
  • Step 3 Use a tool that exports for the intended platform
  • Step 4 Preview at phone size
  • Step 5 Upload with the right name and placement
  • Step 6 Recheck after publishing
  • A workable weekly rhythm for restaurant teams

Why Your Google Business Images Get Cropped

Google wants consistency across Search and Maps. Your restaurant wants control over how its food, brand, and atmosphere appear. Those two priorities don't always line up.

If you upload an image that doesn't match Google's preferred layout, Google will usually resize it, compress it, or crop it to fit the placement. That's why a dining room shot can lose the warm lighting near the edges, and a plated pasta shot can lose the very details that made it sell in the first place.

Google optimizes for layout, not your hero shot

A restaurant image doesn't live in one fixed box. It may appear as a profile element, a post thumbnail, a cover image, or inside a photo gallery. Each surface handles framing differently. Google is trying to make thousands of business listings look coherent across devices, so it favors standard aspect ratios and automated rendering.

That creates a practical trade-off. A tightly framed dish can look dramatic in your camera roll, but it gives Google no room to adapt. When the system crops for a smaller mobile layout, the plate can get clipped and the composition falls apart.

Practical rule: If the image only looks good when every edge stays intact, it's too tightly framed for Google Business Profile.

Cropping hurts restaurants more than most businesses

A solicitor's office can survive a slightly awkward office photo. Restaurants have less margin for error because customers are evaluating appetite appeal in seconds. Texture, steam, shine, sauce detail, crust, and color all matter.

When those details disappear, the photo stops doing its job. The issue isn't only aesthetics. It's whether the dish still looks worth ordering when seen quickly in Maps or Search.

Three patterns usually fail:

• Edge-heavy compositions that place the food too close to the border
• Tiny text overlays that become unreadable after resizing
• Low-resolution originals that look acceptable on one screen and muddy on another

The fix starts with using the right dimensions for the right image type, then composing for mobile first instead of desktop first.

Google Business Image Size Quick Reference

If you just need the specs, use this table and keep it bookmarked. These are the image settings that matter most for a restaurant Google Business Profile.

Google Business Profile Image Specifications 2026

Those four categories cover most of what restaurant owners manage: brand identity, storefront impression, promotional posts, and food imagery.

What each image type does

The logo is your brand marker. It needs to stay readable when shown small, and square formatting matters because Google crops non-square logos to fit the available space.

The cover photo is your profile's visual headline. For restaurants, that usually means a room shot, a signature dish, or a scene that captures the atmosphere without relying on text.

Post images support updates, specials, events, and limited-time promotions. They need to carry the message quickly because viewers often decide whether to click before reading much copy.

Product and menu photos do the heavy lifting for restaurants. These are often the images closest to purchase intent, so composition matters just as much as dimensions.

If your team also posts to Instagram, Facebook, or other channels, it helps to keep a separate reference for latest social media image dimensions so you don't reuse a crop that works on one platform and breaks on Google.

Core Profile Images Logo and Cover Photo

Your logo and cover photo set the tone before a customer ever looks at a menu item. One signals brand recognition. The other signals what kind of place you are.

Logo rules that keep your brand readable

Google specifies a 1:1 square logo at 720 × 720 pixels, with a minimum of 250 × 250 pixels, and it automatically crops non-square images to fit its layouts. Google also accepts JPG or PNG files, and all images must stay between 10 KB and 5 MB according to Semrush's Google Business Profile photo size guide.

For restaurants, the main mistake is using a logo file built for signage, menus, or packaging instead of one built for tiny digital placements. A long horizontal wordmark may look polished on a storefront, then become cramped or unreadable when Google forces it into a square.

Use a logo version with these traits:

• Simple shape: Avoid extra flourishes, border treatments, and fine print
• Strong contrast: Make sure the logo stands out against its background
• Centered design: Give the mark enough breathing room so auto-cropping doesn't clip it
• Small-screen legibility: If it blurs into a blob at thumbnail size, it's the wrong file

Cover photos need room to breathe

Google cover photos use a 16:9 aspect ratio with 1024 × 576 pixels recommended, 480 × 270 pixels minimum, and a maximum of 2120 × 1192 pixels in the same accepted file formats and size range noted above in these cover photo guidelines for Google Business Profile.

A cover photo isn't the place to cram in your menu, awards, or a promotional banner. Google may crop differently depending on the interface, and text placed near the edges is often the first thing to get sacrificed.

Keep the visual story in the center. The closer your most important detail sits to an edge, the more likely mobile rendering will punish it.

For restaurants, a good cover photo usually falls into one of three categories:

A practical test helps. Open the image on your phone, shrink it mentally, and ask one question: if a first-time customer sees this for two seconds, do they instantly understand your brand?

If the answer is no, choose a different image.

Google Post Image Specifications

Google Posts are one of the few places on your profile where you can actively shape attention around a promotion, update, or event. For restaurants, that makes post images useful for lunch specials, seasonal drinks, tasting menus, holiday hours, and limited-time offers.

The image matters because the visual usually gets judged before the copy. If the photo is cropped awkwardly or loses sharpness, the post looks less trustworthy, even when the offer itself is strong.

The format that holds up best

The standard that holds up best for Google Posts is 1200 × 900 pixels with a 4:3 aspect ratio. According to Zeely's guide to Google Business post image size, that format has become the benchmark, helps prevent unwanted cropping across Google Search and Maps, and stays clear on retina and high-DPI displays.

That same source notes that images smaller than 720 × 720 pixels can trigger visible compression blur that can reduce image legibility by up to 30%, while the minimum acceptable size remains 250 × 250 pixels. File sizes are capped at 5 MB.

For a restaurant, that means the "good enough" file from a phone screenshot or old social post often isn't good enough for Google Posts. It may upload, but it won't present well.

What works in practice

A strong post image usually does one job well. It highlights a single dish, a clear offer, or one event-related scene. Problems start when owners try to fit too much into one frame.

Use this checklist before posting:

• One focal point: A burger, cocktail, brunch spread, or event moment
• Minimal text: If you need text at all, keep it large and central
• Bright, natural contrast: Food needs definition, not heavy filters
• Centered subject: Posts render across different placements, so central framing is safer

If you're creating posts regularly, this reference on Google My Business post image size is a useful companion for your team.

Why restaurants should care more than other local businesses

Google Posts give restaurants a rare chance to push a timely visual into a high-intent local search environment. That's different from a passive gallery image. A strong post can connect appetite and action in the same moment.

A post image shouldn't just look good. It should still make sense after Google shrinks it, crops it, and places it next to competing listings.

That shifts the standard. You're not designing for your own screen. You're designing for Google's feed surfaces and the customer's quickest decision point.

Menu and Product Image Guidelines

Menu and product images often determine whether most restaurants succeed or fail. They aren't just decorative. They're often the closest thing to a digital tasting sample.

Google's general image rules are useful, but they don't answer the restaurant-specific problem: how a food photo survives mobile rendering. A dish can look perfectly composed on desktop and then lose the appetizing details on a smaller mobile view.

The overlooked problem is mobile cropping

Existing guides mention mobile optimization, but they don't provide actual rendering benchmarks for how food imagery performs across desktop and mobile. One of the clearest descriptions of that gap appears in Boostability's Google My Business image guide infographic, which notes that a 1200×900px image can look complete on desktop yet lose 30 to 40% of critical visual detail on a 414px mobile screen in Google Maps.

That matters more for food than for most products. A haircut, office lobby, or storefront can tolerate some visual loss. Food often can't. Remove the steam from ramen, the cheese pull from pizza, or the sauce detail from a composed plate, and the image loses its selling power.

Compose defensively, not artistically

Restaurant owners often get advice to "center the subject." That's directionally right, but too vague for food photography. Food shots need safe space around the plate and enough negative room to survive tighter rendering on mobile.

A practical approach:

• Leave margin around the dish: Don't let the plate touch the frame edge
• Protect height elements: Steam, skewers, garnish, and stacked burgers need extra top room
• Avoid edge garnish: Herbs, crumbs, and sauces near the border are easy to crop away
• Choose cleaner backgrounds: Busy tabletops compete with the dish once the image shrinks

What usually translates well on mobile

Some food images hold up better because they simplify the visual hierarchy. Google compression and reduced screen size reward clarity.

Restaurants should judge product photos at small-screen size first. If the dish doesn't look appealing at a glance on a phone, the original composition isn't doing enough.

Menu photos should sell one decision

A menu or product photo should answer a quick customer question: do I want this item? The best-performing style for that task is usually direct and restrained.

Don't rely on props to create drama. Don't zoom so tightly that the customer can't tell portion, plating, or context. And don't assume that because a shot looks rich on Instagram, it will behave the same way inside Google.

For restaurant teams, the workflow change is simple. Shoot wider than your instinct tells you. Keep the food central. Then test the image on a phone before upload, not after the listing goes live.

Optimizing Image Quality and File Size

Good dimensions don't save a weak file. An image can have the right aspect ratio and still look flat, bloated, or over-compressed after upload.

Restaurants usually hit trouble in two places. First, they upload an original straight from the phone with no cleanup. Second, they compress too aggressively and strip out the very texture that makes food look fresh.

JPG or PNG for restaurant images

For most food photography, JPG is the practical choice. It keeps file size manageable and works well for photos with lots of color variation, shadows, and texture. For logos or graphics with transparency, PNG is usually the cleaner option.

The goal isn't to chase the smallest possible file. The goal is to send Google a file that's clear, reasonably light, and within the platform's limits.

A simple pre-upload workflow

Most restaurant teams don't need Photoshop for this. They need a repeatable process that someone can follow in a few minutes.

Use this sequence:

1. Start with the highest-quality original
   Edit from the original camera image, not from a screenshot, social export, or image pulled from WhatsApp.

2. Crop to the intended use first
   Decide whether the image is for a post, product slot, logo, or cover photo before any export.

3. Apply light edits only
   Fix exposure, white balance, and crop. Avoid heavy sharpening and dramatic filters.

4. Export in the right format
   Use JPG for dishes and room photos. Use PNG for logos and simple graphics.

5. Compress with a dedicated tool
   TinyJPG or TinyPNG are common choices because they reduce size without making the image obviously damaged.

A broader explanation of the technical discipline of image optimization is useful if your team wants the SEO side as well as the visual side.

What usually goes wrong

Restaurant owners often think "high resolution" automatically means "better result." It doesn't. Oversized files can still get compressed badly if they aren't prepared well. On the other end, underpowered exports often create that cheap, fuzzy look that makes premium food seem less premium.

Common mistakes include:

• Exporting tiny files from Canva, social schedulers, or messaging apps
• Uploading screenshots instead of original images
• Using PNG for everything even when JPG would be lighter and more practical
• Oversharpening so sauce, crust, or skin tones look artificial

If you're improving the shot before export, lighting still matters more than any compression setting. This guide to light setup for food photography is a solid reference for getting the original image right before optimization.

Better optimization doesn't rescue a bad photo. It protects a good one from getting worse during upload.

Image SEO Best Practices for Local Search

Google doesn't only "see" the picture. It also reads the context around it. That's where image SEO helps a restaurant show clearer relevance in local search.

This part is less visible than cropping or compression, but it still matters. If your files are named badly and your uploads are vague, Google gets less context about what the image contains and how it connects to your business.

Name files like a local business, not a camera roll

The simplest improvement is file naming. Don't upload IMG_4821.jpg. That tells Google nothing.

Use a naming pattern like:

• restaurant-name-dish-name-city.jpg
• restaurant-name-dining-room-neighborhood.jpg
• restaurant-name-signature-burger-city.jpg

That approach makes the file useful before the image even loads. For local intent, adding the restaurant name, item name, and location creates a much stronger signal than a default camera file name.

If you want a deeper naming framework, this guide on optimizing images for local search is worth reviewing.

Add useful descriptions when you upload

When Google gives you an opportunity to add context, use it. Keep the text descriptive and specific. "Fresh margherita pizza with basil at Corner Bistro Chicago" is better than "pizza" or "great food."

Focus on what a real customer would search for:

Keep metadata practical

Some owners ask about geotags and embedded location metadata. They can support local context, but they aren't where I'd spend most of the effort. File names, image choice, and clear upload descriptions usually have more immediate value for a restaurant team trying to move quickly.

The better checklist is short:

• Use descriptive filenames
• Match each image to the right profile section
• Describe the dish or space clearly
• Stay consistent across locations if you manage multiple branches

Local image SEO works best when it reflects reality. Use actual photos of your actual dishes and actual space. That's better for Google, and it's better for customers.

From Phone to Profile A BeauPlat Workflow

Most restaurant owners don't need more theory. They need a fast way to go from a phone photo to something that looks clean on Google.

This workflow keeps the process practical. It works whether you're the owner, a location manager, or someone on the marketing team handling updates between lunch and dinner service.

Step 1 Capture for flexibility

Start with a smartphone photo, but don't shoot like you're posting straight to Instagram. Give yourself more room around the dish than you think you need. Keep the plate central, avoid cutting off edges, and watch the background for clutter.

Natural or soft side light usually helps texture read better. Before you take the final shot, lower the phone and look at the composition as a customer would. Is the food the first thing they see, or is the table, wrapper, drink cup, or napkin stealing attention?

Step 2 Clean the image before styling

Pick the sharpest frame. Then make only basic corrections: exposure, white balance, straightening, and crop. Don't add tiny promotional text and don't apply filters that shift the food too far from reality.

For restaurants, authenticity matters. A customer who orders a glossy, over-edited burger photo and gets something visibly different in real life won't thank you for creative editing.

Step 3 Use a tool that exports for the intended platform

At this point, many teams lose time moving files between editing apps, design tools, and upload folders. One practical option is BeauPlat, an AI photo studio for restaurants that turns smartphone dish photos into enhanced food visuals and can fit into a workflow where the image is prepared specifically for platform use.

The key is not the branding of the tool. It's the workflow discipline. Your team needs a repeatable process where each photo gets prepared for Google's layout, not just "made prettier."

A simple internal checklist works:

• Choose the destination first: Google post, cover photo, product image, or logo support graphic
• Keep the food honest: Improve clarity and lighting without changing the actual dish
• Export with the right crop: Don't rely on Google to decide the framing for you

Step 4 Preview at phone size

This is the step most owners skip. After export, open the image on your phone and view it small. Don't zoom in. Don't inspect it like a designer. Glance at it like a customer scanning Maps while hungry and in a hurry.

Ask three questions:

1. Can I instantly tell what the dish is?
2. Does the food still look balanced after a tighter crop?
3. Are the most appetizing details still visible?

If one answer is no, fix the crop before upload.

A short visual walk-through can help if your team is building a repeatable content routine:

Watch on YouTube

Step 5 Upload with the right name and placement

Don't dump everything into the main photo section. Match the image to its role. Product photos should support item-level interest. Posts should support an update or promotion. Cover photos should communicate the overall brand feel.

Before uploading, rename the file clearly. Use the restaurant name, dish name, and location if relevant. Then add concise descriptive text in the profile where possible.

Step 6 Recheck after publishing

Google may still present the image a little differently across placements. That doesn't mean the upload failed. It means you should verify how it appears in real conditions.

Check:

• Search view on mobile
• Maps view on mobile
• Desktop profile display
• Any active post placements

This final review catches issues early. If a crop looks weak, replace it quickly instead of letting a poor image sit on a high-intent surface.

A workable weekly rhythm for restaurant teams

The easiest operational model is batch-based. Pick one day each week to photograph a few dishes, one room shot if needed, and any time-sensitive specials. Prep them in one session, export for their intended use, and upload in a short block.

That keeps your Google profile fresh without turning image management into a full-time task.

---

If you're handling Google images in-house and want a faster way to turn everyday dish photos into platform-ready visuals, BeauPlat is built for that restaurant workflow.