Chat
Send messages with typing indicators and read receipts, in one-to-one or group conversations.
Record your screen or voice, use your webcam, make QR codes, test your calls or chat with ChatLite. Nothing to install.
Record your screen or voice, use your webcam, make a QR code and test a call before it matters. No installation and no account.
Chat, call, send files and share your screen with an invite link. No account, nothing to install.
Messages may pass through our server, see Your data
Record a screen, window or tab with optional voice and tab sound. Saves as a video on your device.
Processed in your browser, not sent to a server
Record your voice with a level meter, pause, playback and echo, noise and gain switches.
Processed in your browser, not sent to a server
Use your webcam as a mirror, check the light, take a photo or record a short clip.
Processed in your browser, not sent to a server
Turn a link or text into a QR code and download it as PNG or SVG.
Processed in your browser, not sent to a server
Measure delay, jitter and missed replies and see if it is good enough for voice, video or screen sharing.
Tiny timing requests to this site, nothing stored
Check your camera picture, microphone level, device list and permissions, with a fix for each error.
Processed in your browser, not sent to a server
See whether your network allows direct peer-to-peer WebRTC connections.
Asks public STUN servers, addresses stay on screen
Find out if your browser can share a screen, window or tab, and why not if it cannot.
Processed in your browser, not sent to a server
Independent explainers on camera and microphone permissions, why video calls fail on some networks, and how to protect your data.
Step-by-step help for Google Chrome on Windows, Mac and Android: answer the permission prompt, change the setting for one site, set defaults for all sites, undo a Block, and find out when the problem is outside Chrome.
Why chat and web pages load on an office or campus network while video calls do not connect: blocked UDP, proxies, filters and device policies, how to test it, and what to ask your network administrator for.
A clear comparison of encryption in transit (TLS/HTTPS), end-to-end encryption and the encryption built into WebRTC calls: who can read what, what each protects against, and how to judge a messaging service's claims.
A practical comparison of the three ways to send a big file: direct browser-to-browser (P2P) transfer, a cloud storage link and an email attachment, with the pros, cons, size limits and privacy implications of each.
A non-technical explanation of NAT, STUN, TURN and ICE: why two browsers cannot always connect directly, what each piece does, what host, srflx and relay candidates are, and what it all means for video calls.
What a browser keeps on a computer you share (cookies, site data, cache, history, saved passwords, permissions), how to use private windows, and step-by-step ways to clear it in Chrome, Edge, Firefox and Safari on computers and phones.
Step-by-step guides written from how ChatLite actually works, with the names you see on screen.
How to open ChatLite, set a nickname, send an invite link and exchange a first message, with what the person who invites (host) and the person who accepts (recipient) each see.
What to check when ChatLite cannot use your camera or microphone for a call, a voice message or QR scanning: browser permission, operating system settings, device choice and other apps.
Why a ChatLite chat can deliver messages while a voice or video call fails, how signaling differs from media, and the checks you can run on your side.
How ChatLite sends files directly or through its server, the actual size limits (100 MB direct, 8 MB through the server), what the success message really means and how to confirm receipt.
How to share a tab, window or screen during a ChatLite call, how to stop, and what to check when the button says screen sharing is not supported or the other person sees nothing.
Exactly what ChatLite keeps in your browser and what its server keeps, how to leave a conversation, clear everything from a browser, and how optional accounts change the picture.
The messenger is the best-known tool here: talk, call, send files and share your screen with an invite link.
All you need to start is a nickname and an invite link.
Instant startNo sign-up, no install
Clear data handlingSee exactly how data moves
All in one placeChat, calls, files, screen sharing
From one-to-one chats to small groups, start in seconds without complicated setup.
Send messages with typing indicators and read receipts, in one-to-one or group conversations.
Start a voice call straight from the conversation, right in your browser.
Turn on your camera for a face-to-face call. No plugin or app needed.
Send documents and images. Files travel directly between devices whenever a direct connection is possible.
Share your screen during a call to present, review or troubleshoot together.
Share an invite link or QR code. Friends join with just a nickname.
No sign-up form and no waiting for a verification email.
Your profile is stored in this browser.
Your friend can join without creating an account.
Use text, voice, video, files and screen sharing.
Traffic is encrypted in transit. ChatLite does not currently offer application-level end-to-end encryption, and some data passes through our servers, as summarized below.
Full data-flow detailsNo. Enter a nickname and start chatting. An optional account is available if you want to receive your messages on several devices.
ChatLite connects browsers directly with WebRTC when possible. If the network blocks a direct path, a relay may be used when one is available, but relay availability is not guaranteed, so a call can fail on some networks. Bitrate adapts to network conditions.
Yes. Use a modern browser to chat, call, share files and share your screen without installing anything. You can also install ChatLite as a PWA.
Traffic is encrypted in transit and chat history is stored in your browser. Some messages and files pass through our server for delivery, and push notifications use Google Firebase Cloud Messaging. On shared devices, clear your browser data after use.
Not at the application level. Direct WebRTC connections are encrypted between browsers, but messages relayed through our server, including group messages, are not end-to-end encrypted.
It lets you receive your messages on multiple devices. We store your email, a hashed password and your linked devices on our server.
No account required.