Export Chats From Signal, Snapchat, Slack and Other Apps

The word “backup” is often mistaken for “export.” A backup may restore messages inside the same app while giving you no readable file to print, search, or share.

Official options at a glance

Use official routes first. They are less likely to violate platform rules, expose credentials, or lose structured information through screen capture.

App	Official route	What it provides	Important gap
Signal	Secure Backup, Android on-device backup, or device transfer	Encrypted restoration archive or moved history	No documented readable single-chat export
Snapchat	My Data request	Account archive selected through Snapchat’s request flow	Do not assume expired/deleted chats or every Snap are included
WeChat	Phone migration or Windows/Mac backup and restore	History transferable/restorable in WeChat	No official readable transcript format documented
LINE	Chat › menu › Settings › Export chat history	.txt of messages currently appearing	Not restorable; media is not a full transcript attachment package
Viber	More › Settings › Account › Viber Backup	Cloud backup or same-platform transfer	Intended for restore, not a readable transcript
Teams Free	Microsoft’s Export My Data page	Messages and media request for the consumer service	Different from work/school Teams
Teams work/school	Admin export tools, APIs, or Purview/eDiscovery	Chats, channel messages and metadata according to role/tool	Ordinary members lack a whole-chat export button
Slack	Workspace owner/admin export	Usually JSON ZIP; scope depends on plan and approval	Public-channel export does not ordinarily include DMs/private channels
Google Chat	Google Takeout	Messages, attachments, profile and memberships	Some work/school-created spaces and group messages excluded
Tinder	Download My Data	HTML and possibly JSON; may include messaging activity/messages	Deleted data and information affecting another person’s privacy may be absent
Bumble	Subject Access Request	Account data; conversation requests supported	Both participants may need separate requests for both sides
Hinge	In-app Download My Data or privacy request	User data; past-chat request may return your side	Other member’s information excluded; retention limits apply

An official archive is not automatically complete. Retention settings, disappearing messages, account deletion, workplace policy, other-user privacy, and the request date all affect scope.

Signal: backups now exist, readable export still does not

Signal’s current backup story is broader than it was in earlier years. Signal Secure Backups can restore across platforms and are protected by a 64-character recovery key that Signal says it does not receive. The free archive includes all text messages and the last 45 days of media; Signal documents additional media availability through its paid backup tier. Android also has an on-device backup option, and direct transfers exist.

Those features are designed to restore Signal. Signal’s official help does not document a command that exports one conversation to readable PDF, CSV, HTML, or text. A Signal Desktop “backup” is likewise not a promise of a portable transcript. Do not hand an encrypted restore archive to a recipient and call it a readable export.

For preservation, enable the appropriate official backup before replacing or reinstalling the app, store the recovery key separately, and test Signal’s documented status. For a human-readable record, capture screenshots or a screen recording while the conversation remains available. Save important attachments through Signal’s sanctioned controls when possible.

Disappearing and view-once content need immediate, careful handling. Signal says some short-lived content is not restored from Secure Backups. Do not circumvent another person’s device or platform security.

Snapchat: request My Data, then capture what remains visible

Snapchat offers My Data through its account portal and app support flow. Request the narrowest relevant date range and categories offered, wait for the archive, and preserve the original download ZIP before opening copies.

Do not treat the request as a recovery service. Snapchat’s support has a separate “Can I request a copy of a Snap?” article, and the platform’s deletion behavior means content no longer available to the account may not be returned. State exactly what the delivered archive contains rather than claiming “all chats.”

If a relevant chat is still visible:

1. Capture the friend’s profile and username, not only the display name.
2. Record whether messages show as saved in chat.
3. Capture date dividers and visible times.
4. Use overlap between images.
5. Preserve the My Data archive alongside the screenshots.

Avoid notifying or alerting another user accidentally when the app’s screenshot behavior matters to safety. Follow local advice and platform rules; do not use covert-access tools.

WeChat and Viber: restoration is not transcript export

WeChat officially supports migrating selected chats to another phone and backing up/restoring history through WeChat for Windows or Mac. Its help says both devices should be on the same network for migration and explains that the computer backup can later merge into phone history. It does not document a standard PDF, CSV, or text transcript file for the user.

Viber similarly supports phone-to-phone Wi-Fi transfer and cloud backup. Its support says phone backups are tied to the phone number and platform, and cross-platform restore is not supported. Text, photos, and videos can be included according to backup choices. Desktop and secondary tablet are not the primary backup route.

For either app, create the official restore backup first if continuity matters. Then make a separate readable capture. Do not manipulate proprietary backup files with an unverified converter, especially if it asks for account credentials or uploads the archive.

LINE has a real text export, with a precise limit

LINE is the clearest app in this group for a readable single-chat export. On a main phone or supported subdevice:

1. Open the chat.
2. Tap the menu at the top.
3. Choose Settings › Export chat history.
4. Choose a secure destination for the .txt file.
5. Open the file and compare the first and last entries with LINE.

