Protect messages in chat apps
Chat apps protect and carry messages in different ways. These guides explain native safeguards and how to add Layergram encryption before sharing. The comparison distinguishes documented limits from those still unverified: accepting a long message does not establish that a service preserves the invisible characters used in a cover message.
Conversation protection
Layergram protects content before sharing; it does not change account security, chat backups or the security of linked devices.
| App | Guidance for this chat |
|---|---|
| Protect messages on WhatsApp | Personal WhatsApp chats already use end-to-end encryption. Chat Lock controls local access to a conversation, a different function from encrypting content with Layergram. Also review linked devices and backup settings before sharing sensitive information. |
| Protect messages on Telegram | Telegram distinguishes cloud chats from end-to-end encrypted Secret Chats. Do not attribute the latter’s guarantees to cloud conversations. Choose the conversation type before testing: successful transfer in one chat does not certify every other route. Telegram exposes message_length_max in its client configuration. Layergram’s 4,000 preset was chosen for Telegram, but does not replace checking the actual field. Message bodies and captions are separate fields. Automatic splitting by a client does not establish that Layergram can reconstruct a token cut at an arbitrary character boundary. |
| Protect messages on Messenger | Meta introduced default end-to-end encryption for personal messages and calls on Messenger. Check the conversation indicator and history recovery settings. Protection in a personal chat does not automatically describe every interaction with a business. |
| Protect messages on Discord | Discord can convert overly long messages into text files. Choose a direct message or channel and check its audience before encrypting. A readable file attachment does not establish that importing content from the message body will work. Discord documents 2,000 characters for standard messages and 4,000 with Nitro. Above the limit, text may become a file attachment, which is different from receiving the payload in the chat body. The 2,211-character cover example already exceeds the standard allowance; the encrypted text and link representations require less space. |
| Protect messages on Signal | Signal conversations are already end-to-end encrypted. Key verification helps confirm the link to your contact. For long messages, open the complete content before copying: the preview’s displayed length is not the transport limit. |
| Protect messages on iMessage | Apple Messages can use iMessage, RCS or SMS/MMS. iMessage is end-to-end encrypted; RCS can be encrypted with supported carriers. A green bubble alone does not describe all protections. Check the actual protocol before testing. |
| Protect messages on LINE | LINE applies Letter Sealing to supported communication types. The app’s name alone does not describe every chat or content type. Check protection for the actual conversation and copy the full message without translation or preview shortcuts. |
| Protect messages on WeChat | Citizen Lab’s 2023 technical research examines privacy risks in WeChat and the Weixin ecosystem. That historical study is not certification of today’s app. Identify the service and account you use; test sending, copying and importing separately. |
| Protect messages on KakaoTalk | KakaoTalk offers end-to-end encrypted Secret Chat. Ordinary chats and Open Chat should not automatically be described with the same guarantee. If text opens in a long-message viewer, check that copying captures the complete content. |
| Protect messages on Viber | Viber distinguishes end-to-end encrypted personal and group chats from Communities, Channels and bots, which have different protection. REST Bot API limits do not certify personal chats. Check the conversation type and its encryption lock. |
Encrypted message length
The 4,000 preset is intended for Telegram; other apps may accept more or less. Count the final output, including invisible characters, prefixes and line breaks. An API limit does not establish the limit for personal chats. Bytes, Unicode code points and UTF-16 code units are different measurements for many texts.
No universal personal-chat limit was confirmed in the primary sources reviewed. Acceptance of 4,000 characters is not guaranteed.
Prepare and check delivery
Before relying on a chat for sensitive content, try a harmless message in the same format and of a similar length. The recipient must import the complete output into Layergram and recover exactly the original text. A delivery tick or a readable preview does not establish that the encrypted content arrived intact.
- Update both apps and verify your contact’s identity through a trusted channel.
- Write and encrypt in Layergram; use the integrated keyboard where available, or copy and share the output.
- Paste the complete output into the message body. Do not edit, translate or manually split it.
- If it is rejected or altered, shorten the original and encrypt again, or try the text format. Check decryption again.
Formats and space required
The following comparison is calculated from the public LMF v3 format; it is not a transport test in these ten apps. A headerless frame containing 256 ciphertext bytes occupies 452 binary bytes. Base64URL, a link and a cover encode the same frame; session data, acknowledgements and the chosen cover can increase the actual output.
| Representation | Example length |
|---|---|
| ASCII encrypted text | 606 characters |
| Layergram link | 620 characters |
| Minimum cover with invisible characters | 2,211 characters |
A link adds 14 characters to the token; it is not a short link. Public code supports authenticated fragments, but export may require one carrier within its capacity. Do not cut a token manually or assume automatic multiple sends. Always compare the actual output of your installed version.
Frequently asked questions
- Does Layergram hide who talks to whom?
- No. The platform can still observe accounts, timing, recipients and other metadata. A recipient can copy decrypted content or take screenshots.
- Do invisible cover messages work in every chat?
- This is not guaranteed. Filtering, normalization and copying can remove invisible characters. If the test fails, try shorter content or the text format and check again.
Sources and related guides
Sources checked on 30 October 2026. Chat features are documented by the respective services; LMF measurements come from the cited public specification and code. Documentary checks do not certify every operating system, app version and account combination. These guides are maintained by the Layergram editorial team, independently of the named platforms.
- WhatsApp — privacy
- WhatsApp — Chat Lock
- Telegram — FAQ
- Telegram — client configuration
- Meta — Messenger encryption
- Discord — Sending Messages
- Discord — Nitro
- Signal — private communication
- Signal — key verification
- Apple — iMessage, RCS and SMS/MMS
- LINE — Letter Sealing
- LINE — encryption report
- WeChat — privacy policy
- Citizen Lab — primary technical research (2023)
- KakaoTalk — Secret Chat
- Viber — encryption by chat type
- Viber — bot API (separate scope)
- Layergram — LMF v3 §8
- Layergram — carrier capacity
- Layergram — cover length settings