telegram-export-md
Turn Telegram's unreadable
result.jsonexport into clean, searchable Markdown files.
🌐 Languages: English · فارسی
Telegram Desktop's built-in Export chat history gives you a giant result.json
(plus folders full of media) — technically complete, practically unreadable.
telegram-export-md converts it into one tidy Markdown file per chat, with
formatting, replies, forwards, polls, and media all preserved.
Zero dependencies. Pure Python standard library.
Before → After
Before — raw export JSON:
{"id": 183, "type": "message", "date": "2021-01-01T10:00:00",
"from": "Arian", "text": [{"type": "plain", "text": "hello "},
{"type": "bold", "text": "everyone"}, {"type": "plain", "text": "?"}]}
After — rendered Markdown:
**2021-01-01 10:00 — Arian**
hello **everyone**?
---
**2021-01-02 18:30 — Arian**

*1920×1080*
Features
- 📄 One Markdown file per chat, plus an
index.mdtable of contents - 🖥 Terminal UI (optional extra) — browse exports, tick chats, convert, and preview the Markdown with Textual
- 📡
fetchmode (optional extra) — pull chats straight from Telegram's servers, no desktop app needed - 🎨 Telegram formatting preserved — bold, italic, code, pre, strikethrough, underline, links
- 💬 Replies resolved — quoted with sender and a snippet of the original message
- ↩️ Forwards, edits, and polls rendered faithfully
- 🖼 Media support — photos embed, everything else links;
--copy-mediamakes the backup self-contained - 🔍 Filters — pick chats by name or id, slice by date range
- 🧹 Service messages (joins, pins, calls) can be excluded
- 🐍 No dependencies — works on Python 3.10+, Windows/macOS/Linux
Install
# from PyPI
pipx install telegram-export-md
# optional: fetch mode (pull chats from Telegram's servers via their API)
pipx install 'telegram-export-md[fetch]'
# optional: terminal UI (browse + convert + preview)
pipx install 'telegram-export-md[ui]'
# or directly from this repo
uv tool install git+https://github.com/Retro-Zero/telegram-export-md.git
# or
pip install git+https://github.com/Retro-Zero/telegram-export-md.git
Usage
1. Export your data
In Telegram Desktop: Settings → Advanced → Export chat history.
Tick JSON as the format and check Include photos and videos if you want media.
This creates a folder containing result.json and media subfolders.
2. Convert
tg-export-md ~/Downloads/Telegram-Export -o ~/telegram-backup
Result:
telegram-backup/
├── index.md
├── Gaming Crew.md
├── Saved Messages.md
└── media/
└── Gaming Crew/
├── photo_1.jpg
└── video_1.mp4
Options
| Option | Description |
|---|---|
export |
Path to the export folder (containing result.json) or to result.json itself |
-o, --output |
Output directory (default: ./markdown) |
--chat TEXT |
Only export chats whose name or id contains TEXT |
--since YYYY-MM-DD |
Only messages on or after this date |
--until YYYY-MM-DD |
Only messages on or before this date |
--copy-media |
Copy media into the output folder (self-contained backup) |
--no-media |
Omit media references entirely |
--no-service |
Skip service messages (joins, pins, calls, …) |
--quiet |
Only print errors |
Examples
# One chat, as a searchable text archive
tg-export-md export/ -o backup --chat "Gaming Crew" --copy-media
# Everything from 2022, text only
tg-export-md export/ -o backup --since 2022-01-01 --no-media
# Point straight at the JSON file
tg-export-md export/result.json -o backup
Automatic backup with fetch
No desktop app? No problem. tg-export-md fetch pulls chats straight from
Telegram's servers into the same result.json + media format the desktop
export produces — so the converter above works unchanged, and you get backups
you can schedule.
Setup (once)
-
Get free API keys at my.telegram.org → API development tools
-
Make the keys available — either:
export TG_API_ID=123456 export TG_API_HASH=yourhash
or save them in
~/.config/telegram-export-md/config.ini:[telegram] api_id = 123456 api_hash = yourhash
-
Install with the extra:
pipx install 'telegram-export-md[fetch]'
Run
Run without flags for an interactive picker: after login it lists your chats and lets you choose which ones to export, which media types to download (photo, video, voice, audio, document, sticker, animation), and optional limits — last N messages per chat, a per-file size cap, and a date range.
tg-export-md fetch -o ~/telegram-export
The first run asks for your phone number and a login code Telegram sends you — the session is saved, so later runs are automatic. Everything the picker asks is also available as a flag, so cron jobs stay hands-free:
tg-export-md fetch -o ~/telegram-export --chat "Family" --media-types photo,video --last 500 --max-size 100mb
tg-export-md ~/telegram-export -o ~/telegram-backup
| Flag | Description |
|---|---|
--chat TEXT |
only fetch chats whose name or id contains TEXT |
--since / --until YYYY-MM-DD |
date range |
--last N (alias --limit) |
only the last N messages per chat (newest) |
--media |
download all media types |
--media-types TYPES |
which media to download: photo,video,voice,audio,document,sticker,animation |
--max-size SIZE |
skip files larger than this (e.g. 50mb, 1gb) |
Terminal UI
Prefer pointing and clicking? tg-export-md ui launches a terminal UI (built
with Textual):
- Browse to your export folder in the file tree
- Tick the chats you want and set options (copy media, skip service messages, output folder)
- Hit Convert — it runs in the background with a live log
- Preview the rendered Markdown of any chat, then go back and tweak
pipx install 'telegram-export-md[ui]'
tg-export-md ui
Notes
- Large exports — the whole
result.jsonis loaded into memory; exports up to a few hundred MB work fine on a modern laptop. Streaming support is on the roadmap. - Media paths without
--copy-mediapoint back into your original export folder. Use--copy-mediafor a backup you can move or archive. - Restricted chats — in chats where the other side enabled Restrict saving
content, the full text history still exports, but their media can't be saved by
anyone (by design).
fetchkeeps the messages with media placeholders and prints a per-file warning, plus a "could not be saved" count in the end summary. Secret chats (end-to-end encrypted) are never visible to the API at all. - Media availability —
fetchdownloads whatever media is still available at fetch time; files that are already gone are kept as references in the JSON and counted in the end summary. - Export JSON is generated by Telegram Desktop (Windows/macOS/Linux). Exports from other clients may differ slightly — open an issue if something doesn't parse.
Roadmap
- Streaming parse for huge exports
- Support the HTML export format
- Per-year splitting (
--split) -
--format obsidianfor vault-friendly output
Contributing
Bug reports, feature requests, and PRs are welcome. Please open an issue first for anything beyond a small fix.
License
Metadata
Release files for telegram-export-md 0.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| telegram_export_md-0.4.1.tar.gz | 272.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| telegram_export_md-0.4.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 300.1 kB
Release files / telegram_export_md-0.4.1.tar.gz
| Download URL | telegram_export_md-0.4.1.tar.gz |
|---|---|
| Size | 272.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7cb63d343f0cdfe10be63a35f06ea7c8e9f75077308055628a988afeee74bfc5
|
|
BLAKE2b-256 checksum How to use checksums |
f3d7f040337f370ba1a5f5ef3898e8f5ae2b02a96a3691217b519960e0e80c76
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 15, 2026.
Transparency logRelease files / telegram_export_md-0.4.1-py3-none-any.whl
| Download URL | telegram_export_md-0.4.1-py3-none-any.whl |
|---|---|
| Size | 27.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9e17e671ca4b29fc78fa0b0fddea37f34da51ee473633bb1cd27b47011c50531
|
|
BLAKE2b-256 checksum How to use checksums |
063d3b5cd227737f7891444d3ca69b066205d71ce1eed99155d5dda5dbe7965b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 15, 2026.
Transparency log