Chase Boulay · September 28, 2026

Your PDF Menu Is Losing You Orders

Picture someone sitting in a car outside your restaurant on Atwells Avenue, deciding whether to come in or order from you tonight. They pull up your website on their phone and tap "Menu."

A PDF starts downloading. It opens in a separate viewer, sideways, tiny, the whole page crammed onto a phone screen. They pinch to zoom, drag around, lose their place, try to find the price of the chicken parm, give up, and check the place across the street instead.

I see this on restaurant sites all over Rhode Island, and it's one of the easiest things to fix and one of the most expensive to ignore. Your menu is the single most-visited part of your website. Here's why it shouldn't be a PDF, and what to do instead.

A PDF Isn't Part of Your Website. It's a File Your Website Points To.

A PDF is a document meant for printing. When you put it on your site, you're not putting your menu on a web page. You're handing the visitor a file and hoping their phone opens it nicely.

On a phone, that usually means one of a few bad outcomes. It opens in a separate app and the person has to find their way back. It downloads to their phone and they have to hunt for it. It renders at print size, so an 8.5 by 11 page is shrunk to fit a screen the width of a credit card. Or it takes ten seconds to load because the file is huge.

None of that happens with a menu that's written as regular text on a web page. It loads like any other page, it fits the screen, it reads top to bottom with a thumb scroll, and prices are readable without zooming.

What to do: Open your menu on your own phone right now. If you have to pinch to read a price, that's what every customer is doing too.

Google Can't Do Much With It Either

When someone searches "clam cakes Warwick" or "vegan options Providence," Google is looking for pages that talk about those things. A text menu on your site is a page full of the exact dishes people search for. A PDF is a file sitting off to the side. Google can read PDFs, but the words inside one don't help your actual pages show up the way words on the page do.

Every dish name, every ingredient, every "gluten-free" and "spicy" on a real menu page is a chance to match a search. Locked in a PDF, most of that is wasted.

Photos of a Printed Menu Are Worse

The only thing worse than a PDF is a photo of the printed menu, or a screenshot of it, uploaded as an image. It has every problem of the PDF plus a few more. It's blurry when zoomed. It can't be read by anyone using a screen reader. It can't be searched, copied, or translated. And to Google it's just a picture with no words in it at all.

If your menu is currently a photo on your site or your Facebook page, that's the first thing I'd change.

A Text Menu Can Be Updated in Minutes

Here's the reason owners actually use PDFs: the printer gave them one, and it felt easier than dealing with the website. Changing a PDF means calling whoever made it, waiting, getting a new file, and getting it uploaded. So the menu on the site drifts out of date and nobody fixes it.

A text menu on a well-built site is just text. Change a price, remove the dish you stopped making, add the fall special. On a site built right, that's a small edit, not a project. And it means your online menu can actually be your current menu instead of the one from last spring.

Even if someone else maintains your site for you, a text change is a quick request. A new PDF is a whole round trip.

What to do: Compare the menu on your website to the one on your tables. Count the differences. That's how long it's been.

Prices Change. Your Menu Has to Keep Up.

Food costs move. Menus get reprinted. And the website is the last thing anyone remembers to update. The result is a customer who saw one price online and gets charged another at the table, and now you're having an awkward conversation or eating the difference.

Some owners try to dodge this by leaving prices off the online menu entirely. That backfires. People want to know what dinner is going to cost before they commit, especially a family of four or someone planning a date. A menu with no prices reads as "expensive" to a lot of people, and they go somewhere that tells them.

Put the prices on. Then keep them current, which is easy when the menu is text.

Third-Party Apps Are Showing Your Menu Anyway

If you're on DoorDash, Uber Eats, or Grubhub, your menu is already online as real text, with photos, on their site. Every one of those orders costs you a commission. People who search for you often land on the delivery app's page before they land on yours, because the app's page is easier to read.

That's backwards. Your own website should have the best, most readable version of your menu, with a clear way to order directly or call for pickup. When your site's menu is a PDF and the delivery app's menu is clean and tappable, you're paying a commission for the privilege of having a worse website than the app.

You don't have to leave the apps. Just make sure your own menu is at least as easy to use, and put a "Call for pickup" or "Order direct" option right on it.

Labels, Specials, and Sections Belong on the Page

A text menu can do things a PDF can't. Mark dishes gluten-free, vegetarian, or spicy with a small label people can scan for. Put a "Today's Specials" section at the top that you change each morning. Split the page into sections with jump links so someone looking for dessert doesn't scroll past forty entrees.

Add a few real photos of your most popular dishes, taken in your dining room, not stock images. They help people who are on the fence decide. But keep the photos small so the page stays fast. A menu page that takes five seconds to load on a phone loses people just as fast as a PDF does. There's more on what a restaurant site actually needs in restaurant websites: what actually matters.

Keep a Printable Version If You Want, But Don't Lead With It

None of this means you can't also offer a PDF. Some people like to print a menu for a catering order or a big group. Put a small "Download printable menu" link at the bottom of the text menu for them.

Just don't make it the only menu, and don't make it the first thing people hit. The default, the thing the "Menu" button goes to, should be a page that works on a phone in a parking lot.

The Bottom Line

Your menu is the most-visited page on your website and it has to work on a phone. A PDF doesn't. Put your menu on the page as real text with prices, sections, and a few labels. Keep it current, which is easy once it's text. Make it at least as good as the delivery app's version, and put a direct-order option on it.

Then the person sitting in the car outside your place can actually read what you make, and comes in.