Latest, 21 Oct 2026:12 usersMove the mouse over the chart for any month
Ratings count
monthly, 3 months
Latest, 21 Oct 2026:0 ratingsMove the mouse over the chart for any month
The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.
About Meetly
Meetly — Private, Encrypted, Peer-to-Peer
Meetly is a Chrome side-panel extension that lets you chat and share files with people you trust—directly and encrypted. No accounts, no friend lists, no server storage. Just you and the other person.
Key Features
Peer-to-peer (P2P): Built on WebRTC, your texts and files travel straight between your browser and your peer's—no relay server, so platforms can't log your conversations or files.
End-to-end encryption (E2EE): Uses ECDH P-256 key exchange + AES-GCM 256. Even the signaling server can't eavesdrop. A fresh one-time key is generated for every connection.
Safety number (MITM defense): After connecting, both sides see a safety code. Verify it out-of-band (e.g. by phone) to confirm you're really talking to the right person and block man-in-the-middle attacks.
Nicknames: Set a nickname and the other side sees it on connect. Change it mid-chat and it syncs instantly; every message shows who sent it.
Large file transfer: P2P speed is bounded only by your bandwidth, not by server attachment limits—great for raw assets and sensitive docs.
Always at hand: A browser side panel means you can chat or send files while browsing, without switching apps.
Getting started
After install, click the Meetly toolbar icon to open the side panel.
Your unique ID appears at the top—copy and send it to someone you trust.
Enter their ID in the connect box and click "Connect".
Wait for key negotiation (🔒 Encrypted shows up), verify the safety code, then start chatting.
Type in the bottom box to send text, or use the 📎 button to send a file.
Privacy promise
Meetly uploads no messages, files, or chat logs to us or any third party. The WebRTC signaling needed to establish a connection is briefly exchanged via the public PeerJS server and never touches message content; everything is end-to-end encrypted. See the privacy policy below.