Menu layout: one page, two columns or a folder

A guest opens the menu, reads for a minute or two and decides what to eat. Everything the venue wants from the menu happens in those minutes: the dishes it most wants to sell are noticed or missed, the guest feels guided or lost, and the server either takes an order or comes back later because nobody is ready.

Menu layout shapes all of that before a single word is read. A single page, two columns and a folder each lead the eye differently, take a different amount of time to read and suit a different size of menu. This guide compares the three, covers where dishes sit on the page, how type and space make a menu readable, and works through the layout that suits a menu of eighteen dishes. Every figure in it is an example.

Layout is the arrangement of everything on the menu: how many pages, how many columns, where each section sits, how dishes are listed and how much space surrounds them. It is the part of menu design that decides how the guest moves through the menu, before the wording or the prices do their work.

Three things follow from it. The first is reading order: which section the guest sees first, and which dishes in each section they are most likely to notice. The second is effort: how long it takes to understand the menu and choose, which affects how quickly tables order. The third is the impression: a calm, well-spaced page says something about the venue before the guest reads a word, and so does a crowded one.

None of these are about decoration. A beautiful menu that is hard to read fails at its job; a plain one that guests understand at a glance does it well.

Most dining menus fall into one of three formats, with variations.

A single page with one column lists the menu from top to bottom, usually in the order of the meal: starters, mains, sides, desserts. The guest reads it like a short list.

A single page with two columns, or a page folded once, puts sections side by side: starters and mains on the left, sides and desserts on the right, or food on one side and drinks on the other. The guest takes in more at a glance.

A folder or booklet spreads the menu across several pages: food in one place, wine in another, cocktails and desserts elsewhere. The guest turns pages to find what they want.

Each has a place. The right one depends mainly on how many dishes the menu has, how the guest is expected to read it, and how often it changes.

A single column is the simplest layout and often the easiest to read. The guest starts at the top and reads down, section by section, in the order they will eat. There is no question of where to look next.

It suits short menus best. A café with a dozen items, a set menu with three courses, or a focused dinner menu of ten or twelve dishes can sit comfortably in one column on a single page, with space around each section. The guest sees the whole menu without turning anything over.

The limit is length. A single column that runs past the bottom of the page, or that crams thirty dishes into small type to fit, loses the simplicity that made it attractive. Once a menu needs more than about fifteen or twenty lines of dishes with descriptions, a single column begins to feel long, and the dishes at the bottom get less attention than those at the top.

Two columns let a single page hold more without feeling crowded. The guest can see two sections side by side, and the whole menu still fits on one sheet, so nothing is hidden behind a page turn.

It works well for mid-sized menus. Starters and small plates in the left column and mains and sides in the right is a common arrangement; so is food on the left and drinks on the right for a casual venue. The guest's eye takes in the shape of the meal at once.

The care needed is in the reading order. Guests reading a two-column page usually start at the top of the left column, but they may jump across. Keep each column in a sensible order of its own, make the sections clear with headings and space, and avoid running one section from the bottom of the left column to the top of the right, which breaks the reading.

Columns also shorten the line length, which helps readability. Typographers often suggest lines of roughly 45 to 75 characters for comfortable reading, and Wikipedia's article on line length explains the reasoning. A single column across a wide page can produce lines far longer than that.

A folder or booklet gives a long menu room to breathe. A venue with a full food menu, a long wine list and a cocktail list can give each its own pages rather than squeezing everything onto one sheet.

The cost is effort. Guests have to turn pages to understand the menu, and many read only the first page or two closely. A dish on page three is easy to miss. Folders also take longer to read, which can slow the order on a busy night, and they are more expensive to print and to keep clean.

They suit venues where the guest is expected to take their time: a long dinner, a wine-led restaurant, a menu with many choices that the venue is happy to talk guests through. They suit a quick lunch far less. If you use a folder, keep the food on the first spread the guest sees, and put the longer lists, such as wine, after it.

Not every menu is a page in a guest's hand. A few other formats are common.

Most venues use more than one. The main menu may be a single page, with a separate wine list, a specials card and a board for the bar. The layout decisions for each are the same in principle: what does the guest need to see, in what order, at what distance?

The right layout depends mostly on menu size: how many dishes there are, and how much text each one carries. A short menu suits a single column; a mid-sized one two columns; a long one a folder or separate lists.

That relationship works in both directions. A venue choosing a layout should count its dishes first. But a venue whose menu has grown to fill a folder might also ask whether it needs that many dishes at all. Long menus take longer to read, are harder for the kitchen to prepare well and often hide the dishes that matter.

Count the lines honestly: dishes, descriptions, sections and any notes on allergens or dietary choices. Then ask what layout lets the guest read all of it comfortably. If the answer is a folder, and the venue is not a place where guests linger, the menu itself may be the problem rather than the layout.

