How to Make a QR Code Menu for Restaurants in 2026 (Free, No App)

It was 11:47 PM at Sunny's, a 12-seat cafe in Bandra West that I helped reopen last month after a rebrand. The owner messaged me a photo of the printed menu she had taped to the front window for the morning crowd. The chickpea bowl was struck through in red pen because the chickpeas had not arrived. The flat white had a new price scribbled above the old one. There was a coffee ring on the corner. She asked, "is this fine for tomorrow?" I told her no, and that we were going to fix the actual problem at 8 AM.

The actual problem is that printed menus stopped being the right format for any restaurant whose offering shifts more than twice a year. That is most of them. The QR menu is not a pandemic ghost. It is the working tool that mid-range casual restaurants quietly kept after the rest of hospitality decided whether to keep it or bin it.

Who kept the QR menu, who dropped it, and why it matters

Fine dining mostly dropped them. If guests are paying 4,500 rupees per head, handing them a phone instead of a leather-bound list is a status downgrade. The Bombay Canteen kept printed menus. So did Indian Accent. So did basically every place with a sommelier on staff.

Mid-range casual kept them and kept iterating. Cafes, gastropubs, neighbourhood Italian places, breakfast spots, every restaurant where the menu changes seasonally or whenever the chef gets bored. This is also where Toast and Square saw their highest QR menu adoption in 2024 and 2025: places with 30 to 120 covers, a tight kitchen, and an owner who is also the person updating the menu at midnight.

Chai stalls and roadside dhabas never adopted them and should not. The menu is on a board. The board works. Friction matters more than novelty, and a QR menu at a 40-rupee cutting chai stall is solving a problem that does not exist.

The sweet spot is obvious. If your menu changes more than once a quarter, and your average check is between 400 and 2,500 rupees, you should have one. If you already have one and nobody scans it, the problem is rarely the QR. The problem is almost always the page behind it.

What critics get wrong

You will read think pieces arguing that QR menus are lazy hospitality. They are not lazy. They are data. Every scan, every category tap, every time-of-day pattern is visible to the owner. A printed menu tells you nothing. A QR menu tells you that 62 per cent of weekend brunch guests open the cocktail section first and only 9 per cent of weekday lunch guests do. That changes how you train the floor.

The other complaint, that QR menus are antisocial, is selective. The people writing it have never watched a table of six pass a single printed menu around while two of them stare at their phones anyway. The phone was always at the table. The QR just gave it something useful to do.

Choosing the format: PDF, Google Doc, Toast, Square, or custom page

The format you pick is the whole game. Here is what actually works, ranked.

Custom mobile-first HTML page. Best in class. Loads in under a second, looks like the restaurant, no third-party branding. Costs a weekend to build or a few thousand rupees to a freelancer. If you take this seriously, do this. Squarespace and Webflow both work for the non-technical owner.

Toast or Square hosted menu.Sensible if your POS is already Toast or Square. The menu syncs with your inventory and item-level pricing. Downside: the page carries the platform's branding and is not lightning fast. Acceptable trade for the integration if you are running 80+ covers a day and need the inventory sync.

Public Notion page. Fine for a soft launch or a pop-up. Notion at least renders cleanly on mobile and is free. Treat it as a placeholder while you build the real thing.

Google Doc. On a phone, this is a pinch-and-zoom punishment. Skip it.

PDF. Avoid. Half your guests will see a download prompt. The other half will be zooming into 7-point text. If your menu is a PDF today, rebuilding it as an HTML page is the single highest-impact two-hour task on your list.

Uber Eats and Zomato menus are not menus, they are listings. Do not point your table QR there. You pay 22 to 35 per cent on every order placed through them, and that is fine for delivery, but a dine-in guest who orders through Zomato is a margin disaster.

Print sizes and placements that actually get scanned

Three placements cover almost every restaurant.

Table tent at 2 by 3.5 inches. The standard. Card stock, matte laminate so it does not glare under spot lights, QR no smaller than 2.5 cm square. Print the short URL beneath it in 8-point type. Tents get knocked over, get sauce on them, occasionally walk home in a tote bag. Budget for replacements every six months.

Table edge sticker at 1.5 by 1.5 inches. Lower profile, harder to steal, slightly harder to spot. Best for restaurants with a minimalist aesthetic where a tent looks fussy. Use a UV-cured vinyl print, not a paper sticker. Paper peels after three months of wipe-downs.

Bill closer at 3 by 3 inches. The most undervalued real estate in the restaurant. The check arrives, the meal is over, the guest is in the happiest 90 seconds they will spend with you. A 3-inch square QR on the bill folder or printed on the receipt paper itself, pointing at a single page with two buttons (leave a Google review, follow on Instagram), is the highest-converting placement you have. More on this in a moment.

