Blog · 2026-09-17

LINE Rich Menu: Sizes, Layouts, Templates and Tap Routing (2026)

The six Rich Menu sizes, the hard specs LINE enforces, how to choose a layout, where the templates actually live, plus four limits that are in the official docs and almost nobody mentions: you cannot swap the image, the two tools do not mix, PC users never see it, and only one menu can be live at a time.

The Rich Menu is the most valuable piece of real estate a LINE Official Account has. Users see it every time they open the chat, it costs nothing in message fees, and LINE's own manual describes it as a 24-hour route into engagement.

Most tutorials stop at "make an image in Canva and upload it". This one covers specs, layouts, templates, tap routing, and the four limits that will make you rebuild.

What a Rich Menu is, and why it goes first

It is the collapsible image menu at the bottom of the chat, and every cell can be given an action. The "LINE@ rich menu" you see in older articles is the same thing, since LINE@ was merged into LINE Official Account long ago. Per the official manual, each cell has five possible actions: coupon, URL, text, loyalty card, or no action.

The reason to do it first is practical: it does not count against your message fees. LINE bills broadcasts by recipient delivered. The Rich Menu is not a broadcast, it just sits there. You pay a one-off design cost and get a permanent placement.

One limit up front, clearly documented and almost always missing from Chinese-language tutorials:

Rich menus aren't displayed on LINE for PC (macOS, Windows).

The Rich Menu does not appear in LINE for PC. If a meaningful share of your customers talk to you from a desktop, your important entry points cannot live only in the menu. Give them another route.

Rich Menu sizes: there are six, not two

The sizes you find online contradict each other. Some say 1200×810, others say 2500×1686. Both are right and both are incomplete. The official manual says there are six uploadable image sizes, balancing resolution against file size.

Those six are really two aspect ratios times three resolutions:

LINE also points out that the display frame inside the app is a fixed size. Upload a small image and it looks rough on a high-resolution phone. Upload a large one and it is sharper but heavier and slower to load. In practice, pick the 2500 tier unless your artwork is complex enough to push the file over the limit.

The hard specs, where over the line means the upload fails

These numbers come from the Messaging API documentation on LINE Developers and are enforced at the system level:

The 1 MB cap is the one people trip over. A 2500×1686 PNG exported from Canva blows past it easily. Save as JPEG or compress it first and you are fine. The Rich Menu also does not support transparency, so a PNG with a knocked-out background turns black or white on upload.

Choosing a layout: work backwards from how much you have to say

Rich Menu layouts split into large and compact. Large comes in six-cell, four-cell, three-cell and two-cell splits. Compact is usually three or two. Count how many things you actually need people to tap first, then pick the cell count.

What this looks like in practice:

• Three or four cells works best. More cells means smaller cells, thumbs that miss, and labels that do not fit.
• Large leaves room for a key visual. One merged row across the top and three cells below is the configuration that holds up longest: brand or current campaign on top, three clear actions underneath.
• Compact suits accounts with simple entry points. If you only have booking, address and support, use compact. Do not stretch it into six cells.

Write actions in each cell, not categories. "Our services" gets no taps. "Book online" does. "More information" gets no taps. "Check my points" does.

Order matters too. Most thumbs land on the lower right of the screen, so your most important action works better bottom right than top left.

Our LINE OA platform turns the Rich Menu into a visual drag-and-drop layout with live preview and one-click publish. The cell split is a routing question, not an art question. Which cell gets sign-up and which gets support is planned around your conversion goal, not around what looks tidy.

Where to get Rich Menu templates and assets

You do not need to draw the guide lines yourself. LINE provides templates, and the documentation is explicit about it:

You can download a template image for your rich menu from the LINE Official Account Manager. From the page you create rich menus, click Design guide.

So on the Rich Menu creation page in the console, click Design guide and download the template for your layout. That is free and it is the most accurate source available, far better than a Rich Menu template of unknown origin found online.

Once you have the template:

1. Open a canvas at the matching size in Canva or any design tool.
2. Import the template image as the bottom layer and drop its opacity. It is only there for alignment.
3. Keep icons and text inside the cells with a safe margin. Elements flush to an edge get clipped on some devices.
4. Delete the template layer, export as JPEG or PNG, and confirm the file is under 1 MB.

There is no mystery to Rich Menu assets. Single-line icons in your brand colour are plenty. What actually moves the numbers is the copy and the routing, not how elaborate the illustration is.

Setting it up in the console

Per the official manual the flow is two steps:

1. Click Rich menu on the home page, then create.
2. Configure the fields and save.

A few fields tend to get skipped:

