If your LINE rich menu saved without complaint but nothing appears at the bottom of the chat window, the cause is almost always one of five settings, and the order you check them in decides how long this takes. Start with the display period, because an expired or future-dated one accounts for more of these cases than everything else put together. Then check whether the menu is set to open automatically. Then give LINE time to push it out. Then confirm the device in front of you can render a rich menu at all, since the PC and Chrome versions of LINE never show them. Only after those five is it worth questioning your image or your design.
This is written for someone running a LINE Official Account for the Japanese, Thai or Taiwanese market without reading the console’s original language, so each setting below carries its Japanese label as it appears on screen. The second half deals with the question most people are actually here for, which is why they cannot build a menu with tabs.
Table of Contents
Work through the causes in this order
The display period has expired, or it has not started yet
Every rich menu in the LINE Official Account Manager carries a display period, labelled 表示期間, with a start date and time and an end date and time. Both are required. The console will not warn you on the day your menu lapses, and it will not tell you that the menu sitting in your list looking perfectly healthy is scheduled to begin next Tuesday. Open the menu and read both ends of that period before you touch anything else.
Japanese operators deal with this by setting the end date absurdly far out, often a decade or more, so a menu meant to run permanently never quietly retires on its own. Copy that habit unless you have a real campaign window to respect.
The menu is published but set to stay collapsed
Separate from the display period, there is a setting controlling how the menu behaves when somebody opens the chat room. Set it to display and the menu is already expanded when they arrive. Set it the other way and the menu still exists, still works, but sits folded away behind the text input, and the person has to notice a small menu icon and tap it to bring the panel up. Whole campaigns have run on menus that almost nobody opened because of this one toggle. If your menu appears the moment you tap that icon, you have found your problem, and it is a one-click fix.
LINE has not finished pushing it out
The official manual is unusually candid here. It states that because of how the server processing works, time passes before the menu shows on the user side, and that the amount of time varies with congestion and with how many friends the account has. LINE publishes no figure for this. Small accounts often see the change within a few minutes. Accounts with very large friend bases have reported waits running into hours. If you published recently, stop editing and wait, because republishing repeatedly only puts you back at the end of the queue.
The device cannot display rich menus at all
PC LINE and Chrome LINE do not render rich menus. The manual says so plainly, and there is no workaround. iPad behaves in a way that regularly catches out design teams: Japanese operator guides consistently report that a rich menu displays on the iPad where the LINE account was created or to which the account was transferred, and does not display on any other iPad. So if your designer is reviewing on a shared office tablet, they will see an empty chat window no matter how correct your setup is. Check on a phone. Every single time.
The chat room has not been reopened
Somebody who had the conversation open while you published may keep seeing the old menu until they leave the room and come back to it. Ask whoever is testing to close the chat completely and return before they report a failure. It costs nothing to rule out.
A separate problem is the menu that refuses to save
If the console will not accept your menu at all, you are dealing with a different set of rules, and a small number of them cause nearly all the trouble.
The image comes first. The Official Account Manager accepts a narrow set of specifications, and the failure message it shows is not always specific about which one you missed.
| Requirement | What the console accepts |
|---|---|
| Image dimensions | 2500 × 1686 px for the large layout, 2500 × 843 px for the small layout |
| File format | JPG, JPEG or PNG |
| File size | 1 MB or less |
| Actions | At least one area of the template must have an action assigned |
One mix-up is worth flagging because it costs people an afternoon. A 1040 × 1040 px square is not a rich menu size. That is the format for a rich message, which is the tappable image you send inside a broadcast, and it is a completely different feature with its own billing behaviour. If your designer handed you a square file, they built the wrong asset.
The second rule catches everyone who works by duplicating. Copy an existing menu, leave its display period as it is, and if that period overlaps the display period of a menu already sitting in your scheduled or published tab, the console blocks the save outright. It shows a message and refuses to proceed. Shorten one of the two periods so they no longer collide, or park the new one as a draft until the old one ends.
The third rule is that you cannot set every region of a template to no action. Something has to be tappable. Designers who want a purely decorative strip across the top of a menu tend to hit this while experimenting, and the console will hold the save until an action goes somewhere.
Now the part about tabs, where the console gives up
The reasonable assumption is that tabbed rich menus are an advanced feature tucked away in a panel of the Official Account Manager you have not found yet. Go and look properly. Take your time, check the settings, check the beta features. The panel is not there, because tabbed and switching rich menus are not a feature of the LINE Official Account Manager, and no amount of clicking will produce one.
What a competitor’s tabbed menu is really made of is several separate rich menus, each created through the Messaging API rather than the console, one rich menu alias per menu, and a special action type called richmenuswitch placed on the tab strip of every one of them. Tapping a tab fires that action, which swaps the menu underneath the user for the one its alias points at. The chat window redraws and the result reads as a tab bar. Underneath, it is a set of images replacing each other.
Here is what has to exist on LINE’s side before any of that works:
- A Messaging API channel connected to the same LINE Official Account
- One rich menu created per tab, each with its own uploaded image
- One rich menu alias per menu, with up to 1,000 aliases available on an account
- A richmenuswitch action on each tab region, pointing at the alias of the menu it should reveal
- A default rich menu, so a new friend lands on a specific tab rather than nothing
What building tabs really costs
The good news for your budget is that the Messaging API carries no subscription of its own. It runs on the same LINE Official Account and the same message plan you already pay for, and rich menu operations are not billed as messages. Your costs sit somewhere else entirely.
You need somewhere to run the code that calls the API, which in practice means a small server or a serverless function that somebody keeps alive. You need a developer comfortable with the API to build it, and you need that developer again every time marketing wants a new tab, because no interface exists for a non-technical person to edit any of this. On top of that, the Messaging API upload limit for a rich menu image is 1 MB, so your designer is producing five or six images that each have to survive compression at 2500 px wide.
That ongoing maintenance burden is the entire reason a market of Japanese third-party LINE tools exists. They wrap the API in a console so a marketer can assemble a tab layout without opening a terminal, and they charge a monthly fee for it. Whether that trade is worth making comes down to how often your menu changes. A menu you rebuild twice a year is cheaper to hand to a developer for a week. A menu that changes with every campaign is where those tools earn their fee.
One caveat before you commit to the API route
Everything in the first half of this article still applies once you are building menus through the Messaging API. Propagation delay behaves the same way. PC and Chrome still show nothing. The iPad quirk is unchanged, and users still need to reopen the chat room to pick up a swap. Tabs give you more room to work with. They fix none of the display behaviour above, and a team that moves to the API expecting the invisible-menu problem to go away is going to be disappointed twice.