How to Export Telegram Chat History

Telegram chat export is a desktop feature. The mobile apps can display and share messages, but Telegram’s documented JSON and HTML export requires Telegram Desktop.

Export one Telegram conversation

Use the per-chat command when you need one private chat, group, or channel.

1. Install the latest official Telegram Desktop app and sign in.
2. Open the target chat.
3. Open the ⋮ menu and choose Export chat history.
4. Select the media types to include, any size limit offered, and the date range.
5. Choose Machine-readable JSON for conversion or Human-readable HTML for browsing.
6. Choose a destination folder and start the export.

Do not move individual media files out of the results folder. Relative paths in JSON or HTML connect each message to its attachment.

Export all Telegram account data

The account-wide route is Settings › Advanced › Export Telegram data. Select the chat types and other account categories you need, then choose JSON or HTML and a destination. Telegram’s original announcement also describes Settings › Export Telegram data; the current schema documents the Advanced submenu.

Account-wide JSON normally uses result.json. A single-chat HTML export uses messages.html; full HTML exports use export_results.html. The official schema shows folders for chat photos, videos, files, voice messages, video messages, stickers, and other selected media.

What result.json records

JSON is the strongest input for a timestamped transcript because it separates display text from metadata. A message can include id, type, date, date_unixtime, from, from_id, text and text_entities, reply references, forwarded-from information, edited dates, reactions, and relative media paths. Fields appear only when relevant.

date is a readable ISO-style value; date_unixtime is its Unix representation. Preserve both. A converter should not infer deletion from gaps in IDs, and it should not flatten formatted text without retaining the original entities.

Telegram’s official schema, rather than an example file from one account, is the reliable guide to available fields. Export contents evolve, and chats differ.

JSON versus HTML

Choose JSON if you plan to make a PDF, CSV, or searchable dataset. It preserves structured sender and timestamp values and is less dependent on Telegram’s page styling. Choose HTML if you only need to browse an offline copy. It provides linked pages that open directly in a web browser.

HTML is not inherently more complete. Completeness is controlled by the chats, dates, media categories, and size settings selected before export. Save a screenshot of those options or record them in notes.

New-session security delay

A newly signed-in Telegram Desktop session may not be allowed to export immediately. Users commonly see a client warning requiring confirmation on another device or a wait before trying again. Telegram’s public export pages do not currently specify a universal 24-hour period, so treat “24 hours” as an unverified client-dependent report, not a guaranteed rule.

Do not keep retrying or use unofficial account automation. Follow the prompt in Telegram, confirm from an existing session if offered, and record the actual time the export becomes available.

Secret Chats and deleted messages

Secret Chats cannot be exported through Telegram Desktop. Telegram explains that they are not part of Telegram Cloud and remain tied to their devices of origin. The desktop and web apps load cloud data and do not support that device-bound history.

If a Secret Chat must be preserved, use careful screenshots or a screen recording on the original device while it remains available. Capture participant identity, date dividers, and surrounding context. Avoid triggering self-destructing media merely to document it.

Telegram allows users to delete sent and received cloud messages for both sides without a trace, and says its servers do not retain deleted chats and call logs. An export therefore cannot restore deleted content. Record known gaps candidly.

Convert Telegram JSON to PDF

Open the Telegram-to-PDF tool and select the preserved JSON export or folder package. Processing stays in your browser; message files are never uploaded. Review the chosen time zone, participant labels, replies, reactions, and attachment links before downloading.

Keep result.json, its media folders, export notes, and the PDF together. Hashing or later verification can show whether a saved source file changed, but it cannot prove that Telegram supplied every historical message. Preserve the original device and add screenshots when identity or interface context matters.

Set the export options carefully

Telegram Desktop lets the user define the scope, so an export is only as broad as its recorded settings. Before starting, note the app version, destination folder, chat or account-wide route, date range, media categories, and any maximum file-size control shown.

Option	Effect on the result
Machine-readable JSON	Produces structured records suitable for conversion and analysis
Human-readable HTML	Produces linked pages for offline browsing
Date range	Excludes events outside the chosen start and end dates
Photos, videos, voice messages, video messages, stickers, GIFs, and files	Includes only checked media categories
Size limit	Can omit an individual file above the selected limit while leaving its message record

For one conversation, use ⋮ › Export chat history. For a broader account request, use Settings › Advanced › Export Telegram data and select personal chats, bots, private groups, public groups, or channels as needed. Exact categories vary with account activity and Desktop version.