• Title: for your own management only, never shown to users. When you are running several campaigns, a clear title saves a lot of digging.
• Display period: schedulable. This field connects to the trap in the next section.
• Menu bar text: the strip at the very bottom of the chat. You can customise it, and something more specific than "Menu" earns a few more taps.
• Default display: choose Shown and the menu is already open when the user enters the chat, choose Hidden and they have to tap to expand it. New accounts should use Shown.
• Cell actions: coupon, URL, text, loyalty card, or none. LINE does not allow every cell to be set to no action. Coupon and URL actions need an action label of up to 20 characters, which is what screen readers announce.

Four limits that will make you rebuild

This is where this guide differs from the rest. All four are in the official documentation, and almost no Chinese-language tutorial collects them.

Here is where each one comes from.

On the image not being replaceable, the LINE Developers documentation says:

You can't replace an image set to a rich menu. To update your rich menu image, create a new rich menu object and upload another image.

On the two tools not mixing, the same document states that a menu created in the console can only be retrieved and edited in the console, and the same applies in reverse for menus created through the API.

On only one being live, the official account manual says only one rich menu can be shown to a user, and a configuration with overlapping periods cannot be saved.

On desktop, this is from the Rich menus overview: "Rich menus aren't displayed on LINE for PC (macOS, Windows)."

LINE also notes that after you save a menu the server needs time to process it, so it takes a while to reach users, and the more friends you have the longer it takes. If it has not appeared on your own phone right after saving, do not rush to redo it.

Multi-page menus and per-user menus: the console cannot do either

The two most common advanced requests get the same answer: the LINE Official Account Manager cannot do it, you need the Messaging API.

• Multi-page menus: split the menu into a first and second page, with one cell switching between them. LINE lists this capability under the Messaging API benefits column (Switch between tabs on rich menus). The console has no such action type.
• Per-user menus: different people see different menus. The documentation splits menu scope in two. Both tools can set the default menu for all users, but only the Messaging API can set a menu for an individual user.

Those two are worth very different amounts. Members see "My points, Order lookup, Support" while people who have not bought yet see "First-purchase offer, Popular items, Join as member". The same placement says different things to different people, and it costs nothing extra in message fees.

Building it yourself means handling identity mapping, menu binding and page state, plus one landmine that catches people in practice: if you pause a sub-menu used for paging, anyone already switched to that page falls back to the default menu and does not return automatically. When you change campaigns, build the new menu first, point the entry at it, confirm nobody is still on the old one, and only then take the old one down.

We built these capabilities into a product

Everything above runs as one system in our console:

• Rich Menu builder: visual drag-and-drop layout, live preview, one-click publish, no working out sizes and guide lines yourself
• Multi-page and per-user menus: through the Messaging API, showing different menus by tag and funnel stage
• Segmented push: people who came in through the menu get tagged automatically, so later pushes only go to the relevant group
• 8-stage funnel tracking: which cell got tapped, and whether the tap led anywhere
• CRM contact management: who tapped what and which stage they are at, so support has the full context before picking up
• API integration: connect the menu to your own order or membership system

Three tiers, monthly fee in USDT, no lock-in:

The official account in your plan is registered under your own name, not parked under ours. Pausing it or moving it is your call.

If you want the whole account structure first, read the complete LINE Official Account guide. Full platform specs and the onboarding process are at LINE OA platform.

FAQ

Does the LINE Rich Menu cost anything? The menu itself is free and does not consume your message allowance. It works fine on the Light plan at 0 per month. What costs money is outbound broadcasting, which is billed by recipient delivered.

How do I build my own Rich Menu in LINE? In the Official Account Manager, click Rich menu on the home page, then create, pick a layout, upload the image, set the action on each cell, and save. Download the template from Design guide in the console to get your alignment exactly right.

How do I set up a multi-page Rich Menu? The console has no paging feature. You need the Messaging API to create several menus and set switch actions between them. When you change campaigns, do not simply pause a sub-menu that is still in use. Anyone already on it falls back to the default menu.

How do I create a Rich Menu in a LINE bot? Call three Messaging API endpoints in order: create the menu, upload the image, set it as the default menu. Remember that a menu created through the API cannot be edited in the console. The two tools do not mix.

Which Rich Menu size should I actually use? Usually 2500×1686 (large) or 2500×843 (compact). The hard limits are width 800 to 2500, height 250 and above, aspect ratio 1.45 and above, file size under 1 MB, JPEG or PNG.

The specs and limits in this article come from the LINE Official Account manual and the LINE Developers Messaging API documentation. LINE adjusts its specs from time to time, so treat the current information in the console and the official docs as authoritative.