LINE Rich Menu Size 2500x1686: Specs & Templates (2026)

#Official Rich Menu Size Specs

The recommended LINE rich menu sizes are 2500×1686 px (large) and 2500×843 px (compact), saved as a JPEG or PNG of 1 MB or less. LINE Official Account Manager also accepts two smaller versions of each shape, and the Messaging API accepts any image 800–2500 px wide whose width is at least 1.45 times its height. All figures are as of October 2026.

Sources: the LINE Official Account Manager manual (in Japanese) and the Messaging API reference. The rules are the same for accounts in Thailand, Japan, Taiwan and every other country.

Tired of resizing artwork by hand? An AI rich menu maker exports images at exactly these sizes.

#Messaging API rules (developers)

• Width: 800 to 2500 px. Height: at least 250 px.
• Ratio: width ÷ height must be 1.45 or more, so a 2500 px wide menu can be at most 1724 px tall.
• File: JPEG or PNG, 1 MB maximum, uploaded as image/jpeg or image/png.
• Object limits: up to 20 tap areas, chatBarText up to 14 characters, name up to 300 characters.

This page is the size reference. For the setup itself, follow our tutorial on how to create a LINE rich menu. Rich messages, card-type messages and Flex Messages use different image sizes: see the LINE rich message guide.

#Full (2500x1686) vs Compact (2500x843)

LINE OA Manager calls the two shapes Large and Compact. LINE recommends the large one when you want to show more content, and the compact one when you want a balanced chat screen that leaves more room for the conversation.

#When to use 2500×1686 (Large)

• You need four to six buttons, or a wide banner above three buttons.
• Your business has several customer journeys: menu, booking, promotions, location (restaurants, retail, beauty, clinics).
• The rich menu is your main navigation.

#When to use 2500×843 (Compact)

• One to three buttons are enough.
• The conversation comes first: customer service, consultations, bookings by chat.
• It is a secondary tab that you switch to with the Messaging API.

#All 12 layouts in LINE OA Manager

Other heights, such as 2500×1000 or 2500×1200, are not available in OA Manager. They are valid through the Messaging API because they respect the 1.45 ratio rule, but most design templates and tools are built for 1686 and 843.

#File Format, Weight & Resolution Rules

A rich menu image has to pass every one of these checks:

1. JPEG or PNG only. The upload API answers HTTP 415 when the Content-Type isn't image/jpeg or image/png, so convert WebP, HEIC or GIF files first.
2. 1 MB maximum. This is the most common reason an upload fails.
3. The exact pixel size. OA Manager only takes the six template sizes. Through the API, draw the image at exactly the size declared in the rich menu object, because tap areas are measured in those pixels.
4. Prefer 2500 px wide. LINE shows every size in the same frame, so 800 or 1200 px images can look rough on high-resolution phones. Bigger files load a little more slowly, which is why the 1 MB cap matters.
5. RGB colours. Export in sRGB; CMYK is a print format.
6. A solid background. Design on an opaque background instead of relying on transparent areas.

#How to get 2500×1686 under 1 MB

• Export photos and gradients as JPEG at quality 75–85.
• Export flat graphics (icons, solid colours) as PNG, ideally with a reduced palette (PNG-8).
• Run the file through Squoosh or TinyPNG and remove metadata.
• Don't upscale a small image to 2500 px: the file gets heavier without getting sharper.

#Tappable Areas (Coordinates & Layout)

In LINE OA Manager you never type coordinates: the template you pick defines the tap areas, and it splits only the links, not your artwork. With the Messaging API you declare up to 20 areas, each with a bounds object: x and y for the top-left corner, then width and height, all in image pixels.

#Example: 6-area grid (3 columns × 2 rows) on 2500×1686

{
  "size": { "width": 2500, "height": 1686 },
  "selected": true,
  "name": "restaurant-main-menu",
  "chatBarText": "Menu",
  "areas": [
    { "bounds": { "x": 0,    "y": 0,   "width": 833, "height": 843 }, "action": { "type": "uri",      "label": "Menu",       "uri": "https://example.com/menu" } },
    { "bounds": { "x": 833,  "y": 0,   "width": 834, "height": 843 }, "action": { "type": "postback", "label": "Book",       "data": "action=book" } },
    { "bounds": { "x": 1667, "y": 0,   "width": 833, "height": 843 }, "action": { "type": "uri",      "label": "Promotions", "uri": "https://example.com/promo" } },
    { "bounds": { "x": 0,    "y": 843, "width": 833, "height": 843 }, "action": { "type": "message",  "label": "Contact",    "text": "Contact" } },
    { "bounds": { "x": 833,  "y": 843, "width": 834, "height": 843 }, "action": { "type": "uri",      "label": "Location",   "uri": "https://example.com/map" } },
    { "bounds": { "x": 1667, "y": 843, "width": 833, "height": 843 }, "action": { "type": "richmenuswitch", "label": "More", "richMenuAliasId": "submenu", "data": "switch=submenu" } }
  ]
}

