Telegram Backup

Back up your Obsidian notes to a Telegram channel (or group, or private chat) with your own Telegram bot. Send the current note with one command, type ;;backup inside a note to push it instantly, or let the plugin back up your whole vault on a schedule. Telegram gives you free, unlimited cloud storage that you can reach from any device, and this plugin turns it into a fast, searchable backup history for your vault.

• Features
• Installation
• Setup: connect your Telegram bot
• Usage
• Settings reference
• Caption template
• Limits
• If Telegram is blocked where you live
• Privacy and security
• Troubleshooting
• FAQ
• Development

Features

• One-command backup of the current note: command palette, ribbon icon, file menu or editor menu.
• Type to back up: write ;;backup anywhere in a note and it is sent immediately; the trigger text disappears from the note.
• Type to send: end a line with ;;send to send only that line (a quick message, a reminder, an idea) to your channel.
• Send selected text to Telegram.
• Three formats: an exact .md file (restorable), readable Telegram messages (headings, bold, lists, check boxes, quotes, code blocks…), or automatic (text when short, file when long).
• Attachments: images, PDFs and other embedded files are sent with the note, as replies or bundled with the note in a zip archive. Unchanged attachments are not sent again.
• Vault, folder and selection archives: zip archives that are split automatically into standalone parts under Telegram's 50 MB limit.
• Incremental backups: send only the files that changed since the last vault backup.
• Automatic backups: back up a note a few minutes after you stop editing it, and/or back up the whole vault every hour, day or week.
• Restore from Telegram: pick an earlier version of a note and save it as a copy or replace the note, directly inside Obsidian.
• Update in place (optional): keep one Telegram message per note and update it instead of posting a new one.
• Backup history with links to the messages in Telegram, plus a status bar item that shows when the last backup ran.
• Captions with hashtags: Obsidian tags become Telegram hashtags (#project/alpha → #project_alpha), so you can search your channel by tag.
• Exclusions by folder or tag for automatic backups and archives.
• Forum topics, silent messages, protected content and a custom Bot API server.
• Command line handlers for the Obsidian CLI, so backups can be started from a terminal or a task scheduler.
• Secure token storage: the bot token lives in Obsidian's secret storage on your device, never in your vault.
• Works on desktop and mobile, in any language (including right-to-left scripts such as Persian and Arabic).

Installation

From the community directory

1. Open Settings → Community plugins and turn off Restricted mode if it is on.
2. Select Browse, search for Telegram Backup, then select Install and Enable.

Beta versions with BRAT

1. Install and enable the BRAT plugin from the community directory.
2. Run the command BRAT: Add a beta plugin for testing and enter this repository's URL: https://github.com/SoheilShiravi/Obsidian-Telegram-Backup.
3. Enable Telegram Backup in Settings → Community plugins.

Manual installation

1. Download main.js, manifest.json and styles.css from the latest release.
2. Create the folder <your vault>/.obsidian/plugins/telegram-backup/ and copy the three files into it. (The .obsidian folder is hidden on some systems.)
3. Restart Obsidian, then enable Telegram Backup in Settings → Community plugins.

The plugin needs Obsidian 1.13.2 or newer.

Setup: connect your Telegram bot

Setting up takes about five minutes. You need the Telegram app on your phone or computer.

Step 1: Create a bot with BotFather

1. In Telegram, search for @BotFather (it has a blue check mark) and open it. Select Start.
2. Send the command /newbot.
3. Send a display name for the bot, for example My Vault Backup.
4. Send a username for the bot. It must end with bot, for example my_vault_backup_bot. If the name is taken, try another one.
5. BotFather replies with a token that looks like 1234567890:AAHdqTcvCH1vGWJxfSeofSAs0K5PALDsaw. Copy it.

[!WARNING] Keep the token secret. Anyone with the token can control your bot. If it ever leaks, open @BotFather, send /revoke, pick your bot, and use the new token.

Step 2: Create a private channel for your backups

A private channel is the best place for backups: only you can see it, and it can hold an unlimited number of files.

• Android: tap the pencil button → New Channel.
• iPhone: open Chats, tap the new message button → New Channel.
• Desktop: open the menu (☰) → New Channel.

Give it a name such as Obsidian Backups, choose Private Channel, and finish creating it. You can skip adding members.

You can also use a group, a group with topics, or a private chat with your bot. See Other destinations.

Step 3: Make the bot an administrator of the channel

1. Open the channel, then open its info page (tap the channel name).
2. Select Edit (or Manage channel) → Administrators → Add Admin (or Add Administrator).
3. Search for your bot's username, select it, and make sure Post messages is allowed.
4. If you plan to use Update the previous message, also allow Edit messages of others and Delete messages of others.
5. Save.

Step 4: Connect the plugin

1. In Obsidian, open Settings → Telegram Backup.
2. Bot token: select Link…. In the Select secret window, select Add secret…, enter a name such as telegram-backup-token (lowercase letters, numbers and dashes) and paste the token from BotFather as the value. Then select the new secret and select Save.
   • Secrets are kept in Obsidian's keychain on this device and are encrypted by your operating system. They are never written into the vault, so on each device where you use the plugin you add the secret once.
   • You can view, change or delete secrets later in Settings → Keychain.
3. Chat ID: select Detect. The plugin asks Telegram which chats your bot has seen. Choose your channel from the list.
   • If the list is empty, post any message in your channel (or, for a private chat, send /start to your bot) and select Detect again. Telegram only remembers these updates for 24 hours.
4. Select Check next to Check the connection. You should see three check marks: the bot, the chat and the permission to post.
5. Select Send test message. A confirmation message appears in your channel.

You're done. Open a note and run Telegram Backup: Back up current note, or type ;;backup at the end of the note.

Finding the chat ID manually

If Detect does not work (for example because another app is reading your bot's updates), use one of these:

• Public channels: use the channel's username, for example @my_backups.
• Telegram Web: open your channel at https://web.telegram.org/a/. The address ends with the chat ID, for example #-1001234567890.
• Bot API in a browser: post a message in the channel, then open https://api.telegram.org/bot<YOUR_TOKEN>/getUpdates in a browser (replace <YOUR_TOKEN>). Look for "chat":{"id":-100….

Channel and supergroup IDs start with -100.

Other destinations

• Private chat with your bot: open your bot in Telegram and select Start. Then select Detect in the plugin and choose the private chat with your name. Backups arrive in your chat with the bot.
• Group: add the bot to the group (it must be allowed to send messages), then use Detect. If BotFather blocks adding the bot to groups, send /setjoingroups to BotFather and enable it.
• Group with topics: use the group's chat ID, then set Topic ID to the topic's number. To find it, copy the link of any message in the topic: in https://t.me/c/1234567890/42/100, the topic ID is 42.

Usage

All commands are in the command palette (Ctrl/Cmd + P) under Telegram Backup. None of them has a default hotkey; you can assign your own in Settings → Hotkeys.

Back up a note

• Run Back up current note, select the paper plane icon in the ribbon, right-click a file and choose Back up to Telegram, or right-click inside the editor and choose Back up note to Telegram.
• Back up current note as a file and Back up current note as text messages override the format setting for one backup.
• Canvases, bases, PDFs, images and any other file can be backed up as files too.

Type a trigger in the note

With triggers enabled (they are by default):

The trigger fires the moment you type its last character, in both Live Preview and Source mode. Undoing the removal does not send the note again. You can change both triggers in the settings, for example to /backup (if you do not use Obsidian's Slash commands core plugin) or !tg.

Send selected text

Select text and run Send selected text, or right-click the selection and choose Send selection to Telegram.

Archives

Large backups are split into several archives (MyVault-2026-10-18_2130-part1.zip, …-part2.zip, …). Every part is a complete zip file on its own; extract all parts into the same folder to get everything back. A progress notice with a Cancel button is shown while an archive is created and uploaded. Each archive caption has a hashtag (#vault_backup, #changes_backup, #folder_backup, #files_backup) so you can find them quickly in Telegram.

Automatic backups

• Back up notes when they change: a note is sent a few minutes after your last edit (1 to 60 minutes). Notes that did not change since their last backup are never sent again. Failed automatic backups are retried every few minutes, for example after you come back online.
• Scheduled vault backup: every hour, 6 hours, 12 hours, day or week, either the whole vault or only changed files. Scheduled backups run while Obsidian is open; a missed backup runs shortly after you start Obsidian. They are off on mobile by default because mobile apps are paused in the background.

If you use the plugin on several devices with a synced vault, turn on scheduled backups on one device only.

Restore

• Run Restore current note from a backup, choose a version, then Save as copy (keeps the current note) or Replace note.
• Or run Show backup history and select Restore next to a backup. Deleted notes can be restored from the history too.
• Zip archives of up to 20 MB (vault, folder and changed-files archives, and notes bundled with their attachments) can be downloaded into the Telegram downloads folder of your vault with Download.

Restoring works for notes that were sent as a file (the default format). Telegram only lets bots download files of up to 20 MB, and only backups that are still in the plugin's history can be restored from inside Obsidian. You can always download any file manually in Telegram.

History and status bar

Show backup history lists recent backups with their time, size and format, failures with the reason, links to open each message in Telegram (for channels and groups), and restore buttons. Show backups of current note shows only the current note. On desktop the status bar shows when the last backup happened; select it to open the history.

Command line

Obsidian's command line interface (desktop) can start backups, for example from a cron job or the Windows Task Scheduler. Turn it on in Settings → General → Command line interface. If Obsidian is not running, the first command starts it; add vault="My vault" to target a specific vault.

obsidian telegram-backup                                  # status
obsidian telegram-backup:vault                            # back up the whole vault
obsidian telegram-backup:changes                          # back up changed files
obsidian telegram-backup:note path="Inbox/Idea.md"        # back up one note
obsidian telegram-backup:send text="Hello from the terminal"

Settings reference

All settings appear in Obsidian's settings search.

Caption template

The caption template is used as the caption of backup files and as the header of text messages. It supports Telegram HTML formatting (<b>, <i>, <u>, <s>, <code>, <a href="…">) and these placeholders:

Dates accept any Moment.js format: {{date:DD MMMM YYYY}}, {{modified:HH:mm}}. A line whose placeholders are all empty is removed, so a tags line disappears for notes without tags.

The default template:

📝 <b>{{title}}</b>
📁 <code>{{path}}</code>
🕒 {{datetime}}
{{tags}}

How notes look as text messages

Long notes are split into several messages (at most 4096 characters each). A note that would need more than 10 messages is sent as a file instead.

Limits

These limits come from the Telegram Bot API:

If Telegram is blocked where you live

The plugin talks to the Telegram Bot API over HTTPS. If Telegram is blocked in your country, choose one of these options:

1. VPN: a VPN that routes all traffic of your device works for Obsidian on desktop and mobile without any change in the plugin.

2. System proxy (desktop): Obsidian follows the proxy configured in your operating system's network settings, so a proxy app in "system proxy" mode works too.

3. Your own Bot API server: run the official Telegram Bot API server on a server you control, and set Bot API server to its address. A self-hosted server also raises the upload limit to 2000 MB.

4. Your own reverse proxy: forward requests to api.telegram.org through a server you control, for example a small Cloudflare Worker:

   export default {
     async fetch(request) {
       const url = new URL(request.url);
       url.hostname = "api.telegram.org";
       return fetch(new Request(url, request));
     },
   };
   

   Then set Bot API server to the worker's address, such as https://my-proxy.example.workers.dev.

[!WARNING] Only use servers you trust. Every request contains your bot token and your notes. Never point the plugin at a proxy run by someone else.

Privacy and security

• Network use: the plugin connects only to the Telegram Bot API server in the settings (https://api.telegram.org by default), through two kinds of requests: Bot API calls (/bot<token>/<method>, to send, edit and check messages and files) and file downloads (/file/bot<token>/<path>, only when you restore or download a backup). It sends data only when you start a backup or when you turn on automatic or scheduled backups.
• What is sent: the content of the notes and files you back up, embedded attachments, file names and paths, tags, and the vault name (in captions and archive names).
• No telemetry: the plugin does not collect analytics and does not contact any other server.
• Telegram is not end-to-end encrypted for bots: messages in channels, groups and bot chats are stored on Telegram's servers, and Telegram can technically access them. Do not back up anything you would not store in a regular cloud service, and use Excluded folders and Excluded tags for sensitive notes.
• Bot token: stored in Obsidian's keychain (secret storage), on this device only. It is not written to the vault or to data.json, so it is not synced or committed to git with your vault. Obsidian encrypts secrets with your operating system's secret store; on systems without one (some Linux desktops), it shows a warning that secrets are stored without encryption.
• Local data: the plugin's data.json (in .obsidian/plugins/telegram-backup/) keeps the settings and the backup history: note paths, times, message links and Telegram file IDs.
• Vault access: vault, folder and changed-files backups list the files in your vault to decide what goes into the archive, and scheduled backups check file modification times to see whether anything changed. Files in Excluded folders and notes with Excluded tags are skipped. Single-note backups read only that note and the files it embeds.
• Files outside the vault: the plugin reads and writes only files inside your vault. The configuration folder is read only if you turn on Include the configuration folder.

Troubleshooting

FAQ

Can I restore my whole vault from Telegram? Yes. Download all parts of a vault backup from your channel, extract them into an empty folder, and open that folder as a vault in Obsidian. For a recent state, extract the last full backup first and then the newer "changed files" archives in order.

Does it work on my phone? Yes, on Android and iOS. The status bar item is desktop-only, and scheduled backups are off on mobile unless you turn them on.

Will my channel fill up with copies? Each backup is a new message by default, which gives you a version history. Choose Update the previous message to keep one message per note instead. Unchanged notes are never sent automatically, and unchanged attachments are not re-sent.

Can I use several vaults? Yes. Use a separate channel, or one channel for all vaults: captions and archive names include the vault name.

Why is a note sent as a file even though I chose text messages? Notes that would need more than 10 messages are sent as a file so the chat is not flooded.

Development

You need Node.js 22 or newer.

npm install        # install dependencies
npm run dev        # rebuild main.js on every change
npm run build      # type-check and create a production build
npm run lint       # check the code with eslint-plugin-obsidianmd
npm test           # run the unit tests

To try your changes, copy main.js, manifest.json and styles.css into <vault>/.obsidian/plugins/telegram-backup/ (or create a symbolic link to this folder) and reload Obsidian. The Hot-Reload plugin reloads the plugin automatically after each build.

src/
├── main.ts              Plugin lifecycle, settings and state storage
├── settings.ts          Settings, defaults and validation
├── settings-tab.ts      Settings tab (declarative setting definitions)
├── commands.ts          Commands and context menus
├── triggers.ts          ;;backup and ;;send editor triggers (CodeMirror 6)
├── actions.ts           Notices, status bar and error reporting
├── cli.ts               Obsidian command line handlers
├── backup/              Note, archive, automatic and restore logic
├── format/              Markdown → Telegram HTML, message splitting, templates
├── telegram/            Bot API client (requestUrl), multipart uploads, errors
├── zip/                 ZIP writer and archive splitting (deflate by fflate)
├── ui/                  Modals, status bar and progress notice
└── utils/               Small helpers
test/                    Unit tests (Node.js test runner)

Releases are built by GitHub Actions: npm version patch updates manifest.json and versions.json and creates the version tag, and pushing the tag publishes a release named after the version with main.js, manifest.json and styles.css attached.

Credits

• fflate (MIT) for fast deflate compression.
• Built with the Obsidian API.

License

MIT