On Windows or Mac, LINE documents Chats › [open chat] › menu › Save chat. LINE explicitly says only messages that currently appear in the chat are saved. Scroll and check history before exporting, and do not claim missing or unavailable content was included.

The text file is a reading copy and cannot restore history into LINE. Preserve media separately and note where a text placeholder corresponds to a file. LINE’s Standard Backup is a different product feature for restoring chats and normally saves text only; do not confuse it with Export chat history.

Slack: scope belongs to the workspace, not each member

Slack exports are controlled by workspace owners and administrators. On Free and Pro, owner/admin exports cover public channels. Slack says exports contain file links rather than the files themselves; Free exports also exclude data more than one year old under the current plan rules.

Broader private-channel and direct-message exports are restricted. Free and Pro owners can apply under limited circumstances and must show legal process, member consent, or an applicable legal right or requirement. Business+ owners can apply for self-service all-channel exports subject to law and policy. Enterprise offers additional organization and single-user options.

Slack’s ZIP uses JSON for public or all-conversation exports. A qualifying single-user export may be JSON or TXT. JSON messages include fields such as user, text, and a Unix-style ts timestamp. File URLs may stop working later, so authorized administrators should preserve permitted files separately while access remains valid.

Employees should not install scraping extensions or use another person’s token. Ask the workspace owner, HR, legal, or compliance team to preserve the relevant channels. Workplace monitoring and exports are governed by law and policy, not only technical availability. See the HR complaints guide for a careful escalation path.

Microsoft Teams: consumer and workplace routes are different

Microsoft Teams Free users can use Microsoft’s Export My Data route for messages and media. Follow the current support page and preserve the delivered archive.

Work and school Teams do not give every member the same account-download control. Organizations can use Microsoft Graph export APIs, migration export tooling, or Microsoft Purview/eDiscovery according to licensing, permissions, retention, and legal authority. Microsoft’s export API supports 1:1 chats, group chats, meeting chats, and channel messages, but it requires administrator-approved protected application permissions.

If you are an ordinary member, ask an administrator to preserve the named chat, channel, date range, and attachments. Screenshots can document what you can see now, but they should not replace an authorized organizational export when one is required.

Google Chat: Takeout includes messages and attachments

Google’s official Chat help says a personal Google account can download profile information, direct/group/space memberships, messages, and attachments through Google Takeout.

1. Go to Google Takeout while signed in to the correct account.
2. Deselect unrelated products, then select Google Chat.
3. Create the export using a secure delivery destination.
4. Download all archive parts before their links expire.
5. Keep originals and inspect copies.

Google notes that group messages and spaces created by work or school users are not included in a personal Chat history export. Work/school users should contact their administrator. Organization-wide exports also omit some groups or spaces created outside the domain.

Dating apps: request early, before deletion or unmatching

Dating-app exports protect the other person’s privacy, so a download may not recreate both sides of a chat.

Tinder’s Download My Data tool returns a ZIP with a browser-readable index.html and may include JSON. Tinder says it may include messaging activity and messages, but content deleted under retention rules or restricted for another person’s privacy or safety can be excluded.

Bumble directs users to make a Subject Access Request through support. Its June 2026 guidance says that for a past-match conversation, both participants need separate requests to obtain each side.

Hinge offers Settings › Download My Data for active accounts. Its support says exports exclude personal information about other members. A separate past-chat article says a request may provide your half of messages from the past two years, and that account deletion can make chats unavailable. Request data before deleting an account.

Keep profile identifiers, match details, and request correspondence with the archive. A screenshot of a display name alone may not identify the account.

The screenshot and screen-recording fallback

A disciplined capture is more useful than a folder of random images. Prepare the phone first: connect power, disable pop-up previews, set a readable text size, keep orientation fixed, and make enough free space for a long recording.

Then capture:

1. Start with the app name and conversation header.
2. Open the profile or details screen to show username, number, channel, or members.
3. Return to the earliest needed message.
4. Expose date and time controls where the app permits it.
5. Scroll slowly in one direction.
6. For screenshots, overlap one or two messages between every image.
7. For video, pause briefly on each date divider and important attachment.
8. Continue past the final relevant message to show context.
9. Save attachments separately without changing the original capture.
10. Keep originals; highlight and redact only copies.

Do not crop the contact header, bubble edges, dates, or scroll order. Do not splice a video without preserving the untouched original. Record any gap caused by disappearing content, an unloaded image, or app retention. The preservation guide and screenshots guide provide a fuller workflow.

Where Text Exporter fits

Text Exporter for iPhone (coming soon) will use on-device OCR for screenshots and screen recordings from apps that lack a suitable official export. It will let the user review OCR and participant assignments, then create PDF, CSV, and TXT with a SHA-256 manifest. Content will stay on the device.

OCR does not turn a screenshot into native platform data. It cannot recover hidden timestamps, deleted messages, usernames outside the frame, or original attachments. Use an official export when one exists, preserve screenshots as the source, and treat OCR corrections as a separate overlay. The app will have a one-time price rather than a subscription.