Take an example menu of eighteen dishes: five starters, seven mains, three sides and three desserts, each with a one-line description. Which layout suits it?

A single column would hold it, but only just. Eighteen dishes with descriptions, plus four section headings, fill a page in a type size that is comfortable to read, with little room left for space around the sections. The desserts at the bottom would get the least attention.

Two columns suit it better. Starters and mains in the left column, sides and desserts in the right, or starters and sides on the left with mains given the right column to themselves. Each column then carries nine or ten dishes, the type can be generous, and the whole menu sits on one sheet. Desserts may also move to a separate card brought after the mains, which gives them their own moment and frees space on the main page.

A folder would be too much. Eighteen dishes do not need several pages, and spreading them out would only add page turns.

Within any layout, where a dish sits affects how likely it is to be noticed. That is menu placement: deciding which dishes go first in each section, which get more space, and which sit in the places the eye reaches easily.

Claims about exactly where the eye lands first on a menu are often repeated, but the evidence for any single rule is mixed. What is reliable is simpler. Guests read section by section, so the first dishes in each section are the ones nobody misses. A dish given a little more space, or a box around it, stands out from the list. And a dish buried in the middle of a long section is easy to skip.

Use those simple facts with care. Put the dishes you most want guests to notice near the top of their sections, give one or two of them a little more room, and keep the rest in a sensible order. Our guide to menu engineering, and the four dishes you must act on covers how to decide which dishes deserve that attention.

Sections are what make a menu readable. A guest who can see at a glance where the starters end and the mains begin can find what they want quickly; a guest faced with an unbroken list cannot.

Follow the order of the meal: small plates or starters first, then mains, then sides, then desserts. Give each section a clear heading and enough space before it that the break is obvious. If a section is long, consider splitting it: mains might divide into meat, fish and vegetables, or into dishes from the grill and dishes from the kitchen.

Keep sections roughly balanced. A menu with two starters and fourteen mains feels lopsided, and a guest scanning for a light lunch may give up. If one section dominates, ask whether some of its dishes belong elsewhere, or whether the section needs to be shorter.

Menu typography is the choice of typefaces, sizes, weights and spacing. It decides whether guests can read the menu easily, in the light where they will actually read it.

Start with size. Body text should be large enough to read comfortably in your dining room's light, which in a dim room is larger than it looks at a desk. Test a printed copy at a table in the evening, not on a screen in the office. Use one typeface for dish names and descriptions, or two that work together, rather than several.

Contrast matters as much as size: dark text on a light background is easiest to read, and pale grey text on cream may look elegant and be hard to read. Keep descriptions in normal sentence case rather than capitals, which slow reading. Use weight or size to separate dish names from descriptions, and keep prices in the same style throughout, so they are easy to find without dominating.

How prices sit on the page affects how guests read the menu. A column of prices down the right-hand edge, linked to each dish by a line of dots, invites the guest to read the prices first and choose by cost. Placing the price straight after the description, in the same type, keeps attention on the dish.

Many menus drop the currency sign and the trailing zeros, showing 14 rather than 14.00, which makes the prices quieter on the page. Whether that changes what guests spend is debated, but it does make the menu calmer to read.

Whatever you choose, be consistent and clear. Every dish should have its price where the guest expects it, any supplement should be shown plainly, and service charges or cover charges should be stated where guests will see them. A price that surprises the guest on the bill costs more goodwill than it ever earns.

Descriptions help guests choose, but long ones slow the reading and fill the page. A line or two is usually enough: the main ingredients, the cooking method if it matters, and anything that makes the dish worth choosing.

Write for the guest rather than the kitchen. "Charred hispi cabbage, brown butter, hazelnuts" tells the guest what they will eat. A paragraph about where the cabbage was grown and how long it was brined tells them more than they need at the moment of choosing, and pushes other dishes down the page.

Keep allergen and dietary information clear and consistent: a short mark beside the dish, explained once at the foot of the page, works better than a long note on every line. Our guide to menu design for reading, not for framing covers the wider principles of writing a menu guests can use.

White space, the empty space around text, is what makes a menu feel calm and readable. A page filled to the edges looks busy and makes every dish harder to find; a page with generous margins and space between sections lets the eye rest and find its way.

It is tempting to fill space with more dishes, more decoration or a larger logo. Resist it. Space between sections tells the guest where one ends and the next begins. Space around a featured dish makes it stand out more than any box. Margins keep the text away from the edges, where it is harder to read and easier to lose in printing.

If the menu does not fit with comfortable space, the answer is rarely to shrink the space. It is usually to change the layout, from one column to two or from one page to a separate drinks list, or to shorten the menu.

Photos can help a guest choose, especially for unfamiliar dishes, but they take a lot of space and set expectations the plate has to meet. A menu with a photo beside every dish can look more like a fast-food board than a dining menu, which may or may not suit the venue.

