LINE Taiwan Pricing After November 2026: Plans and Message Counts
Taiwan LINE Official Account pricing changed on November 1, 2026. The medium-volume plan now costs NT$1,000 per month, and the high-volume plan NT$1,400, excluding tax. Included monthly messages remain 3,000 and 6,000 respectively. Choose a plan using counted outbound messages, not incoming support messages, webhook deliveries, or the number of message objects in your API payload.
Key takeaways
- The light plan remains NT$0 with 200 included messages; light and medium plans do not allow additional-message purchases.
- High-volume additional messages use progressive tiers: the first 50,000 additional messages cost NT$0.20 each; subsequent additional messages cost NT$0.15 each.
- Messaging API reply messages do not count toward the plan’s message allowance; push, multicast, broadcast, and narrowcast do.
- These are Taiwan Official Account prices, not a worldwide LINE rate card or a price for connecting an ordinary LINE account.
Compare the Taiwan plans after November 1
LINE’s 2026 developer announcements confirm that the revision took effect. The Taiwan official price-change notice provides the following figures. All amounts below are in New Taiwan dollars and exclude tax.
| Plan | Previous monthly fee | Monthly fee from November 1, 2026 | Included messages per month | Additional messages |
|---|---|---|---|---|
| Light / 輕用量 | 0 | 0 | 200 | Not available |
| Medium / 中用量 | 800 | 1,000 | 3,000 | Not available; upgrade if more are needed |
| High / 高用量 | 1,200 | 1,400 | 6,000 | Progressive additional-message charges |
The included allowances did not increase with the paid plans’ monthly fees. Do not preserve an old monthly fee in a budget merely because the included message count still looks familiar. Conversely, do not describe the change as a charge on every customer message: sending method still matters.
Use the dated revision notice for the November terms rather than an older calculator or copied pricing table. Verify the plan and applicable terms in the account’s billing interface before changing a subscription.
Count recipients and sending methods, not webhook traffic
LINE’s Messaging API pricing guide separates counted methods from reply messages.
| Activity | Treatment in the Messaging API plan count |
|---|---|
| Reply message | Not counted |
| Push, multicast, broadcast, narrowcast | Counted |
| A received webhook or its internal queue copies | Not a counted outbound send by itself |
| Several message objects in one send request | Object count alone does not determine the message count |
LINE counts by recipients. Its official example sends four message objects in one push request to a chatroom with five people: the count is five, not four or twenty. Therefore, request totals and JSON-array lengths are poor substitutes for the platform’s message-usage records.
For budgeting, keep separate records for incoming conversations, reply operations, counted outbound methods, and platform-reported usage. Reconcile them rather than claiming every successful HTTP request equals one chargeable message.
A slow AI answer deserves particular attention: switching from reply to push changes the counting category. That is not a reason to reuse an old reply token or push automatically after an uncertain send. Use the LINE reply-token and slow-response guide to design that decision separately from the budget.
Calculate high-volume charges progressively
The Taiwan revision notice defines tiers over additional messages, after the high plan’s 6,000 included messages:
| Additional-message position in the month | Price per message, excluding tax |
|---|---|
| 1–50,000 | NT$0.20 |
| 50,001 onward | NT$0.15 |
For a high-plan estimate, subtract 6,000 from the month’s counted volume, with a minimum of zero. Charge the first 50,000 remaining messages at 0.20 and only the remainder at 0.15, then add the 1,400 monthly fee.
These are illustrative calculations, not customer invoices:
- 10,000 counted messages: 4,000 additional messages. NT$1,400 + 4,000 × NT$0.20 = NT$2,200 before tax.
- 60,000 counted messages: 54,000 additional messages. NT$1,400 + 50,000 × NT$0.20 + 4,000 × NT$0.15 = NT$12,000 before tax.
The cheaper tier does not reprice the first 50,000 additional messages. These examples exclude separate vendor services and any account-specific credits or discounts; they are plan estimates, not final invoices.
For message capacity alone, light covers up to 200 counted messages and medium up to 3,000. Above that, evaluate high volume. Feature requirements can also influence the choice: the smallest sufficient allowance is not necessarily the best overall product fit.
Keep the sender identity in the comparison
If customers must interact with your LINE Official Account, retain the official Messaging API path and budget for its actual sends. Connecting another application does not create a separate Official Account allowance. Our multiple-tools checklist explains the shared-channel boundary and why tool ownership matters.
UnifyPort addresses a different requirement: an unofficial interface for supported conversations on a connected ordinary LINE account. The LINE authorization reference documents QR login, with QR URL and PIN delivered asynchronously through webhooks. It is not an import of your Official Account’s plan, audience, or Messaging API channel.
For that separate integration, supported messages arrive as normalized message.received events. Configure signing_secret and follow the webhook delivery contract to verify HMAC-SHA256 over the delivery timestamp, a dot, and the raw request body before storing and routing events.
Do not assume this route transfers Official Account friends, native campaign features, or existing conversations. Compare identity, supported capabilities, operating responsibility, and total costs before comparing price labels. No savings or feature parity is implied here.
FAQ
Did Taiwan’s included message allowances change?
No. The revision retains 200, 3,000, and 6,000 included monthly messages for light, medium, and high volume. The paid monthly fees and high-volume additional-message tiers changed.
Are Messaging API replies charged like push messages?
They are treated differently in the plan count. Reply messages are not counted; push messages are. That distinction does not make hosting, development, or other vendor services free.
Does passing 50,000 additional messages make all of them cost NT$0.15?
No. The tiers are progressive. Only additional messages from number 50,001 onward use that rate.
Should a Japan or Thailand account use this table?
No. This article covers the Taiwan revision. Confirm the applicable market’s official plan instead of converting these prices into another currency.
Next step and sources
Recalculate one month’s counted sends against the Taiwan price-change notice. If your requirement is instead ordinary-account message intake, review the UnifyPort LINE authorization boundary before choosing an architecture.
Official sources checked on 2026-11-11:
Turn messaging integration into a stable product pipeline.
Start by sending through one API, then bring every inbound message back into your business system with standard events.