How can I export Telegram chat history from the desktop app?

Introduction to Telegram Chat History Export

Telegram offers a built-in tool to export your chat history directly from the desktop application, enabling you to save messages, media, and account data in either human-readable HTML or machine-readable JSON formats. Whether you are backing up important conversations, migrating to another platform, or performing a personal audit, understanding the nuances between export formats and their limitations is critical. In this guide, we compare the export options side by side, walk through the exact steps, and highlight boundaries you must consider before starting an export. By the end, you will be equipped to choose the right configuration and handle any pitfalls that may arise.

Feature Positioning & Evolution

The export feature first appeared in Telegram Desktop around 2018 and has since been refined through incremental updates. As of the latest version in 2026, it remains accessible from Settings → Advanced → Export Telegram data. This tool is designed to export all your cloud chats, including private conversations, groups, and channels. However, it cannot export secret chats (end-to-end encrypted), deleted messages, or data from accounts you do not own. The export is a one-time snapshot; there is no incremental or scheduled backup functionality. Understanding this constraint early helps set realistic expectations for what the tool can deliver.

Comparing Export Options: A Side‑by‑Side Analysis

When you open the export dialog, you are presented with several choices that affect the output's size, readability, and utility. The two major dimensions of comparison are format and media inclusion. Below we break down what each combination offers and when you should prefer one over the other, so you can match the configuration to your specific use case.

Format: HTML vs. JSON

The export tool offers two output formats, each suited to different downstream needs:

HTML – Produces a folder with an index.html file and subfolders per chat. Each page is styled for readability in any browser. This is the best choice if you only need to view the backup later or share it with non-technical parties.
JSON – Generates a single result.json file (and a separate JSON per chat for large exports). This format is ideal if you intend to process the data programmatically, import into a database, or perform search/analysis.

There is no built‑in conversion tool. Once you export in one format, you cannot convert it to the other without third‑party scripts. Choose based on your future use case — if you are uncertain, HTML offers easier immediate readability, while JSON preserves more structural detail for later processing.

Media Inclusion: With vs. Without

You can toggle media files (photos, videos, voice messages, stickers, GIFs) on or off, and the implications are significant for both storage size and long-term accessibility:

Including media – Produces a much larger export directory (potentially gigabytes). The tool downloads every file from Telegram’s servers at the time of export. This is the only way to obtain a self-contained copy of your media, as the cloud links in HTML/JSON point to Telegram’s CDN and may become inaccessible if deleted from the server.
Excluding media – The export will contain only text messages and metadata (file names, sizes, MIME types). This is much faster and lighter, suitable for a textual archive or when you only need message content.

Note that media can be selectively included/excluded per type (photos, videos, etc.). This is useful if you want only certain media categories — for instance, archiving photos but skipping large video files to save space.

Decision Tree: Which Export Configuration Should You Use?

Now that you understand the options, here is a simple decision tree based on your primary goal. This framework helps you translate your intent into concrete export settings:

Do you need a friendly backup to browse later? → Choose HTML with all media included. This creates a browsable archive similar to viewing Telegram in a browser.
Are you planning to process the data with scripts or import into another service? → Choose JSON, with or without media depending on whether you need the actual files or just metadata.
Is storage space a major concern? → Export only text (no media) or limit media by type (e.g., photos only).
Do you need to export just one chat instead of your whole account? → Unfortunately, the built‑in tool only exports all chats at once. For a single chat, consider using a third‑party bot or the Telegram API, but be aware of security risks and rate limits.

Use this decision tree as a shortcut to avoid trial and error. Once you have settled on a configuration, follow the step-by-step instructions below to execute the export.

Operation Steps: Exporting Chat History from Telegram Desktop

Below are the exact steps to initiate an export on the latest version of Telegram Desktop (as of October 2026). These instructions assume you have already chosen your preferred format and media settings using the decision tree above.

Step 1: Open Settings

Launch Telegram Desktop. Click the three‑line menu (☰) at the top left, then select Settings. Alternatively, use the shortcut Ctrl + , (Windows/Linux) or Cmd + , (macOS).

Step 2: Navigate to Advanced Settings

In the Settings window, scroll down and click Advanced. Under the Data section, find and click Export Telegram data.

Step 3: Configure Export Options

A dialog titled Export Telegram data appears. Here you can fine-tune the export to match your needs:

Choose the format (HTML or JSON).
Check/uncheck Include photos, Include videos, etc. Unchecking all means text only.
Optionally limit the export to specific chats by unchecking Export all chats and selecting individual ones (this is a recent improvement – check if your version supports it).
Set the Size limit per file (default 100 MB) – larger exports are split into multiple files.

Take a moment to review your selections before proceeding. If you are exporting a large account, consider limiting chats or media to reduce the risk of failure.

Step 4: Start Export

Click Export. A progress bar shows download status. Depending on the amount of data, this can take from seconds to hours. Do not close the app during export, as doing so will abort the process and require a fresh start. When finished, Telegram opens the output folder automatically.

Step 5: Verify the Export

Open the index.html (for HTML) or result.json (for JSON) to ensure data integrity. Spot‑check a few conversations and media files. Note that large exports may produce multiple JSON files – they are named like messages_1.json, messages_2.json, etc., and you may need to combine them for full coverage.

Exceptions & Trade‑Offs

Even with a successful export, there are important limitations to be aware of. Knowing these exceptions beforehand can prevent frustration later — especially if your use case involves sensitive or high-volume data.

Secret Chats Are Not Exportable

Secret chats use End‑to‑End Encryption (E2EE) and are deliberately excluded from the export tool. This is by design to preserve user privacy. If you need a backup of a secret chat, consider copying messages manually or requesting the other party to forward them. There is no workaround within the official tool.

No Incremental or Scheduled Backups

The export is a one‑time operation. To have an up‑to‑date archive, you must manually re‑export periodically. There is no official API or desktop setting for automatic backups. Some third‑party scripts (not affiliated with Telegram) try to simulate this, but they violate the Terms of Service and may get your account rate‑limited or banned. For ongoing archival needs, weigh the inconvenience of manual exports against the risks of unsanctioned automation.

Media Preservation vs. Cloud Availability

When you export with media, Telegram downloads the original files from its servers. However, if a message was deleted by either party before the export, it will not be included. Also, if you export without media, the resulting archive only contains links (thumbnails) that may break if Telegram removes the underlying file from its CDN. For permanent offline access, always include media — especially for messages that contain irreplaceable photos or videos.

Large Chat Performance

Exporting a chat with hundreds of thousands of messages can be slow. In such cases, Telegram may split the output into multiple files. Expect the process to use significant CPU and memory. As an empirical observation, a chat with 100,000 messages and heavy media can take 30–60 minutes on a modern machine. You can reduce time by excluding media or selecting only specific chats (if your version supports that). Planning for this overhead ensures you do not start an export when you have limited time or system resources.

Integration with Bots and Third‑Party Tools

While the built‑in export is sufficient for most users, some may want to export data into other systems like email archives, note‑taking apps, or databases. Below are general approaches, but note that Telegram does not officially endorse any third‑party tools, and you assume all associated risks.

JSON → Database import: The JSON output is well‑structured. You can write a script (Python, Node.js) to parse the result.json or segmented files and insert records into a SQL database. Each message object contains fields like id, type, date, text, and from.
HTML → PDF conversion: Tools like wkhtmltopdf can render the HTML export into a single PDF for offline reading. This is useful for archival purposes but loses interactive elements.
Third‑party archive bots: Some bots claim to export individual chats by being added to a group and downloading history. Use extreme caution: bots have access to messages while they are in the group. Telegram’s terms prohibit mass data harvesting, and such bots may be shut down or compromise your data.

If you choose to use a script, follow the principle of least privilege: only process the exported JSON files locally, never share your credentials or session. For database imports, start with a small sample export to validate your parsing logic before tackling the full archive.

Troubleshooting Common Export Issues

Even with careful preparation, you may encounter issues during or after the export. Below are frequent problems and their remedies, ordered by how commonly they occur.

Export Button Is Greyed Out

Symptom: The “Export” button cannot be clicked.
Cause: You may have unchecked all data types or set invalid options.
Resolution: Ensure at least one data type (e.g., “Personal chats”) is checked. If you have selected “Export all chats”, try selecting specific chats instead.

Export Fails Midway with Network Error

Symptom: Progress bar stops and shows “Network error”.
Cause: Unstable internet connection or Telegram server timeout on large requests.
Resolution: Retry the export. If it fails repeatedly, try excluding media to reduce size, or select fewer chats. Also, check your internet stability. The export tool does not resume from where it failed; it restarts from scratch. To mitigate this, consider exporting in smaller batches if your account is very large.