Export JSON first when a PDF is the goal. If easy visual browsing matters, create a separate HTML export rather than changing the only result folder. Keep each output in its own directory and preserve the settings used for it.

Read Telegram message fields in context

result.json can describe account information and multiple chats, or a single selected conversation. A chat entry identifies its type and contains a messages array. Each message’s id is useful for reference, but an ID gap does not establish that someone deleted a message.

The date field is readable while date_unixtime supplies a machine-oriented Unix value. from is a display label and from_id is the associated exported identifier when available. A message may contain plain text, a mixed text_entities array for links and formatting, or media metadata instead of ordinary text.

Replies can use reply_to_message_id; forwarded items can name their origin; edits can carry an edited date; and reactions can identify emoji and counts or actors according to what Telegram exports. Fields are conditional. Preserve an unknown field instead of treating it as an error, and do not turn a missing optional field into a factual conclusion.

Media paths are relative to the result folder. Moving result.json alone breaks those links. A file may also be absent because its category was unchecked, it exceeded the chosen size, it was unavailable, or it was not downloaded. Keep those explanations distinct.

Export groups and channels

Groups and channels need additional identity context. A group record can include many senders, service events, replies, and membership changes. A channel can contain posts attributed to the channel rather than an identifiable individual. Comments may belong to a linked discussion group rather than the channel’s own message sequence.

Capture the conversation information page, public link or username where applicable, and member or administrator labels relevant to the dispute. Display names can change. Preserve exported IDs and public message links instead of replacing them with current names.

In an account-wide export, select the appropriate private and public group or channel categories. Afterward, locate the expected chat in result.json and check its first and last dates. If it is absent, document the selection and access state; do not infer that no conversation existed.

Understand Secret Chat boundaries

Secret Chats are separate from cloud chats and remain tied to their originating devices. That is why signing into Telegram Desktop cannot expose them to Export chat history. A similarly named cloud conversation is not a replacement for the Secret Chat.

If lawful preservation is necessary, keep the original mobile device and capture the visible Secret Chat carefully. Include its header, date dividers, and overlapping context. Some media may self-destruct when opened, so do not open an unseen item merely to improve a record. Label screenshots and recordings as visual captures, not Telegram JSON exports.

Convert Telegram JSON step by step

The free Telegram-to-PDF tool processes supported JSON locally in the browser. The selected conversation is not uploaded.

1. Copy the complete Telegram result folder to controlled storage and retain an untouched copy.
2. Open the tool and select result.json or the supported package.
3. Choose the intended chat and review sender labels.
4. Set the display time zone, then compare several rendered times with Telegram Desktop.
5. Inspect replies, edits, reactions, service events, and media references.
6. Download the PDF and record the conversion date and settings.

The PDF is a presentation copy. Keep it with result.json, all media subfolders, screenshots of export settings, and acquisition notes. If a media item was omitted by the export size setting, say so rather than leaving a blank page unexplained.

Preserve Telegram evidence for a dispute

A defensible workflow keeps both native structure and visible identity context. Preserve the computer and phone sessions where practical, the complete export folder, account and chat information screens, public links, and relevant attachments. Include enough messages around a reply or forwarded item to show what it refers to.

Record who performed the export, when, on which computer, from which Telegram account, and with which options. Make excerpts only from a working copy and label omitted ranges. The preservation guide explains source handling; the authentication guide covers identity and authorship context.

Courts and other decision-makers set their own requirements. Follow the directions for disclosure, filing, translation, redaction, and exhibits. The court guide gives general background but is not legal advice.

Troubleshoot an incomplete export

First inspect the scope. Check whether you used per-chat or account-wide export, the selected date range, chat categories, media checkboxes, and size limit. Confirm that Telegram Desktop had finished before closing it and that all files remain together.

If export is blocked after a new login, follow the client prompt. A confirmation on an existing device or a waiting period may be required, but Telegram’s public export documentation does not promise a fixed delay. Do not bypass the control with unofficial automation.

If messages visible on mobile are absent from Desktop, determine whether the conversation is a Secret Chat. For cloud history, allow Desktop to synchronize and retry to a new folder without overwriting the first attempt. Deleted-for-both-sides content cannot be supplied by a converter. Preserve the observed gap and any lawful contemporaneous screenshot instead.