--- name: telegram-export-7bdc4241f66d description: >- Exports and downloads Telegram chats, media, and channel content. Use when a user asks to export Telegram chat history, download media from Telegram channels or groups, archive Telegram conversations, backup Telegram messages, extract images, videos or links from Telegram, bulk download from Telegram channels, or migrate Telegram data. Covers Telegram Desktop's built-in export and Python scripts built on the Telethon library. license: Apache-2.0 compatibility: 'Python 3.8+ with Telethon 1.x, or Telegram Desktop (Linux, macOS, Windows)' metadata: author: terminal-skills version: "1.1.0" category: content repository: https://codeberg.org/Lonami/Telethon tags: "telegram, telethon, export, media, backup" --- # telegram-export ## Overview Export messages, media, and data from Telegram chats, groups, and channels. This skill covers two approaches: Telegram Desktop's built-in export (GUI, good for personal use) and Telethon (Python library for programmatic access through Telegram's MTProto API, signed in as your own account). Use cases range from personal chat backups to bulk media download from channels to data analysis of group conversations. ## Instructions ### Step 1: Get Telegram API Credentials All programmatic approaches require API credentials from Telegram. 1. Go to https://my.telegram.org and log in with your phone number. 2. Click "API development tools." 3. Create a new application — fill in app title and short name (anything works). 4. Save your `api_id` (integer) and `api_hash` (string). The credentials are free and tied to your Telegram account: one `api_id` per phone number. The `api_hash` is a secret that Telegram does not let you revoke, so keep both in environment variables (`TELEGRAM_API_ID`, `TELEGRAM_API_HASH`), never in a script. ### Step 2: Install Telethon Telethon is the most popular Python library for Telegram's MTProto API. The 1.x line (1.45.0, September 2026) is in maintenance mode but still follows Telegram's API changes. Its GitHub repository was archived in February 2026; the source now lives on Codeberg. ```bash python3 -m venv .venv && source .venv/bin/activate # Debian/Ubuntu refuse pip outside a virtual environment pip install telethon cryptg python -c "import telethon; print(telethon.__version__)" ``` `cryptg` is optional: it does the encryption in C instead of Python, which is what makes large media downloads fast. ### Step 3: Basic Client Setup ```python # tg_login.py — sign in once; later runs reuse archive.session import asyncio, os from telethon import TelegramClient API_ID = int(os.environ["TELEGRAM_API_ID"]) API_HASH = os.environ["TELEGRAM_API_HASH"] async def main(): # "archive" is the session name: auth is stored in archive.session async with TelegramClient("archive", API_ID, API_HASH) as client: me = await client.get_me() print(f"Logged in as {me.first_name} (ID: {me.id})") asyncio.run(main()) ``` On first run, Telethon prompts for your phone number, the verification code Telegram sends you, and the two-step verification password if one is set. After that, `archive.session` stores the auth key — no re-login needed as long as the script runs from the same directory. Never name a script `telethon.py`: it shadows the library. ### Step 4: List Available Chats and Channels Public chats can be addressed by username (`"@telegram"`) or `t.me` link. Private groups have neither: take their ID from this listing and pass it as an integer. ```python # list_chats.py — every chat, group and channel of the account import asyncio, os from telethon import TelegramClient async def main(): async with TelegramClient("archive", int(os.environ["TELEGRAM_API_ID"]), os.environ["TELEGRAM_API_HASH"]) as client: async for dialog in client.iter_dialogs(): # supergroups are both is_group and is_channel, so test is_group first kind = "Group" if dialog.is_group else "Channel" if dialog.is_channel else "User" print(f"[{kind}] {dialog.name} | ID: {dialog.id}") asyncio.run(main()) ``` ### Step 5: Export Chat Messages ```python # export_messages.py — write every message of a chat to JSON Lines, oldest first # usage: python export_messages.py @telegram telegram_news.jsonl import asyncio, json, os, sys from telethon import TelegramClient def media_kind(msg): for kind in ("photo", "video", "voice", "audio", "document"): if getattr(msg, kind): return kind return None async def export_chat(chat, output_file): chat = int(chat) if chat.lstrip("-").isdigit() else chat count = 0 async with TelegramClient("archive", int(os.environ["TELEGRAM_API_ID"]), os.environ["TELEGRAM_API_HASH"]) as client: with open(output_file, "w", encoding="utf-8") as f: # reverse=True yields oldest first; the default is newest first async for msg in client.iter_messages(chat, reverse=True): record = { "id": msg.id, "date": msg.date.isoformat(), "sender_id": msg.sender_id, "text": msg.raw_text or "", # msg.text would add Markdown markup "reply_to": msg.reply_to_msg_id, "views": msg.views, "forwards": msg.forwards, "media": media_kind(msg), "file_name": msg.file.name if msg.file else None, } f.write(json.dumps(record, ensure_ascii=False) + "\n") count += 1 print(f"Exported {count} messages to {output_file}") asyncio.run(export_chat(sys.argv[1], sys.argv[2])) ``` Writing one JSON object per line keeps memory flat on channels with hundreds of thousands of posts. `iter_messages` also accepts `limit=`, `search=`, `from_user=`, `min_id=` (resume after the last exported ID) and `filter=` (for example `InputMessagesFilterPhotos` from `telethon.tl.types`). ### Step 6: Download Media from Chats and Channels ```python # download_media.py — download media of chosen kinds from a date range; safe to re-run # usage: python download_media.py @telegram ./telegram_news 2026-01-01 2026-10-01 import asyncio, os, sys from datetime import datetime, timezone from telethon import TelegramClient async def download_media(chat, output_dir, start, end, kinds=("photo", "video")): chat = int(chat) if chat.lstrip("-").isdigit() else chat count = 0 async with TelegramClient("archive", int(os.environ["TELEGRAM_API_ID"]), os.environ["TELEGRAM_API_HASH"]) as client: # offset_date is an exclusive upper bound: messages before `end`, newest first async for msg in client.iter_messages(chat, offset_date=end): if msg.date < start: break # past the range, stop if not msg.file or not any(getattr(msg, kind) for kind in kinds): continue target = os.path.join(output_dir, f"{msg.date:%Y-%m}", f"{msg.id}{msg.file.ext or ''}") if os.path.exists(target): continue # downloaded on an earlier run os.makedirs(os.path.dirname(target), exist_ok=True) partial = await msg.download_media(file=target + ".part") os.replace(partial, target) # only complete files get the final name count += 1 print(f"[{count}] {msg.date:%Y-%m-%d %H:%M} {target} ({(msg.file.size or 0) / 1e6:.1f} MB)") print(f"Downloaded {count} files to {output_dir}") start, end = (datetime.fromisoformat(d).replace(tzinfo=timezone.utc) for d in sys.argv[3:5]) asyncio.run(download_media(sys.argv[1], sys.argv[2], start, end)) ``` Valid `kinds` are the message properties `photo`, `video`, `voice`, `audio` and `document` (`document` matches every non-photo file; `photo` also matches a link's preview image and a changed chat photo). Passing a directory as `file=` lets Telethon pick the original file name, but a re-run then saves duplicates as `name (1).ext`; naming files by message ID avoids that. `download_media(..., progress_callback=fn)` calls `fn(received_bytes, total_bytes)` for large files. ### Step 7: Takeout Session for Large Exports Telegram has a dedicated export mode ("takeout") with lower flood limits. Telethon sends the history requests through it; file downloads stay ordinary requests. Wrap the loops from steps 5 and 6 in it when archiving large chats: ```python from telethon import errors try: # enable only what the export needs: contacts, users, chats, megagroups, channels, files async with client.takeout(channels=True, megagroups=True, files=True) as takeout: async for msg in takeout.iter_messages(chat, reverse=True, wait_time=0): ... # same body as before except errors.TakeoutInitDelayError as e: print(f"Telegram requires a wait of {e.seconds} s before this session may start a takeout") ``` `TakeoutInitDelayError` is part of the flow, not a failure: Telegram can delay an export for security reasons and notifies the account's other devices in the meantime. Wait `e.seconds` and run again from the same session file. ### Step 8: Telegram Desktop Export (No Code) Telegram Desktop has a built-in export feature — no API credentials or code needed. 1. Open Telegram Desktop. 2. Go to **Settings → Advanced → Export Telegram data** (whole account), or open one chat's **⋮** menu and choose **Export chat history**. 3. Select what to export: chat types (personal chats, private or public groups and channels) and media (photos, videos, voice messages, stickers, files). 4. Choose format: **Human-readable HTML**, **Machine-readable JSON**, or both. 5. Set the media size limit and date range if needed. 6. Click "Export" and wait. The export folder holds `result.json` (or HTML pages) with media sorted into `photos/`, `video_files/`, `voice_messages/` and `files/` (inside `chats/chat_N/` for a whole-account export). This is the simplest approach for personal chat backups, but it cannot be automated or run headlessly, and a newly signed-in desktop session may have to wait before Telegram allows the export. ## Examples ### Example 1: Archive an entire Telegram channel with all media **User prompt:** "I want to download everything from a Telegram channel — all messages, photos, and videos. The channel has about 5,000 posts." With `TELEGRAM_API_ID` and `TELEGRAM_API_HASH` set and the scripts from steps 3, 5 and 6 saved: ```bash python tg_login.py # once: phone, code, 2FA password python export_messages.py @telegram telegram_news.jsonl python download_media.py @telegram ./telegram_news 2013-01-01 2026-10-01 du -sh telegram_news && wc -l telegram_news.jsonl ``` The result is one JSON object per post in `telegram_news.jsonl` and media grouped by month, named by message ID: ```text Exported 5012 messages to telegram_news.jsonl [1] 2026-09-28 14:02 ./telegram_news/2026-09/5127.mp4 (18.4 MB) [2] 2026-09-21 09:30 ./telegram_news/2026-09/5124.jpg (0.2 MB) ... Downloaded 3274 files to ./telegram_news ``` If the download stops (network drop, a long flood wait), run the same command again: finished files are skipped. ### Example 2: Extract all shared links from a group chat for research **User prompt:** "My team shares a lot of articles in our Telegram group. Extract all URLs that have been shared in the last 6 months so I can build a reading list." The group is private, so its ID comes from `list_chats.py` (`[Group] Platform Team | ID: -1001892043317`). Links are read from message entities, which also catches links hidden behind text — a regex over the text misses those. ```python # export_links.py — unique URLs shared in a chat during the last 180 days import asyncio, os from datetime import datetime, timedelta, timezone from telethon import TelegramClient from telethon.tl.types import MessageEntityTextUrl, MessageEntityUrl CHAT = -1001892043317 CUTOFF = datetime.now(timezone.utc) - timedelta(days=180) async def main(): links, scanned = set(), 0 async with TelegramClient("archive", int(os.environ["TELEGRAM_API_ID"]), os.environ["TELEGRAM_API_HASH"]) as client: async for msg in client.iter_messages(CHAT): if msg.date < CUTOFF: break scanned += 1 for entity, text in msg.get_entities_text(): if isinstance(entity, MessageEntityTextUrl): links.add(entity.url) # link behind a word or phrase elif isinstance(entity, MessageEntityUrl): links.add(text) # URL typed in the message with open("links.txt", "w", encoding="utf-8") as f: f.write("\n".join(sorted(links)) + "\n") print(f"Extracted {len(links)} unique URLs from {scanned} messages to links.txt") asyncio.run(main()) ``` Output: `Extracted 318 unique URLs from 2140 messages to links.txt`, and `links.txt` with one URL per line, sorted. ## Guidelines - Always use Telethon over direct HTTP scraping — it uses Telegram's official MTProto protocol and handles encryption and pagination properly. - Treat `archive.session` like a password: it signs in to the account without a code. Keep it and the API credentials out of Git and out of shared folders; terminate a leaked session from the list of active sessions in Telegram's settings. - Export only chats you are a member of and entitled to copy. Chat exports contain other people's personal data — store them accordingly and do not republish private conversations. - Telegram puts accounts that sign in through unofficial API clients under observation and bans those used for flooding or spamming. Export at the pace the library sets; do not strip the waits to go faster. - Flood waits are only partly automatic: Telethon sleeps through waits up to `flood_sleep_threshold` (60 seconds by default) and raises `FloodWaitError` with `.seconds` for longer ones. Raise the threshold (`TelegramClient(..., flood_sleep_threshold=3600)`) or catch the error, sleep and resume. - `iter_messages` pages through history by itself and, when more than 3,000 messages are requested, waits a second between requests. A history of 100K+ messages takes a while — print progress and write results as you go. - Resolving usernames is rate-limited (flood waits start around 50 lookups in a short period). Resolve a chat once and reuse it, or use numeric IDs. - Telegram Desktop export is the simplest option for one-time personal backups — no code, no API setup. Use Telethon when you need automation, filtering, or integration with other tools. - Large downloads take time even with `cryptg`. Plan for hours on big channels and make every script resumable, as in step 6. --- Source attribution: terminal-skills Original project: https://github.com/TerminalSkills/skills/blob/8a9852d489f274538be9bf1c9121aeb403750b1c/skills/telegram-export/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding any notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS Copyright 2025 Terminal Skills Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: terminal-skills Original project: https://github.com/TerminalSkills/skills/blob/8a9852d489f274538be9bf1c9121aeb403750b1c/skills/telegram-export/SKILL.md Attribution basis: Source repository record Fields of work: Marketing Roles: Content Marketer, Marketing Analyst, Social Media Manager Specialties: API Tools: Telethon, Telegram Desktop Country applicability: Country not specified Classification basis: Source category, role and specialization labels Instruction SHA-256: 7353f471da7cf5ac68c2012e6018b58486aea6402a1b6a862b6a657affb7c177