Missing Messages in Export

Symptom: Some messages that appear in the app are not in the exported file.
Possible Causes: The messages were deleted after the export started; they are in a secret chat (not exported); or the chat is a “saved messages” note that was edited after the export.
Verification: Compare the message IDs in the export with those visible in the app (you can use the “Search” feature to find the message and note its date). If the message was edited, only the latest version appears in export.

Output Folder Contains Only a Few MB

Symptom: The export completes quickly but the folder is tiny.
Cause: You may have excluded all media and selected only a few chats, or the export process ended prematurely.
Resolution: Check the index.html or result.json for completeness. If it contains only partial data, re‑export with more inclusive settings and monitor the progress bar to ensure it runs to completion.

Applicable & Non‑Applicable Scenario Checklist

Use this checklist to decide if the built‑in export fits your needs. It summarizes the insights from the previous sections into a quick reference you can consult before starting.

✅ When to Use

You want a one‑time full backup of your Telegram cloud chats.
You need to preserve media for offline access.
You are leaving Telegram and want a personal archive.
You plan to process the data programmatically (choose JSON).
You are a single user with a moderate‑sized account (under a few GB of media).

These scenarios align well with what the built-in tool was designed to handle, minimizing friction and risk.

❌ When Not to Use

You need a continuous, automated backup solution (use Telegram API with caution).
You only want to export a specific private chat (consider manual copy or a third‑party tool, but risks apply).
You are a large organization needing to export all employee chats (the tool does not support multi‑account management).
You require exporting secret chats (not possible by design).
You need to comply with legal eDiscovery requirements that demand chain‑of‑custody – the export lacks audit trails.

In these cases, the built-in export will fall short, and you should explore alternative solutions — accepting the associated trade-offs.

Best Practices Checklist

To ensure a smooth export and a reliable archive, follow these recommendations. They combine technical precautions with practical habits that save time and prevent data loss.

Close unnecessary applications to free up RAM and disk I/O.
Ensure you have enough free storage – the export folder can be 2× to 3× the size of the original data due to unpacked media.
Use a stable, fast internet connection to avoid timeouts.
Do not use Telegram during export to prevent conflicts (the tool may lock the local database).
Verify the export immediately – open a few HTML pages or parse the JSON to confirm completeness.
Store the export securely – it contains your entire conversation history. Encrypt the folder or store it offline.
If exporting for legal reasons – document the export time, settings, and a hash of the output to maintain integrity. Telegram does not provide a built‑in digital signature, so you must create one yourself (e.g., SHA‑256 checksum).

Adhering to these practices will help you avoid common pitfalls and ensure that your exported data remains trustworthy and accessible for years to come.

Frequently Asked Questions

Can I export only one chat without exporting everything else?

In the latest versions of Telegram Desktop, you can choose to export only specific chats. In the export dialog, uncheck “Export all chats” and manually select the chats you want. If your version does not show this option, you must export all and then manually discard the unwanted folders, or use a third‑party script to filter the JSON afterwards.

Does Telegram Premium give me any additional export capabilities?

As of 2026, Telegram Premium does not add any extra export features. The export tool is identical for free and Premium users. Premium benefits like larger file uploads and faster downloads do not affect the export process itself.

Can I resume an interrupted export?

No. If the export fails or is cancelled, it must be started from the beginning. The tool does not support incremental or partial resumption. To minimise risk, consider selecting a smaller subset of chats first if your account is very large.

Can I export chat history using the mobile app or web version?

No. The export feature is only available in Telegram Desktop. Mobile apps and the web client do not have an export option. You must use the desktop app on Windows, macOS, or Linux.

Does the export include data from channels I administer?

Yes. The export includes all channels where you are a member or admin, as long as you have access to their message history. Note that private channels you were removed from prior to export will not be included.

Conclusion

Exporting your Telegram chat history from the desktop app is a straightforward process that gives you a portable archive of your conversations. By understanding the differences between HTML and JSON formats, the implications of including media, and the inherent limitations (no secret chats, no incremental backups), you can choose the configuration that best aligns with your needs. For a one‑time backup or programmatic processing, the built‑in tool is sufficient. For ongoing or granular exports, consider alternative approaches—but be aware of the lack of official support. After export, always verify the output and store it securely. With this guide, you are now equipped to confidently create a safe copy of your Telegram data, whether for personal record-keeping, migration, or long-term preservation.