---
title: "Verify LINE Webhook Signatures — Free Online Tool | WebhookRelay"
meta:
"og:description": "Free online LINE webhook signature verifier. Validate the x-line-signature header against your channel secret. Paste the payload, secret and signature to check it instantly — runs in your browser, no signup."
"og:title": "Verify LINE Webhook Signatures — Free Online Tool"
description: "Free online LINE webhook signature verifier. Validate the x-line-signature header against your channel secret. Paste the payload, secret and signature to check it instantly — runs in your browser, no signup."
---
# **Verify LINE Webhook Signatures**
The LINE Messaging API signs each webhook with HMAC-SHA256 over the raw request body and sends the **base64** result in the `x-line-signature` header. The key is your channel secret from the LINE Developers Console. Paste the raw body, the channel secret and the header value.
**Raw request body (payload)**
**Channel secret**
**Computed signature**
**Signature to verify **(x-line-signature)
**Paste the x-line-signature value above to compare**
Everything runs in your browser — the payload and secret never leave this page. Want to verify a different provider? See the [webhook signature verifier hub](https://webhookrelay.com/verify-line-webhook-signature/verify-webhook-signature/) or the generic [HMAC generator](https://webhookrelay.com/verify-line-webhook-signature/hmac-verification/).
## **How LINE signs webhooks**
1. Take the **raw** request body exactly as received — do not parse or re-serialize it, as even changing escape characters breaks the signature.
2. Compute HMAC-SHA256 using your channel secret as the key.
3. Base64-encode the digest and constant-time compare it to `x-line-signature`.
**References & official docs:**
- [LINE — Verify webhook signature](https://developers.line.biz/en/docs/messaging-api/verify-webhook-signature/)
- [LINE — Messaging API reference: signature validation](https://developers.line.biz/en/reference/messaging-api/)
## **Verify LINE signatures in code**
**Node.js**
```
const crypto = require('crypto');
const expected = crypto
.createHmac('sha256', process.env.LINE_CHANNEL_SECRET)
.update(rawBody) // raw request body, unmodified
.digest('base64');
const received = req.headers['x-line-signature'];
const valid = crypto.timingSafeEqual(
Buffer.from(expected), Buffer.from(received));
```
**Python**
```
import hmac, hashlib, base64
expected = base64.b64encode(hmac.new(
channel_secret.encode(), raw_body, hashlib.sha256).digest()).decode()
received = request.headers['X-Line-Signature']
valid = hmac.compare_digest(expected, received)
```
## **Frequently asked questions**
**Where is the LINE channel secret?**
In the LINE Developers Console on your channel's "Basic settings" tab. It is used as a raw UTF-8 string. Re-issuing the channel secret immediately invalidates the previous one.
**Why does LINE signature verification fail?**
Almost always because the body was parsed and re-serialized. LINE signs the exact bytes — including escape characters and UTF-8 line breaks — so verify against the unmodified raw body before any JSON parsing.
## **Verify other providers**
[Stripe](https://webhookrelay.com/verify-line-webhook-signature/verify-stripe-webhook-signature/) [ GitHub](https://webhookrelay.com/verify-line-webhook-signature/verify-github-webhook-signature/) [ Shopify](https://webhookrelay.com/verify-line-webhook-signature/verify-shopify-webhook-signature/) [ Slack](https://webhookrelay.com/verify-line-webhook-signature/verify-slack-webhook-signature/) [ Twilio](https://webhookrelay.com/verify-line-webhook-signature/verify-twilio-webhook-signature/) [**S** Standard Webhooks](https://webhookrelay.com/verify-line-webhook-signature/verify-standard-webhooks-signature/) [ Square](https://webhookrelay.com/verify-line-webhook-signature/verify-square-webhook-signature/) [**A** Airwallex](https://webhookrelay.com/verify-line-webhook-signature/verify-airwallex-webhook-signature/) [**M** MyFatoorah](https://webhookrelay.com/verify-line-webhook-signature/verify-myfatoorah-webhook-signature/) [ Zendesk](https://webhookrelay.com/verify-line-webhook-signature/verify-zendesk-webhook-signature/) [ DocuSign](https://webhookrelay.com/verify-line-webhook-signature/verify-docusign-webhook-signature/) [**K** Klarna](https://webhookrelay.com/verify-line-webhook-signature/verify-klarna-webhook-signature/) [**A** Attio](https://webhookrelay.com/verify-line-webhook-signature/verify-attio-webhook-signature/)
[HMAC Generator](https://webhookrelay.com/verify-line-webhook-signature/hmac-verification/) [CloudEvents Validator](https://webhookrelay.com/verify-line-webhook-signature/cloudevents-validator/) [Webhook Tester (Bin)](https://webhookrelay.com/verify-line-webhook-signature/webhook-bin/)
Receiving LINE webhooks on a server behind a firewall or on localhost? Webhook Relay can [forward them to your internal service](https://webhookrelay.com/verify-line-webhook-signature/webhooks/) and even [verify or transform them](https://webhookrelay.com/verify-line-webhook-signature/features/transform-webhooks/) before delivery.