Use our URL QR code generator, paste your menu URL, and download the SVG. SVG scales without pixelation, which matters when your printer wants to scale to fit a slightly different template than the one you exported for. Pair it with a Wi-Fi QR on the same tent. Two QRs, two jobs, no awkward exchange with the server about the password.

The bill QR for Google Reviews: the trick nobody uses enough

The cafe in Indiranagar I worked with last year had eight months of consistent five-star food and zero new Google reviews. Owner blamed the area. I asked to see the bill. The bill had a thank-you message and a hand-drawn star. Charming. Useless.

We added a 3-inch square QR to the bill folder pointing to a small landing page with three buttons in this order: leave a Google review, follow on Instagram, join the supper club list. The Google review button used the direct review URL format that opens the review composer in one tap on both iOS and Android.

Reviews went from 1 to 2 a month to 11 to 14. That is roughly a 6x lift, but the number I trust more is what we saw across four other restaurants we tried it at that quarter: 3 to 5x review growth in the first 60 days, sustained. The mechanism is dumb and effective. A happy guest already has their phone out paying the bill. You are removing every step between "I had a nice time" and the star rating.

Two notes. First, do not gate the review button. Asking for a star rating before sending the guest to Google violates Google's review policy and will get your listing flagged. Second, do not put this QR on the menu and expect review lift. The menu QR gets scanned at the start of the meal when the guest has no opinion yet. The bill QR gets scanned at the end when they do.

A story from a cafe owner I trust

The five mistakes that quietly kill scan rates

No fallback URL under the QR. One in eight scans fails the first time, either because of glare, an old phone, or a guest who has never scanned before. Print the short URL in 8-point under every QR. The brain is a better backup than the camera.

The page is too heavy. A steakhouse in Worli was wondering why its scan rate was 22 per cent while a cafe two blocks away was at 80. The steakhouse page was 4.8 MB with an autoplay kitchen video above the fold. We stripped it to 180 KB and rebuilt the menu in plain HTML. Scan rate climbed to 71 per cent inside three weeks. Same code. The QR was never the problem.

Locked PDF. See above. If it is a PDF in 2026, you are losing guests at the download prompt. Rebuild it.

Dynamic QR for everything. A static QR is permanent. A dynamic QR can change destination after you print, but it costs more and adds a redirect hop. Use a dynamic QR only where the destination might actually change. Menu page on your own domain? Static is fine. Promotional QR for a six-week winter menu? Dynamic.

The QR does only one job. A menu QR is one job. A bill QR can do three. Always think about what the guest is doing the moment they scan, and design the page for that moment.

What I'd skip

Dynamic QRs for the main menu, unless you update it weekly. A static QR pointed at a stable URL on your own domain does the same job for free and never expires. Dynamic codes are sold hard by every QR platform because they generate recurring revenue. For a menu that changes seasonally, you do not need them.

Branded QR codes with the logo in the middle. They scan slightly worse, they cost more to design, and the guest does not care. Save the brand work for the table tent itself, not the QR.

Full QR ordering for sit-down service under 50 covers. Toast and Square will sell you a flow where the guest scans, orders, and pays without a server. For a 30-seat cafe, that removes the very human touch your regulars come for. Keep the human. Use the QR for the menu only.

Multi-language menus printed in three versions. One QR, one page, a small language switcher at the top. The page does the work, not the printer.

Counter service, drive-thru, and pickup

Everything above assumes table service. Counter service is different. The guest wants to read the menu before they are at the front of the line, not after. Put the QR on the door, on a small sandwich board on the pavement, and on the back of every receipt. Keep the big board on the wall. The QR is the pre-order, not the main course.

Pickup-only formats should move the QR to the bag seal sticker. Every order that walks out the door has one shot at coming back. The sticker QR points at a single page with two buttons: leave a review, reorder. We tested this with a cloud kitchen in HSR Layout and saw repeat orders inside 30 days climb roughly 18 per cent. Tiny intervention. Real money.

Common mistakes I keep seeing

The pattern across every restaurant that thinks "QR menus do not work" is the same. They printed a tent with a QR that points at a PDF. The PDF takes seven seconds to load on cellular. The text is set in 8-point. There is no fallback URL. The owner blamed the diners.

The pattern across every restaurant where it does work is also the same. The QR points at an HTML page on their own domain. The page is under 300 KB. The first thing visible is the menu, not a slideshow of the chef. The bill carries its own QR pointing at a review and follow page. The owner checks the analytics on Sunday and tweaks the page on Monday.

That is the whole playbook. The restaurants hub has a sample table tent layout you can copy and a sample bill-QR landing page. The FAQ covers print sizing, contrast, and laminate choices.

Last updated June 2026 by Priya Sharma.