If you use photos on a printed menu, use few and use them well: one or two dishes you most want to sell, photographed honestly, given room on the page. A photo of a dish that looks nothing like what arrives is worse than no photo at all.

On a phone, the balance is different. Guests scrolling a menu on their phone expect photos more often, and the screen gives each dish its own space. That is one reason a printed menu and a phone menu are best designed separately, even when they share the same content.

More and more guests read the menu on their phone, opened from a QR code at the table or from the venue's website. A phone screen has its own layout rules: one column, short lines, sections the guest can jump to, and text large enough to read without zooming.

A PDF of the printed menu is a poor substitute. Two columns on a page become tiny text on a phone, and guests pinch and scroll to read them. Our guide to the menu on your website, not in a PDF covers why, and our look at QR menus against paper menus, five years on covers how guests use each.

The practical answer is to keep the content in one place and lay it out twice: once for the printed page, with columns and space, and once for the phone, as a single scrolling column with photos where they help.

Whether drinks, specials and desserts share the main menu or get their own cards is a layout decision that affects the whole page.

A separate drinks list keeps the food menu short and lets a long wine or cocktail list have the space it needs. A specials card, changed daily or weekly, saves reprinting the main menu every time a special changes. A dessert menu brought after the mains gives desserts a moment of their own, when the guest is deciding whether to stay for another course.

The trade-off is more pieces of paper and more for the server to hand out. For a small venue, a single page with food on one side and drinks on the other may be simpler. For a larger one, separate lists usually make each easier to read.

The best test of a menu layout is watching guests use it. Before printing a new layout in quantity, try it on a few tables, or show it to people who do not know the menu and ask them to choose a meal.

Watch for the signs. Do guests find the sections quickly, or turn the menu over looking for something? Do they ask the server questions the menu should answer? How long does a table take to be ready to order? Do the dishes you most want to sell get ordered more or less often than before?

Ask the servers too. They know which questions guests ask, which dishes guests overlook and where the menu confuses people. A layout that servers dislike is usually one that guests find hard. Keep notes, change what does not work and test again.

An invented neighbourhood restaurant has a menu of twenty-two dishes printed as a folder: starters on the first page, mains on the second and third, sides and desserts on the back. Servers notice that guests take a long time to order, often ask whether there are vegetarian mains, and rarely order the sides.

The restaurant trims the menu to eighteen dishes and moves to a single page with two columns: starters and sides on the left, mains on the right, grouped into meat, fish and vegetables, with a clear heading for each. Desserts move to a small card brought after the mains. The type gets larger and the margins wider.

Within a few weeks, servers report that tables are ready to order sooner, vegetarian guests find their mains without asking, and sides are ordered more often now that they sit beside the starters. Desserts hold steady on their own card. The food has not changed; the layout has.

In servearound, the menu is kept once and laid out more than once. The same dishes, prices, photos and allergens feed the guest menu on the phone at the table, opened from each table's QR code, the venue's public menu page, digital menu boards and print designs. When a dish is marked sold out on the till, it shows as sold out on every guest menu at once.

Print designs start from a layout that your own menu fills in. A menu block has its own columns setting, the space between columns and the leader between a dish's name and its price, and it warns when a column does not fit. Designs can run to several pages and be printed or saved as a PDF, each published version is kept, and a design tells you when a price or a dish has changed on the menu since it was last printed. See the menus module.

It depends on the menu size. A short menu suits one column, a mid-sized menu two columns on one page, and a long menu a folder or separate lists.

As a rough guide, up to about fifteen dishes with short descriptions sit comfortably on one page in one column. Beyond that, two columns usually read better.

Usually a single page with two columns, with desserts on a separate card if space is tight. A folder would add page turns the menu does not need.

Near the top of their sections, with a little more space around them. Guests read section by section, so the first dishes in each section are hard to miss.

Large enough to read comfortably in your dining room's evening light. Test a printed copy at a table, not on a screen.

Many menus drop them to make prices quieter. Whatever you choose, keep prices consistent and next to each dish, not in a column of their own.

For a short drinks list, a single page with food and drinks can work. Long wine or cocktail lists are easier to read on a separate list.

Not well. A two-column PDF becomes tiny text on a phone. Keep the content in one place and lay it out separately for the phone.

Watch guests read it, time how long tables take to order, ask servers what guests ask about, and check whether the dishes you feature are ordered more.

Menu layout decides how guests read the menu before a word of it is read. A single page with one column suits a short menu, two columns on one page suit a mid-sized one, and a folder suits a long menu in a venue where guests take their time. Choose by menu size first, and if the menu only fits in a folder, ask whether it needs to be that long.

Within the layout, put the dishes that matter near the top of their sections, follow the order of the meal, use type large enough for the evening light and leave generous white space. Keep the content in one place, lay it out separately for print and for phones, and test every new layout on real guests before printing it in quantity.