LINE Rich Menu Size 2500x1686: Official Specs, Templates & Image Guide (2026)

#Official Rich Menu Size Specs

LINE supports two officially-sanctioned image sizes for Rich Menus, both fixed-width at 2500 pixels. These specs come straight from the LINE Developers documentation and apply to every channel — Thailand, Japan, Taiwan, and global.

Quick rule of thumb: design at 2500 x 1686 px unless you have a strong reason for the slim 2500 x 843 layout (single-row CTA, minimal screen take-over).

If you are getting started, our complete LINE Rich Menu tutorial walks through design choices end-to-end. This page is the size & spec reference you should bookmark.

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

LINE only accepts these two height values for the 2500 px width. Any other size (e.g. 2500x1000, 2500x900, 2500x1200) will be rejected by the Messaging API and the LINE Official Account Manager — there is no other supported height.

#When to use 2500 x 1686 (Full)

• You want 3 rows of CTAs (e.g. 2x3 grid = 6 tiles, or 3x3 grid)
• You want a hero banner + sub-actions in the same menu
• Your audience is engaged and won't mind half the screen being a menu
• You're a restaurant, retail, beauty, or healthcare business with multiple flows (menu, booking, promo, contact)

#When to use 2500 x 843 (Compact)

• You only need a single horizontal strip of 2-4 actions
• Chat content is the primary value (e.g. customer service bots)
• You want to maximize the chat scrollback visible to users
• You're delivering a secondary menu behind a switch from a main menu

#File Format, Weight & Resolution Rules

The LINE rich menu image file must respect all of the following:

1. Pixel dimensions exactly: 2500x1686 or 2500x843 — not 2500x1685, not 2499x1686.
2. JPEG or PNG only. WebP, AVIF, GIF and TIFF are rejected.
3. Max 1 MB uncompressed file weight. Above 1 MB the upload returns HTTP 400 with size of an uploaded file exceeds maximum allowed size.
4. sRGB color space. CMYK and Display P3 PNGs render with shifted colors on iOS LINE clients.
5. No transparency required (LINE composites against the chat background) — flatten alpha if you save PNG.

#How to hit 2500x1686 under 1 MB

The most common issue: the design is right but the file is 1.4-2.5 MB. Fix it by:

• Exporting JPEG quality 75-85 (rather than PNG) for photographic content
• Using PNG-8 / indexed color if your menu is mostly flat colors and icons
• Running the final file through Squoosh or TinyPNG — typically saves 40-60%
• Avoiding embedded ICC profiles and metadata (mogrify -strip on the CLI)

Pro tip: in Figma, export at 1x (so 2500 px width) with "Color Profile: sRGB" then strip metadata. This consistently yields ~600-900 KB.

#Tappable Areas (Coordinates & Layout)

Each rich menu can declare up to 20 tappable areas, but 6 to 9 areas perform best based on engagement studies. Coordinates are integers in image-pixel space (not percentages).

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

{
  "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",      "uri": "https://example.com/menu" } },
    { "bounds": { "x": 833,  "y": 0,   "width": 834, "height": 843 },  "action": { "type": "postback", "data": "action=book" } },
    { "bounds": { "x": 1667, "y": 0,   "width": 833, "height": 843 },  "action": { "type": "uri",      "uri": "https://example.com/promo" } },
    { "bounds": { "x": 0,    "y": 843, "width": 833, "height": 843 },  "action": { "type": "message",  "text": "Contact" } },
    { "bounds": { "x": 833,  "y": 843, "width": 834, "height": 843 },  "action": { "type": "uri",      "uri": "https://example.com/loyalty" } },
    { "bounds": { "x": 1667, "y": 843, "width": 833, "height": 843 },  "action": { "type": "richmenuswitch", "richMenuAliasId": "submenu", "data": "switch=submenu" } }
  ]
}

833 + 834 + 833 = 2500 (the middle column compensates for the rounding). This is the canonical 6-tile grid.

#Layouts that consistently perform well

