01Fundamentals
LINE Rich Menu image sizes, requirements, and a pre-upload checker
Inspect file type, pixel dimensions, aspect ratio, and file size locally before mapping tappable areas.
RICH MENU FIELD GUIDE
Build LINE Rich Menus correctly—from image to live actions
LINE-referenced guides with an image checker, JSON examples, and production-minded workflows you can apply directly.
12practical guides
TH / ENThai and English
LINE APILINE Developers sources
KNOWLEDGE / TOOLS / CHECKLISTS
Start with the problem in front of you
Every page includes canonical links, hreflang, Article schema, and official sources.
02Planning
LINE Official Account Manager vs Messaging API for Rich Menus
Choose the right tool up front because a single Rich Menu cannot be edited across OA Manager and the Messaging API.
03Workflow
How to retrieve and safely edit an existing LINE Rich Menu
Use a non-destructive workflow: import the existing menu, but publish the revision under a new Rich Menu ID.
04Pillar guide
How to build a LINE Rich Menu with the Messaging API and a visual editor
Complete the full workflow from artwork to a live menu while keeping design, validation, and publishing as separate gates.
05Code examples
LINE Rich Menu JSON examples for common actions
Learn the Rich Menu object from a complete example and identify which fields must match your artwork and backend.
06Troubleshooting
LINE Rich Menu errors: a systematic troubleshooting guide
Do not guess from a short message. Check authentication, JSON, image, resource state, and rate limits in that order.
07Experience design
Choosing the right LINE Rich Menu action
Choose an action from the user outcome and backend data requirement, not from the artwork label alone.
08Advanced
Build multi-page LINE Rich Menus with aliases and tab switching
Use stable aliases as destinations so menu IDs can change without rewriting every tab action.
09Business patterns
Rich Menu layout patterns for restaurants, stores, and clinics
Start with the jobs customers perform most often, not with the number of slots in a template.
10Analytics
Track LINE Rich Menu clicks with UTM parameters and analytics
Use consistent UTM names for menu, version, and button position so layout decisions can be tied to outcomes.
11Quality gate
LINE Rich Menu pre-publish checklist
Use one repeatable quality gate to prevent misaligned areas, broken destinations, and irreversible default changes.
12Security
How to handle a LINE channel access token safely
A token authorizes API calls for a channel. Treat it as a production credential, not ordinary configuration text.