MarkUpTo
Open the tool
Small business

Make a Restaurant Menu With AI and Print It Yourself

Short answer

Paste your real dishes and prices into a prompt asking ChatGPT or Claude for the menu as a complete HTML file, preview it in a free tool like MarkUpTo, and export a 300 DPI PDF to print. When prices change, click the number and retype it, then re-export: seconds, not a redesign. The same file, downloaded as .html and hosted free, becomes the page behind your QR code.

Menus are the perfect case for AI design, and almost nobody realises it yet. They are mostly text, which AI image generators butcher and language models type perfectly. They change constantly, which punishes anything you cannot edit in seconds. And paying a designer 150 dollars every time the supplier raises the salmon price is exactly the expense a small restaurant does not need.

Here is the whole workflow: design, print, updates, and the QR version, with real costs, which are mostly zero.

Step 1: the prompt, with your real menu in it

The single biggest mistake is asking for "a menu for an Italian restaurant" and letting the AI invent dishes you then have to replace one by one. Give it everything up front:

"Design a single-page restaurant menu as a complete HTML file with all styling included. Page size: US Letter, portrait. Restaurant: [name]. Style: [rustic and warm / clean and modern / classic fine dining]. Use exactly these sections, dishes, descriptions, and prices: [paste your full menu]. Prices aligned right. Leave comfortable margins."

Because a language model types your text character for character, every dish name, every allergen note, every price arrives exactly as you wrote it. No BRUSCHETTE ALA POMODORRO. If you have brand colours or a font, name them in the prompt.

Iterate on the big design decisions in the chat, two or three rounds: denser or airier, different section styling, a header treatment. Then stop, because from here on the chat is the expensive way to edit.

Step 2: preview and polish by clicking

Paste the HTML into MarkUpTo. The menu renders exactly as a browser sees it, at the page size you choose. Turn on visual editing and finish the details directly: nudge a heading size, fix a description, adjust a colour. Each change is a click, costs nothing, and cannot disturb the rest of the layout, which matters because re-prompting an AI for one tweak regenerates the whole file and famously shifts things you never mentioned.

Step 3: print it properly

Export a PDF at 300 DPI. That is the resolution at which text prints crisp instead of faintly fuzzy, and the export happens at true print resolution rather than screen resolution, which is the failure behind most blurry home-printed menus (the full story here).

Practical print choices that hold up in service:

The part that pays off forever: updates

This is the reason the HTML workflow beats both designers and design apps for menus. Keep your menu's HTML file. When the salmon goes up two dollars:

  1. Paste the file into the editor (or reopen it if it is still there).
  2. Click the price. Type the new one. Fix the seasonal dish while you are in there.
  3. Re-export the PDF. Print the changed pages.

Ninety seconds, zero cost, zero AI involvement, and the rest of the menu is untouched by construction, not by luck. Restaurants that update prices weekly are exactly who the no-re-prompting rule was written for.

The free QR menu, from the same file

Since your menu already is a web page, the digital version is nearly free effort:

  1. In MarkUpTo, switch to Web mode and check the menu at phone width, because guests will read it on phones. Ask the AI for a mobile-friendly single-column version if your print layout crowds a small screen.
  2. Download it as a .html file and host it free (Netlify's drag-and-drop deploy takes about a minute; full steps here).
  3. Point any free QR code generator at the URL, and put the code on tables, the door, and the takeaway bag.

Updating the QR menu is uploading the new file. The printed QR codes never change, so a price update costs literally nothing and reaches every table instantly.

What this replaces, and what it does not

Honestly drawn lines: this workflow replaces the recurring cost of menu updates and produces genuinely professional single-sheet and QR menus. It does not replace a brand designer if you are building a full identity from scratch, and elaborate folded or bound menus are a print-shop conversation where your PDF is the starting artwork. For the weekly reality of running a place, though, the loop of click, retype, re-export is the thing you will actually use.

Beyond the main menu: the whole paper system

Once the main menu exists as HTML, every other piece of printed paper in the room becomes a five-minute variant, because you can ask the AI to reuse the exact style:

Everything matches because everything inherits one design, which is the visual consistency restaurants usually pay an agency to maintain, produced from one prompt pattern and a printer.

The mistakes worth avoiding

Three from the school of experience. First, do not let the AI invent menu language: paste your descriptions verbatim, because models will otherwise embellish, and "pan-seared" becoming "artisanally kissed by flame" is how menus get mocked online. Second, print one test page before printing thirty, checking that prices did not wrap oddly and margins clear your printer's edges; the exact-print guide covers the common surprises. Third, date your files. Saving menu-june.html beside menu-april.html costs nothing and settles every "wait, which version is current" debate during a rush.

What this costs, added up honestly

Worth stating plainly, because the arithmetic is the argument. The design: free with the AI chat you already use. The editing and exporting: free in the browser. The web menu hosting: free on a static host. The QR codes: free from any generator. What you actually pay for is paper, ink or a print shop run, and sleeves or lamination, which is to say the same materials you were already buying, minus the recurring design fees and minus the reprints that price changes used to force. For a small spot updating prices monthly, that is a few hundred dollars a year staying in the till, and, maybe more valuable during a Friday service, the ability to fix a menu mistake between lunch and dinner without waiting on anyone.

Frequently asked questions

Can ChatGPT make a restaurant menu?

Yes, and the trick is to ask for it as an HTML file with your exact dishes and prices pasted into the prompt. The text comes out perfectly spelled, the layout is professional, and you can export a print-ready PDF at 300 DPI or host a web version for a QR code.

How do I update menu prices without redoing the whole design?

Keep the HTML file and edit it directly in a visual editor: click the price, type the new one, re-export. It takes seconds, costs nothing, and nothing else on the menu changes. Re-prompting the AI for each price change regenerates the entire design and risks altering things you liked.

What size should a printed menu be?

US Letter and Legal are the practical standards for single-sheet menus, with half-Letter working well for drink lists and specials. Print at 300 DPI on decent cardstock, and laminate or sleeve menus that guests handle daily.

How do I make a QR code menu?

Download your menu as a .html file and host it free on a static host, then generate a QR code that points to the URL. Guests scan and see the live menu, and updating it means uploading a new file, with no reprinting.