One inbox for every site
Each website keeps its own widget, colours and domains. Your team answers all of them from one list.
Live chat that doesn't slow your site down.
A chat widget for your website, one inbox for your team, and that inbox on your phone. The script on each page is 4.8 KB. Pidge is free for one website.
No card needed. Live on your site in about five minutes.
Pidge
Questions? Chat with us.
Try it, type anything
Hi! This is what your visitors would see. Send a message and see how it feels. 🙂
Chat by Pidge
- 4.8 KB loaded on each page
- 14 ad-block filter lists tested
- Hosted in Norway
- Free for 1 website
Speed
4.8 KB on every page. The rest waits for a click.
The chat bubble needs one small script. The chat itself, 23.7 KB more, downloads when someone opens it, so visitors who never chat don't pay for it. Our build fails if that script passes 5 KB, so the number can't creep up. For scale, we measured Crisp's widget the same way.
21× less
5× less
7 fewer requests
Show the file sizes and how we measured them
| File | Over the wire (brotli) | Unpacked |
|---|---|---|
| pidge l.js (every page) | 4.8 KB | 12.6 KB |
| pidge chat (when opened) | 23.7 KB | 75.8 KB |
| crisp l.js | 2.8 KB | 7.5 KB |
| crisp client_default.js | 81.0 KB | 278.8 KB |
| crisp client_default.css | 13.4 KB | 129.5 KB |
| crisp en_default.js | 5.2 KB | 16.1 KB |
| crisp ticket worker | 3.1 KB | 7.8 KB |
| Crisp, before the chat is opened | 105.5 KB | 439.6 KB |
We measured Crisp on doomhosting.com on 14 October 2026 in Chrome, from Oslo, with brotli compression. The Pidge numbers come from the same build that serves this page.
What you get
Translation both ways
Write in English and a Swedish visitor reads Swedish. Their messages reach you in English, with the original one click away.
Inbox on your phone
Add the inbox to your home screen on Android or iPhone and get a notification for each new chat.
Replies by email
If someone closes the tab before you answer, they get your reply by email. When they answer it, that lands back in the same chat.
Live typing preview
You see what a visitor is typing before they send it, so you can start on the answer early.
One chat per customer
If your site tells Pidge who's logged in, a customer who switches from phone to laptop stays in the same chat.
Screenshots and log files
Visitors can paste a screenshot or drop in a log file. Big photos are resized on their device first.
Quiet bans
A banned visitor stops seeing the chat on all your sites. They aren't told they've been banned.
Ad blockers
Visitors with ad blockers still see it.
Some ad blockers hide chat widgets that load from a chat company's domain. Pidge can load
from a subdomain of your own site, like chat.yoursite.com, after you add
one DNS record, so to the browser it's part of your site. Without one it loads from
app.pidge.chat, which none of the filter lists we check block today.
Which lists block chat widgets, and how to check your site
Your chats, visitor details and files are stored on servers in Norway. Norway is in the EEA, so the GDPR applies.
- EasyList
- EasyPrivacy
- Fanboy's Annoyances
- uBlock Origin filters
- uBlock Origin privacy
- uBlock Origin annoyances
- AdGuard Base
- AdGuard Tracking Protection
- AdGuard Widgets
- Brave
- Also uBlock badware and quick fixes, AdGuard's other annoyances list and Peter Lowe's list.
For developers
Talk to it from your own code.
Tell the chat who's logged in, open it from a button, or let your bot answer. Keys, webhooks and signing secrets are on the inbox's Developers page.
- REST API. Read chats, send messages, set a visitor's details. On every plan, including free.
- Webhooks for new messages and visitor changes, signed and retried for about 24 hours.
- Widget commands on your page, like
$pidge.push(["do", "chat:open"]). - Your bot can answer. Once someone on the team replies in a chat, the bot's messages there are refused, so it never talks over a person.
On WordPress, Shopify, Squarespace, Wix, Webflow, Ghost or Framer? The install guides show where the snippet goes on each.
Moving from Crisp? Your existing $crisp code keeps
working, signed emails too. The REST paths and webhook signatures follow Crisp's, so a
backend that talks to Crisp needs a new base URL and key.
How to switch ·
How Pidge and Crisp compare
<!-- on every page --> <script> window.$pidge = []; window.PIDGE_WEBSITE_ID = "your-website-id"; </script> <script src="https://chat.yoursite.com/client/l.js" async></script> <!-- once the customer is logged in --> <script> $pidge.push(["set", "user:email", [email, signature]]); </script> # from your backend curl -u "$KEY_ID:$KEY" \ https://app.pidge.chat/v1/website/$SITE/conversations/1
Pricing
Free for one website. $10 per website a month when you want everything.
Free
$0for one website
No card and no time limit.
- One website
- Two people replying
- Live chat, the inbox and the phone inbox
- Replies by email, 50 a month
- Webhooks
- The full API
- No translation
Paid
$10per website, per month
Or $100 a year per website: two months free.
- As many websites as you add
- Unlimited teammates and chats
- Translation both ways, 100,000 characters per website a month
- Replies by email, 1,000 per website a month
- The full API
- Webhooks
Everything unlocked for your first 14 days. No card needed. After that you stay on the free plan unless you choose to pay, and nothing is deleted.
Every widget shows a small "Chat by Pidge" link, on both plans. VAT or sales tax is added at checkout where it applies.
Questions
What's on the free plan?
One website, two people replying, the inbox and the phone inbox, webhooks, and 50 reply emails a month. Translation is off, and the API can read but not write. If your workspace has more websites or people, nothing is removed: the oldest website keeps its chat, and the first two people, owners first, can reply. Everyone else can still read every chat.
What happens after the first 14 days?
For 14 days a new account has everything included, no card needed. Then it stays on the free plan unless you pay. Nothing is deleted, and paying later turns everything back on straight away.
Where is the chat data stored?
On servers in Norway, run by a Norwegian company. Norway is in the EEA, so GDPR applies just as it does in the EU. Files sent in chats are stored there too.
Can one inbox cover several websites?
Yes. Each website has its own widget, colours and domains, and your team answers all of them from one list. On the paid plan, each website is $10 a month.
Is there an iPhone app?
You add the inbox to your home screen from the browser, on iPhone or Android, and it sends notifications like an app. There's nothing to install from an app store.
How do I add it to my site?
Paste two lines of code into every page, then list your domain in the inbox. On WordPress there's a plugin. The install guides cover Shopify, Squarespace, Wix, Webflow, Ghost and Framer step by step.
Is there an API?
Yes: a REST API, signed webhooks and commands for the widget on your page. The API docs list every endpoint with examples. It all works on the free plan too.
We use Crisp today. How much work is moving?
Usually an afternoon. Your $crisp.push calls keep working as they are, signed emails too. The REST paths and webhook signatures follow Crisp's, so a backend that talks to Crisp needs a new base URL and key. Pidge vs Crisp also lists what Crisp has that Pidge doesn't.
What if Pidge isn't right for us?
Cancel whenever you like from the billing page; the plan runs to the end of the period you paid for, then you're back on the free plan. If you ask within 14 days of a payment, you get that payment back in full. See the refund policy.
Who sends the invoice?
Payments go through Paddle, our payment provider. They add VAT or sales tax for your country, take the payment and send the invoice. Your invoices are in the billing portal, linked from the inbox.
Want it on your site?
Start free
Free for one website. $10 per website a month for everything.