833 + 834 + 833 = 2500: the middle column takes the extra pixel, so the grid covers the full width without gaps. The richmenuswitch action in the last tile only works once the submenu alias exists.

#Tile sizes of the OA Manager layouts

LINE doesn't publish an official "safe zone" for rich menus. In practice, keep each label and icon well inside its tile, away from the borders, so a tap near the edge never lands on the neighbouring button. More layout and design advice is in the design section of our rich menu tutorial.

#The 1000 Rich Menus Per Channel Limit

Through the Messaging API, one LINE Official Account (one Messaging API channel) can hold up to 1,000 rich menus. Rich menu aliases, used for tab switching, have their own limit of 1,000 per account. Once the menu limit is reached, the create request returns HTTP 400 and you must delete a rich menu before creating a new one.

#What counts, and why accounts hit the limit

• The limit concerns rich menus created through the Messaging API. Menus made in LINE OA Manager are managed separately: the API can't list them, and OA Manager doesn't show API-created menus.
• An uploaded image can't be replaced, so every redesign or variant becomes a new rich menu. Per-user menus multiply the count quickly.

#How to stay under it

1. List everything with GET https://api.line.me/v2/bot/richmenu/list.
2. Delete what you no longer use with DELETE https://api.line.me/v2/bot/richmenu/{richMenuId}.
3. Reuse menus: link one rich menu to many users (up to 500 user IDs per bulk request) instead of creating a copy per customer.
4. Mind the rate limit: creating and deleting rich menus through the API is capped at 100 requests per hour (menus managed in OA Manager aren't affected).

#Ready-to-Use Templates

These free sources already use the correct sizes:

• Design guide in LINE OA Manager: blank template images for every layout, on the rich menu creation page.
• LINE Rich Menu Maker by LINE Thailand: the 12 standard layouts, icon sets by business type and Thai text; it saves a 2500 px wide JPEG.
• LY Marketing Campus: free template images for rich menus, rich messages and coupons (Japanese).
• LINE Biz-Solutions Taiwan downloads: rich menu templates for retail, F&B, beauty and seasonal campaigns (Traditional Chinese).
• Canva: plenty of rich menu templates; set a custom canvas of 2500×1686 or 2500×843 before exporting.

Tips for choosing and editing them are in our list of free rich menu templates.

#Make the Image with AI at the Right Size

LineBot.pro's AI rich menu maker picks the size from the number of buttons, so you never resize anything by hand:

The labels are drawn inside their tiles, the image is compressed under 1 MB, and you also get the rich menu JSON with tap areas that match the artwork. Each menu costs 10 credits, and new accounts get 50 free credits. LineBot.pro doesn't publish to LINE: upload the image in LINE OA Manager with the matching template. The five-button layout has no OA Manager template, so use it through the Messaging API.

Generate a correctly sized rich menu →

#Common Size & Upload Errors

Error messages and limits are taken from the Messaging API reference.

#Frequently Asked Questions

Q: Is 2500x1686 still the right LINE rich menu size in 2026?

Yes. As of October 2026, 2500×1686 (large) and 2500×843 (compact) are the recommended sizes in LINE Official Account Manager, and LINE's own API examples use 2500×1686.

Q: Can I use 2500x1000 or 2500x1200 for a rich menu?

Not in LINE OA Manager, which only accepts its six template sizes. Through the Messaging API, yes: both respect the rules (800–2500 px wide, at least 250 px high, width ÷ height of 1.45 or more). At 2500 px wide, the tallest valid menu is 1724 px.

Q: What size is a 6-button rich menu?

2500×1686 px with the 3×2 template. Each tile is about 833×843 px.

Q: What is the maximum file size for a LINE rich menu image?

1 MB, for both JPEG and PNG. Export photos as JPEG at quality 75–85, or reduce the PNG palette, to get under the limit.

Q: How many rich menus can a LINE Official Account have?

In OA Manager you can create several, but only one is displayed at a time, so you schedule them by display period. Through the Messaging API you can create up to 1,000 rich menus and 1,000 aliases per account.

Q: Why does my rich menu look blurry?

You probably uploaded an 800 or 1200 px wide version, or upscaled a small image. LINE shows every size in the same frame, so start from a 2500 px wide original.

Next steps:

• Set it up step by step: how to create a LINE rich menu
• Rich message, card and Flex image sizes: LINE rich message guide
• No account yet? Read the LINE Official Account setup guide
• Skip the design work with the AI rich menu maker