• 3 × 2 on 2500x1686 → 6 large tiles, ~833x843 px each
• 3 × 3 on 2500x1686 → 9 tiles of ~833x562 px each
• 4 × 1 on 2500x843 → 4 wide tiles of 625x843 px each
• 3 × 1 on 2500x843 → 3 wide tiles of ~833x843 px each

For deeper guidance on how to design for these layouts, see our Rich Menu design tutorial.

#The 1000 Rich Menus Per Channel Limit

A frequently-misunderstood quota: each LINE Messaging API channel can store a maximum of 1000 rich menus — including unused ones. Once you hit 1000, the API returns:

#What counts toward the 1000

• Every rich menu you create with POST /v2/bot/richmenu
• Rich menus created from the LINE Official Account Manager UI
• Auto-generated rich menus from third-party tools

#What does not count

• The image upload itself (rich menus without an image still count, but the image isn't a separate object)
• Rich menu aliases (a separate, smaller alias quota)
• Default vs. user-linked menus — both count once

#How to stay under the limit

1. Delete old rich menus with DELETE /v2/bot/richmenu/{richMenuId} after switching to a new one.
2. Use the list rich menus endpoint to audit.
3. Reuse aliases instead of creating fresh menus for every variation.
4. If you operate rich menu A/B tests, clean up losing variants automatically via webhook + cron.

If you regularly hit the cap, LineBot.pro's rich menu manager handles deletion and rotation automatically.

#Ready-to-Use Templates

The fastest path from spec to live menu is starting from a template:

• 6-tile grid (3x2, 2500x1686) — restaurants, retail, beauty
• 9-tile grid (3x3, 2500x1686) — large catalogs, education
• Hero + 3 (banner top + 3 CTAs, 2500x1686) — promotion-heavy SMEs
• 4-tile strip (4x1, 2500x843) — customer-service bots, news

Generate a custom Rich Menu in 60 seconds with our AI generator — it outputs a 2500x1686 PNG ready for upload.

#Common Size & Upload Errors

#Frequently Asked Questions

Q: Is the LINE Rich Menu size 2500x1686 still valid in 2026? Yes — 2500x1686 (full) and 2500x843 (compact) remain the only supported sizes in 2026. LINE has not changed Rich Menu spec since the 2019 Messaging API revision.

Q: Can I use 2500x1000 or 2500x1200 for a Rich Menu? No. The LINE API rejects any height other than 1686 or 843 for a 2500-pixel-wide image. There is no flexibility on this.

Q: What is the maximum file size for a LINE Rich Menu image? 1 MB. Both PNG and JPEG count under the same 1 MB ceiling. The API responds with HTTP 400 above this size.

Q: How many rich menus can a single LINE Official Account have? Up to 1000 rich menus per channel. Delete unused ones with DELETE /v2/bot/richmenu/{richMenuId}. Rich menu aliases have a separate, smaller quota.

Q: Does the 2500x1686 size work for both Thai and Japanese LINE accounts? Yes — the spec is global. The same image dimensions, file size, and tappable area rules apply across Thailand (TH), Japan (JP), Taiwan (TW), and worldwide LINE Official Accounts.

Q: What happens if my image is 2499x1686 instead of 2500x1686? The upload is rejected. LINE checks pixel dimensions exactly. Always export at the canonical 2500x1686 px.

Q: Can I have transparent backgrounds in a Rich Menu PNG? You can upload a PNG with alpha, but LINE flattens it against the chat background, which differs in light vs dark mode. Best practice: design with a solid background.

Q: How do I switch between full and compact rich menus? Both sizes work the same in the API — only the size.height value differs. You can swap between them by deleting the current menu and creating a new one with the other height, or by rich menu switch actions between two different menus.

Next steps:

• Build your menu visually with LineBot.pro Rich Menu Builder
• Read the full Rich Menu design & creation tutorial
• Set up your LINE Official Account first if you haven't yet
• Explore LINE Rich Menu services for done-for-you design